FlightXml2 - Issues InFlightInfo by TailNumber

Hi,

We have found issues requesting method “InFlightInfo” (FlightXML2). We need to retrieve enroute flight data with ident=tailNumber but response doesn’t contain the expected data, while it’s working as expected using ident=flightCode.

For example today flight with tailNumber=”EC-HQL” and FlightCode=” VLG6331” following test

- Test InFlightInfo using ident=TailNumber (“EC-HQL”):
{“InFlightInfoResult”:{“faFlightID”:“”,“ident”:“ECHQL”,“prefix”:“”,“type”:“”,“suffix”:“”,“origin”:“”,“destination”:“”,“timeout”:“”,“timestamp”:0,“departureTime”:0,
“firstPositionTime”:0,“arrivalTime”:0,“longitude”:0,“latitude”:0,“lowLongitude”:0,“lowLatitude”:0,“highLongitude”:0,“highLatitude”:0,“groundspeed”:0,“altitude”:0,
“heading”:0,“altitudeStatus”:“”,“updateType”:“”,“altitudeChange”:“”,“waypoints”:“”}}

- Test InFlightInfo using ident=FlightCode(“VLG6331”)
{“InFlightInfoResult”:{“faFlightID”:“VLG6331-1432625700-schedule-0261:2”,“ident”:“VLG6331”,“prefix”:“”,“type”:“A320”,“suffix”:“”,“origin”:“LIMC”,“destination”:“LEBL”,“timeout”:“ok”,“timestamp”:1432802463,“departureTime”:1432800205,“firstPositionTime”:1432800205,
“arrivalTime”:0,“longitude”:3.9344800000000001994,“latitude”:42.359070000000002665,“lowLongitude”:3.9344800000000001994,“lowLatitude”:42.359070000000002665,
“highLongitude”:8.2850999999999999091,“highLatitude”:45.20859999999999701,“groundspeed”:410,“altitude”:283,“heading”:220,“altitudeStatus”:“”,“updateType”:“TA”,“altitudeChange”:“D”,“waypoints”:“”}}

We’ve encountered similar behavior using tail number instead of flightCode in “FlightInfoEx” method.

Could you please tell us why for enroute flights the same service is responding wrongly using tail number as input value?

Thanks a lot,
Lore

Adding another sample of ‘in progress’ flight. The aircraft with tail number ‘EC-LAA’ used for flight VLG7100

- test InFlightInfo using tail number
{“InFlightInfoResult”:{“faFlightID”:“”,“ident”:“ECLAA”,“prefix”:“”,“type”:“”,“suffix”:“”,“origin”:“”,“destination”:“”,“timeout”:“”,“timestamp”:0,“departureTime”:0,“firstPositionTime”:0,
“arrivalTime”:0,“longitude”:0,“latitude”:0,“lowLongitude”:0,“lowLatitude”:0,“highLongitude”:0,“highLatitude”:0,“groundspeed”:0,“altitude”:0,“heading”:0,
“altitudeStatus”:“”,“updateType”:“”,“altitudeChange”:“”,“waypoints”:“”}}

- test InFlightInfo using flight code
{“InFlightInfoResult”:{“faFlightID”:“VLG7100-1432646100-schedule-0215:0”,“ident”:“VLG7100”,“prefix”:“”,“type”:“A320”,“suffix”:“”,“origin”:“LECO”,“destination”:“EGLL”,“timeout”:“ok”,“timestamp”:1432819825,
“departureTime”:1432819319,“firstPositionTime”:1432819319,“arrivalTime”:0,“longitude”:-7.7201899999999996638,“latitude”:43.838880000000003179,“lowLongitude”:-8.3666599999999995418,“lowLatitude”:43.313740000000002794,“highLongitude”:-7.7201899999999996638,“highLatitude”:43.838880000000003179,“groundspeed”:443,“altitude”:167,“heading”:30,“altitudeStatus”:“”,
“updateType”:“TA”,“altitudeChange”:“C”,“waypoints”:“”}}

We are using Rest/Json accessing protocol.

InFlightInfo must be called with the effective ident that the flight is actually operating as, since that method does not do all of the canonicalization lookups that FlightInfoEx performs.

What should be the correct ident value (for InFlightInfo calling) that enables us to retrieve the enroute flight in case we get only the aircraft tail number? In case InFlightInfo doesn’t admit tailNumber as ident, what should be the correct method to retrieve the enroute flight by tail number?

Thanks in advance,

Call FlightInfoEx first, and use the “ident” or the “faFlightID” that is in its response.

