SITA Flight Status API Service

SITA Advanced Data Services
dots.support@sita.aero
version 2.1.0-SNAPSHOT

Table of Contents

1 Revision History
2 Registration and API Sign Up
- 2.1 API Key Usage
- 2.2 Security
3 Flight Status API
- 3.1 Resources - FlightInfoV2
- 3.2 Notes
  - 3.2.1 'view' parameter
4 SeamlessTravel/ACRIS API
- 4.1 Introduction
- 4.2 Resources - SeamlessTravel/ACRIS
  - 4.2.1 GET Flight by Airline, Flight Number, Operation Date, Departure Airport and Arrival Airport
  - 4.2.2 GET Flights by Airport and Direction
5 Error Response
- Response fields
- HTTP response
Appendix A - Status Codes
Appendix B - Flight Status Use Cases
Appendix C - Diverted Flights

1 Revision History

Date	Document Version	Description	Author
`10 May 2022`	`1.0`	`Initial version`	`J. McMullin`

2 Registration and API Sign Up

To access the APIs you will need a registration key, also known as an API key. These can be obtained by creating an account on https://www.developer.aero/ and registering your interest for access to the API.

2.1 API Key Usage

The API key will be passed in an HTTP header as follows:

Name of header: x-apikey
Value of header: The API key as generated for the application.

2.2 Security

All incoming requests will be REST over HTTPS.
Users are authenticated using their API key.
Certain response payload elements will be filtered based on permissions associated with the x-apikey value used.
The API key used in the REST call will be included in the response headers returned to the end user.

Top of Page

3 Flight Status API

The SITA Flight Status API is a REST-based service which provides information about flights around the world.

A user may:

Search for the latest flight details based on a combination of airport, airline and flight number details
Search for flight updates created within a specific time window. These can be at a global level or filtered to an airport/airline/flight number level

3.1 Resources - FlightInfoV2

This section describes the Flight Status API service. Detailed API structure, example requests and responses, JSON schema for request (where appropriate) and responses, and error response codes and formats are included.

3.1.1 GET Flight by Airline and Flight Number
3.1.2 GET Flights by Airport, Airline and Direction
3.1.3 GET Flights by Airport and Direction
3.1.4 GET Flight Updates by Airport, Airline and Flight Number
3.1.5 GET Flight Updates by Airport and Airline
3.1.6 GET Flight Updates by Airport
3.1.7 GET Flight Updates

3.1.1 GET Flight by Airline and Flight Number

GET /flightinfo/v2/flights/airline/{airlineCode}/flightNumber/{flightNumber}

Path parameters
Request parameters
Request headers
Response fields
Curl request
HTTP response

Retrieve a single flight according to airline and flight number showing both the departure and arrival flight details. Results are filtered by operation date (default is current UTC date).
Payload elements are filtered based on permissions associated with the 'x-apikey' used in the request.

operationDate
In this scenario the operationDate is considered to be the local date on which the flight departed/arrived.

operationDate & searchByUTC
A user can force the operationDate value to be considered as UTC by providing the parameter 'searchByUTC=true'.

Path parameters

/flightinfo/v2/flights/airline/{airlineCode}/flightNumber/{flightNumber}
Parameter	Description
`airlineCode`	2-character airline IATA code or 3-character airline ICAO code
`flightNumber`	Flight number

Request parameters

Parameter	Optional	Description
operationDate	true	Local date of operation (yyyy-MM-dd). Default value is current UTC date
searchByUTC	true	Search based by UTC. Default value is false
showCargo	true	Include cargo flights. Default value is false

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
X-apiKey	false	Authorization header that contains the API key.

Response fields

Refer to Response Fields table.

Curl request

            $ curl 'https://flifo.api.aero/flifo/flightinfo/v2/flights/airline/KL/flightNumber/1394?operationDate=2020-01-22' -i -X GET \
                -H 'Content-Type: application/json' \
                -H 'X-apiKey: ff228ab88758a84637f1f88d86899365'

