Chart Supplements
GET/api/v1/chart-supplements/{icaoCodeOrIdent}Commercial Pilot

Get Chart Supplements

Gets time-limited pre-signed URLs for all chart supplement pages for an airport. Multi-page supplements will have one URL per page. The URLs expire after a limited period; request new URLs if they have expired.

Code Examples

curl \
  -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  "https://api.preflightapi.io/api/v1/chart-supplements/KJFK"

Description

Returns the airport's name, city, code, and a list of page URLs. Accepts both ICAO codes and FAA identifiers — ICAO prefixes (K, P) are automatically stripped to resolve the FAA identifier (e.g., KDFW resolves to DFW, PA88 resolves to A88).

GET /api/v1/chart-supplements/KDFW
GET /api/v1/chart-supplements/DFW
GET /api/v1/chart-supplements/KW05 — resolves to FAA identifier W05

Parameters

NameInTypeDescription
icaoCodeOrIdent*pathstringICAO code or FAA identifier (e.g., KDFW, DFW). Case-insensitive. Automatically resolves ICAO/FAA format mismatches.

Response Schema

200Returns the chart supplements for the airportChartSupplementsResponseDto
airportNamestringnullable

Official airport name.

airportCitystringnullable

City the airport is associated with.

airportCodestringnullable

Airport ICAO code or FAA identifier used to query this data.

404If no chart supplements are found for the given identifierApiErrorResponse
codestring

Machine-readable error code (e.g., "AIRCRAFT_NOT_FOUND").

messagestring

Human-readable error message suitable for display.

detailsstringnullable

Additional error details (only included in development environment).

servicestringnullable

Name of the external service that failed (only included for 503 errors).

validationErrorsRecord<string, string[]>nullable

Field-level validation errors (only for validation failures).

timestampstring

UTC timestamp when the error occurred.

traceIdstringnullable

Correlation ID for tracing the request.

pathstringnullable

Request path that generated the error.

Search Documentation

Search docs, endpoints, and schemas