We’re testing following flight that is currently in enroute status:
http://it.flightaware.com/live/flight/IBE3160

If we call FlightInfoEx by tailNumber (=‘EC-HUI’) with parameters howMany=15 and offset=0 we retrieve following list. If you check we get 2 scheduled flights and past flights until 28th of may. It’s missing current enroute flight with flight code IBE3160:

*ident=IBE522 filed_ete=02:05:00 faFlightID=IBE522-1432746600-schedule-0185 actualdeparturetime=1970-01-01T00:00:00.000Z actualarrivaltime=1970-01-01T00:00:00.000Z originName=Londra-Heathrow destinationName=Madrid-Barajas
ident=IBE510 filed_ete=02:10:00 faFlightID=IBE510-1432722900-schedule-0256:0 actualdeparturetime=1970-01-01T00:00:00.000Z actualarrivaltime=1970-01-01T00:00:00.000Z originName=Londra-Heathrow destinationName=Madrid-Barajas
ident=IBE514 filed_ete=02:20:00 faFlightID=IBE514-1432633200-schedule-0210 actualdeparturetime=2015-05-28T10:10:00.000Z actualarrivaltime=2015-05-28T12:03:00.000Z originName=Londra-Heathrow destinationName=Madrid-Barajas
ident=IBE3160 filed_ete=02:05:00 faFlightID=IBE3160-1432623900-schedule-0080:0 actualdeparturetime=2015-05-28T06:42:15.000Z actualarrivaltime=2015-05-28T08:37:51.000Z originName=Madrid-Barajas destinationName=Londra-Heathrow
ident=IBE3253 filed_ete=02:00:00 faFlightID=IBE3253-1432560900-schedule-0071:2 actualdeparturetime=2015-05-27T13:49:55.000Z actualarrivaltime=2015-05-27T15:25:52.000Z originName=Milano-Malpensa destinationName=Madrid-Barajas
ident=IBE3127 filed_ete=02:25:00 faFlightID=IBE3127-1432533300-schedule-0133:2 actualdeparturetime=2015-05-27T06:10:08.000Z actualarrivaltime=2015-05-27T08:09:27.000Z originName=Francoforte sul Meno destinationName=Madrid-Barajas
ident=IBE3231 filed_ete=02:08:00 faFlightID=IBE3231-1432461300-schedule-0110:0 actualdeparturetime=2015-05-26T10:24:52.000Z actualarrivaltime=2015-05-26T12:22:22.000Z originName=Roma-Fiumicino destinationName=Madrid-Barajas
ident=IBE3235 filed_ete=02:15:00 faFlightID=IBE3235-1432405200-schedule-0161:0 actualdeparturetime=2015-05-25T18:38:05.000Z actualarrivaltime=2015-05-25T20:33:45.000Z originName=Roma-Fiumicino destinationName=Madrid-Barajas
ident=IBE3251 filed_ete=02:05:00 faFlightID=IBE3251-1432378800-schedule-0439:2 actualdeparturetime=2015-05-25T11:17:30.000Z actualarrivaltime=2015-05-25T12:57:42.000Z originName=Milano-Linate destinationName=Madrid-Barajas
ident=IBE3250 filed_ete=01:34:00 faFlightID=IBE3250-1432365300-schedule-0221:2 actualdeparturetime=2015-05-25T07:50:00.000Z actualarrivaltime=2015-05-25T09:38:00.000Z originName=Madrid-Barajas destinationName=Milano-Linate
ident=IBE3253 filed_ete=02:10:00 faFlightID=IBE3253-1432301700-schedule-0097:2 actualdeparturetime=2015-05-24T13:46:13.000Z actualarrivaltime=2015-05-24T15:26:07.000Z originName=Milano-Malpensa destinationName=Madrid-Barajas
ident=IBE3127 filed_ete=02:25:00 faFlightID=IBE3127-1432274100-schedule-0024:2 actualdeparturetime=2015-05-24T06:09:53.000Z actualarrivaltime=2015-05-24T08:12:35.000Z originName=Francoforte sul Meno destinationName=Madrid-Barajas
ident=IBE3192 filed_ete=02:24:00 faFlightID=IBE3192-1432130400-schedule-0193:2 actualdeparturetime=2015-05-22T14:23:50.000Z actualarrivaltime=2015-05-22T16:38:05.000Z originName=Madrid-Barajas destinationName=internazionale di Monaco di Baviera
ident=IBE3148 filed_ete=02:43:00 faFlightID=IBE3148-1432024500-schedule-0053:0 actualdeparturetime=2015-05-21T08:45:45.000Z actualarrivaltime=2015-05-21T11:17:21.000Z originName=Madrid-Barajas destinationName=Praga-Ruzyně
ident=IBE3235 filed_ete=02:14:00 faFlightID=IBE3235-1431886800-schedule-0243:0 actualdeparturetime=2015-05-19T18:35:47.000Z actualarrivaltime=2015-05-19T20:40:17.000Z originName=Roma-Fiumicino destinationName=Madrid-Barajas *