HTTP response

            View sample response here.

Start of Section

3.1.2 GET Flights by Airport, Airline and Direction

GET /flightinfo/v2/flights/airport/{airportCode}/airline/{airlineCode}/direction/{direction}

Path parameters
Request parameters
Request headers
Response fields
Curl request
HTTP response

Retrieve all flights arriving to or departing from a specified airport for a given airline. Results are filtered by operation date (default is current UTC date).
Payload elements are filtered based on permissions associated with the 'x-apikey' used in the request.

operationDate

If the operation date is not provided the search is based on the current UTC date/time. The search window will be current UTC date/time → current UTC date/time + 4 hours (futureWindow default value).
The user can adjust the search window by providing values for the pastWindow/futureWindow in their request.

If the operation date is provided the search window will be operationDate (00:00:00) → operationDate + 4 hours (futureWindow default value) e.g. 2021-01-12 00:00:00 → 2021-01-12 04:00:00.

In this scenario the operationDate is considered to be the local date/datetime on which the flight departed/arrived.
The user can adjust the search window by providing values for the pastWindow/futureWindow in their request.

operationDate & searchByUTC

A user can force the operationDate value to be considered as UTC by providing the parameter 'searchByUTC=true'. By doing so the user has the ability to search for flights in the past/future based on UTC date/time.

Path parameters

/flightinfo/v2/flights/airport/{airportCode}/airline/{airlineCode}/direction/{direction}
Parameter	Description
`airportCode`	3-character airport IATA code or 4-character airport ICAO code
`airlineCode`	2-character airline IATA code or 3-character airline ICAO code
`direction`	1-character direction indicator (A/D)

Request parameters

Parameter	Optional	Description
operationDate	true	Local date/datetime of operation (yyyy-MM-dd or yyyy-MM-ddTHH:mm:ss). Default value is current UTC date
pastWindow	true	Hours in past to return. Default value is 0
futureWindow	true	Hours in future to return. Default value is 4
searchByUTC	true	Search based by UTC. Default value is false
showCargo	true	Include cargo flights. Default value is false
groupMarketingCarriers	true	Group marketing and operating carrier flights into a single record. Default value is false
departureOrArrivalAirport	true	Filter results based on origin or destination airport
view	true	View 'full' or 'local' leg, based on direction. Default value is local. See notes for further details.

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
X-apiKey	false	Authorization header that contains the API key.

Response fields

Refer to Response Fields table.

Curl request

            $ curl 'https://flifo.api.aero/flifo/flightinfo/v2/flights/airport/AMS/airline/KL/direction/A?operationDate=2020-01-22T12:00:00' -i -X GET \
                -H 'Content-Type: application/json' \
                -H 'X-apiKey: ff228ab88758a84637f1f88d86899365'

HTTP response

            View sample response here.

Start of Section

3.1.3 GET Flights by Airport and Direction

GET /flightinfo/v2/flights/airport/{airportCode}/direction/{direction}

Path parameters
Request parameters
Request headers
Response fields
Curl request
HTTP response

Retrieve all flights arriving to or departing from a specific airport. Results are filtered by operation date (default is current UTC date).
Payload elements are filtered based on permissions associated with the 'x-apikey' used in the request.

operationDate

If the operation date is provided the search window will be operationDate (00:00:00) → operationDate + 4 hours (futureWindow default value) e.g. 2021-01-12 00:00:00 → 2021-01-12 04:00:00.

operationDate & searchByUTC

Path parameters

/flightinfo/v2/flights/airport/{airportCode}/direction/{direction}
Parameter	Description
`airportCode`	3-character airport IATA code or 4-character airport ICAO code
`direction`	1-character direction indicator (A/D)

Request parameters

