Use the IATA code if it exists. Either the AirportIATA code or the AirportICAO code for the airport where a multi leg flight originated. For single leg flights it will be the same as the departure airport. Use the IATA code if it exists. Either the AirportIATA code or the AirportICAO code for the previous airport of a multi leg flight. For single leg flights it will be the same as the origin airport. Use the IATA code if it exists. Either the AirportIATA code or the AirportICAO code for the next airport of a multi leg flight. For single leg flights it will be the same as the final airport. Use the IATA code if it exists. Either the AirportIATA code or the AirportICAO code for the final airport of a multi leg flight. For single leg flights it will be the same as the arrival airport. Required for arrival slot request. The airport the flight departed from. The arrival airport is the SlotCoordinatedAirportIATA. Required for arrival slot request. NB! The use of 'U' to indicate an ambulance flight is not in accordance with FlightServiceTypeIATA. The following service types are defined in the IATA GCR ( General aviation Clearance Request) standard. Required for departure slot request. The airport the flight will depart to. Required for departure slot request. The GADeleteSlotInfo must match the data given in GAInsertUpdateSlotInfo. See GAInsertUpdateSlotInfo for further details.InsertUpdateSlotScheduleInfo
Term / Type Comments / Description SlotCoordinatedAirportIATA / AirportIATA DepartureFlightId ScheduleSeason ScheduleStartDate / DateUTC ScheduleEndDate / DateUTC ScheduleFlightDays
The string is always seven characters long. '0' indicates no flight on that day, the day number ('1'..'7') indicates a flight on that day. The first day of the week is always Monday.
"1234567" - flights on all days.
"1234500" - flights on Monday - Friday, no flights on Saturday and Sunday.
"1030500" - flights on Moday, Wednesday and Friday.
For flights staying at the SlotCoordinatedAirportIATA over midnight UTC time, see ScheduleOverMidnights, the pattern indicates the day of the arriving flight.ScheduleFlightWeeks OriginAirport / AirportIATAorICAO
See also: OriginAirportIATA, OriginAirportICAO PreviousAirport / AirportIATAorICAO
See also: PreviousAirportIATA, PreviousAirportICAONextAirport / AirportIATAorICAO
See also: NextAirportIATA, NextAirportICAOFinalAirport / AirportIATAorICAO
See also: FinalAirportIATA, FinalAirportICAOSIBTotp / TimeUTC SOBTotp / TimeUTC ScheduleOverMidnights / Count ArrivalFlightServiceTypeIATA / FlightServiceTypeIATA DepartureFlightServiceTypeIATA / FlightServiceTypeIATA AircraftIATAType
Reference Document: IATA codeset 7800.AircraftICAOType
Reference Document: ICAO document 8643.AircraftRegistration
An aircraft can be re-registered in special cases, for instance if it's sold to an operator in another country.AircraftSeatingCapacity / Count
DeleteSlotScheduleInfo
Term / Type Comments / Description SlotCoordinatedAirportIATA / AirportIATA DepartureFlightId ScheduleSeason ScheduleStartDate / DateUTC ScheduleEndDate / DateUTC ScheduleFlightDays
The string is always seven characters long. '0' indicates no flight on that day, the day number ('1'..'7') indicates a flight on that day. The first day of the week is always Monday.
"1234567" - flights on all days.
"1234500" - flights on Monday - Friday, no flights on Saturday and Sunday.
"1030500" - flights on Moday, Wednesday and Friday.
For flights staying at the SlotCoordinatedAirportIATA over midnight UTC time, see ScheduleOverMidnights, the pattern indicates the day of the arriving flight.
GAInsertUpdateSlotInfo
Term / Type Comments / Description AircraftRegistration It is possible to request both an arrival or departure slot for one aircraft in one operation.
Optional if ArrivalFlightId or DepartureFlightId is used.
If both arrival and a departure information is given than it will always be for the same aircraft.AircraftICAOType AircraftTypeDescription AircraftSeatingCapacity Arrival slot request information Deparing from PreviousAirport , arriving at SlotCoordinatedAirportIATA.
All elements are optional as arriving slot request is optional.ArrivalFlightId PreviousAirport SIBT Required for arrival slot request. 
Departure slot request information Departing from SlotCoordinatedAirportIATA, arriving at NextAirport.
All elements are optional as departing slot request is optional.DepartureFlightId Optional if aircraft registration is used. NextAirport SOBT Required for departure slot request. DepartureFlightServiceTypeIATA
GADeleteSlotInfo
Term / Type Comments / Description SlotCoordinatedAirportIATA AircraftRegistration Arrival slot request information ArrivalFlightId PreviousAirport SIBT Departure slot request information DepartureFlightId NextAirport SOBT
SequenceNumberSet
sequenceNumber gaSequenceNumber
The AirportIATA code for the Airport that the schedule is relative to. For slot coordinated airports schedule data is typically given as arrival and departure information (turnaround). Schedules in general are flight oriented.
The FlightId of an arriving flight.
The FlightId of a departing flight.
Defines the season this schedule applies to. Three character string where the first character defines the season and the tho next the year.
The first day of the Schedule.
The last day of the schedule. This is actually the last day for the arriving flight. A departing flight can be up to ScheduleOverMidnights days later.
Also known as DOOP, days of operation. This is a pattern that defines the days of the week which has scheduled flights.
Also known as WOOP, weeks of operation. Allowed values are:
The FlightServiceTypeIATA for an arriving flight.
The FlightServiceTypeIATA for a departing flight.
3 character code as designated by International Air Transport Association (IATA) to uniquely designate Aircraft Type. Local (non-IATA) codes can be added as required as long as they are unique for aircraft types within the defined context.
3-4 character code as designated by International Civil Aviation Organisation (ICAO) to uniquely designate Aircraft Type. Local (non-ICAO) codes can be added as required as long as they are unique for aircraft types within the defined context.
An aircraft registration is a unique alphanumeric string that identifies an aircraft. In accordance with the Convention on International Civil Aviation all aircraft must be registered with a national aviation authority and they must carry proof of this registration in the form of a legal document called a Certificate of Registration at all times when in operation.
Maximum number of passengers that can be seated in the aircraft with the current configuration.
The AirportIATA code for the Airport that the schedule is relative to. For slot coordinated airports schedule data is typically given as arrival and departure information (turnaround). Schedules in general are flight oriented.
The FlightId of an arriving flight.
The FlightId of a departing flight.
Defines the season this schedule applies to. Three character string where the first character defines the season and the tho next the year.
The first day of the Schedule.
The last day of the schedule. This is actually the last day for the arriving flight. A departing flight can be up to ScheduleOverMidnights days later.
Also known as DOOP, days of operation. This is a pattern that defines the days of the week which has scheduled flights.
The airport for which an arrival or departure slot, or both, are requested.
Optional if aircraft registration is used.
Overview
Content Tools