TFRs and drones: how to check for restrictions and document it

A temporary flight restriction, or TFR, is a short-notice order from the FAA that closes off a defined piece of airspace for a period of time, and it applies to a drone the same as to any other aircraft. For a drone pilot, a TFR can turn a legal flight into a violation between one day and the next, because restrictions appear on short notice around events, disasters, and security operations that were not there when the job was planned. Checking for them is a preflight duty, not an optional courtesy.

The risk with TFRs is that they stay invisible until you look. A LAANC authorization does not clear a TFR, a clear sky says nothing about one, and a restriction can publish hours before a flight. This article covers what TFRs are and the forms they take, why they bind drone operators specifically, how to check for them before every flight, and how to document that you did.

What a TFR is and the forms it takes

Temporary flight restrictions come from a family of regulations, and the archetype is 14 CFR 91.137, which lets the FAA restrict airspace around a disaster or hazard: to protect people and property from a surface hazard, to give disaster-relief aircraft room to work, or to keep sightseeing aircraft from crowding an incident. A restriction under that rule is issued as a notice and specifies the hazard and the airspace it covers.

Other restrictions come from neighboring rules. Presidential movement creates restrictions under a separate provision, space operations under another, and aerial demonstrations and major sporting events under yet another, while security-related restrictions come from the special security instructions in the rules. The details differ, but the effect on a drone pilot is the same: a defined volume of airspace becomes off-limits, or limited to specific operations, for a defined time.

Why TFRs apply to drone operators

A drone pilot sometimes assumes TFRs are a manned-aviation concern, and that assumption is wrong. Part 107 ties drone operations directly to the TFR rules: the remote pilot in command must comply with the temporary flight restriction provisions and the special security instructions, the same sections that bind every other aircraft. A drone is an aircraft, and a restriction that closes airspace closes it to drones.

The consequences are real. Flying a drone into an active TFR, whether around a wildfire, a stadium, or a Presidential visit, can bring FAA enforcement and, in security cases, a response from law enforcement. Restrictions around firefighting are a recurring problem, because a drone in the airspace can ground the aircraft fighting the fire. The restriction does not care that the flight was planned in good faith. Compliance is on the pilot, which makes the check that finds the restriction the thing that matters.

How to check for TFRs before every flight

Checking for TFRs is straightforward, and the discipline is in doing it at the right time. The FAA publishes active restrictions on its TFR website, and the FAA's B4UFLY app surfaces them alongside other airspace information for a given location. A LAANC request is also checked against current restrictions, so an authorization app will flag many of them, though a pilot should never rely on that alone.

The timing is where flights go wrong. A restriction checked during planning a week out says nothing about one that publishes the morning of the flight, so the meaningful check happens close to the operation, ideally the same day. For a program, that means a same-day restriction check belongs on the preflight sequence as a required step with a defined source, not a habit that depends on the individual pilot remembering to look.

Stadium and standing restrictions

Not every restriction is a surprise. Major sporting events carry a standing restriction that recurs on a predictable schedule, generally covering the airspace within about three nautical miles of the stadium and up to and including 3,000 feet, from roughly one hour before the event until about one hour after. It typically applies to large-scale professional and collegiate sporting events, and it is issued as a standing notice rather than a fresh one each week.

For a drone program that operates near venues, these recurring restrictions are worth mapping in advance. A site that is clear on a Tuesday can sit inside an active restriction on game day, and a pilot who knows the venue's schedule avoids booking a job into a window that will be restricted. The standing nature of these restrictions makes them easy to plan around once a program knows they exist.

Documenting the TFR check

Checking for restrictions protects the flight; recording the check protects the program. A note that a pilot checked for TFRs, at what time, from what source, and with what result turns a preflight action into evidence that the action happened. Under the preflight-familiarity standard, the pilot who can show what they checked before departure is far better positioned than one who cannot.

The record matters most if something goes wrong. If a question later arises about whether a flight respected the airspace, a timestamped record of the restriction check, tied to the flight it belongs to, answers it directly. A check that happened but left no trace reads, after the fact, the same as one that never happened, so the small step of recording the result is what gives the check lasting value.

Common mistakes in checking for TFRs

Assuming a LAANC authorization clears a TFR. A LAANC authorization grants airspace access at a location; it does not lift a temporary flight restriction over that location. A pilot with a valid authorization can still be flying into an active TFR, which is a separate and serious violation.

Checking for restrictions only during planning. A TFR can publish hours before a flight, so a check done a week out is stale by the time the drone leaves the ground. The check that counts happens close to the operation, ideally the same day.

Reading a clear sky or quiet area as no restriction. TFRs are invisible from the ground and often cover ordinary-looking places around events or incidents. The only reliable way to know is to check an official source, not to judge by the surroundings.

Overlooking recurring restrictions near venues. Stadiums and speedways carry standing restrictions on event days that catch operators who only checked the location on a quiet afternoon. A program working near venues should map those schedules in advance.

Checking but never recording it. A restriction check that leaves no record cannot show, later, that it happened. Noting the time, source, and result of the check is what turns a preflight habit into defensible evidence.

FAQ

Do TFRs apply to drones?

Yes. Part 107 requires the remote pilot in command to comply with the temporary flight restriction rules and special security instructions that bind all aircraft. A drone is an aircraft, and airspace closed by a TFR is closed to drone operations for the duration of the restriction.

How do I check for a TFR before flying my drone?

Check the FAA's TFR website or the FAA's B4UFLY app for the flight location close to the operation, ideally the same day. LAANC authorization apps also screen against active restrictions, but a pilot should confirm through an official TFR source rather than relying on that alone.

What is a stadium TFR and does it affect drones?

It is a standing restriction around large sporting events, generally within about three nautical miles of the stadium and up to 3,000 feet, from roughly an hour before to an hour after. It applies to drones, so operations near a venue on event day are restricted.

Does a LAANC authorization account for TFRs?

Only partly. A LAANC request is checked against current restrictions, so the app will flag many of them, but a LAANC authorization does not grant permission to fly inside an active TFR. The pilot remains responsible for confirming that no restriction covers the flight.

Closing thought

TFRs are the airspace hazard that appears without warning, and the drone rules leave no room to treat them as someone else's problem. A restriction can close the airspace over a planned job on the morning of the flight, and only a check against an official source, done close to the operation, will catch it. Programs that make the same-day restriction check a required, recorded step protect their pilots from a violation that no clear sky and no LAANC authorization will prevent.

If you are keeping airspace and restriction checks disciplined across a drone program, FlybyOps was built for the operational record problem at the center of regulated drone work. Role-based access control, a document vault with expiration tracking, a pilot registry that tracks certification and currency, and an append-only audit log are all part of how the platform gives every preflight check a place on the record.