/faa_registry/aircraft

POST /api/faa_registry/aircraft

Price: 1 credit

Get an FAA civil aircraft registration by N-Number: registration status, serial number, manufacturer, model, aircraft and engine type, certificate dates, Mode S codes, registered owner, airworthiness, temporary certificates, or the reservation record for a reserved N-Number.

How to use it

Use this to identify an aircraft and its registered owner from a tail number. A reserved N-Number returns the reservation record instead of an aircraft description. Find N-Numbers by owner name or serial number with faa_registry/aircraft/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• n_number string required — Aircraft registration N-Number, with or without the leading N (examples: "N1115Y", "1115Y"; minLength: 1)

Response

• @type string (default: "FaaRegistryAircraft")
• n_number string required
• url string required
• registration_status string nullable
• serial_number string nullable
• manufacturer string nullable
• model string nullable
• manufacture_year integer nullable
• aircraft_type string nullable
• engine_type string nullable
• certificate_status string nullable
• certificate_issued_at integer nullable
• certificate_expires_at integer nullable
• registration_type string nullable
• is_dealer boolean nullable
• is_fractional_owner boolean nullable
• mode_s_code_octal string nullable
• mode_s_code_hex string nullable
• pending_number_change string nullable
• number_change_authorized_at integer nullable
• owner object nullable
  • @type string (default: "FaaRegistryParty")
  • name string nullable
  • street string nullable
  • street2 string nullable
  • city string nullable
  • state string nullable
  • county string nullable
  • zip_code string nullable
  • country string nullable
• other_owner_names array (default: [])
• airworthiness object nullable
  • @type string (default: "FaaRegistryAirworthiness")
  • classification string nullable
  • category string nullable
  • type_certificate_data_sheet string nullable
  • type_certificate_holder string nullable
  • engine_manufacturer string nullable
  • engine_model string nullable
  • exception_code string nullable
  • issued_at integer nullable
• temporary_certificates array (default: [])
  • @type string (default: "FaaRegistryTemporaryCertificate")
  • certificate_number string nullable
  • issued_at integer nullable
  • expires_at integer nullable
• fuel_modifications array (default: [])
• reservation object nullable
  • @type string (default: "FaaRegistryReservation")
  • reservation_type string nullable
  • mode_s_code_octal string nullable
  • reserved_at integer nullable
  • renewal_at integer nullable
  • purge_at integer nullable
  • pending_number_change string nullable
  • number_change_authorized_at integer nullable
  • reserving_party object nullable
    • @type string (default: "FaaRegistryParty")
    • name string nullable
    • street string nullable
    • street2 string nullable
    • city string nullable
    • state string nullable
    • county string nullable
    • zip_code string nullable
    • country 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 — The registry rejected this N-Number or holds no record for it 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.