Flight shedule table by carrier

Hello. I need to build a flight shedule table by carrier with the following columns: Source City, destination city, flight number, departure time, flight duration and days of operation (days of week). For example: [AMS, PAR, AF1241, 09:30, 1:15, 1 2 3 4 5 6 7].

Is it possible to build such table with your api? How many requests required?

I suggest that we need a function Airlines Flight Schedules.
I can specify a date for the week, origin, destination, airline
But in response, returns the structure ArrayOfAirlineFlightScheduleStruct does not contain the flight number
So I need to use flight number too in filter.

And if i have 70’000 routes for all airlines, I need to make 70’000 requests to build my shedule table , and it will cost 70’000 * $0.0050 = $364 ? I’m right ?

Hi,
Indeed you could use AirlineFlightSchedules or just Scheduled(for next 24 hours https://flightxml.flightaware.com/soap/FlightXML2/doc#op_Scheduled )
From your message I understand that you would like the returned AirlineFlightScheduleStruct to have the flight number, right?
Looking at the returned AirlineFlightScheduleStruct I see there is an actual_ident(meant to give you the operating carrier) and an ident field (for the marketing airline):
https://flightxml.flightaware.com/soap/FlightXML2/doc#type_AirlineFlightScheduleStruct
I may misunderstand your question, but you could find the flight number from one of these 2 idents.

So for example here I request next 3 schedules between Charles de Gaulle Airport and Schiphol Airport:
https://flightxml.flightaware.com/json/FlightXML2/AirlineFlightSchedules?startDate=1455206406&endDate=1455306406&origin=LFPG&destination=EHAM&howMany=3
and I get:


{"AirlineFlightSchedulesResult":{"next_offset":3,"data":{"ident":"KQA3034","actual_ident":"AFR1440","departuretime":1455209400,"arrivaltime":1455213900,"origin":"LFPG","destination":"EHAM","aircrafttype":"A321","meal_service":"","seats_cabin_first":0,"seats_cabin_business":0,"seats_cabin_coach":0},{"ident":"KLM2022","actual_ident":"AFR1440","departuretime":1455209400,"arrivaltime":1455213900,"origin":"LFPG","destination":"EHAM","aircrafttype":"A321","meal_service":"","seats_cabin_first":0,"seats_cabin_business":0,"seats_cabin_coach":0},{"ident":"AMX6508","actual_ident":"KLM1244","departuretime":1455212400,"arrivaltime":1455217200,"origin":"LFPG","destination":"EHAM","aircrafttype":"B738","meal_service":"","seats_cabin_first":0,"seats_cabin_business":0,"seats_cabin_coach":0}]}}

Origin and dest are optional, so if you want schedules by operating carrier for example Air France you could use something like this:
https://flightxml.flightaware.com/json/FlightXML2/AirlineFlightSchedules?startDate=1455206406&endDate=1455306406&airline=AFR&howMany=3
with result:


{"AirlineFlightSchedulesResult":{"next_offset":3,"data":{"ident":"AFR7980","actual_ident":"BTI349","departuretime":1455225300,"arrivaltime":1455227940,"origin":"EVRA","destination":"EYVI","aircrafttype":"B735","meal_service":"","seats_cabin_first":0,"seats_cabin_business":0,"seats_cabin_coach":0},{"ident":"AFR4835","actual_ident":"AEA6072","departuretime":1455205500,"arrivaltime":1455208500,"origin":"LEPA","destination":"LEBL","aircrafttype":"E190","meal_service":"","seats_cabin_first":0,"seats_cabin_business":0,"seats_cabin_coach":0},{"ident":"AFR3597","actual_ident":"DAL476","departuretime":1455237000,"arrivaltime":1455264900,"origin":"KJFK","destination":"LEBL","aircrafttype":"B764","meal_service":"","seats_cabin_first":0,"seats_cabin_business":0,"seats_cabin_coach":0}]}}

Does this help?

Yes, thank you for help. But I have one question. Can I use IATA codes in query parameters and get the response with the IATA codes, not ICAO? For example AFR1140 - AF1140, LFPG - CDG ?

You can use IATA codes when requesting the schedules with AirlineFlightSchedules, however the results will only have ICAO for both idents and airports.
I see that including IATA would be easy and very useful for users. I will request this for our next API version.

https://flightxml.flightaware.com/json/FlightXML2/AirlineFlightSchedules?startDate=1455206406&endDate=1455306406&origin=CDG&howMany=3

result:



{"AirlineFlightSchedulesResult":{"next_offset":3,"data":{"ident":"BAW8097","actual_ident":"VLG8245","departuretime":1455217200,"arrivaltime":1455223200,"origin":"LFPG","destination":"LEBL","aircrafttype":"A320","meal_service":"","seats_cabin_first":0,"seats_cabin_business":0,"seats_cabin_coach":0},{"ident":"IBE5243","actual_ident":"VLG8245","departuretime":1455217200,"arrivaltime":1455223200,"origin":"LFPG","destination":"LEBL","aircrafttype":"","meal_service":"","seats_cabin_first":0,"seats_cabin_business":0,"seats_cabin_coach":0},{"ident":"JAI6766","actual_ident":"AFR1448","departuretime":1455220500,"arrivaltime":1455226500,"origin":"LFPG","destination":"LEBL","aircrafttype":"A321","meal_service":"","seats_cabin_first":0,"seats_cabin_business":0,"seats_cabin_coach":0}]}}

Hi, I’m just hitting upon this same issue myself so thought I’d resurrect this discussion rather than start a new one.

I’d like to be able to cross-reference the flight number, as printed on customer boarding passes, with the flight ident returned from AirlineFlightSchedules. Unfortunately, the boarding passes display the IATA code rather than ICAO code as far as I can tell?

Is there any way this API could return an [iata_ident] field or something?

Thanks in advance,

Nat

Our APIs always return ICAO codes when possible, due to known ambiguity and conflicting IATA code issues. This is not something that is possible to change.

If you need to display IATA codes to your users, then you can use a local lookup table to perform such conversions. The airport databases are available from various sources, including us flightaware.com/commercial/data/airports

Just wanted to show my support for including IATA in the response which would save more than 30 lines of code in my example matching User input to possible ICAO & IATA codes. Not to mention the headache of dealing with proceeding zero’s in flight numbers.

Sent from my iPhone using Tapatalk

Thanks, we will keep this in mind for our upcoming FlightXML3 release in the coming months.