Parameter	Optional	Description
operationDate	true	Local date/datetime of operation (yyyy-MM-dd or yyyy-MM-ddTHH:mm:ss). Default value is current UTC date
pastWindow	true	Hours in past to return. Default value is 0
futureWindow	true	Hours in future to return. Default value is 4
searchByUTC	true	Search based by UTC. Default value is false
showCargo	true	Include cargo flights. Default value is false
groupMarketingCarriers	true	Group marketing and operating carrier flights into a single record. Default value is false
departureOrArrivalAirport	true	Filter results based on origin or destination airport
view	true	View 'full' or 'local' leg, based on direction. Default value is local. See notes for further details.

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
X-apiKey	false	Authorization header that contains the API key.

Response fields

Refer to Response Fields table.

Curl request

            $ curl 'https://flifo.api.aero/flifo/flightinfo/v2/flights/airport/AMS/direction/A?operationDate=2020-01-22T12:00:00' -i -X GET \
                -H 'Content-Type: application/json' \
                -H 'X-apiKey: ff228ab88758a84637f1f88d86899365'

HTTP response

            View sample response here.

Start of Section

3.1.4 GET Flight Updates by Airport, Airline and Flight Number

GET /flightinfo/v2/flights/updates/airport/{airportCode}/airline/{airlineCode}/flightNumber/{flightNumber}

Path parameters
Request parameters
Request headers
Response fields
Curl request
HTTP response

Retrieve a single flight and its updates based on airline, flight number and arrival/departure airport. Results are filtered by operation date (default is current UTC date).
Payload elements are filtered based on permissions associated with the 'x-apikey' used in the request.

operationDate

In this scenario the operationDate is considered to be the local date on which the flight departed/arrived.

operationDate & searchByUTC

A user can force the operationDate value to be considered as UTC by providing the parameter 'searchByUTC=true'.

Path parameters

/flightinfo/v2/flights/updates/airport/{airportCode}/airline/{airlineCode}/flightNumber/{flightNumber}
Parameter	Description
`airportCode`	3-character airport IATA code or 4-character airport ICAO code
`airlineCode`	2-character airline IATA code or 3-character airline ICAO code
`flightNumber`	Flight number

Request parameters

Parameter	Optional	Description
operationDate	true	Local date of operation (yyyy-MM-dd). Default value is current UTC date
from	true	Date interval start e.g. 2020-01-01T12:00:00-0000. Default is current UTC date/time - 2 minutes
to	true	Date interval end e.g. 2020-01-01T12:05:00-0000. Default is current UTC date/time - 1 minutes
includeUpdates	true	Show updated fields
groupMarketingCarriers	true	Group marketing and operating carrier flights into a single record. Default value is false
groupRecords	true	Group updates in a single record
verbose	true	Show additional information such as version
showCargo	true	Include cargo flights. Default value is false

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
X-apiKey	false	Authorization header that contains the API key.

Response fields

Refer to Response Fields table.

Curl request

            $ curl 'https://flifo.api.aero/flifo/flightinfo/v2/flights/updates/airport/AMS/airline/KL/flightNumber/1394?from=2020-01-22T12:00:00.000Z&to=2020-01-22T13:00:00.000Z' -i -X GET \
                -H 'Content-Type: application/json' \
                -H 'X-apiKey: ff228ab88758a84637f1f88d86899365'

HTTP response

            View sample response here.

Start of Section

3.1.5 GET Flight Updates by Airport and Airline

GET /flightinfo/v2/flights/updates/airport/{airportCode}/airline/{airlineCode}

Path parameters
Request parameters
Request headers
Response fields
Curl request
HTTP response

Retrieve all updates created within the from/to search window for flights arriving to or departing from an airport, operated or marketed by the provided airline.
Payload elements are filtered based on permissions associated with the 'x-apikey' used in the request.

Path parameters

/flightinfo/v2/flights/updates/airport/{airportCode}/airline/{airlineCode}
Parameter	Description
`airportCode`	3-character airport IATA code or 4-character airport ICAO code
`airlineCode`	2-character airline IATA code or 3-character airline ICAO code

