/api/v1/notams/radiusCommercial PilotGet Notams By Radius
Gets NOTAMs within a radius of a geographic point.
Code Examples
curl \
-H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
"https://api.preflightapi.io/api/v1/notams/radius?latitude=40.6413&longitude=-73.7781&radiusNm=10&classification=value&feature=value&freeText=value&effectiveStartDate=value&effectiveEndDate=value"curl \
-H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
"https://api.preflightapi.io/api/v1/notams/radius?latitude=40.6413&longitude=-73.7781&radiusNm=10&classification=value&feature=value&freeText=value&effectiveStartDate=value&effectiveEndDate=value"Description
Performs a spatial query using PostGIS to find NOTAMs whose geometry falls within the specified radius of the given coordinates. Only NOTAMs with stored geometry are returned — NOTAMs that lack geographic data (no point or polygon in the source GeoJSON) are excluded from spatial queries.
The same optional filters available on the airport endpoint (classification, feature, freeText, effectiveStartDate/effectiveEndDate) can be combined with the spatial search.
Examples
GET /api/v1/notams/radius?latitude=32.8998&longitude=-97.0403&radiusNm=25
GET /api/v1/notams/radius?latitude=32.8998&longitude=-97.0403&radiusNm=10&classification=DOMESTICParameters
| Name | In | Type | Description |
|---|---|---|---|
| latitude | query | number | Latitude in decimal degrees (-90 to 90) |
| longitude | query | number | Longitude in decimal degrees (-180 to 180) |
| radiusNm | query | number | Search radius in nautical miles (greater than 0, max 100) |
| classification | query | string? | Optional NOTAM classification filter: INTERNATIONAL, MILITARY, LOCAL_MILITARY, DOMESTIC, FDC |
| feature | query | string? | Optional NOTAM feature type filter: RWY, TWY, APRON, AD, OBST, NAV, COM, SVC, AIRSPACE, ODP, SID, STAR, CHART, DATA, DVA, IAP, VFP, ROUTE, SPECIAL, SECURITY |
| freeText | query | string? | Optional text search within NOTAM text (max 80 characters, alphanumeric and /.-() only) |
| effectiveStartDate | query | string? | Optional effective start date filter (ISO 8601). Must be paired with effectiveEndDate. |
| effectiveEndDate | query | string? | Optional effective end date filter (ISO 8601). Must be paired with effectiveStartDate. |
Response Schema
Total number of NOTAMs returned in this response.
UTC timestamp when the query was executed.
Description of the queried location (e.g., "KDFW", "32.8970,-97.0380 (25nm)", or "KDFW -> KAUS").
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.