Insights / What a drone operations control center actually does
The room, and why it exists
An airline operations control center (OCC) is not where flights are planned. Planning happened months ago. The OCC is where the plan meets the day: a thunderstorm over the hub, a crew member timing out, an aircraft with a fault that will take four hours to clear. The room exists because a plan that cannot be changed in real time, by someone with the whole picture and the authority to act, is not an operation. It is a hope.
Drone operations are arriving at the same realization from the other direction. A company buys three aircraft, trains two pilots, wins an inspection contract, and finds that the hard part is not flying. It is knowing where the aircraft are, whether today's flight is legal and safe, who decides when it is not, and proving all of that afterward. Those are the four functions of an OCC, and they scale down to a fleet of three without losing their shape.
Function one: the live picture
The wall of an airline OCC is a map. Every aircraft, its position, its status, its next constraint. Nobody in the room asks "where is flight 214" because the answer is on the wall. The picture is shared, so two people never act on different versions of reality.
For a drone fleet this is live telemetry on a map: position, altitude, battery, link quality, mission progress, for every aircraft, visible to the operator on site and to whoever is responsible back at base. The point is not the map itself. The point is that a decision made without the picture is a guess, and that the picture is the same for everyone. The live map in Airffic World exists for exactly this reason; a Raspberry Pi pushing position data is enough to put a hobbyist's aircraft on it.
Function two: the rules, applied before the flight
The OCC does not improvise legality. Crew duty limits, aircraft airworthiness, airspace restrictions and weather minima are known before the aircraft moves, and the system flags a violation before a human has to remember it. The rule lives in the process, not in a person.
Drone regulation is national and it moves fast. In Japan the rules changed nearly every year from 2015 to 2025: registration above 100 g, Remote ID, four categories of permit, no-fly zones layered over airports and cities. A pilot cannot hold all of that in memory, and should not have to. The OCC function is a pre-flight confirmation that encodes the current rules and refuses to clear a flight that does not meet them. The five-stage pre-flight checklist is the paper version; the software version reads the same list and adds the airspace check the paper cannot do. For the rules themselves, the guide to flying legally in Japan covers registration, DIPS, Remote ID and permits in the order an operator meets them.
Function three: the decision, and who owns it
This is the function most drone operations skip, and it is the one an airline would never skip. In the OCC there is a duty manager. When the storm arrives, one person decides whether flight 214 holds, diverts or cancels, and everyone knows who that person is. Authority is explicit, so the decision is fast and nobody is waiting for permission from someone who is not watching.
A drone operation needs the same thing at its own scale: a named person with go/no-go authority for each flight, criteria they apply (wind, visibility, airspace, aircraft state, crew state), and a rule for what happens when the criteria are not met. "The pilot decides" is fine if the pilot has the picture and the criteria. "Whoever is around decides" is a single point of failure dressed up as flexibility. The article on running drone inspection as a system goes into how this gets written down so it survives the departure of the one person who used to do it by instinct.
Function four: the record
Every airline flight leaves a record: who flew, what was checked, what was decided and why, what happened. The record is not paperwork for its own sake. It is what lets the airline learn from an incident instead of repeating it, and it is what the regulator asks for first.
For drones the record is the flight log, the pre-flight confirmation as completed, the go/no-go decision and its basis, and the telemetry. When something goes wrong, and eventually something does, an operation with the record can explain itself. An operation without it is relying on memory in the one situation where memory is least reliable.
The four functions at three sizes
| Function | Airline OCC | Drone fleet of 3 | Drone fleet of 30 |
|---|---|---|---|
| Live picture | Wall map, every aircraft, every status | Telemetry on a shared map, visible on site and at base | Same, with alerts on link loss, low battery, geofence breach |
| Rules before flight | Dispatch system enforces duty, airworthiness, airspace | Checklist app that knows current national rules | Automated airspace and permit checks per mission |
| Decision authority | Duty manager, named per shift | One named person with go/no-go criteria | Duty controller role, rotated, with written criteria |
| Record | Full flight record, retained for years | Flight log plus completed checklist | Searchable logs, incident reports, trend review |
Nothing in the right-hand columns requires an airline's budget. It requires deciding that the functions matter, and then choosing tools that do them rather than tools that only fly the aircraft.
What an OCC is not
It is not a control tower. Air traffic control separates aircraft in shared airspace and belongs to the state. UTM, the drone equivalent, is being built by governments and large providers. An OCC is the operator's own room: it manages the operator's fleet within the airspace the state allows. Confusing the two leads companies to wait for a national system that will never manage their fleet for them.
It is also not a person. The most common failure is a very good operations lead who is, in effect, the OCC. Everything works until they take a holiday. The functions above are designed so that the room keeps working when the best person in it is away, which is the whole reason airlines built rooms instead of relying on heroes.
Where automation changes the job
As flights move to pre-planned routes and autonomous execution, the human job shifts from flying to monitoring. The OCC functions do not go away. They become more important, because now the question is not "can the pilot fly this" but "who takes over, and how, when the automation meets something it was not designed for." The airline answer is that the controller is always ready to intervene and the system is always designed to be intervened in. How that applies to autonomous drone routes is covered in the guide to autonomous drone operations.
Build the four functions first. Automation sits on top of them, not instead of them.