How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

FAA Air Carrier Pilot Records Database (PRD) API

Data submission API for the FAA Pilot Records Database. Five paths covering pilot record create/update/delete, pilot data tracking, and asynchronous pilot data search request and response. Access is restricted by the FAA to operators under 14 CFR Part 121, 135, 125, 91K, Air Tour, Public Aircraft, or Part 91 Corporate — this is an accreditation-style gate, not a self-serve signup. Credentials are client_id and client_secret request headers declared as ordinary parameters, not as securitySchemes. The OpenAPI 3.0.0 definition is published openly in the FAA portal catalog and was harvested verbatim.

FAA Air Carrier Pilot Records Database (PRD) API is one of 12 APIs that U.S. Department of Transportation publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Aviation, Pilot Records, Airlines, Compliance, and FAA. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 8 operations across 5 paths, and defines 4 schemas. It is described by OpenAPI 3.0.0, at version v1.

Requests are made against 3 base URLs: https://external.apic4e.faa.gov, https://external-api.faa.gov/AirCarrierApi, https://dev-external.apic4e.faa.gov/Test/AirCarrierApi.

8 operations 5 paths 4 schemas 2 DELETE4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v1
Base URL
https://external.apic4e.faa.gov
Resource Areas
1

Paths & Operations 8

Across 5 paths, the API surfaces 8 operations — 2 DELETE, 4 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Operations 8
PUT
/AirCarrierApi/Pilot
update existing pilot record database Air carrier Api
2 params body → 201
POST
/AirCarrierApi/Pilot
add new records pilot record database Air carrier Api
2 params body → 200
DELETE
/AirCarrierApi/Pilot
performs delete on pilot record database air carrier api
2 params → 200
PUT
/AirCarrierApi/PilotDataTracking
update existing pilot tracking record database Air carrier Api
2 params body → 201
POST
/AirCarrierApi/PilotDataTracking
query pilot tracking record database air carrier api details
2 params body → 200
DELETE
/AirCarrierApi/PilotDataTracking
performs delete on pilot tracking record database air carrier api
2 params → 200
POST
/AirCarrierApi/AcPilotDataSearchRequest
add new records pilot record database Air carrier Api
2 params body → 200
POST
/AirCarrierApi/AcPilotDataSearchResponse
add new records pilot record database Air carrier Api
2 params body → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

pilotData_example
trackingData_example
pilotDataSearch_example
pilotDataSearchResponse_example

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

us-dot-faa-air-carrier-prd-api-openapi.yml Raw ↑

Other APIs U.S. Department of Transportation publishes across the network.

FAA Aeronautic Product Release API (APRA)
FAA Safety Assurance System (SAS) API
FAA Data Catalog (CKAN Action API v3)
DOT Data Hub Open Data API
Bureau of Transportation Statistics Open Data API
NHTSA vPIC (Vehicle Product Information Catalog) API
NHTSA Safety API (recalls, complaints, safety ratings)
FRA Safety Data Web Services
FMCSA QCMobile API
USDOT ITS JPO Operational Data Environment (ODE) REST API
U.S. Department of Transportation Airport Status Web Service
Where this information came from

This is an independent, third-party profile of FAA Air Carrier Pilot Records Database (PRD) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.