Flight Data (1.0.0)

Download OpenAPI specification:Download

Introduction

The Flight Data APIs, part of the Laminar Data Hub provides current flight information and positional information for flight by airline, airport, flight information region (FIR), or tile.

Licensing

The Flight Data APIs currently require a contract to use.

Schemas

Click the download button at the top of this document to download the OpenApi spec for this API.

Related products

Flight Status (FlightStats APIs) - Current flight information for flights about three days in advance of departure until about seven days after arrival

Flight Track (FlightStats APIs) - Current positional information on an active flight, including position (lat/long), altitude, bearing, speed and route

Historical Flight Status (FlightStats APIs) - Status for flights back to 2006

Flights By Airline

Flights by airline

Retrieves a list of flight summaries for a given airline using an extended version of FIXM 3.0, including scheduled and airborne flights.

Summaries include:

  • Departure and arrival aerodromes
  • Departure and arrival times (estimated and/or actual)
  • Positional information (including heading and altitude)
  • GUFI (Globally Unique Flight Identifier)

Your query must be defined using one of the optional Flight Status parameters listed below to return detail on flights that are not currently active.

The optional flight status parameter allows you to filter flights according to whether they are airborne, cancelled, completed, filed or scheduled.

path Parameters
airline.prefix
required
string

The ICAO prefix for an airline e.g. BAW (Case sensitive)

query Parameters
user_key
required
string

User Key Authentication Parameter

status
string

(optional) Flight Status (AIRBORNE, CANCELLED, COMPLETED, FILED or SCHEDULED) Case Sensitive

Responses

Flights By Airline and Flight Number

Flights by flight number

Retrieves a list of flight summaries for a given airline with a given flight number, including scheduled and airborne flights.

Summaries include:

  • Departure and arrival aerodromes
  • Departure and arrival times (estimated and/or actual)
  • Positional information (including heading and altitude)
  • GUFI (Globally Unique Flight Identifier)

The optional flight status parameter allows you to filter flights according to whether they are airborne, cancelled, completed, filed or scheduled.

path Parameters
airline.prefix
required
string

The ICAO prefix for an airline e.g. BAW (Case sensitive)

flight.number
required
string

The ICAO number of the flight e.g. 039 (ignores any leading zero)

query Parameters
user_key
required
string

User Key Authentication Parameter

status
string

(optional) Flight Status (AIRBORNE, CANCELLED, COMPLETED, FILED or SCHEDULED) Case Sensitive

Responses

Flight Detail By GUFI

Flights by GUFI

Retrieves the most complete picture of a single flight, available in both GeoJSON and an extended version of FIXM 3.0.

Completed flights will remain accessible in the API for 6 hours after the flight has landed.

Note that the example GUFI below will not work; you will need a current one from one of the other API calls (e.g. Flights by Airline).

Flights by GUFI includes:

  • Departure and arrival aerodromes
  • Departure and arrival times (estimated and/or actual)
  • Positional information (including heading, altitude and speed)

To request GeoJSON use the HTTP header "Accept : application/json" using the "Accepts" dropdown or add the query string "format=json" to the request URL

Note that full representation of the data model (including units of measure) can be found in the schema repository on GitHub

path Parameters
gufi
required
string

GUFI of the flight to look up e.g. 761b728a-9a50-4222-8325-8be4a1574241

query Parameters
user_key
required
string

User Key Authentication Parameter

Responses

Response samples

Content type
"string"

Flight Delay by GUFI

Flight delay (XML and GeoJSON response)

Retrieves the delay for a single flight. Available in both JSON and XML. Completed flights will remain accessible in the API for 6 hours after the flight has landed. Note that the example GUFI below will not work; you will need a current one from one of the other API calls (e.g.Flights by Airline).

Flights Delay includes:

  • Initial Delay - The first delay placed on this flight, Delay in minutes, Regulations causing the delay
  • Latest Delay - the latest delay placed on this flight, Delay in minutes, Regulations causing the delay
  • Flight Properties - Callsign, Iata Flight Number, Carrier

Please note that this API currently only returns delay data for flights operating in European airspace. Queries on other flights will receive a response, but the accuracy of the content is not guaranteed.

The Flight Delay API has a GeoJSON response option available. To request GeoJSON use the HTTP header "Accept : application/json" using the "Accepts" dropdown or add the query string "format=json" to the request URL.

Note that full representation of the data model (including units of measure) can be found in the schema repository on GitHub.

path Parameters
gufi
required
string

GUFI of the flight to look up e.g. 761b728a-9a50-4222-8325-8be4a1574241

query Parameters
user_key
required
string

User Key Authentication Parameter

Responses

Response samples

Content type
"string"

Flights By Aerodrome Pair

Flights by aerodrome pair

Retrieves a list of flight summaries between a pair of aerodromes using an extended version of FIXM 3.0, including scheduled and airborne flights.

Summaries include:

  • Departure and arrival aerodromes
  • Departure and arrival times (estimated and/or actual)
  • Positional information (including heading and altitude)
  • GUFI (Globally Unique Flight Identifier)

Your query must be defined using one of the optional Flight Status parameters listed below to return detail on flights that are not currently active.

The optional flight status parameter allows you to filter flights according to whether they are airborne, cancelled, completed, filed or scheduled.

path Parameters
origin.icao
required
string

The ICAO code for an aerodrome of origin e.g. EGLL (Case sensitive)

destination.icao
required
string

The ICAO code for an aerodrome destination e.g. KJFK (Case sensitive)

query Parameters
user_key
required
string

User Key Authentication Parameter

status
string

(optional) Flight Status (AIRBORNE, CANCELLED, FILED or SCHEDULED) Case Sensitive

