How to check drone NOTAMs and TFRs before you fly

A drone preflight check should not stop at weather, battery status and a general map glance. Temporary Flight Restrictions, or TFRs, can affect drones, and the cited FAA sources for this guide say those restrictions are communicated through NOTAMs. This guide is a repeatable source-check workflow for U.S. drone pilots, not a live clearance tool or a flight-specific legal answer.

Ordered FAA source-check workflow

• Open FAA TFR source.
• Check FAA NOTAM Search.
• Check FAA Graphic TFRs.
• Use B4UFLY/provider context as support.
• Recheck or stop if unclear or restrictive.

Workflow: open the FAA TFR source, check FAA NOTAM Search, check FAA Graphic TFRs, use B4UFLY/provider context only as support, then recheck or stop if information is unclear, stale, conflicting or restrictive. This workflow is not live clearance or FAA authorization.

The workflow figure belongs early because the reader's first job is sequence: open the official FAA TFR and NOTAM sources first, use B4UFLY/provider context as support, and recheck or stop when information is unclear, stale, conflicting or restrictive.

What NOTAMs and TFRs mean for this workflow

For this guide, a TFR is a temporary FAA airspace restriction that may be issued for specific reasons, events or hazards. A NOTAM is the notice channel pilots use to find time-sensitive aviation information, including restrictions that may matter before a drone operation. The FAA TFR page is the primary source for the drone-specific boundary here: TFRs include drones, pilots must check NOTAMs before flight, and some restrictions may require permission through the process identified by the FAA source.

That does not mean a headline, map marker, app message or summary can finish the decision for you. A useful NOTAM/TFR workflow is a source discipline: identify the place, time, altitude, operation type and responsible source surfaces, then compare what those sources say before the operation. If the plan changes, the check changes.

Use official FAA surfaces first

Start with the FAA Temporary Flight Restrictions page to understand the agency lane and the source boundary. Then use FAA NOTAM Search for the NOTAM surface itself and FAA Graphic TFRs for the official TFR route. Those FAA applications are reachable public surfaces, with an important limit: a static capture of those tools does not prove the current result for a particular location.

Use the FAA B4UFLY page as the official path for B4UFLY context and approved provider surfaces. The cited FAA material says B4UFLY features can cover controlled airspace, special-use airspace, critical infrastructure, national parks, military training routes and TFRs. Those features are useful for preflight awareness, but they do not replace operation-specific official checks or local or property permission.

Aloft Air Aware is included here only as an attributed first-party provider source. Aloft says Air Aware is an FAA-approved B4UFLY service using official FAA data updated near real time for TFRs and airspace. That supports an attributed provider-feature statement only. It is not a Drone Home ranking, not a guarantee that a provider surface contains each restriction relevant to a flight, and not a substitute for checking the official FAA surfaces when the answer matters.

Which source answers which preflight question

• FAA TFR page - best for TFR concepts and FAA boundary.
• FAA NOTAM Search - best for notice lookup.
• FAA Graphic TFRs - best for official graphical TFR context.
• FAA B4UFLY page - best for approved provider context.
• Aloft Air Aware - attributed provider feature only.

Source roles: FAA TFR page explains TFR concepts and FAA boundaries; FAA NOTAM Search supports notice lookup; FAA Graphic TFRs provide official graphical TFR context; FAA B4UFLY identifies approved provider context; Aloft Air Aware is an attributed provider feature source only. Recheck current sources for the actual operation.

The source comparison should make the hierarchy visible. FAA TFR, NOTAM Search and Graphic TFR surfaces carry the official-source role for this guide. B4UFLY and named provider surfaces can help with preflight awareness, but provider statements stay attributed and cannot become Drone Home endorsement or a substitute for current FAA checks.

A repeatable preflight check sequence

