Drones as Communications Relays and Situational-Awareness Tools
Small uncrewed aircraft are often bought as flying cameras, but their value to incident communications runs deeper. Used well, a drone can push live video and mapping to command, and in some configurations it can extend radio or data coverage into the terrain shadows where ground infrastructure falls short. This guide walks through the ideas, the honest limits, and how a small department can start.
Beyond the camera
The first drone a department buys is almost always framed as an aerial camera. It is easy to justify: a view of a roof, a search area, or a hazmat scene that no ground position can match. That is a real benefit, and for many agencies it is where the program stays. But an uncrewed aircraft is a payload platform that happens to hover, and a camera is only one of the payloads it can carry. When you think about the aircraft as a movable point in the sky rather than as a camera on a stick, other uses come into view.
Two of those uses matter most for incident communications. The first is situational awareness: getting a live, overhead, and geolocated picture into the hands of the incident commander so decisions rest on what is actually happening, not on what a crew reported five minutes ago. The second is coverage extension: putting a small relay or repeater payload up high enough to bridge radio or data gaps that terrain, distance, or a large footprint would otherwise create. Both use the same simple fact. Height buys line of sight, and line of sight is the currency of both radio and observation.
Radio at the frequencies most departments use tends to travel by line of sight. A hill, a ridge, or a large building casts a radio shadow the same way it casts a visual one. Raising an antenna even a modest distance can clear an obstruction that a handheld on the ground cannot see past. A drone is one way to gain that height quickly, without waiting for a tower or a high vantage point that may not exist.
The airborne relay concept
An airborne relay is straightforward in principle. You place a radio repeater or a data link on the aircraft, fly it up to a position with clear sight lines to the units that cannot otherwise reach each other, and let it pass traffic between them. A crew working in a canyon, a stairwell shadow, a deep basement approach, or the far side of a ridge can be linked back to command through the aircraft rather than through a ground repeater that the terrain blocks.
Where this earns its keep:
- Terrain shadows and canyons. Wildland, swiftwater, and rural rescue incidents frequently put crews in low ground where handhelds do not reach the command post. An overhead relay can fill the gap that geography created.
- Large-footprint incidents. A sprawling industrial fire, a wide search area, or a mass-gathering event can outrun the effective range of on-scene portables. Height extends the reachable area.
- Comms-degraded areas. When fixed infrastructure is damaged, congested, or simply absent, a temporary airborne link can restore a working channel while permanent options are arranged.
Be honest about what this is and is not. An airborne relay is a temporary bridge, useful for the duration of a flight or an incident, not a substitute for the fixed towers, repeaters, and mutual-aid infrastructure your region depends on every day. It is also technically involved. Putting any transmitting payload on an aircraft has to respect both aviation rules for the flight and communications rules for the transmitter, and the two are separate bodies of authority. Confirm current requirements and get the authorizations that apply before you fly anything that transmits.
People use the terms loosely. A simple relay carries signal from one point to another. A repeater receives on one frequency and rebroadcasts on another so that units out of range of each other can talk through it. Which one you need, and whether your radios and licensing support it, is a conversation to have with your radio administrator and your vendor before you buy hardware, not after.
Tethered drones for persistent overhead work
Battery flight time is the hard ceiling on free-flying drones, and for a long incident that ceiling is a problem. A tethered drone answers it. Instead of running on an onboard battery alone, the aircraft is connected to the ground by a thin cable that supplies power and, often, a protected data link. As long as the ground power holds, the aircraft can stay up far longer than any battery would allow, which changes what it is good for.
Persistent overhead presence opens up roles that a short flight cannot fill:
- Continuous relay. A tethered aircraft can hold a communications payload aloft for the length of a long incident rather than cycling down every time a battery runs low.
- Scene lighting. A lighting payload overhead can illuminate a large work area more evenly than ground lights, which cast long shadows and blind spots.
- Steady observation. A camera that stays in one overhead position for hours gives command a stable, continuous picture instead of intermittent snapshots.
The tether is a trade. You gain endurance and a hardened link, and you give up range and mobility. The aircraft can only go where the cable reaches, the cable itself is something crews have to manage and keep clear of hazards and other aircraft, and the ground power source is now a piece of equipment you have to bring, fuel or charge, and maintain. For a fixed command post at a long-duration event, that trade often makes sense. For a fast-moving search, it usually does not.
Live video and mapping to command
The most immediately useful thing a drone does for most departments is feed the incident commander a live overhead view. Done well, that feed is more than a picture on a screen. It is geolocated, so command can tie what they see to map coordinates and to the positions of assigned units. It can support mapping products such as an overhead image of the whole scene that helps with size-up, resource placement, and documentation after the fact.
To make aerial awareness genuinely useful rather than a novelty, a few things have to be true:
- The feed reaches the decision-maker. Video that only the pilot can see helps the pilot. Getting it to the command post, and ideally to key positions, is what changes decisions.
- Someone interprets it. An overhead view is data, not judgment. A trained observer who can describe what command is looking at, and what it means, is as important as the aircraft.
- It integrates with the rest of the picture. Aerial video is one input alongside radio reports, crew accountability, and dispatch information. It supplements the common operating picture; it does not replace the discipline of maintaining one.
An overhead camera can make a scene look calmer or worse than it is. Thermal artifacts, camera angle, and glare all mislead. Treat aerial imagery as one report among many, corroborated against what crews on the ground are telling you, not as ground truth that overrides them.
Realistic limits
Every honest drone program is built around its constraints, not around a sales brochure. The limits below are not reasons to avoid a program. They are the boundaries you plan inside of.
- Flight time and battery. A free-flying small aircraft measures its endurance in minutes, not hours. Add a heavier payload and endurance drops further. Continuous coverage means either a tether or a rotation of aircraft and charged batteries, with the logistics that implies.
- Weather. Wind, rain, cold, and reduced visibility all limit or ground small aircraft. The incidents where you most want eyes in the sky, storms and severe weather, are often the ones where you cannot safely fly.
- Line of sight and control link. The benefits depend on clear sight lines, and so does the link that controls the aircraft. The same terrain and structures that block radio can degrade the control and video link. Lose the link and you lose the asset.
- Payload weight. Small aircraft carry small payloads. A relay, a light, and a good camera all compete for the same limited lift, and adding any of them cuts endurance. You cannot bolt everything onto one small airframe.
- Airspace and regulation. Flights must follow the aviation rules that apply to your operation and location, and some operations require specific authorizations. These vary and they change, so the standing instruction is to confirm current rules and obtain the authorizations that apply before you plan around a capability.
- Trained pilots and cost. Aircraft, payloads, batteries, and maintenance are the visible costs. The larger one is people. Pilots must be trained and current, and a program needs enough of them that a qualified pilot is actually available when a call comes in, not just on paper.
The most important limit is the one that is easiest to forget: a drone is not a replacement for ground communications infrastructure. Towers, repeaters, mutual-aid channels, and interoperability agreements are what carry your traffic on an ordinary day. A drone is a tool that fills specific gaps on specific incidents. Build the ground foundation first, then add the aircraft as a supplement.
Coordinating with the incident comms plan
A drone that is not written into the incident communications plan is a loose end. If it is carrying a relay or repeater payload, it is now part of your communications architecture, and it has to be documented like any other part: which channels it bridges, who it serves, and what happens to those units if it goes down. Crews relying on an airborne link need to know it is airborne, and need a fallback for when the battery runs out, the weather turns, or the link drops.
Just as important is airspace deconfliction. The moment you put an aircraft over an incident, you have created an air operation, and it has to be coordinated with any other aircraft that might be there: medical helicopters, law enforcement aviation, and firefighting aircraft. This is a life-safety issue, not a paperwork one.
- Assign responsibility. On a larger incident, air operations belong to a designated position in the command structure, not to whoever happens to be holding the controller.
- Deconflict before you launch. Know what else is or might be flying, and have a clear procedure to clear the airspace immediately for inbound crewed aircraft. A medical helicopter always takes priority.
- Brief the frequencies. Whoever is flying needs a reliable way to talk to command and to be reached instantly. The drone pilot cannot be on a channel no one is monitoring.
- Write down the fallback. If the aircraft is providing a relay, the comms plan states in plain language what units switch to when it is no longer overhead.
Treat every flight over an incident as an air operation from the start. That means it appears in the incident action plan, its pilot is reachable on a monitored channel, and there is a standing rule that the airspace clears immediately for any crewed aircraft. Coordination is what keeps a helpful tool from becoming a hazard.
Practical first steps for a small department
A small department does not need to leap to tethered relays and mapping payloads. The path in is incremental, and each step is useful on its own.
- Start with awareness, not relay. A basic program that puts a live overhead camera in front of command delivers value quickly and teaches the fundamentals. Coverage extension is a more advanced and more regulated step to grow into later.
- Get the people right first. Identify who will be trained, make sure they can maintain currency, and confirm you have enough pilots that the capability is real when a call comes in. A single trained pilot is a hobby, not a program.
- Confirm the rules that apply to you. Before you build workflows around any capability, verify the current aviation rules and the authorizations your operations require. Do this early, because it shapes what you can realistically plan for.
- Write the small procedures now. How the pilot reaches command, how airspace is cleared for a medical helicopter, who decides to launch and to land. These cost nothing and prevent the worst outcomes.
- Look for shared resources. A regional team, a mutual-aid partner, or a shared program can put capability within reach of a department that could never staff and fund one alone. Coordination agreements often beat buying your own airframe.
- Keep records from day one. Pilot currency, maintenance, battery cycles, incident use, and your standard procedures should live somewhere organized and retrievable, not in a folder on one person's laptop.
The goal is not to have the most impressive drone. It is to have a capability you can rely on, that your crews understand, and that fits cleanly into how you already run an incident. Modest and dependable beats ambitious and fragile every time.
Takeaways
- A drone is a payload platform, not just a camera. Its two biggest communications roles are pushing live situational awareness to command and, in some configurations, extending radio or data coverage into gaps.
- Height buys line of sight, which is what both radio and observation depend on. That is the core reason an airborne relay can bridge terrain shadows, canyons, and large or degraded scenes.
- Tethered drones trade range and mobility for endurance, making them suited to persistent relay, lighting, and observation at long, fixed incidents.
- The limits are real and non-negotiable: battery and flight time, weather, line of sight and control link, payload weight, airspace and regulation, and the cost of trained, current pilots.
- A drone supplements ground communications infrastructure. It never replaces the towers, repeaters, and mutual-aid channels you rely on every day.
- Any drone over an incident is an air operation. Write it into the comms plan, deconflict the airspace, and clear immediately for crewed aircraft.
- Small departments should start with awareness, get the people and procedures right, confirm current rules and authorizations, and consider shared regional resources before buying their own.
A drone capability is only as reliable as the records and plans behind it. RunBoard gives your department one place to keep incident communications plans, standard procedures, pilot and equipment records, and training and currency tracking organized and retrievable, so that when the aircraft goes up, everyone knows the channels, the fallback, and who is responsible. Confirm the current aviation rules and authorizations that apply to your operations, then let RunBoard keep the supporting documentation in order.