Request parameters

Parameter	Optional	Description
from	true	Date interval start e.g. 2020-01-01T12:00:00-0000. Default is current UTC date/time - 2 minutes
to	true	Date interval end e.g. 2020-01-01T12:05:00-0000. Default is current UTC date/time - 1 minutes
includeUpdates	true	Show updated fields
groupMarketingCarriers	true	Group marketing and operating carrier flights into a single record. Default value is false
groupRecords	true	Group updates in a single record
verbose	true	Show additional information such as version
showCargo	true	Include cargo flights. Default value is false
arrivalDeparture	true	1-character direction indicator (A/D)

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
X-apiKey	false	Authorization header that contains the API key.

Response fields

Refer to Response Fields table.

Curl request

            $ curl 'https://flifo.api.aero/flifo/flightinfo/v2/flights/updates/airport/AMS/airline/KL?from=2020-01-22T12:00:00.000Z&to=2020-01-22T13:00:00.000Z' -i -X GET \
                -H 'Content-Type: application/json' \
                -H 'X-apiKey: ff228ab88758a84637f1f88d86899365'

HTTP response

            View sample response here.

Start of Section

3.1.6 GET Flight Updates by Airport

GET /flightinfo/v2/flights/updates/airport/{airportCode}

Path parameters
Request parameters
Request headers
Response fields
Curl request
HTTP response

Retrieve all updates created within the from/to search window for flights arriving to or departing from an airport.
Payload elements are filtered based on permissions associated with the 'x-apikey' used in the request.

Path parameters

/flightinfo/v2/flights/updates/airport/{airportCode}
Parameter	Description
`airportCode`	3-character airport IATA code or 4-character airport ICAO code

Request parameters

Parameter	Optional	Description
from	true	Date interval start e.g. 2020-01-01T12:00:00-0000. Default is current UTC date/time - 2 minutes
to	true	Date interval end e.g. 2020-01-01T12:05:00-0000. Default is current UTC date/time - 1 minutes
includeUpdates	true	Show updated fields
groupMarketingCarriers	true	Group marketing and operating carrier flights into a single record. Default value is false
groupRecords	true	Group updates in a single record
verbose	true	Show additional information such as version
showCargo	true	Include cargo flights. Default value is false
arrivalDeparture	true	1-character direction indicator (A/D)

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
X-apiKey	false	Authorization header that contains the API key.

Response fields

Refer to Response Fields table.

Curl request

            $ curl 'https://flifo.api.aero/flifo/flightinfo/v2/flights/updates/airport/AMS?from=2020-01-22T12:00:00.000Z&to=2020-01-22T13:00:00.000Z' -i -X GET \
                -H 'Content-Type: application/json' \
                -H 'X-apiKey: ff228ab88758a84637f1f88d86899365'

HTTP response

            View sample response here.

Start of Section

3.1.7 GET Flight Updates

GET /flightinfo/v2/flights/updates

Request parameters
Request headers
Response fields
Curl request
HTTP response

Retrieve all updates created within the from/to search window.
Payload elements are filtered based on permissions associated with the 'x-apikey' used in the request.

Request parameters

Parameter	Optional	Description
from	true	Date interval start e.g. 2020-01-01T12:00:00-0000. Default is current UTC date/time - 2 minutes
to	true	Date interval end e.g. 2020-01-01T12:05:00-0000. Default is current UTC date/time - 1 minutes
includeUpdates	true	Show updated fields
groupMarketingCarriers	true	Group marketing and operating carrier flights into a single record. Default value is false
groupRecords	true	Group updates in a single record
verbose	true	Show additional information such as version
showCargo	true	Include cargo flights. Default value is false

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
X-apiKey	false	Authorization header that contains the API key.

Response fields

Refer to Response Fields table.

