Air support video belongs on the command wall. Not just in the aircraft
A helicopter has the best seat over a scene. That advantage is wasted if the only people who see it are on board. The feed has to reach command, live.
A vehicle pursuit is running and the helicopter is up. The tactical flight officer has the whole thing: the suspect vehicle, the turns before they happen, the units strung out a block or two back. Command and those ground units are getting it the only way they can, one radio sentence at a time, always a beat behind what the aircraft already sees. The worst of it is the hand-off, when the suspect bails or cuts down a side street and the air has to talk the closest unit onto him by description alone. That is where the seconds go. The best view of the chase and the people who have to act on it are in two different places.
The relay problem
When air support video only reaches command through verbal relay, you lose the thing that made it valuable: directness. What command acts on is a description of the feed, a few seconds old, filtered through someone else’s read of the scene. The same relay problem affects any drone feed that's stuck with the pilot.
Air support as one feed among many
You have an aircraft overhead and radios on every channel, but that doesn’t give everyone responding a shared picture. BabbarOps brings the air support feed onto the same shared wall as everything else, drones, fixed cameras, and witness video, live, for everyone with a need to know.
- One login to watch. Command and supporting units open the agency account and see the air feed directly.
- Every altitude on one wall. Helicopter overhead, drones on the perimeter, cameras at ground level, one picture.
- Hardware agnostic. It works with the aviation assets you already operate.
From the air to the plan
Because the feed sits beside the live incident workspace, what air support sees feeds straight into the command view everyone is acting on: assignments, perimeter, and intel updated against the same operational picture. The aircraft’s perspective stops being a separate channel.
The aircraft sees it; right now everyone else hears about it. Close that gap and the hand-off changes: the closest unit is looking at the same frame as the pilot, and you stop losing the seconds it takes to describe a thing that is already on screen.
Yes. BabbarOps brings helicopter and fixed-wing video onto the same shared wall as drones, fixed cameras, and witness video. Command and supporting units open the agency account with one login and see the air feed directly, instead of hearing about it over the radio.
Yes. BabbarOps is hardware agnostic and works with the aviation assets you already operate. Feeds come in over standard streaming protocols like RTMP, RTSP, and SRT, so no proprietary hardware is required.
When air support video only reaches command through verbal relay, command acts on a description of the feed, a few seconds old and filtered through someone else's read of the scene. Putting the live feed on the command wall removes that relay and lets command look at the scene directly.
No. BabbarOps live video is live-only and is not retained, so there is no recorded file in the platform after the stream ends. BabbarOps is not a system of record; your agency's existing evidence systems keep that role.
Sukh Bhela is a California police sergeant who has served as a UAS operator, UAS supervisor, and incident commander during critical incidents. His experience leading patrol operations and integrating drone technology into public safety responses led him to found BabbarOps, where he builds tools for live situational awareness and incident command. He writes about policing, drone operations, leadership, and the technology shaping the future of emergency response.
The views expressed here are the author's own, written in his personal capacity. They do not represent, and are not made on behalf of, any law enforcement agency or employer.
BabbarOps is an independent commercial product and is not affiliated with or endorsed by any law enforcement agency. Capabilities depend on agency hardware and network conditions.