Urban Operations Communications

Why Communications Matter in Urban Environments

Urban operations multiply communication problems. Buildings block line-of-sight RF, cell infrastructure can fail or be deliberately disrupted, and the density of both friendly and unfriendly radio traffic makes the spectrum noisy. The 2020 Christmas Day Nashville bombing illustrated this directly: damage to a single AT&T facility took out cell, internet, and the fiber backhaul that other carriers depended on across a wide area of Middle Tennessee. A 2010 flood event in Hickman County took cell towers offline within 24-48 hours of grid power loss, depending on each tower’s generator fuel.

The lesson from those events is that information — not water, food, or fuel — is the most contested commodity once infrastructure breaks. Knowing which roads are passable, which neighbors need help, and where resources are staged matters more than any single physical resource. Urban operators face this problem in compressed form: short distances, dense obstacles, time-critical decisions, and a strong likelihood that the everyday infrastructure (cell networks, public Wi-Fi, internet routing) is either degraded or untrusted.

Building the Network Before You Need It

A communications network is built out of people first and hardware second. The hardware question — “which radio should I buy?” — cannot be answered without first knowing who is on the network, what they already own, what frequencies they monitor, and when they monitor them. Trying to build that network during the disaster itself is a losing proposition: batteries are dead, people are stressed, and there is no time to program radios or coordinate channels.

Practical steps to take before any operation:

• Identify who is actually in the network. Trust matters as much as access — historically, communications networks built for contested environments are organized around vetted relationships, not just shared frequencies.
• Standardize on hardware where possible. A network where everyone runs the same radio model and the same programming is dramatically easier to operate than a patchwork.
• Document call signs, frequencies, schedules, and meet-up locations. If batteries are limited, pre-arranged transmission windows save power and reduce the time the network is emitting.
• Plan for terrain. In urban areas, certain rooftops, hilltops, or open intersections may be the only places a handheld can reach a repeater or another node. Identify those in advance.
• Plan power. A four-hour battery in a radio that goes dead at the wrong time is the same as no radio at all. Have charging plans that don’t depend on grid power.

Choosing Radio Hardware for Urban Use

The radio market for small-team use breaks into a few rough categories.

Cheap analog handhelds (Baofeng-class). A UV-5R or similar can transmit and receive across UHF and VHF and is capable of hitting FRS, GMRS, MURS, ham, and business-band frequencies. Build quality, water resistance, and front-end filtering are all mediocre. They are useful precisely because they are everywhere — knowing how to program and operate one is a baseline skill, and in an emergency they may be the only way to reach a neighbor who has the Walmart blister-pack version of the same hardware.

Digital business-band (Hytera-class DMR). DMR provides better error correction, slightly better range and battery efficiency, and — because fewer people use DMR than analog FM — less interference and a smaller listening audience. With the appropriate model and license, AES-256 encryption (including rotating keys) is available. Encryption protects message content, not location: any transmitter is detectable and can be direction-found regardless of whether the payload is encrypted.

Mesh data radios (Meshtastic, Beartooth, goTenna Pro). These trade voice bandwidth for digital messaging that hops between nodes, building an ad hoc network as devices move. They pair with a phone over Bluetooth and integrate with mapping software. Range per node is typically 1-2 km in broken terrain, less in dense urban environments where 900 MHz signals struggle to penetrate building materials. Adding nodes (including elevated repeater nodes) extends coverage. Beartooth Mark II adds voice and image messaging on top of position and text, at roughly the middle of the price/performance band.

High-end MANET radios (Persistent Systems MPU5, Silvus StreamCaster). These move enough data to handle drone telemetry, video feeds, and robotic control. They generally operate at higher frequencies (around 1-2.4 GHz) and higher wattages. Higher frequency means worse penetration through urban obstacles — a real consideration for street-level operations.

Map and Software Layer

Voice on a handheld is a thin pipe. Pairing radios with software that handles position reporting, markers, and routes drastically reduces what has to be said over the air.