Curl request

            $ curl 'https://flifo.api.aero/flifo/flightinfo/v2/flights/updates?from=2020-01-22T12:00:00.000Z&to=2020-01-22T13:00:00.000Z' -i -X GET \
                -H 'Content-Type: application/json' \
                -H 'X-apiKey: ff228ab88758a84637f1f88d86899365'

HTTP response

            View sample response here.

Start of Section

3.2 Notes

3.2.1 'view' parameter

'view' parameter

The 'view' query parameter can have the value 'local' or 'full' (default value is 'local').
The purpose of this parameter is to enable the user to decide if they wish to see just the 'local' view of the flight (e.g. only the
departure details if 'direction' parameter provided was 'D') or the 'full' view which will return both departure and arrival details for the flight(s) if 'direction' parameter provided was 'D'.

flifo/flightinfo/v2/flights/airport/JFK/airline/B6/direction/D?view=#local# flifo/flightinfo/v2/flights/airport/JFK/airline/B6/direction/D?view=#full#

Table 1. 'view' parameter response payload formats
flifo/flightinfo/v2/flights/airport/JFK/airline/B6/direction/D?view=#local#	flifo/flightinfo/v2/flights/airport/JFK/airline/B6/direction/D?view=#full#
`{ "flightRecords": [ { "flightIdentifier": { "operatingCarrier": { "iataCode": "B6", "flightNumber": "209", "name": "JetBlue Airways" }, "aircraft": { "iataCode": "A321", "registration": "N959JB" } }, "departure": { "airport": { "iataCode": "JFK", "cityText": "New York" }, "scheduled": "2021-01-19T05:01:00-05:00", "estimated": "2021-01-19T05:01:00-05:00", "status": "SC", "statusText": "Scheduled", "terminal": "5", "gate": "21" }, "serviceType": "J", "duration": "208" } ] }`	{ "flightRecords": [ { "flightIdentifier": { "operatingCarrier": { "iataCode": "B6", "flightNumber": "209", "name": "JetBlue Airways" }, "aircraft": { "iataCode": "A321", "registration": "N959JB" } }, "departure": { "airport": { "iataCode": "JFK", "cityText": "New York" }, "scheduled": "2021-01-19T05:01:00-05:00", "estimated": "2021-01-19T05:01:00-05:00", "status": "SC", "statusText": "Scheduled", "terminal": "5", "gate": "21" }, "arrival": { "airport": { "iataCode": "SDQ", "cityText": "Santo Domingo" }, "scheduled": "2021-01-19T09:29:00-04:00", "estimated": "2021-01-19T09:47:00-04:00", "status": "SC", "statusText": "Scheduled", "gate": "B4" }, "serviceType": "J", "duration": "208" } ] }

            {
              "flightRecords": [
                {
                  "flightIdentifier": {
                    "operatingCarrier": {
                      "iataCode": "B6",
                      "flightNumber": "209",
                      "name": "JetBlue Airways"
                    },
                    "aircraft": {
                      "iataCode": "A321",
                      "registration": "N959JB"
                    }
                  },
                  "departure": {
                    "airport": {
                      "iataCode": "JFK",
                      "cityText": "New York"
                    },
                    "scheduled": "2021-01-19T05:01:00-05:00",
                    "estimated": "2021-01-19T05:01:00-05:00",
                    "status": "SC",
                    "statusText": "Scheduled",
                    "terminal": "5",
                    "gate": "21"
                  },
                  "serviceType": "J",
                  "duration": "208"
                }
              ]
            }

            {
              "flightRecords": [
                {
                  "flightIdentifier": {
                    "operatingCarrier": {
                      "iataCode": "B6",
                      "flightNumber": "209",
                      "name": "JetBlue Airways"
                    },
                    "aircraft": {
                      "iataCode": "A321",
                      "registration": "N959JB"
                    }
                  },
                  "departure": {
                    "airport": {
                      "iataCode": "JFK",
                      "cityText": "New York"
                    },
                    "scheduled": "2021-01-19T05:01:00-05:00",
                    "estimated": "2021-01-19T05:01:00-05:00",
                    "status": "SC",
                    "statusText": "Scheduled",
                    "terminal": "5",
                    "gate": "21"
                  },
                  "arrival": {
                    "airport": {
                      "iataCode": "SDQ",
                      "cityText": "Santo Domingo"
                    },
                    "scheduled": "2021-01-19T09:29:00-04:00",
                    "estimated": "2021-01-19T09:47:00-04:00",
                    "status": "SC",
                    "statusText": "Scheduled",
                    "gate": "B4"
                  },
                  "serviceType": "J",
                  "duration": "208"
                }
              ]
            }