Instead, calling InFlightInfo by flightCode=IBE3160 the needed flight data is retrieved (faFlightID is not admitted as parameter of InFlightInfo):
ident=IBE3160 faFlightID=IBE3160-1432710300-schedule-0072:0 departureTime=2015-05-29T07:10:27.000Z arrivalTime=1970-01-01T00:00:00.000Z origin=LEMD destination=EGLL

Since we get the only tail number information and we need to retrieve the enroute flight, could you please help us resolving it?

I post another sample for FlightInfoEx using tail number EC-JXV that is going to Florence.

http://it.flightaware.com/live/flight/VLG1507

Response of FlightInfoEx return following list without current flight:

FlightInfoEx by EC-JXV → ident=VLG1506 filed_ete=02:04:00 faFlightID=VLG1506-1432715100-schedule-0203:0 actualdeparturetime=2015-05-29T10:33:01.000+02:00 actualarrivaltime=2015-05-29T12:25:20.000+02:00 originCity=Florence (Firenze) IT destinationCity=Madrid ES
FlightInfoEx by EC-JXV → ident=VLG1500 filed_ete=01:18:00 faFlightID=VLG1500-1432650600-schedule-0003:0 actualdeparturetime=2015-05-28T16:53:46.000+02:00 actualarrivaltime=2015-05-28T18:13:24.000+02:00 originCity=Florence (Firenze) IT destinationCity=Orly (near Paris) FR
FlightInfoEx by EC-JXV → ident=VLG6922 filed_ete=00:38:00 faFlightID=VLG6922-1432632300-schedule-0051:0 actualdeparturetime=2015-05-28T11:56:41.000+02:00 actualarrivaltime=2015-05-28T12:40:00.000+02:00 originCity=Florence (Firenze) IT destinationCity= IT
FlightInfoEx by EC-JXV → ident=VLG6800 filed_ete=01:38:00 faFlightID=VLG6800-1432546200-schedule-0020:2 actualdeparturetime=2015-05-27T11:54:46.000+02:00 actualarrivaltime=2015-05-27T13:22:00.000+02:00 originCity=Florence (Firenze) IT destinationCity=Berlin DE
FlightInfoEx by EC-JXV → ident=VLG1506 filed_ete=02:13:00 faFlightID=VLG1506-1432443600-schedule-0322:0 actualdeparturetime=2015-05-26T07:11:09.000+02:00 actualarrivaltime=2015-05-26T08:53:26.000+02:00 originCity=Florence (Firenze) IT destinationCity=Madrid ES
FlightInfoEx by EC-JXV → ident=VLG1500 filed_ete=01:28:00 faFlightID=VLG1500-1432305000-schedule-0240:0 actualdeparturetime=2015-05-24T16:41:45.000+02:00 actualarrivaltime=2015-05-24T17:56:12.000+02:00 originCity=Florence (Firenze) IT destinationCity=Orly (near Paris) FR
FlightInfoEx by EC-JXV → ident=VLG1507 filed_ete=02:08:00 faFlightID=VLG1507-1432294200-schedule-0255:0 actualdeparturetime=2015-05-24T13:36:21.000+02:00 actualarrivaltime=2015-05-24T15:11:00.000+02:00 originCity=Madrid ES destinationCity=Florence (Firenze) IT
FlightInfoEx by EC-JXV → ident=VLG1506 filed_ete=01:55:00 faFlightID=VLG1506-1432283100-schedule-0059:0 actualdeparturetime=2015-05-24T10:39:26.000+02:00 actualarrivaltime=2015-05-24T12:25:41.000+02:00 originCity=Florence (Firenze) IT destinationCity=Madrid ES
FlightInfoEx by EC-JXV → ident=VLG6205 filed_ete=01:24:00 faFlightID=VLG6205-1432137000-schedule-0095:0 actualdeparturetime=2015-05-22T20:17:00.000+02:00 actualarrivaltime=2015-05-22T21:55:00.000+02:00 originCity=London, England GB destinationCity=Florence (Firenze) IT
FlightInfoEx by EC-JXV → ident=VLG8247 filed_ete=01:25:00 faFlightID=VLG8247-1432038900-schedule-0018:0 actualdeparturetime=2015-05-21T14:50:18.000+02:00 actualarrivaltime=2015-05-21T15:59:15.000+02:00 originCity=Paris FR destinationCity=Barcelona ES
FlightInfoEx by EC-JXV → ident=VLG8246 filed_ete=01:47:00 faFlightID=VLG8246-1432029600-schedule-0185:0 actualdeparturetime=2015-05-21T12:12:07.000+02:00 actualarrivaltime=2015-05-21T13:50:15.000+02:00 originCity=Barcelona ES destinationCity=Paris FR
FlightInfoEx by EC-JXV → ident=VLG1845 filed_ete=01:45:00 faFlightID=VLG1845-1431936900-schedule-0151:2 actualdeparturetime=2015-05-20T10:36:10.000+02:00 actualarrivaltime=2015-05-20T12:15:48.000+02:00 originCity=Frankfurt am Main DE destinationCity=Barcelona ES
FlightInfoEx by EC-JXV → ident=VLG1844 filed_ete=02:03:00 faFlightID=VLG1844-1431925800-schedule-0205:2 actualdeparturetime=2015-05-20T07:28:16.000+02:00 actualarrivaltime=2015-05-20T09:15:20.000+02:00 originCity=Barcelona ES destinationCity=Frankfurt am Main DE
FlightInfoEx by EC-JXV → ident=VLG1507 filed_ete=02:02:00 faFlightID=VLG1507-1431788400-schedule-0391:0 actualdeparturetime=2015-05-18T17:09:42.000+02:00 actualarrivaltime=2015-05-18T18:44:00.000+02:00 originCity=Madrid ES destinationCity=Florence (Firenze) IT