1. Define the planned operation in plain terms: launch area, operating area, time window, expected altitude, recreational or Part 107 purpose, and whether the site is near a stadium, emergency area, public event, airport, national park, military route or other sensitive area.
2. Open the FAA TFR page first. Use it to confirm that TFRs can apply to drones, that pilots must check NOTAMs, and that the FAA source is the controlling path for TFR concepts and permission-process references.
3. Search FAA NOTAM Search for the relevant location and time window. Do not treat a saved screenshot, an old search, or someone else's summary as current evidence for your flight.
4. Check FAA Graphic TFRs for the same operation window. If the route or timing changes, repeat the check rather than carrying over an earlier result.
5. Use the FAA B4UFLY page to choose an approved B4UFLY provider surface, then check the same operation there. If using Aloft Air Aware, keep the statement attributed to Aloft and remember that Drone Home is not ranking providers.
6. Put the results together conservatively. If the sources conflict, the operation is unusual, the area is sensitive, or permission appears necessary, stop and use the relevant official process or qualified help before flying.

This sequence is intentionally redundant. TFRs and NOTAMs are time-sensitive, and a drone flight can be affected by the combination of place, time and operation type. Checking more than one reviewed source surface helps a pilot catch the category of issue this guide is about, while still leaving the final operating decision outside Drone Home.

What this guide cannot decide

This guide cannot determine whether a specific flight may proceed. It cannot tell you that an address, event, stadium, park, disaster area, airport vicinity, client site or route is free of restrictions. It cannot provide FAA authorization, local permission, landowner permission, waiver status, LAANC status, emergency-response permission, law-enforcement approval or insurance clearance.

It also does not replace Part 107 responsibilities. The FAA Part 107 summary supports a general reminder that FAA operating requirements and airspace workflows still matter. The summary is not the controlling legal text, and this page does not restate all Part 107 requirements. If your operation depends on regulatory interpretation, use the current official sources and qualified help.

When to stop, recheck or seek the official path

• Restriction or conflict appears: stop and do not infer permission.
• Source unclear, stale or unavailable: recheck official sources and defer if unresolved.
• Authorization, waiver, controlled airspace or local rule may apply: use the appropriate official/compliance path.
• Sources reviewed with no restriction found: continue only with all other applicable rules and a current recheck.

Decision branches: stop when a restriction or conflict appears; recheck official sources when information is unclear, stale or unavailable; use the appropriate official/compliance path when authorization, waiver, controlled airspace or local rules may apply; if sources are reviewed with no restriction found, continue only with all other applicable rules and current recheck. This article does not grant clearance.

The stop/recheck figure belongs before the recap because it turns the boundary into a practical habit. If a source is restrictive, conflicting, stale, unavailable or outside the pilot's authority, the article should push the reader back to current official sources or the appropriate official/compliance path, not toward an assumed go-ahead.

Recheck and correction triggers

Recheck this guide if the FAA TFR page, FAA B4UFLY page, FAA NOTAM Search, FAA Graphic TFRs, FAA Part 107 summary, or any named B4UFLY provider page changes. Recheck it before publication if a specific provider feature, event type, permission path, app capability or official source status is added. Recheck it after a major event, disaster TFR context, or FAA source redesign that changes how pilots find NOTAM or TFR information.

If a later version needs to answer a specific location, event, date, airspace authorization, waiver, stadium restriction, emergency restriction or provider-app result, that should be treated as new source-specific work. This field guide stays with the source hierarchy, the repeatable check sequence and the limits of what Drone Home can decide.

Sources

• FAA Temporary Flight Restrictions page: https://www.faa.gov/uas/getting_started/temporary_flight_restrictions
• FAA B4UFLY page: https://www.faa.gov/uas/getting_started/b4ufly
• FAA NOTAM Search: https://notams.aim.faa.gov/notamSearch/
• FAA Graphic TFRs: https://tfr.faa.gov/
• FAA Part 107 summary: https://www.faa.gov/newsroom/small-unmanned-aircraft-systems-uas-regulations-part-107
• Aloft Air Aware, attributed provider feature source: https://www.aloft.ai/air-aware/