Top of Page

4 SeamlessTravel/ACRIS API

4.1 Introduction

The SeamlessTravel resources provides users with the ability to search for flights based on a) airport and direction or b) individual flight details.

Response payloads conform to the ACRIS SeamlessTravel specification. More details can be found at https://acris.aero/.

4.2 Resources

This section describes the SeamlessTravel/ACRIS API service.
Detailed API structure, example requests and responses, JSON schema for request (where appropriate) and responses, and error response codes and formats are included.

4.2.1 GET Flight by Airline, Flight Number, Operation Date, Departure Airport and Arrival Airport
4.2.2 GET Flights by Airport and Direction

4.2.1 GET Flight by Airline, Flight Number, Operation Date, Departure Airport and Arrival Airport

GET /aci-v1/flightDetails/{airlineCode}/{flightNumber}/{operationDate}/{departureAirportCode}/{arrivalAirportCode}

Path parameters
Request parameters
Request headers
Response fields
Curl request
HTTP response

Path parameters

/aci-v1/flightDetails/{airlineCode}/{flightNumber}/{operationDate}/{departureAirportCode}/{arrivalAirportCode}
Parameter	Description
`airlineCode`	2-character airline IATA code or 3-character airline ICAO code
`flightNumber`	Flight number
`operationDate`	Local date of operation (yyyy-MM-dd)
`departureAirportCode`	3-character airport IATA code or 4-character airport ICAO code
`arrivalAirportCode`	3-character airport IATA code or 4-character airport ICAO code

Request parameters

Parameter	Optional	Description
suffix	true	Flight suffix (4A, 123B)

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
X-apiKey	false	Authorization header that contains the API key.

Response fields

Refer to Response Fields table.

Curl request

            $ curl 'https://flifo.api.aero/flifo/aci-v1/flightDetails/KL/1394/2020-01-22/LED/AMS' -i -X GET \
                -H 'Content-Type: application/json' \
                -H 'X-apiKey: ff228ab88758a84637f1f88d86899365'

HTTP response

            View sample response here.

Start of Section

4.2.2 GET Flights by Airport and Direction

GET /aci-v1/flight/{airportCode}/{direction}

Path parameters
Request parameters
Request headers
Response fields
Curl request
HTTP response

Path parameters

/aci-v1/flight/{airportCode}/{direction}
Parameter	Description
`airportCode`	3-character airport IATA code or 4-character airport ICAO code
`direction`	Direction field (arrival/departure)

Request parameters

Parameter	Optional	Description
length	true	Length
offset	true	Offset
timeRange	true	Time range in hours
startTime	true	Start time

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
X-apiKey	false	Authorization header that contains the API key.

Response fields

Refer to Response Fields table.

Curl request

            $ curl 'https://flifo.api.aero/flifo/aci-v1/flight/AMS/arrival' -i -X GET \
                -H 'Content-Type: application/json' \
                -H 'X-apiKey: ff228ab88758a84637f1f88d86899365'

HTTP response

                    View sample response here.

Start of Section

5 Error Response

Response fields

Path	Type	Description
`errors`	`Object`	Object that holds the error information
`errors.error[].description`	`String`	Error Description
`errors.error[]`	`Array`	Array of errors
`errors.error[].invalidParam`	`String`	Indicates the invalid query parameter
`errors.error[].code`	`Number`	API Internal Error Code

