NOTAM & TFR Feed: airport NOTAMs, drone-site TFRs and changes only

Get current NOTAMs for the airports you care about and FAA Temporary Flight Restrictions (TFRs) near your sites as clean, machine-readable records, ready for a spreadsheet, a dispatch dashboard, a drone-ops checklist or an AI agent:

• Airport NOTAMs from the FAA NOTAM system for US airports (KJFK, KLAX, 2W5 ...) and the international NOTAMs it distributes (EGLL, CYYZ, LFPG ...).
• FAA TFRs (security, VIP movements, wildfires and other hazards, UAS public gatherings, space operations) with their areas, altitudes and times, filtered by state, type or distance from your drone job sites.

Built for drone operators (Part 107 asks you to check local airspace and any flight restrictions before every flight), flight schools, charter and business-aviation dispatch, flight-ops teams and developers of EFB, ops and drone software.

What you get for each NOTAM

• qCode and a plain category: runway, taxiway, apron, aerodrome, obstacle, navaid, airspace, uas, procedure, lighting, services, other
• closed = true for closures (Q-code condition LC or "CLSD" in the text)
• validFrom / validTo in ISO 8601 UTC, permanent, estimatedEnd (EST), schedule (item D)
• lowerFt / upperFt, lat / lon, radiusNm from the ICAO Q-line
• text (clean plain text) and icaoText (full ICAO format when published)

Example (real record from our tests):

{
  "recordKey": "NOTAM:KJFK:12/171",
  "location": "KJFK",
  "category": "taxiway",
  "closed": true,
  "qCode": "QMXLC",
  "validFrom": "2025-12-10T19:44:00Z",
  "validTo": null,
  "permanent": true,
  "text": "TWY PB BTN HANGAR 12 RAMP AND TWY Q CLSD",
  "change": "new"
}

What you get for each TFR

• tfrType, regulation (for example 91.137(a)(2) for firefighting), tfrReason, state, facility
• areas: every area with lower and upper limits (value, unit, reference MSL/AGL/FL and feet), times, circle (centre and radius) and polygon coordinates
• distanceNm from your nearest tfrNear site (0 = the site is inside the TFR) and matchedWatch with the site labels

Changes-only mode

With mode: changes and a stateStoreId, each run returns only:

• new NOTAMs and TFRs,
• updated ones (with changedFields, for example validTo when an end time is extended),
• removed ones that are no longer published (cancelled, replaced or expired).

Records already delivered are not delivered or charged again. Schedule the Actor every hour or before each shift and send the output to e-mail, Slack or your own system.

Input

Field	Description
locations	Up to 50 ICAO or FAA identifiers. Empty = TFRs only
categories	Optional NOTAM category filter
activeWithinHours	Keep only records in force now or starting within N hours
includeTfr	Add FAA TFRs (default true)
tfrNear	Up to 50 sites: lat, lon, radiusNm (default 5), optional label
tfrStates, tfrTypes	Optional TFR filters
mode, stateStoreId	snapshot, or changes with a named store
maxRecords, maxPagesPerLocation, maxTfrDetails	Limits (defaults 2000, 20 pages of 30 NOTAMs, 200 TFRs)
proxyConfiguration	Apify Proxy (datacenter) by default

Drone operator example:

{
  "locations": ["KORL", "KMCO"],
  "activeWithinHours": 24,
  "tfrNear": [{ "label": "Lake Buena Vista job", "lat": 28.39, "lon": -81.54, "radiusNm": 10 }],
  "mode": "changes",
  "stateStoreId": "orlando-drone-ops"
}

Pricing

• $0.003 per delivered NOTAM or TFR, plus $0.005 per run start.
• In changes mode you pay only for new, updated and removed records.
• A run fails without delivering anything if a source cannot be read or a location is unknown, so you never receive a partial feed that looks complete.

Data sources

• FAA NOTAM Search (notams.aim.faa.gov), including international NOTAMs distributed through the FAA system.
• FAA TFR list and TFR detail files (tfr.faa.gov).

Both are U.S. Government works. The FAA NOTAM Search does not answer cloud container addresses directly, so the Actor reads it through Apify Proxy (datacenter); no CAPTCHA or login is involved.

Important

This feed is for planning, monitoring and automation. It is not an official pre-flight briefing. Before every flight obtain an official briefing (for example 1800wxbrief.com, the FAA NOTAM Search, B4UFLY or your national AIS) and follow your approved procedures. A NOTAM or TFR missing from the feed does not mean that no restriction applies. Times and limits are as published by the FAA; categories are derived from the Q-code or keyword and may not capture every detail of the text.

Limits

• NOTAMs are read per location. FDC NOTAMs that are not tied to the locations you list, and NOTAMs of countries that do not distribute them to the FAA system, are not included.
• Locations with more NOTAMs than maxPagesPerLocation allows are read partially; the SUMMARY record lists them in truncatedLocations, and they never produce removed records.
• tfrNear distances use the published TFR polygon or circle; a TFR without geometry is not matched to sites.