We’ve noticed that for other airline flight FlightInfoEx is working correctly:

http://it.flightaware.com/live/flight/AZA204

In this case tailNumber EI-IXJ allows following response containing also enroute flight (see record highlighted below):

FlightInfoEx by EI-IXJ → ident=AZA204 filed_ete=02:40:00 faFlightID=AZA204-1432726200-schedule-0393:0 actualdeparturetime=2015-05-29T14:08:47.000+02:00 actualarrivaltime=1970-01-01T01:00:00.000+01:00 originCity=Rome IT destinationCity=London, England GB
FlightInfoEx by EI-IXJ → ident=AZA1594 filed_ete=00:55:00 faFlightID=AZA1594-1432718400-schedule-0093:0 actualdeparturetime=2015-05-29T11:35:00.000+02:00 actualarrivaltime=2015-05-29T12:24:00.000+02:00 originCity=Cagliari, Sardinia IT destinationCity=Rome IT
FlightInfoEx by EI-IXJ → ident=AZA1593 filed_ete=00:50:00 faFlightID=AZA1593-1432711500-schedule-0077:0 actualdeparturetime=2015-05-29T09:50:00.000+02:00 actualarrivaltime=2015-05-29T10:34:49.000+02:00 originCity=Rome IT destinationCity=Cagliari, Sardinia IT
FlightInfoEx by EI-IXJ → ident=AZA1602 filed_ete=00:50:00 faFlightID=AZA1602-1432702200-schedule-0047:0 actualdeparturetime=2015-05-29T07:12:00.000+02:00 actualarrivaltime=2015-05-29T08:01:00.000+02:00 originCity=Bari IT destinationCity=Rome IT
FlightInfoEx by EI-IXJ → ident=AZA1603 filed_ete=00:52:00 faFlightID=AZA1603-1432618175-airline-0240:0 actualdeparturetime=2015-05-28T22:40:00.000+02:00 actualarrivaltime=2015-05-28T23:23:00.000+02:00 originCity=Rome IT destinationCity=Bari IT
FlightInfoEx by EI-IXJ → ident=AZA583 filed_ete=01:15:00 faFlightID=AZA583-1432656900-schedule-0008:0 actualdeparturetime=2015-05-28T20:07:00.000+02:00 actualarrivaltime=2015-05-28T21:18:00.000+02:00 originCity=Tirana AL destinationCity=Rome IT
FlightInfoEx by EI-IXJ → ident=AZA584 filed_ete=01:20:00 faFlightID=AZA584-1432647300-schedule-0025:0 actualdeparturetime=2015-05-28T18:07:12.000+02:00 actualarrivaltime=2015-05-28T19:00:00.000+02:00 originCity=Rome IT destinationCity=Tirana AL
FlightInfoEx by EI-IXJ → ident=AZA333 filed_ete=01:55:00 faFlightID=AZA333-1432636800-schedule-0302:0 actualdeparturetime=2015-05-28T13:04:07.000+02:00 actualarrivaltime=2015-05-28T15:04:02.000+02:00 originCity=Paris FR destinationCity=Rome IT
FlightInfoEx by EI-IXJ → ident=AZA318 filed_ete=02:05:00 faFlightID=AZA318-1432624500-schedule-0038:0 actualdeparturetime=2015-05-28T09:35:00.000+02:00 actualarrivaltime=2015-05-28T11:19:00.000+02:00 originCity=Rome IT destinationCity=Paris FR
FlightInfoEx by EI-IXJ → ident=AZA1162 filed_ete=00:50:00 faFlightID=AZA1162-1432616400-schedule-0442:0 actualdeparturetime=2015-05-28T07:02:00.000+02:00 actualarrivaltime=2015-05-28T07:58:27.000+02:00 originCity=Lamezia Terme, Catanzaro IT destinationCity=Rome IT
FlightInfoEx by EI-IXJ → ident=AZA1163 filed_ete=01:00:00 faFlightID=AZA1163-1432579500-schedule-0165:0 actualdeparturetime=2015-05-27T20:57:47.000+02:00 actualarrivaltime=2015-05-27T22:05:00.000+02:00 originCity=Rome IT destinationCity=Lamezia Terme, Catanzaro IT
FlightInfoEx by EI-IXJ → ident=AZA809 filed_ete=03:35:00 faFlightID=AZA809-1432671373-ed-0005:0 actualdeparturetime=2015-05-27T05:10:00.000+02:00 actualarrivaltime=2015-05-27T08:26:00.000+02:00 originCity=Tel Aviv IL destinationCity=Rome IT
FlightInfoEx by EI-IXJ → ident=AZA721 filed_ete=01:55:00 faFlightID=AZA721-1432445226-airline-0039:2 actualdeparturetime=2015-05-26T18:05:00.000+02:00 actualarrivaltime=2015-05-26T19:44:00.000+02:00 originCity=Athens GR destinationCity=Rome IT
FlightInfoEx by EI-IXJ → ident=AZA718 filed_ete=01:55:00 faFlightID=AZA718-1432445226-airline-0036:2 actualdeparturetime=2015-05-26T15:15:00.000+02:00 actualarrivaltime=2015-05-26T16:53:17.000+02:00 originCity=Rome IT destinationCity=Athens GR
FlightInfoEx by EI-IXJ → ident=AZA343 filed_ete=00:59:00 faFlightID=AZA343-1432461000-schedule-0113:0 actualdeparturetime=2015-05-26T12:15:00.000+02:00 actualarrivaltime=2015-05-26T13:02:00.000+02:00 originCity=Nice FR destinationCity=Rome IT

