When I plan my flights, I use Windy, a global weather app, to gauge wind speeds on my planned route from point A to point B. It helps me to estimate my ETA to the final destination. For example, if there are 100mph west to east headwinds on my route from ATL to SEA, I will mentally add an 45 minutes or so to my real-life schedule as I plan my day.
I work a corporate job, so on weekdays, I prefer long haul flights to the IFATC-controlled regions, and getting the right flight plan timed to my schedule (i.e. 30-60 minutes from destination at 6pm) can be a taxing exercise. Some mornings, in trying to get the right flight plan, I feel like a poor man’s Magellan.
As I was planning my route from Singapore to Paris this morning, it struck me: There has to be a better way.
I’m thinking there must be a way to have a gauge of ETA prior to reaching cruising speed/altitude using the following inputs:
- Time of departure
- Cruising airspeed (Mach)
- Cruusing altitude
- Average expected headwind/tailwind at the above altidude (could be user generated, or better yet, calculated using current winds along the route at that altitude)
- Approach delay (~20 minute adder)
Part 1.5 is this request is to have an ETA metric in the same way that we have the “time to destination” on the flight control panel. My counting fingers get tired manually adding the current time plus the ETD in its current form.
Am I being too needy?