/flightaware/aircraft

POST /api/flightaware/aircraft

Price: 5 credits

Get aircraft registration details (make/model, owner, registry data) by tail number

How to use it

Get registration details for an aircraft by its tail number (registration, e.g. 'N815UA'). Returns the manufacture year, make/model, aircraft class, seat and engine counts, owner (name, location, type), engine description, weight and speed classes, Mode S transponder code (octal and hex), airworthiness and certificate dates, registry status/source and a photo. Detailed registry data is most complete for US-registered aircraft.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• registration string required — Aircraft registration (tail number) (examples: "N815UA", "N77525"; minLength: 2)

Response

• @type string (default: "FlightawareAircraft")
• registration string required
• year integer nullable
• model string nullable
• aircraft_class string nullable
• seat_count integer nullable
• engine_count integer nullable
• owner_name string nullable
• owner_location string nullable
• owner_type string nullable
• airworthiness_class string nullable
• serial_number string nullable
• engine string nullable
• weight string nullable
• speed string nullable
• mode_s_code string nullable
• mode_s_hex string nullable
• status string nullable
• certificate_issue_date string nullable
• airworthiness_date string nullable
• last_action_date string nullable
• expiration_date string nullable
• registry_source string nullable
• image string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No aircraft found for the given registration Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.