Drones, Part 107, and What EMA and Communications Should Know

Why the Part 107 certificate matters

In the United States, most drone flying that is not purely recreational falls under a set of FAA rules known as Part 107. If a member of your agency flies a drone as part of the job, whether that is documenting a scene, searching for a missing person, or mapping storm damage, that is a commercial or organizational operation in the eyes of the FAA, and it generally requires a Remote Pilot Certificate issued under Part 107.

The certificate is earned by an individual, not an agency. A person studies aeronautical knowledge, passes a knowledge test at an approved testing center, and holds the certificate as their own credential. That distinction matters for records and staffing. A department does not get certified. Its people do, and if those people leave, the qualification leaves with them unless someone else is trained and tested.

There is a separate path many public-safety agencies pursue instead of, or alongside, Part 107. A government entity can operate under what is often called a public aircraft operation or a certificate of authorization arrangement with the FAA. That path can grant flexibility that the standard Part 107 rules do not, but it also carries its own responsibilities and oversight. The two paths are not interchangeable, and choosing between them is a decision worth making deliberately with legal counsel rather than by default.

For a communications officer or emergency manager, the takeaway is simple. The moment a drone becomes part of how your agency does its work, you have entered a regulated space with credential requirements, recordkeeping expectations, and a public that will ask questions. Knowing the shape of that space is the first responsibility.

What Part 107 authorizes, and what it does not

The standard Part 107 rules describe a fairly conservative kind of flying. Understanding the baseline helps you understand where the exceptions and waivers come in.

• The remote pilot must keep the aircraft within visual line of sight, meaning they can see it with their own eyes without relying only on the camera feed.
• Operations are generally limited to daytime or civil twilight with proper lighting, though the rules were expanded some years ago to allow routine night operations for certified pilots who meet the requirements.
• There are altitude limits, speed limits, and restrictions on flying over people and moving vehicles that are not part of the operation.
• Flying in controlled airspace near airports generally requires authorization, which for many areas is available through an automated system rather than a phone call.

Several of these baseline limits can be waived. The FAA has a waiver process that lets an operator request permission to do something the standard rules would not allow, such as flying over people or beyond visual line of sight, provided the operator can show how they will keep the operation safe. Public-safety agencies frequently rely on waivers and on the emergency-response provisions the FAA offers for time-critical situations.

The phrase you will hear most often as the technology matures is beyond visual line of sight, usually shortened to BVLOS. This is flying where the pilot cannot see the aircraft directly and instead relies on the aircraft, its sensors, and its systems to stay clear of hazards. BVLOS unlocks the most ambitious uses, including long searches and deliveries, and it is also the most restricted and the most actively evolving part of the rules. Treat any claim that BVLOS is broadly available today with caution. It is expanding, but it remains the exception that requires specific approval, not the default.

Where drones earn their keep in the field

Public-safety agencies have adopted drones widely because the return on a single flight can be immediate and obvious. The value is rarely in the gadget. It is in the overhead perspective delivered fast, safely, and cheaply compared with the alternatives.

• Scene size-up. An incident commander who can see the whole footprint of a structure fire, a crash, or a spreading brush line from above makes better resource decisions than one working from the curb. A drone can show the back side of a building, the roof, and the direction a problem is moving without putting a person there.
• Search operations. For a lost hiker, a missing child, or a person in the water, an aircraft with a camera can cover ground far faster than a foot team. Thermal sensors that detect heat can find a person in darkness or in cover that would defeat the naked eye.
• Mapping and damage assessment. After a storm, a flood, or a large fire, a drone can produce current overhead imagery and stitched maps that help an emergency manager document the extent of damage, prioritize response, and support requests for outside assistance.
• Hazmat standoff. When the hazard is a chemical release, a rail incident, or an unstable structure, a drone lets responders read placards, gauge the scene, and monitor a plume from a safe distance rather than committing people into the danger area.
• Overwatch. During a large event, a search of a wide area, or a tactical operation, an overhead view can improve situational awareness and coordination for everyone on the ground.

None of these uses requires the aircraft to be exotic. What they require is a trained pilot, a clear reason to fly, and a plan for what happens to the imagery afterward. That last point is where the operational value meets the controversy, and it is where a communications officer should be paying attention.

Privacy and civil-liberties questions

The same overhead camera that helps find a lost child can also record a backyard, a gathering, or a person who never consented to being watched. This is the tension at the center of the public conversation about public-safety drones, and it is a genuine one that reasonable people weigh differently.

On one side, agencies argue that a drone is a tool no different in kind from a helicopter or an officer standing in a public place, that its use is governed by policy and law, and that the lifesaving value is real and demonstrated. On the other side, civil-liberties advocates raise concerns about persistent surveillance, about imagery being retained and reused beyond the original purpose, about flights that were justified for one reason drifting into general monitoring, and about the chilling effect that overhead cameras can have on lawful activity such as protest.

These are not questions technology answers. They are questions of policy, transparency, and law, and they vary by state and locality. Some jurisdictions have passed specific statutes governing when public agencies may use drones and how long they may keep the footage. Others have not. An emergency manager or communications officer should be able to state plainly what their agency's policy is on why drones fly, who authorizes a flight, what happens to the recorded data, how long it is kept, and who can request it. If you cannot answer those questions, that gap is itself the story a reporter will write.

Airspace deconfliction and the coming traffic