HTTP response

                HTTP/1.1 400 Bad Request
                Content-Type: application/json
                Content-Length: 159
                
                {
                  "errors" : {
                    "error" : [ {
                      "description" : "Error Description",
                      "code" : 9999,
                      "invalidParam" : "parameterName"
                    } ]
                  }
                }

Appendix A - Status Codes

Code	Description
AD	Arrived-Diverted
AP	Approach
AR	Arrived
AT	See Agent
BC	Boarding Complete
BD	Boarding
BO	Boarded
CD	Baggage Delay
CO	Closed
CL	Closed
CX	Cancelled
DE	Deleted
DL	Delayed
DP	Departed
DV	Diverted
EN	Enroute
EX	Expected
FB	First Bag Unloaded
FC	Final Call
GC	Gate Closed
GG	Go To Gate
GT	Gate Time (Gate Time HH:MM can be found in gateInfo field)
IA	In Air
ID	In Air-Diverted
IR	In Range
LB	Last Bag Unloaded
LD	Landed-Diverted
LN	Landed
LR	Landed-Recovered
OG	Landed (On Ground)
ON	On Time
TX	Taxiing
PD	Possible Delay
RA	Arrived-Recovered
RE	In Air-Recovered
RG	Return To Gate
SC	Scheduled
UN	Unknown
VN	TEST
WX	Weather

Start of Appendix

Appendix B - Flight Status Use Cases

A selection of Use cases for SITA Flight Status API can be viewed here. Sample use cases include:

Appendix C - Diverted Flights

A diverted flight is a flight that has been re-routed from its original arrival destination to a new arrival destination.

Flight diversions are unforeseen events which can be caused by factors such as:

Aircraft emergency
Passenger emergency
Mechanical failure
Poor weather conditions

A recovery flight is a flight that is created to route the aircraft/passengers from the diversion airport to their original arrival destination.

When the Flight Status API service has been notified that a flight has been diverted, a 'diversion' element is added to the departure flight record.
The diversion element contains a 'recovery' element which contains details of the airport wherethe flight has been diverted and also details of the recovery flight if/when it has been confirmed.

Diverted flight scenario

Original flight route was DEL → YYZ.
Flight was diverted after departure and now has routing of DEL → YUL → YYZ.
Departure flight record will be updated with details of the diversion/recovery flight.
The system will now contain two arrival records for AC43 at YYZ, one for the original scheduled arrival flight DEL → YYZ.
The other will be for the 'recovery' flight YUL → YYZ.

AC43 DEL → YYZ flight search

