Drone NOTAMs: what they are and when to file one

A NOTAM, or Notice to Air Missions, is an official notice about a condition in the airspace system that a pilot needs to know before flying, from a closed runway to a temporary flight restriction. For a drone operator, the important thing to understand about NOTAMs is a split: you are almost always required to check them, and you are almost never required to file one. This article covers what NOTAMs are, why checking them is a preflight duty, and the narrow cases where a drone operation does file one.

The confusion comes from the word file. NOTAMs feel like paperwork, and the instinct is that a drone flight must generate one. Under Part 107 it does not. The obligation runs the other way: the FAA and others issue NOTAMs, and the pilot's job is to find and read the ones that affect the flight. This article draws that line and explains where the rare filing cases sit.

What a NOTAM is

A NOTAM is a notice that communicates a change or hazard in the airspace system to the people who need it before they fly. The term now stands for Notice to Air Missions, a renaming of the older Notice to Airmen, and the notices cover a wide range: closed or shortened runways, lighting or equipment outages, obstacles, airspace changes, and temporary flight restrictions. If a condition affects the safety of a flight and is not shown on published charts, a NOTAM is how it gets communicated.

Two points matter for drone operators. First, a temporary flight restriction is a type of NOTAM, so the restrictions that close airspace around events and incidents live in the same system. Second, NOTAMs are distributed through the FAA's federal NOTAM system and searchable through its NOTAM Search tool, which lets a pilot pull the notices tied to a location. Understanding that TFRs are NOTAMs keeps a pilot from treating them as separate problems checked in separate places.

Why you must check NOTAMs

The duty to check NOTAMs sits inside the preflight rules. Part 107 requires the remote pilot in command to assess the operating environment before flight, including the airspace and any restrictions that apply, which means finding the notices that affect the operation. The broader preflight-action standard that runs across aviation makes the same point: a pilot must become familiar with all available information concerning a flight, and NOTAMs are part of that information.

The reason is practical rather than bureaucratic. A NOTAM might report a temporary restriction over the flight area, a nearby obstacle, or an airspace change that affects the operation, and none of it is visible from the launch point. A pilot who skips the check is flying without information that was available and free to obtain, which is exactly the position the preflight rules are written to prevent.

When a drone operator files a NOTAM

Here is the part that surprises people: under Part 107, a drone operator is not required to file a NOTAM. The FAA states plainly that a NOTAM is not required for Part 107 flights, and that filing one is only required when an operator holds a Certificate of Authorization to fly as a public aircraft under Part 91 and that certificate carries a NOTAM requirement. For the ordinary commercial operator flying under Part 107, there is nothing to file.

That narrows the filing question considerably. A public agency operating under a COA may have a condition in its authorization that requires issuing a NOTAM for its operations, and in that case the requirement comes from the COA, not from Part 107. Outside that situation, a Part 107 operator's entire NOTAM obligation is to check, not to file. Confusing the two leads programs to look for a filing process that does not apply to them.

How to check NOTAMs for a drone flight

Checking NOTAMs means pulling the notices tied to the flight location and reading the ones that matter. The FAA's NOTAM Search tool lets a pilot search by location and returns the active notices for that area, including temporary flight restrictions. A standard preflight briefing and many airspace apps surface the same information, so the pilot has more than one way to reach it.

As with restrictions generally, timing decides whether the check is useful. A NOTAM can publish close to a flight, so a check run days ahead can miss one issued the morning of the operation. The reliable practice is to check close to flight time and to treat the notices for the specific location, not a general impression of the area, as the thing being reviewed. For a program, that makes the NOTAM check a defined preflight step with a named source rather than an informal habit.

NOTAMs and the flight record

Because the NOTAM obligation is to check rather than to file, the record a program keeps is the record of the check. A note that a pilot reviewed NOTAMs for the flight location, at a given time, and what the relevant notices were, turns the preflight review into evidence that it happened. That is the same discipline that applies to restrictions and weather, and it serves the same purpose.

The value shows up when a flight is questioned. If someone later asks whether an operation accounted for a notice that was active that day, a timestamped record of the NOTAM check, attached to the flight, answers it. The notices themselves are transient and disappear from view once they expire, so a program that captures what was checked and when holds something the live system will not show a month later.

Common mistakes with drone NOTAMs

Believing a Part 107 flight has to file a NOTAM. Standard commercial drone operations under Part 107 do not file NOTAMs. Searching for a filing process wastes effort on a requirement that applies only to public-aircraft operations under a COA that specifically calls for it.

Skipping the NOTAM check because nothing was filed. Filing and checking are opposite obligations. A pilot who files nothing still has to check the notices that affect the flight, and skipping that check because there was nothing to file misunderstands the duty entirely.

Treating a TFR as separate from NOTAMs. A temporary flight restriction is a NOTAM, and it appears in the NOTAM system as well as on the FAA's restriction resources. Knowing they are the same thing keeps a pilot from assuming one check covers what the other missed.

Checking NOTAMs only at planning time. A notice can publish close to a flight, so a check run days ahead can be stale by launch. The meaningful review happens near flight time, against the notices for the specific location.

Not recording the NOTAM check. Because the obligation is to check, the check is what needs a record. A note of the time, source, and relevant notices is what lets a program show later that the review happened.

FAQ

Do I need to file a NOTAM to fly my drone?

Not under Part 107. The FAA states that a NOTAM is not required for Part 107 flights. Filing is only required when an operator flies as a public aircraft under a Certificate of Authorization that specifically requires a NOTAM. Ordinary commercial operators have nothing to file.

What does NOTAM stand for?

NOTAM stands for Notice to Air Missions, a renaming of the earlier Notice to Airmen. A NOTAM communicates a change or hazard in the airspace system, such as a closed runway, an obstacle, an airspace change, or a temporary flight restriction, to pilots before they fly.

Do I have to check NOTAMs for a Part 107 flight?

Yes. Part 107 requires assessing the operating environment, including airspace and restrictions, before flight, and the general preflight standard requires becoming familiar with all available information. NOTAMs are part of that information, so checking the notices for the flight location is a preflight duty.

Is a TFR the same as a NOTAM?

A temporary flight restriction is issued as a type of NOTAM, so a TFR is a NOTAM, though not every NOTAM is a TFR. Restrictions appear in the NOTAM system alongside runway closures, obstacles, and other notices, and also on the FAA's dedicated restriction resources.

Closing thought

The word NOTAM makes drone operators reach for a filing process that, under Part 107, does not exist for them. The real obligation is the reverse: the system issues notices, temporary flight restrictions among them, and the pilot has to find and read the ones that affect the flight. Programs that treat the NOTAM check as a defined, recorded preflight step, run close to flight time against the specific location, meet the duty that applies and skip the paperwork that does not.

If you are making sure every crew flies a job with its airspace picture confirmed, FlybyOps was built for the operational record problem at the center of regulated drone work. A project and job hierarchy with map-based scoping, role-based access control, a pilot registry that tracks certification and currency, and an append-only audit log are all part of how the platform keeps each job's preflight checks attached to the flight they cover.