For most of aviation history, the low airspace just above rooftops was empty. That is changing, and the change is the single biggest structural issue for emergency managers to track. Multiple forces are pushing more aircraft into that space at once.

• Medical and EMS delivery. There is active work on using drones to move medical supplies, blood, and time-sensitive materials, and in some pilot efforts to deliver items such as automated defibrillators ahead of ground responders. These uses are promising and still developing. Where they operate, they add aircraft to the same low airspace your responders may want to use.
• Commercial package delivery. Companies continue to expand routine delivery flights, which depends heavily on the BVLOS approvals discussed earlier. As that approval scales, the number of aircraft in residential airspace grows with it.
• Public-safety flights themselves. As more agencies adopt drones, the odds rise that two different agencies, or an agency and a commercial operator, want the same piece of sky at the same time.

The result is a deconfliction problem. When a helicopter is inbound for a medical transport, when a news aircraft is orbiting, and when your own drone is up over the same scene, someone has to keep them apart. Today that is handled through a combination of established procedures, direct coordination, and the requirement that public-safety flights yield to crewed aircraft. As traffic grows, more automated systems for coordinating this low-altitude traffic are being developed and tested. They are not yet a finished, universal system you can assume is in place.

Remote ID is one piece of this picture that is already established. It is a requirement that most drones broadcast identification and location information while flying, functioning something like a digital license plate. It helps authorities and, in time, other systems know what is in the air. It is a foundation for future coordination, not a complete traffic-management solution on its own.

The spectrum question rides alongside the airspace question. Drones depend on radio links for control and for video. As more aircraft fly in the same area, the demand on those radio frequencies grows, and interference becomes a practical concern for reliable operation. It is worth knowing whether your area has congestion issues before you depend on a link during a critical flight.

Security and supply-chain concerns

A recurring controversy in public-safety drone use concerns where the aircraft and their software come from. Some drones widely used in the field are made by foreign manufacturers, and this has raised questions at the national and state level about data security and supply-chain risk.

The concern, stated neutrally, is that an aircraft made by a company subject to a foreign government could potentially transmit imagery, flight data, or location information in ways the operating agency does not intend or control. Some government bodies have restricted or banned the purchase of drones made by certain foreign manufacturers for their own use, and some funding streams attach conditions related to where equipment is made.

The counterargument, also stated neutrally, is that some of these aircraft have been the most capable and affordable options available, that agencies can mitigate risk through configuration choices and network controls, and that the evidence for specific harm is contested. Manufacturers named in these discussions have generally disputed the characterizations of their products.

You do not have to resolve this debate to plan around it. What you should do is know two things. First, whether any law, grant condition, or policy that applies to your agency restricts the origin of drones you may buy or use. Grant-funded purchases in particular can carry conditions that are easy to miss. Second, what your own agency's stance and data-handling practices are, so you can answer a pointed question without being caught flat. This is an area where the rules and the lists of restricted equipment change over time, so treat any specific fact as something to verify at the moment you need it.

Counter-drone and detection questions

If drones are a tool for your agency, they can also be a hazard or a threat operated by someone else. A drone flying over a large public event, a critical facility, or an active incident scene can create real risk, from simple distraction of aircraft to more deliberate misuse. This has driven interest in counter-drone and detection technology.

Here the legal ground is more constrained than many people expect. Detecting a drone, meaning knowing that one is present and where it is, is one thing. Interfering with it, jamming its signal, taking control of it, or bringing it down, is a very different thing legally. Authority to actively counter a drone is tightly limited and rests with specific federal entities. A local agency generally cannot lawfully jam or disable an aircraft on its own, and the tools that do so may themselves be illegal to operate. This is a frequent point of confusion worth being precise about.

Detection alone still raises questions. Systems that identify and track nearby drones can improve safety at an event, and Remote ID contributes to this. As with any monitoring technology, the questions of what data is collected, how long it is kept, and who has access apply here too. If your jurisdiction is considering detection tools, the same policy discipline you apply to your own drone imagery should extend to what those systems capture.

Starting a program responsibly

An agency that wants to fly does not need to solve every controversy first. It needs to build a program deliberately rather than accumulating aircraft and hoping the structure catches up. A responsible start looks roughly like this.

• Decide the mission before the hardware. Name the specific problems a drone will solve for your agency, whether that is search, size-up, mapping, or documentation. The mission drives every other choice.
• Get the credential path right. Determine whether your people will fly under Part 107, under a public aircraft arrangement, or both, and make that decision with legal counsel rather than by copying a neighbor.
• Certify and train real people. Identify who will earn and hold the remote pilot certificate, and plan for more than one so a single departure does not ground the program. Build recurring training and currency into the calendar, not just the initial test.
• Write the policy first. Put authorization, purpose, data retention, access, and privacy protections in writing before the first operational flight, and be prepared to share that policy publicly.
• Confirm the equipment fits your constraints. Check whether any law or grant condition limits what you may purchase, and settle your data-handling approach up front.
• Keep clean records. Track certifications and their currency, training completed, flights conducted, waivers held and their expiration, and maintenance. When a board member, an auditor, or a reporter asks, the answer should be a document, not a memory.

A drone program lives or dies on the unglamorous parts. The flying is the easy part to get excited about. The credential renewals, the currency requirements, the waiver expirations, the maintenance intervals, and the policy reviews are what keep the program legal, safe, and defensible over years rather than a single grant cycle. Those are exactly the things that slip when they live in one person's head or a spreadsheet nobody updates.