/flifo/flightinfo/v2/flights/airline/AC/flightNumber/43?operationDate=2022-05-11&view=full

            {
                "flightRecords": [
                    {
                        "flightIdentifier": {
                            "operatingCarrier": {
                                "iataCode": "AC",
                                "icaoCode": "ACA",
                                "flightNumber": "43",
                                "name": "Air Canada"
                            },
                            "marketingCarriers": [
                                {
                                    "iataCode": "UA",
                                    "icaoCode": "UAL",
                                    "flightNumber": "8653",
                                    "name": "United Airlines"
                                }
                            ]
                        },
                        "departure": {
                            "airport": {
                                "iataCode": "YUL",
                                "icaoCode": "CYUL",
                                "cityText": "Montreal"
                            },
                            "scheduled": "2022-05-10T12:35:00-04:00",
                            "actual": "2022-05-10T22:13:00-04:00",
                            "status": "DV",
                            "statusText": "Diverted",
                            "diversion": {
                                "original": {
                                    "airport": {
                                        "iataCode": "DEL",
                                        "icaoCode": "VIDP",
                                        "cityText": "Delhi"
                                    },
                                    "flightNumber": "8653",
                                    "iataCode": "UA",
                                    "icaoCode": "UAL",
                                    "name": "United Airlines",
                                    "scheduled": "2022-05-10T12:35:00-04:00"
                                }
                            }
                        },
                        "arrival": {
                            "airport": {
                                "iataCode": "YYZ",
                                "icaoCode": "CYYZ",
                                "cityText": "Toronto"
                            },
                            "scheduled": "2022-05-11T05:40:00-04:00",
                            "estimated": "2022-05-11T06:25:00-04:00",
                            "status": "DV",
                            "statusText": "Diverted",
                            "diversion": {
                                "original": {
                                    "airport": {
                                        "iataCode": "DEL",
                                        "icaoCode": "VIDP",
                                        "cityText": "Delhi"
                                    },
                                    "flightNumber": "8653",
                                    "iataCode": "UA",
                                    "icaoCode": "UAL",
                                    "name": "United Airlines",
                                    "scheduled": "2022-05-11T05:40:00-04:00"
                                }
                            }
                        },
                        "serviceType": "J",
                        "duration": "1025"
                    },
                    {
                        "flightIdentifier": {
                            "operatingCarrier": {
                                "iataCode": "AC",
                                "flightNumber": "43",
                                "name": "Air Canada"
                            },
                            "marketingCarriers": [
                                {
                                    "iataCode": "UA",
                                    "flightNumber": "8653",
                                    "name": "United Airlines"
                                }
                            ],
                            "aircraft": {
                                "iataCode": "77L",
                                "model": "Boeing 777-200LR",
                                "registration": "CFNND"
                            }
                        },
                        "departure": {
                            "airport": {
                                "iataCode": "DEL",
                                "cityText": "New Delhi"
                            },
                            "scheduled": "2022-05-10T22:05:00+05:30",
                            "estimated": "2022-05-10T23:14:00+05:30",
                            "actual": "2022-05-10T23:18:00+05:30",
                            "status": "ID",
                            "statusText": "In Air-Diverted",
                            "terminal": "3",
                            "gate": "9",
                            "diversion": {
                                "recovery": {
                                    "airport": {
                                        "iataCode": "YUL",
                                        "icaoCode": "CYUL",
                                        "cityText": "Montreal"
                                    },
                                    "flightNumber": "8653",
                                    "iataCode": "UA",
                                    "icaoCode": "UAL",
                                    "name": "United Airlines",
                                    "scheduled": "2022-05-10T12:35:00-04:00"
                                }
                            }
                        },
                        "arrival": {
                            "airport": {
                                "iataCode": "YYZ",
                                "cityText": "Toronto"
                            },
                            "scheduled": "2022-05-11T05:40:00-04:00",
                            "estimated": "2022-05-11T06:36:00-04:00",
                            "status": "ID",
                            "statusText": "In Air-Diverted",
                            "terminal": "T1",
                            "gate": "E71",
                            "diversion": {
                                "recovery": {
                                    "airport": {
                                        "iataCode": "YUL",
                                        "icaoCode": "CYUL",
                                        "cityText": "Montreal"
                                    },
                                    "flightNumber": "8653",
                                    "iataCode": "UA",
                                    "icaoCode": "UAL",
                                    "name": "United Airlines",
                                    "scheduled": "2022-05-11T05:40:00-04:00"
                                }
                            }
                        },
                        "serviceType": "J",
                        "duration": "1025"
                    }
                ]
            }

Linking diverted flights

The json on the left in the below example shows flight AC43 DEL → YYZ has been diverted. Both the departure and arrival details for this flight have been updated to contain a 'diversion.recovery' element.
The recovery element provides details of the recovery flight which has been created for this flight.

The json on the right in the below example shows flight AC43 YUL → YYZ which has been created as the recovery flight for AC43 DEL → YYZ.
Both the departure and arrival details for this flight have been updated to contain a 'diversion.original' element.
The original element provides details of the original flight which this flight is related to.

Start of Appendix

Top of Page

Last updated 2022-05-17 09:32:14 +0100

SITA Flight Status API Service

About us

Contact