AeroCopilotHelp Center

NOTAMs and TFRs in AeroCopilot

How AeroCopilot ingests and surfaces FAA NOTAMs and TFRs — sourcing, refresh cadence, route geofiltering, decoding, and AI relevance classification.

NOTAMs and TFRs are the most operationally consequential, and most frequently misread, items on a pre-flight briefing. AeroCopilot pulls both from the FAA's authoritative feeds, refreshes them every 5 minutes, and applies route-aware filtering and AI decoding so you spend your time on the items that actually affect your flight.

NOTAMs

Source: Federal NOTAM Service (FNS), FAA · Refresh: every 5 minutes.

AeroCopilot ingests per-airport NOTAMs from FNS and decodes them into structured fields. The viewer pulls NOTAMs for departure, destination, and any alternates declared on the flight plan.

Display rules

  • Cap at 15 with FDC-first sort so high-density airports (the canonical example: KSFO with 40+ active NOTAMs) do not flood the briefing. A "Show all" expand reveals the rest.
  • Full text, no truncation. When the raw text is cryptic, an AI interpretation fallback chain renders a plain-English explanation underneath.
  • Dedup test suite runs against the ingest path — duplicate NOTAMs from overlapping FNS deliveries are collapsed before display.

AI tools

Three AI tools layer on top of the raw feed:

  • AI NOTAM Decode — plain-English explanation of an individual cryptic NOTAM.
  • AI NOTAM Intelligence — operational impact, pilot action items, and risk level for a NOTAM in the context of your flight.
  • NOTAM Relevance Filter — classifies each NOTAM as Critical, Relevant, or Informational for your specific route, aircraft, and operation.

TFRs

Source: FAA · Refresh: every 5 minutes.

Active and upcoming TFRs are ingested with their geometry polygons, altitude floors and ceilings, effective windows, and citation NOTAMs. The standalone /tfrs page filters by type (VIP, Sporting, Hazards, Security) per 14 CFR 91.137–145, with severity color coding and expandable cards.

What the briefing shows

Each TFR card surfaces:

  • NOTAM ID
  • Type badge
  • Area (city, state)
  • Altitude floor and ceiling, with SFC and UNL fallbacks when the FAA leaves either unbounded
  • Effective Zulu window
  • Description (the prior placeholder reading literal "HAZARDS" was fixed)

Route geofilter

On a planned flight, TFRs are filtered to a 20 NM corridor along the route. A transparency line tells you exactly how many additional TFRs are active elsewhere — you are never silently filtered into believing nothing else exists.

Where this data shows up

NOTAMs and TFRs are surfaced in five places:

  1. Pre-flight briefing — the structured 35+ section briefing including a 91.103 checklist and route-filtered hazard panels.
  2. Map overlays — TFR layer plus the broader hazards layer.
  3. AI Copilot — getNotams is one of the core 49 AI tools; the Copilot can pull NOTAMs for any airport on demand.
  4. Dashboard widgets — NOTAM Highlights for your home airport and TFR Proximity for nearby restrictions with distance.
  5. Briefing diff — when you reopen a saved briefing, NEW / UPDATED / EXPIRED badges appear on every NOTAM and TFR delta since your last refresh.

NOTAMs and TFRs sit on top of the regulatory layer. The same compliance ingest covers 14 CFR (Parts 1, 43, 61, 67, 89, 91, 97, 107, 119, 121, 125, 133, 135, 137, 141, 142), the AIM (refreshed every 6 months), and FAA Advisory Circulars. ChatFAR cites the binding regulation alongside any AC referenced.