FlightXML2 Arrival Flights Marked as Schedule


#1

We are using Flight Aware in order to get flights for several aircraft.
We have an example for a flight that happened on October 24 between Kuala Lumpur, Malaysia and Muscat, Oman that is still marked as scheduled when querying your web service (in bold below). However that same exact flight is indicated as landed when looking at your website directly (see attached pictures).
{
“faFlightID”: “OMA144-1508650013-airline-0035:0”,
“ident”: “OMA144”,
“aircrafttype”: “A330”,
“filed_ete”: “06:25:00”,
“filed_time”: 1508832995,
“filed_departuretime”: 1508876100,
“filed_airspeed_kts”: 437,
“filed_airspeed_mach”: “”,
“filed_altitude”: 0,
“route”: “”,
“actualdeparturetime”: 1508876670,
“estimatedarrivaltime”: 1508900643,
“actualarrivaltime”: 1508900643,
“diverted”: “”,
“origin”: “LIMC”,
“destination”: “OOMS”,
“originName”: “Malpensa Int’l”,
“originCity”: “Milan”,
“destinationName”: “Seeb Int’l”,
“destinationCity”: “Muscat”
},
{
“faFlightID”: “OMA143-1508650013-airline-0154:0”,
“ident”: “OMA143”,
“aircrafttype”: “A330”,
“filed_ete”: “07:02:00”,
“filed_time”: 1508835406,
“filed_departuretime”: 1508840700,
“filed_airspeed_kts”: 400,
“filed_airspeed_mach”: “”,
“filed_altitude”: 0,
“route”: “”,
“actualdeparturetime”: 1508841154,
“estimatedarrivaltime”: 1508864842,
“actualarrivaltime”: 1508864842,
“diverted”: “”,
“origin”: “OOMS”,
“destination”: “LIMC”,
“originName”: “Seeb Int’l”,
“originCity”: “Muscat”,
“destinationName”: “Malpensa Int’l”,
“destinationCity”: “Milan”
},
{
“faFlightID”: “OMA822-1508635800-schedule-0000:0”,
“ident”: “OMA822”,
“aircrafttype”: “A330”,
“filed_ete”: “06:35:00”,
“filed_time”: 1508779291,
“filed_departuretime”: 1508808600,
“filed_airspeed_kts”: 418,
“filed_airspeed_mach”: “”,
“filed_altitude”: 0,
“route”: “”,
“actualdeparturetime”: 1508809614, => Tuesday, October 24, 2017 1:46:54 AM
"estimatedarrivaltime": 1508832250, => Tuesday, October 24, 2017 8:04:10 AM
"actualarrivaltime": 1508832250,
“diverted”: “”,
“origin”: “WMKK”,
“destination”: “OOMS”,
“originName”: “Kuala Lumpur Int’l”,
“originCity”: “Sepang, Selangor”,
“destinationName”: “Seeb Int’l”,
“destinationCity”: “Muscat”
},
{
“faFlightID”: “OMA821-1508563549-airline-0284:0”,
“ident”: “OMA821”,
“aircrafttype”: “A330”,
“filed_ete”: “07:01:00”,
“filed_time”: 1508773621,
“filed_departuretime”: 1508777100,
“filed_airspeed_kts”: 413,
“filed_airspeed_mach”: “”,
“filed_altitude”: 0,
“route”: “”,
“actualdeparturetime”: 1508778516,
“estimatedarrivaltime”: 1508802534,
“actualarrivaltime”: 1508802534,
“diverted”: “”,
“origin”: “OOMS”,
“destination”: “WMKK”,
“originName”: “Seeb Int’l”,
“originCity”: “Muscat”,
“destinationName”: “Kuala Lumpur Int’l”,
“destinationCity”: “Sepang, Selangor”
},

Can you please tell us why the faFlightID field still contain the schedule keyword instead of the airline keyword?
We are using this flight in order to filter flights between scheduled and actual flights. So thank you for clarifying this issue.


#2

Flight IDs are an opaque internal identifier, you should not try to assign any meaning to them.