Data Gltich - Bad Arrival Time on FXML3 Airport Board, Not Correcting

FlightAware AeroAPI
1

This one popped up in the FXML3 airportboard at KPAE.

FA Flight ID: RA76950-1516295305-adhoc-0

Link: https://flightaware.com/live/flight/RA76950

Your website is correctly showing an ETA at PAE of 4:45 PM PST, unfortunately, the data in the feed shows it already arrived at PAE at 9:08 AM PST.

2

When the actualarrivaltime == actualdeparturetime, then that is an indication that the flight is “result unknown” and that we do not have enough information to know its true arrival time. Please see the FAQ https://flightaware.com/commercial/flightxml/faq.rvt#departureArrivalSame

3

I’d nominate the “actual arrival == actual departure” for deprecation in FXML3… and it’s particularly strange in cases like this where you have enough info to show an ETA.

For this case, it’s displayed erroneously on your site/app too - here’s a screenshot from another flight happening now (2:15 PM PST), RA76511-1517079027-adhoc-0, from your site. You’ve got enough info to have an ETA of 6:43 PM PST, but your progress bar is showing 100%, and it shows in “Arrivals” instead of “En Route / Scheduled.”

21%20PM
21%20PM1269×942 371 KB
38%20PM
38%20PM1180×1057 212 KB

4

Here’s the FXML3 data from AirportBoard, which is showing 100% progress and a status of “Estimated Arrival,” even though you’ve got a solid ETA several hours in the future, and know the aircraft is quite some distance from its destination.

{"ident":"VDA5334",
"faFlightID":"RA76511-1517079027-adhoc-0",
"airline":"VDA",
"airline_iata":"VI",
"flightnumber":"5334",
"tailnumber":"RA-76511",
"type":"Form_Airline",
"blocked":false,
"diverted":false,
"cancelled":false,
"origin":{"code":"BIKF",
"city":"Keflavik",
"alternate_ident":"KEF",
"airport_name":"Keflavik Int'l"},
"destination":{"code":"KPAE",
"city":"Everett,
 WA",
"alternate_ident":"",
"airport_name":"Snohomish County"},
"route":"6700N\/05000W CANEL 6830N\/07000W 6800N\/08000W 6400N\/10000W 6000N\/11000W 5500N\/11700W BOOTH J508 SHARD V349 HUH V23 PAE",
"distance_filed":3637,
"filed_departure_time":{"epoch":1517079027,
"tz":"GMT",
"dow":"Saturday",
"time":"06:50PM",
"date":"01\/27\/2018",
"localtime":1517079027},
"estimated_departure_time":{"epoch":1517079027,
"tz":"GMT",
"dow":"Saturday",
"time":"06:50PM",
"date":"01\/27\/2018",
"localtime":1517079027},
"actual_departure_time":{"epoch":1517079027,
"tz":"GMT",
"dow":"Saturday",
"time":"06:50PM",
"date":"01\/27\/2018",
"localtime":1517079027},
"departure_delay":0,
"filed_arrival_time":{"epoch":0},
"estimated_arrival_time":{"epoch":1517107319,
"tz":"PST",
"dow":"Saturday",
"time":"06:41PM",
"date":"01\/27\/2018",
"localtime":1517078519},
"actual_arrival_time":{"epoch":1517079027,
"tz":"PST",
"dow":"Saturday",
"time":"10:50AM",
"date":"01\/27\/2018",
"localtime":1517050227},
"status":"Estimated arrival",
"progress_percent":100,
"aircrafttype":"IL76",
"full_aircrafttype":"IL76",
"adhoc":false}
5

In other words, in an instance like this, progress shouldn’t be 100%, status shouldn’t be “Estimated Arrived,” and it should show in the Airport Board array for scheduled instead of arrived.