Route Waypoints


#1

Hello. On the flight map, you have the option of displaying the waypoints for the planned route; however, these waypoints appear as black dots.

Would it be possible to associate these black dots with waypoint names? This would allow people to see not only the black dot but also the name of that black dot.

Thanks.


#2

I don’t even understand this feature. Those black dots don’t even correspond to waypoints… I used to think they did, but I just tested a flight that has 3 waypoints and a STAR in the flightplan, and the route shows about 30 black dots… Noticed this for awhile, never understood it hah.

Here’s the flight I used as an example. http://flightaware.com/live/flight/ACA431/history/20120816/0230Z/CYUL/CYYZ


#3

It’s the ETMS modeled route, as updated throughout the flight (the textual route is frozen at departure time).


#4

It would be nice if the projected route (the blue, dashed lines) matched the actual route. It’s interesting to follow a flight from Europe to the U.S. and notice how many times the projected route changes. Sometimes, these changes are very large and seem to be completely random. Another interesting thing to notice for these types of flights is that the displayed waypoints in the Route section are INCORRECT. It seems as though FlightAware uses routes from previous flights to fill the gaps.

This random and erroneous information needs to be stopped. It seems like every flight-tracking Web site displays information just to attract people to that Web site; aesthetics are the main objective while accuracy takes a back seat.

I dream of a flight-tracking Web site that displays accurate flight-plan information…

I dream of a time when flight-tracking Web sites like FlightAware and Flightwise are merely a thing of the past…


#5

FlightAware doesn’t make up any route date or use previous route data for a flight.

What’s an example of an inaccuracy?


#6

Right now, at 1831Z, the route for DAL595 (flightaware.com/live/flight/DAL595) is displayed as follows:

BERGI UL602 NALAX UL46 REMSI UP6 NELBO UN551 TADEX UN551 NIBOG RESNO 5600N 02000W 5800N 03000W 5800N 04000W 5700N 05000W LOACH FOXXE MT YYB J551 YVV J551 ECK FWA OOM PXV LTOWN6

This route, however, does not reflect the actual route of the aircraft, as can be seen on the tracker display. To verify, copy and paste the above route into simroutes.com (use the Generate Routes tab near the top of the page).

Am I the only one that is receiving this anomaly?


#7

mduell explained above that, “the textual route is frozen at departure time,” so I don’t think there is any anomaly. The text route is the original route and the waypoints/route/etc on the map are constantly updating.


#8

Okay… so, on this link (flightaware.com/live/flight/DAL5 … /EHAM/KMEM), you will see that there is a textural route displayed for DAL595 for tomorrow. My question regarding this is how does FlightAware know what tomorrow’s route will be when the actual route for DAL595 hasn’t even been filed?


#9

For planning purposes, that is what the FAA’s ETMS system has predicted.


#10

I see, so those “frozen” textural routes from international flights, as in the case of DAL595, are also predicted by ETMS?


#11

Probably the wrong thread to ask this, but any particular reason that on international flights we cannot use the Aviation Sectional view mode? I understand it’s only available for the US/some of Canada, but is still of great use when tracking Intl flights during their departing/arriving phase in North America, especially when their routes have been altered from the textual planned route as we have been discussing.


#12

And another question is why do the textural routes not show the complete route for certain flights? An example is UAL48 (flightaware.com/live/flight/UAL4 … /KEWR/VABB). This is the route:

GREKI JUDDS MARTN TAFFY N153C STEAM OYSTR 5600N 05000W 5900N 04000W 6100N 03000W 6200N 02000W 6300N 01000W ISVIG SOLKA TOGMI PIVAK INLOG R30 SPB B160 DB B238 RISOP NAMIN LEDOR NAM1T SW BESTA RUGEL GEKLA WT

This route ends at the the waypoint WT, and WT is 2,700 nautical miles away from the destination, so it is unlikely that UAL48 was planned to go direct from WT to VABB.


#13

Yeah I see this a lot on longhaul flights. Sometimes it shows the full route other times not… must be an issue with the plans that come in from the FAA.