In particular for some cases like Vueling tailNumber value is always blank in AirlineFlightInfo structure (see sample detailed below):

– sample below using faFlightID ‘VLG1326-1432733400-schedule-0106:2’ → tail number not relationed to flightID
AirlineFlightInfo by VLG1326-1432733400-schedule-0106:2 → {ident=VLG1326 faFlightID=VLG1326-1432733400-schedule-0106:2 tailnumber=‘’}

– sample below using a RyanAir flight (tailNumber EI-EVG; flight code RYR9111) → in this case tail number is correctly relationed to flightID
FlightInfoEx by EI-EVG -->{ ident=RYR9111 filed_departuretime=2015.05.29 AD at 16:35:00 CEST filed_ete=01:25:00 faFlightID=RYR9111-1432750200-schedule-0019:0 actualdeparturetime=2015.05.29 AD at 16:49:13 CEST actualarrivaltime=1970.01.01 AD at 01:00:00 CET originCity=Barcelona ES destinationCity=Turin (Torino) IT }
AirlineFlightInfo by RYR9111-1432750200-schedule-0019:0 → {ident=RYR9111 faFlightID=RYR9111-1432750200-schedule-0019:0 tailnumber=EIEVG }

Maybe for some airline companies the relation {tailNumber <–> enroute flight} is missing ? For Vueling airline it’s missing, but for major airlines like AirFrance it isn’t. Could you please check it?

Aircraft tailnumber information is not available for all flights. This is a limitation in the data that some airlines provide to us, however we have a new data source that we expect will provide additional registration assignments in the next few weeks.

Additionally, the aircraft ownership information (via TailOwner) is currently only available for U.S. registered aircraft (generally registrations beginning with “N”).