/api/v1/notams/number/{notamNumber}Commercial PilotGet Notams By Number
Gets NOTAMs by NOTAM number in various formats.
Code Examples
curl \
-H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
"https://api.preflightapi.io/api/v1/notams/number/value"curl \
-H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
"https://api.preflightapi.io/api/v1/notams/number/value"Description
Searches the database for NOTAMs matching the given number. Unlike most NOTAM endpoints, this does *not* filter out cancelled or expired NOTAMs — so results may include recently expired or cancelled NOTAMs that have not yet been purged. This is *not* a historical archive; the database periodically purges stale NOTAMs.
Supported Input Formats
- Bare number —
3997
- Number/year —
3997/2025or3997/25
- Month-prefix —
03/420
- Domestic —
BNA 420,BNA 03/420,!BNA 03/420
- FDC —
FDC 4/3997,!FDC 4/3997
- ICAO —
A1234/25
Disambiguation
Bare numbers (e.g., 3997) may match multiple NOTAMs across different accounts or years. Include the year, account ID, or full domestic format to narrow results.
Examples
GET /api/v1/notams/number/3997 — bare number (may return multiple matches)
GET /api/v1/notams/number/3997%2F2025 — number with year (%2F = /)
GET /api/v1/notams/number/BNA%20420 — domestic format (%20 = space)
GET /api/v1/notams/number/A1234%2F25 — ICAO formatParameters
| Name | In | Type | Description |
|---|---|---|---|
| notamNumber* | path | string | NOTAM number in any supported format (URL-encoded) |
Response Schema
GeoJSON type, always "Feature".
Unique NOTAM feature identifier.
Machine-readable error code (e.g., "AIRCRAFT_NOT_FOUND").
Human-readable error message suitable for display.
Additional error details (only included in development environment).
Name of the external service that failed (only included for 503 errors).
Field-level validation errors (only for validation failures).
UTC timestamp when the error occurred.
Correlation ID for tracing the request.
Request path that generated the error.
Machine-readable error code (e.g., "AIRCRAFT_NOT_FOUND").
Human-readable error message suitable for display.
Additional error details (only included in development environment).
Name of the external service that failed (only included for 503 errors).
Field-level validation errors (only for validation failures).
UTC timestamp when the error occurred.
Correlation ID for tracing the request.
Request path that generated the error.