• Register

Crew Check-In Times

Summary

Crew check-in report contains time events relevant for the crew check-in.

Request

Code snippet: URL

GET /v1/flight_operations/crew_services/COMMON_CHECK_IN_TIMES

Parameters

Name Type Description Required Schema / Format
flightDesignator Query

IATA flight designator consists of airline code, flight number and suffix (optional).

The flight number must consist of at least 3 digits, zero-padded for numbers less than 100, e.g. LH001, LH023, LH100, LH1376.

 yes

xsd:string

([0-9][A-Z]|[A-Z][0-9]|[A-Z]{2})([0-9]{3,4})([A-Z]?)
flightDate Query Flight date of operation, date of first leg of a flight in UTC. yes

xsd:date

[0-9]{4}[-][0-9]{2}[-][0-9]{2}Z

YYYY-MM-DDZ
departureAirport Query Departure airport IATA code. yes

xsd:string

[A-Z]{3}
arrivalAirport Query

Arrival airport IATA code.

 yes

xsd:string

[A-Z]{3}
dutyType Query

Duty type, like on-duty or dead head.

 yes

xsd:string

Possible values:

  • "OD" for on-duty
  • "DH" for dead head
crewCategory Query

Crew category: cockpit or cabin.

 yes

xsd:string

Possible values:

  • "COC" for cockpit
  • "CAB" for cabin
RN Query Rotation Number no

xsd:string

[0-9]{1,6}
nextFlightDesignator Query

IATA flight designator consists of airline code, flight number and suffix (optional).

If duty type is DH the next on duty flight can be specified to retrieve the briefing room of this flight.

 Required if dutyType is "DH"

xsd:string

([0-9][A-Z]|[A-Z][0-9]|[A-Z]{2})([0-9]{3,4})([A-Z]?)
nextFlightDate Query Flight date of operation of the queried next flight, date of first leg of a flight in UTC. Required if dutyType is "DH"

xsd:date

[0-9]{4}[-][0-9]{2}[-][0-9]{2}Z

YYYY-MM-DDZ
nextArrivalAirport Query

Arrival airport IATA code of the queried next flight.

 Required if dutyType is "DH"

xsd:string

[A-Z]{3}

Responses

Code Description Content-Type Schema
200 Crew check-in information has been generated as requested. application/json → Crew Check-In Times Model
404 The requested flight has not been found or outside the supported time window (+-6 day from now). application/json → Processing Errors Model
409 Validation of request parameters failed application/json → Processing Errors Model
500 Any other error application/json → Processing Errors Model

Crew Check-In Times

Code snippet: Payload

{
  "flightDesignator" → xsd:string
  "flightDate" → xsd:date
  "departureAirport" → xsd:string
  "arrivalAirport" → xsd:string
  "briefingRoom" → xsd:string
  "briefingBegin" → xsd:dateTime
  "crewAtSecurityCheck" → xsd:dateTime
  "crewBusDeparture" → xsd:dateTime
  "readinessNotification" → xsd:dateTime
  "boardingBegin" → xsd:dateTime
  "paxOnBoard" → xsd:dateTime
}
Name Description Required Schema / Format

flightDesignator

 IATA flight designator consists of airline code, flight number and suffix (optional). yes

xsd:string

[A-Z0-9]{2}[0-9]{1,4}[A-Z]?

flightDate

 Flight date of operation, date of first leg of a flight in UTC. yes

xsd:date

[0-9]{4}[-][0-9]{2}[-][0-9]{2}Z

YYYY-MM-DD Z

departureAirport

 Departure airport IATA code. yes

xsd:string

[A-Z]{3}

arrivalAirport

 Arrival airport IATA code. yes

xsd:string

[A-Z]{3}

briefingRoom

Briefing room.

Note: if DH, then there might be a briefing room dedicated to all DH on same next flight. Otherwise it's just the regular DH meeting point.

xsd:dateTime

[0-9]{4}[-][0-9]{2}[-][0-9]{2}T[0-9]{2}[:][0-9]{2}[:][0-9]{2}Z

YYYY-MM-DD T HH:MM:SS Z

briefingBegin

 Briefing time from personal duty plan if rotation number is provided in request. Calculated beginning time of the briefing otherwise.

xsd:dateTime

[0-9]{4}[-][0-9]{2}[-][0-9]{2}T[0-9]{2}[:][0-9]{2}[:][0-9]{2}Z

YYYY-MM-DD T HH:MM:SS Z
cocJoining Time when Cockpit crew is supposed to join Cabin crew briefing.

xsd:dateTime

[0-9]{4}[-][0-9]{2}[-][0-9]{2}T[0-9]{2}[:][0-9]{2}[:][0-9]{2}Z

YYYY-MM-DD T HH:MM:SS Z
briefingEnd Time of anticipated end of briefing.

xsd:dateTime

[0-9]{4}[-][0-9]{2}[-][0-9]{2}T[0-9]{2}[:][0-9]{2}[:][0-9]{2}Z

YYYY-MM-DD T HH:MM:SS Z

crewAtSecurityCheck

 Beginning time of the security check.

xsd:dateTime

[0-9]{4}[-][0-9]{2}[-][0-9]{2}T[0-9]{2}[:][0-9]{2}[:][0-9]{2}Z

YYYY-MM-DD T HH:MM:SS Z

crewBusDeparture

 Departure time of the crew bus.

xsd:dateTime

[0-9]{4}[-][0-9]{2}[-][0-9]{2}T[0-9]{2}[:][0-9]{2}[:][0-9]{2}Z

YYYY-MM-DD T HH:MM:SS Z

readinessNotification

 Last time when readiness can be revoked.

xsd:dateTime

[0-9]{4}[-][0-9]{2}[-][0-9]{2}T[0-9]{2}[:][0-9]{2}[:][0-9]{2}Z

YYYY-MM-DD T HH:MM:SS Z

boardingBegin

 Beginning time of passenger boarding on gate.

xsd:dateTime

[0-9]{4}[-][0-9]{2}[-][0-9]{2}T[0-9]{2}[:][0-9]{2}[:][0-9]{2}Z

YYYY-MM-DD T HH:MM:SS Z

paxOnBoard

 Time of the first passenger on board.

xsd:dateTime

[0-9]{4}[-][0-9]{2}[-][0-9]{2}T[0-9]{2}[:][0-9]{2}[:][0-9]{2}Z

YYYY-MM-DD T HH:MM:SS Z

Example

Request

Code snippet: Get request
GET /v1/flight_operations/crew_services/COMMON_CHECK_IN_TIMES
  ?flightDesignator=LH106&flightDate=2015-10-27Z&departureAirport=FRA&arrivalAirport=MUC&dutyType=OD&nextFlightDesignator=LH401&nextFlightDate=2015-10-27Z&nextArrivalAirport=JFK

Response

Code snippet: Json
{
  "flightDesignator": "LH400",
  "flightDate": "2015-01-01Z",
  "departureAirport": "FRA",
  "arrivalAirport": "JFK",
  "briefingRoom": "B024",
  "briefingBegin": "2015-01-01T07:50:00Z",
  "cocJoining": "2015-01-01T08:07:00Z",
  "briefingEnd": "2015-01-01T08:17:00Z",
  "crewAtSecurityCheck": "2015-01-01T08:20:00Z",
  "crewBusDeparture": "2015-01-01T08:40:00Z",
  "readinessNotification": "2015-01-01T08:50:00Z",
  "boardingBegin": "2015-01-01T09:10:00Z",
  "paxOnBoard": "2015-01-01T09:15:00Z"
}

version 13 as of 4 years ago by Alexander Fuss

Docs Navigation