Wrong routes on Delta tags

Started by Seneca Driver, April 02, 2010, 01:26:49 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Seneca Driver

I am noticing a lot of bad route information for Delta flight tags passing through the Seattle area.  The routes shown do not match actual routes being flown in some cases.  Is there a solution for this?

Thank you,

Seneca Driver
Seattle

NF2G

There are several wrong routes in whatever database is being used for many airlines, especially for flights to and from the USA.

A current example:

AIC191 is passing over the Albany VOR right now.  The route shows as VOMM-VABB-EDDF.  Can't be. 

According to FlightAware, the actual route is EDDF-KEWR.  This is consistent with the aircraft's location, direction, and altitude.


DaveReid

Quote from: NF2G on April 02, 2010, 02:25:53 PM
AIC191 is passing over the Albany VOR right now.  The route shows as VOMM-VABB-EDDF.  Can't be. 

According to FlightAware, the actual route is EDDF-KEWR.  This is consistent with the aircraft's location, direction, and altitude.

I've found it helps a great deal to do this kind of sanity-check (actual aircraft location vs. routing) to minimise the risk of delivering an invalid route - in fact it's done automatically by my FlightRouteLookup web service.  A lookup for AIC191 with a location of overhead Albany returns the following:

  <?xml version="1.0" encoding="utf-8" ?>
- <Flight>
  <FlightNumber>AIC191</FlightNumber>
  <Callsign>Airindia 191</Callsign>
  <Error>Route leg found is not consistent with entered lat/lon</Error>
- <Leg>
- <Origin>
  <ICAOCode>EDDF</ICAOCode>
  <IATACode>FRA</IATACode>
  <AirportName>FRANKFURT (INTERNATIONAL)</AirportName>
  <Country>GERMANY</Country>
  </Origin>
- <Destination>
  <ICAOCode>KEWR</ICAOCode>
  <IATACode>EWR</IATACode>
  <AirportName>NEWARK</AirportName>
  <Country>UNITED STATES</Country>
  </Destination>
  <GCDistanceNM>3352</GCDistanceNM>
  <DistanceFromOriginNM>3260</DistanceFromOriginNM>
  <DistanceFromDestinationNM>127</DistanceFromDestinationNM>
  </Leg>
  </Flight>


In this case "Route leg found is not consistent with entered lat/lon" indicates that there is another leg for this flight (VAAH-EDDF) which isn't consistent with overflying Albany, whereas the EDDF-KEWR leg is.

Oh, and before I get accused of ugly commercialism, FlightRouteLookup is a free service, always has been and always will be, open to all to use  :-)
This post has been scanned for any traces of negativity, bias, sarcasm and general anti-social behaviour

tarbat

Quote from: DaveReid on April 02, 2010, 02:47:05 PMOh, and before I get accused of ugly commercialism, FlightRouteLookup is a free service, always has been and always will be, open to all to use  :-)

And well worth using for route lookups.  Goto http://www.flightroutelookup.com/FlightRoute/ and select FlightLookup