ATAK (Android Team Awareness Kit). Originally military, now available in a public release. ATAK combines a powerful offline mapping engine — satellite imagery, elevation, GIS overlays, 3D terrain — with a coordination layer that shares positions, markers, and routes between users on the same network. It is the de facto coordination tool for U.S. small-unit operations and is rapidly being adopted by first responders. The public version has plugins disabled, which limits the radios it can natively pair with; specific models from Beartooth, goTenna, and Meshtastic have ATAK plugins on the civilian version.

OsmAnd. Built on OpenStreetMap vector data with optional topo, hillshade, and satellite overlays. Offline maps for the entire United States run roughly 5-6 GB. It handles road routing, points of interest, building outlines, power lines, and waterways, plus offline Wikipedia for geographic features. It is significantly easier to teach to new users than ATAK and works well for urban navigation where building footprints, road networks, and routing matter most.

APRSdroid. Sends position and short text messages as APRS packets through the audio interface of any radio — including a $20 Baofeng with a $20 cable. It does not provide the polish of a commercial digital system, but it works with hardware most people already own.

Radio Etiquette

Hardware and software only matter if the traffic going across them is usable. Three principles govern every transmission: short, clear, powerful.

• Short — minimize transmit time. Longer transmissions are easier for an adversary with direction-finding equipment to locate. Depending on the threat, transmissions should be held to roughly 3-8 seconds, and longer reports should be segmented with the word “break” between elements.
• Clear — concise, unambiguous, no filler words. Use call signs every time on shared nets.
• Powerful — speak with energy, mic about an inch from the mouth, talking past the microphone rather than directly into it. Key the push-to-talk only while actually speaking — not before, not after.

A small, universal vocabulary covers most traffic: “[receiver], this is [sender]” to open; “over” to hand off; “out” to end the conversation; “roger” to acknowledge a directive; “copy” to acknowledge information being recorded; “say again” to request a repeat (avoid “repeat,” which has a separate meaning in some contexts); “affirm”/“negative” instead of yes/no; “station calling” to ask for a missed call sign; and “correction” to fix a previous transmission. A SALUTE-style report (Size, Activity, Location, Unit, Time, Equipment) broken into short segments separated by “break” handles most observation reporting.

Encryption protects content but does nothing about emissions. In a contested urban environment, the operator’s discipline — keeping transmissions brief, segmented, and infrequent — is what reduces the chance of being located.

Detecting Other Networks

A software-defined radio (SDR) like an RTL-SDR — a USB device in the $20-40 range — paired with a phone or laptop allows wide swaths of spectrum to be observed at once. This is useful in two directions: finding people who need help (locating stranded users on FRS or other consumer bands) and understanding what other transmitters are active in an area. Frequency-hopping signals that used to be hard to intercept are visible across the waterfall display of a modern SDR. Interpreting what is seen requires study; the software does not label transmissions for the operator.

Putting It Together

A workable urban communications setup for a small team typically looks like:

1. A pre-built network of known, trusted people with documented call signs, frequencies, and schedules.
2. A common radio platform — analog for breadth, DMR or a mesh data radio for selectivity and encryption.
3. A mapping and coordination layer (ATAK or OsmAnd) on a phone, ideally pre-loaded with offline maps for the area of operations.
4. A digital messaging path (Meshtastic, Beartooth, goTenna Pro, or APRS) so that position and short text traffic does not consume voice channel time.
5. Disciplined radio etiquette to keep transmissions short and emissions minimized.
6. Power planning — spare batteries, USB-C battery packs, and charging methods that survive grid loss.
7. An SDR for situational awareness of the broader spectrum.

None of these layers substitutes for the others. A high-end radio without a network is a paperweight; a network without etiquette is a beacon; a phone without offline maps is a brick the moment infrastructure goes down. The work of building all of these layers is done before anything goes wrong.