Reference · built on requestCommons signalAviation & marine

FAA Temporary Flight Restrictions

Active and scheduled Temporary Flight Restrictions from tfr.faa.gov as a JSON list, per-TFR XML and AIXM, shapefiles, and a WFS layer.

Request accessPricing ↗

About

tfr.faa.gov is the FAA's Temporary Flight Restriction website. A TFR is a NOTAM that closes airspace for a hazard, a special event, or a security reason. The list shows every active or future TFR with date, NOTAM id, facility, state, type, and description, filtered by center, state, or type. The site serves the same list as JSON or XML, each TFR's NOTAM text, an XML and an AIXM file per TFR, and a shapefile of its area. A GeoServer publishes the TFR shapes as a WFS layer and a WMS. Types are AIRSHOW, HAZARDS, SECURITY, SPACE OPERATIONS, SPECIAL, UAS Public Gathering, and VIP.

Through Fibric, an operator polls the list, matches new TFRs to your sites and routes, and proposes a permit hold, an event staffing change, or a crew check-in for your approval.

This is a reference listing. It documents what Fibric would read from FAA Temporary Flight Restrictions and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • The TFR list from tfrapi/getTfrList with notam_id, facility, state, type, description, mod_date, mod_abs_time, and is_new for each TFR
  • The same list as a JSON or XML download through /tfr3/export/json and /tfr3/export/xml, backed by tfrapi/exportTfrList
  • NOTAM text per TFR from tfrapi/getNotamText and tfrapi/getWebText by notamId
  • Per-TFR XML at /download/detail_<id>.xml with effective and expiry times, purpose, facility, CFR type, and area altitudes; AIXM at .aixm50
  • TFR shapes as GeoJSON or shape-zip from the GeoServer WFS layer TFR:V_TFR_LOC, and as a WMS
  • Counts by center from tfrapi/getSummary, and TFRs without a shape from tfrapi/noShapeTfrList

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold drone work under a new TFR

    When a TFR's shape covers a job site, the operator proposes a hold on the flight permit and attaches the NOTAM text and effective window.

    With Permit Check

  • Staff up for an airshow or VIP visit

    The operator watches AIRSHOW and VIP TFRs near your venues and proposes extra coverage for the dates in the description.

    With Event Surge

  • Check in on crews inside a wildfire hazard area

    A HAZARDS TFR for firefighting aircraft near a site triggers a proposed check-in with staff working there, with the TFR area from its XML.

    With Lone Worker

Requirements

  • A mapping from facility (the ARTCC or FDC id) and state to the sites, routes, or events you care about
  • Polling on mod_abs_time and is_new, since the site removes expired NOTAMs in near real time
  • A parser for the XNOTAM-Update XML or the AIXM file per TFR when you need altitudes, times, and area geometry
  • Your own cross-check with NOTAM Search or the United States NOTAM Service for anything you act on
Authentication
Nothing to register. The list, export, download, and GeoServer URLs answer plain HTTPS GET requests without a key.

Limits

  • The FAA calls the site informational; it is not a sole source for 14 CFR 91.103 pre-flight action, and recently entered NOTAMs may lag
  • No published API documentation; the JSON and XML endpoints are the ones the list and detail pages call
  • The map's WFS request is capped at maxFeatures=300, and some TFRs carry no shape at all
  • No push feed or webhook; you poll the list and compare mod_abs_time

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request FAA Temporary Flight Restrictions ↗

Questions and answers

What types of TFR does the list carry?
AIRSHOW, HAZARDS, SECURITY, SPACE OPERATIONS, SPECIAL, UAS Public Gathering, and VIP. HAZARDS covers 91.137(a)(1) surface hazards, 91.137(a)(2) wildfires and disaster relief, 91.137(a)(3) sightseeing restrictions, and 91.138 Hawaii disaster areas.
How do you get a TFR's geometry?
Three ways. Download the shapefile per TFR, which the site fetches from its GeoServer WFS as shape-zip by featureID V_TFR_LOC.<id>. Request the WFS layer TFR:V_TFR_LOC as application/json. Or parse the per-TFR XML and AIXM files, which carry the area definitions.
How current is the list?
The Data as of field shows the Zulu time of the last update, and expired NOTAMs are removed in near real time. The FAA warns that system processing delays can keep recently entered NOTAMs off the site and points to the United States NOTAM Service to confirm.
Ask about FAA Temporary Flight Restrictions

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Federal Aviation Administration (tfr.faa.gov). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy