A drone pilot heading out to shoot establishing footage of a Sunday NFL tailgate launches from a public lot two miles from the stadium, having checked B4UFLY the night before and seen nothing flagged. By kickoff they're airborne inside a restricted 3-nautical-mile bubble that didn't exist twelve hours earlier — because stadium TFRs activate on the event's own schedule, not on a fixed map. That's the trait that separates a TFR from every other airspace rule a pilot learns for Part 107: it isn't permanent, it isn't always visible on the maps checked the day before, and treating a stale check as good enough is how otherwise careful pilots end up violating one without ever meaning to.
What a TFR actually is
A Temporary Flight Restriction is airspace the FAA closes or limits for a defined reason and a defined window, published through the NOTAM (Notice to Air Missions) system rather than baked into permanent sectional charts. The authority comes from several sections of 14 CFR Part 91 depending on the reason: 91.137 covers disaster and hazard areas (wildfires, chemical spills, post-disaster response), 91.138 covers federally declared disaster areas, 91.141 and a related provision cover VIP movement, and 91.145 specifically covers aviation and sporting events. Because each TFR is its own NOTAM with its own coordinates, altitude ceiling, and start and end time, there is no single "TFR shape" to memorize — every one has to be looked up on its own terms before a flight, not assumed from a previous flight at the same location.
Wildfire and disaster TFRs are about protecting other aircraft, not you
A 91.137 TFR over an active wildfire exists almost entirely to protect firefighting aircraft — air tankers and helicopters operate low, slow, and in tight patterns with limited ability to see and avoid a small drone, and a mid-air collision at that altitude is close to unsurvivable for the manned crew. This is also the TFR category drone pilots violate most often, usually with no intent to interfere: a bystander a mile from a visible smoke column assumes a "reasonable distance" from the fire itself is enough, without realizing the restricted volume typically extends several miles out and covers the airspace tanker aircraft actually use to approach and drop retardant, not just the ground footprint of the fire. Every documented drone incursion over an active fire grounds the entire aerial firefighting operation until officials can confirm the area is clear, because there is no way to know a drone's location or intentions in real time the way there is with a coordinated aircraft — which is exactly why land-management agencies run public safety campaigns built around one line: if you fly, we can't.
Stadium and sporting-event TFRs follow a fixed formula
Unlike wildfire TFRs, 91.145 stadium restrictions are predictable because the rule itself is specific: they apply to Major League Baseball, NFL, and NCAA Division I football games at stadiums seating 30,000 or more, plus major auto races such as NASCAR and IndyCar events, and they cover a 3-nautical-mile radius from the stadium up to 3,000 feet AGL, active from one hour before the scheduled start until one hour after the event ends. A pilot who checked the airspace the day before and saw nothing restricted was simply checking too early — the TFR is real and enforceable for that entire window even though it isn't visible on any static chart, and "the game hadn't started yet" is not a defense once the one-hour pre-event window has begun.
VIP-movement TFRs leave drones almost no legal path
Presidential and other VIP-movement TFRs are typically structured as two rings: an inner ring of roughly 10 nautical miles where no flight operations are permitted at all, and an outer ring extending to roughly 30 nautical miles where manned aircraft can sometimes operate under strict conditions — an active flight plan, a functioning transponder, and continuous communication with air traffic control. Drones cannot meet those outer-ring conditions, which means that for practical purposes the entire TFR, not just the inner ring, functions as a no-fly zone for small UAS. These events are also where counter-drone detection systems are most likely to be actively deployed, and a violation here is treated as a security matter rather than a routine airspace infraction, often drawing law-enforcement and Secret Service involvement in addition to any FAA civil penalty.
Checking once is not the same as checking before you fly
Because a wildfire TFR can appear within hours of a fire report and a stadium TFR activates on a clock rather than a fixed date, the only reliable habit is checking the FAA's TFR list (tfr.faa.gov) or a current NOTAM briefing immediately before launch, not the night before or that morning over coffee. B4UFLY and similar apps pull from the same data but can lag during fast-moving events, so cross-checking the official FAA source is worth the extra minute when flying anywhere near a stadium, a wildfire, a major public event, or a route a VIP might use.
Practical checklist
- Re-check tfr.faa.gov or a current NOTAM briefing immediately before launch — a check from the night before or the same morning can already be stale.
- Near any visible wildfire smoke, assume the restricted volume extends well beyond what looks like a safe visual distance from the fire itself.
- For stadium events, remember the 3 nm / 3,000 ft restriction is active from one hour before the scheduled start to one hour after the event ends, not just during the event.
- Treat any known VIP-movement TFR as fully off-limits for a drone, including the outer ring — the conditions that let manned aircraft operate there don't apply to small UAS.
- Expect active counter-drone detection at major public events and VIP movements; a violation there is handled as a security incident, not a routine airspace warning.
- This site's airspace and weather layers are planning references only and do not reflect live TFR status — always confirm directly with the FAA before flying near an active TFR.