Responses

Flight arrivals by aerodrome

Flight arrivals by aerodrome

Retrieves summary information for flights arriving or that are scheduled to arrive at the given aerodrome using an extended version of FIXM 3.0, including scheduled and airborne flights.

Summary information includes:

  • Departure and arrival aerodromes
  • Departure and arrival times (estimated and/or actual)
  • Positional information (including heading and altitude)
  • GUFI (Globally Unique Flight Identifier)
  • Callsign
  • Flight Number
  • Flight Status
  • Flight Plan Timestamp the time when a flight plan property was last updated. (Only present for flights that are not in the SCHEDULED status)

Your query must be defined using one of the optional Flight Status parameters listed below to return detail on flights that are not currently active.

The optional flight status parameter allows you to filter flights according to whether they are airborne, cancelled, completed, filed or scheduled.

To request GeoJSON use the HTTP header "Accept : application/json" using the "Accepts" dropdown or add the query string "format=json" to the request URL.

Note that full representation of the data model (including units of measure) can be found in the schema repository on GitHub

path Parameters
aerodrome.icao
required
string

The ICAO code for an aerodrome to see arrivals for e.g. EGLL (Case sensitive)

query Parameters
user_key
required
string

User Key Authentication Parameter

status
string

(optional) Flight Status (AIRBORNE, CANCELLED, COMPLETED, FILED or SCHEDULED) Case Sensitive

Responses

Response samples

Content type
"string"

Flight Data FIR Load

Flight data FIR load

Retrieves flights within a given FIR. This GeoJSON API, available via RESTful or streaming interfaces.

Contains the following European flight data:

  • Estimated FIR entry time (flights scheduled to enter the chosen FIR)
  • Actual FIR entry timestamp (airborne flights currently in the FIR / flights that have already passed through theFIR)
  • Positional reports (for airborne flights)

Response can be filtered by any one of the following status parameters:

  • airborne
  • cancelled
  • completed
  • scheduled
  • planned
path Parameters
icao.prefix
required
string

First letter of the ICAO designator e.g. E (Case sensitive)

fir.icao
required
string

ICAO code of the FIR e.g. EGTT (Case sensitive)

query Parameters
status
string

(optional) Flight Status (AIRBORNE, CANCELLED, COMPLETED, FILED or SCHEDULED) Case Sensitive

user_key
required
string

User Key Authentication Parameter

Responses

Flight Departures By Aerodrome

Flight departures by aerodrome

Retrieves summary information for flights departing or that are scheduled to depart from the given aerodrome using an extended version of FIXM 3.0, including scheduled and airborne flights.

Summary information includes:

  • Departure and arrival aerodromes
  • Departure and arrival times (estimated and/or actual)
  • Positional information (including heading and altitude)
  • GUFI (Globally Unique Flight Identifier)
  • Callsign
  • Flight Number
  • Flight Status
  • Flight Plan Timestamp - the time when a flight plan property was last updated (only present for flights that are not in the SCHEDULED status).

Your query must be defined using one of the optional Flight Status parameters listed below to return detail on flights that are not currently active.

The optional flight status parameter allows you to filter flights according to whether they are airborne, cancelled, completed, filed or scheduled.

To request GeoJSON use the HTTP header "Accept : application/json" using the "Accepts" dropdown or add the query string "format=json" to the request URL

Note that full representation of the data model (including units of measure) can be found in the schema repository on GitHub

path Parameters
aerodrome.icao
required
string

The ICAO code for an aerodrome to see departures for e.g. EGLL (Case sensitive)

query Parameters
user_key
required
string

User Key Authentication Parameter

status
string

(optional) Flight Status (AIRBORNE, CANCELLED, COMPLETED, FILED or SCHEDULED) Case Sensitive

Responses

Response samples

Content type
"string"

Expanded Route

Expanded route

Expands the provided route text information into a list of detailed waypoints.

Each waypoint in the response includes the following information:

  • coordinates (longitude and latitude)
  • designator name of the waypoint
  • resolved fix
  • elevation
  • elevation unit of measurement

If you have the route text in its ICAO 4444 format then populate the 'routeText' field. If the ICAO 4444 format of the route text does not include the departure and destination aerodromes, you may also optionally specify origin and destination fields containing the location indicators for the aerodromes.

If the first fix in the route is known to be a duplicate fix name, you can specify an optional reference fix which will be used to select the fix which is closest to this geographic point of reference. Reference fixes may be literal fixes, fix radials or regular fixes.

If the first fix in the route is known to be a duplicate fix name, but no reference fix is provided, then no point will be selected for the first fix.

PLEASE NOTE: The 'Accept' header of the request must be 'application/geo+json'

query Parameters
user_key
required
string

User Key Authentication Parameter

Request Body schema: application/json

JSON request body

routeText
required
string

The route text of the flight in it's native format (ICAO 4444)

origin
required
string

Location indicator for the departure aerodrome, MUST be the ICAO code

destination
required
string

Location indicator for the arrival aerodrome, MUST be the ICAO code

referenceFix
required
string

If the first fix in the route is known to be a duplicate fix name, you can specify an optional reference fix which will be used to select the fix which is closest to this geographic point of reference. Reference fixes may be literal fixes, fix radials or regular fixes.

Responses

Request samples

Content type
application/json
{
  • "routeText": "KRDU./.ORF342018..SIE.CAMRN4.KJFK/1532",
  • "origin": "KRDU",
  • "destination": "KJFK",
  • "referenceFix": "SOVED"
}

Response samples

Content type
application/geo+json
{
  • "type": "FeatureCollection",
  • "features": [
    ],
  • "results": {
    }
}
)