Greetings,
We use FlightXML API to track certain charter flights which by their nature don’t have fixed routes but can be tracked fine on your consumer site. For our preliminary work with notifications via API we’ve noticed that typically for our specific charter flights, the arrival event postback typically has the actualarrivaltime set to the same value as actualdeparturetime. In the long_desc string the arrival time seems to show as the original filed arrival time. Arrival events for more regularly scheduled flights (for instance SWA flights) seem to post back with the arrival time displayed on the consumer site. On the consumer site and via API the correct actualarrivaltime can be obtained for our flights as well (presumably a few minutes later than when notification as posted). What’s the deal - is it a timing thing? Can you delay sending the arrival notification until the API has a reasonable value in it based on actualdeparturetime? What is with mixing of UTC and GMT descriptor in long_desc?
M
Examples:
{“long_desc”:“Era Alaska #8040 arrived at Anchorage Intl (PANC) at 20:51 UTC from PAOT/OTZ (Ralph Wien Memorial)”,“short_desc”:“ERR8040 arrived at PANC from PAOT/OTZ”,“summary”:“ERR8040 arrived at PANC from PAOT/OTZ”,“eventcode”:“arrival”,“alert_id”:5861478,“flight”:{“ident”:“ERR8040”,“aircrafttype”:“DH8A”,“origin”:“PAOT”,“destination”:“PANC”,“filed_ete”:“02:36:00”,“route”:“OTZ J117 GAL TAGER6”,“faFlightID”:“ERR8040-1390999423-106-0”,“filed_altitude”:230,“filed_airspeed_kts”:250,“filed_time”:1390999417,“filed_departuretime”:1391020200,“estimatedarrivaltime”:1391028679,“actualarrivaltime”:1391020680,“actualdeparturetime”:1391020680,“estimated_blockin_time”:0,“filed_blockin_time”:0,“actual_blockin_time”:0,“estimated_blockout_time”:0,“filed_blockout_time”:0,“actual_blockout_time”:0,“filed_arrivaltime”:1391029560}}
{“long_desc”:“Era Alaska #8040 arrived at Ralph Wien Memorial (PAOT/OTZ) at 17:25 GMT from PANC (Anchorage Intl)”,“short_desc”:“ERR8040 arrived at PAOT/OTZ from PANC”,“summary”:“ERR8040 arrived at PAOT/OTZ from PANC”,“eventcode”:“arrival”,“alert_id”:5861478,“flight”:{“ident”:“ERR8040”,“aircrafttype”:“DH8A”,“origin”:“PANC”,“destination”:“PAOT”,“filed_ete”:“01:45:00”,“route”:“TED J133 GAL J117 OTZ”,“faFlightID”:“ERR8040-1390999387-77-0”,“filed_altitude”:240,“filed_airspeed_kts”:250,“filed_time”:1390999364,“filed_departuretime”:1391010300,“estimatedarrivaltime”:1391016308,“actualarrivaltime”:1391010360,“actualdeparturetime”:1391010360,“estimated_blockin_time”:0,“filed_blockin_time”:0,“actual_blockin_time”:0,“estimated_blockout_time”:0,“filed_blockout_time”:0,“actual_blockout_time”:0,“filed_arrivaltime”:1391016600}}
{“long_desc”:“Era Alaska #8040 arrived at Anchorage Intl (PANC) at 22:35 GMT from PAOT/OTZ (Ralph Wien Memorial)”,“short_desc”:“ERR8040 arrived at PANC from PAOT/OTZ”,“summary”:“ERR8040 arrived at PANC from PAOT/OTZ”,“eventcode”:“arrival”,“alert_id”:5861478,“flight”:{“ident”:“ERR8040”,“aircrafttype”:“DH8A”,“origin”:“PAOT”,“destination”:“PANC”,“filed_ete”:“02:23:00”,“route”:“OTZ J117 GAL TAGER6”,“faFlightID”:“ERR8040-1390926008-213-0”,“filed_altitude”:230,“filed_airspeed_kts”:250,“filed_time”:1390925991,“filed_departuretime”:1390941900,“estimatedarrivaltime”:1390948539,“actualarrivaltime”:1390939920,“actualdeparturetime”:1390939920,“estimated_blockin_time”:0,“filed_blockin_time”:0,“actual_blockin_time”:0,“estimated_blockout_time”:0,“filed_blockout_time”:0,“actual_blockout_time”:0,“filed_arrivaltime”:1390950480}}