A flight plan gets built to a destination, filed, released. Then conditions stop matching the plan. Visibility starts dropping along the route. Winds are picking up. Every indicator says a storm is building right where the flight is headed. Somebody has to formulate a new plan on the spot, or decide the mission does not continue at all, and be sure that call is sound enough to stand behind.
That is operational control at work: the standing authority to notice conditions have moved and to change or kill the plan because of it, whether or not anything ever goes wrong. It has nothing to do with catching a mistake after the fact.
Operational control is not who is holding the controller. It is who holds the authority to launch, continue, or abort the mission, and whether that authority is written down anywhere.
What operational control actually means
The FAA defines operational control plainly: the exercise of authority over initiating, conducting, or terminating a flight. Under Part 121, the pilot in command and the aircraft dispatcher share that authority jointly, not one person alone.
Part 108 imports that same structure and gives it two drone-specific names, each one meant to be named and documented, not just implied by whoever happens to be flying.
Part 108 draws the line: two roles, not one person wearing both hats
Part 108 names two roles and draws a hard split at Launch. The Operations Supervisor holds operational control over the entire operation: strategic authority over who is authorized, what the standards are, and whether the mission goes at all. That authority is exercised in Planning, before anything leaves the ground. The Flight Coordinator takes tactical oversight of individual aircraft once the mission is underway, monitoring and intervening in real time through Enroute and Return.
The split is separation of function, not redundancy. The Operations Supervisor is looking at the macro picture before launch: is this mission authorized, are the standards met, should it go at all. The Flight Coordinator is looking at the micro picture in real time once airborne: what is this specific aircraft doing right now, has anything changed enough to intervene. That's the point: the person making the real-time call mid-mission is not the same person who decided an hour earlier that conditions were fine to launch.
The split does something else too, something easy to overlook: it protects the decision from commercial pressure. An Operations Supervisor who also flies the mission is deciding whether to launch under whatever pressure happens to be sitting on them that day: schedule, client, cost. Separate the roles and name them, and the authority to stop a mission no longer answers to the person who wants it to happen. Not a checklist item, an actual firewall between the person who wants the flight to happen and the decision about whether it should.
Why most drone programs do not have it
Part 107 was built for a different kind of flight: visual line of sight, short flight times, a pilot who could see the aircraft and land it the moment something looked wrong. That risk profile never needed a management-style function, because the person flying was also the only person who needed to be watching.
That's not the operation most programs are running now. Drones stay up for hours. They fly beyond visual line of sight, out of the pilot's sight entirely, into terrain and air space the original rule never accounted for. Part 108 is the FAA's attempt to close that gap with the Operations Supervisor and Flight Coordinator split. Most programs are still operating on Part 107's assumptions and have not rebuilt around what they're actually flying today.
The default pattern: the pilot plans the mission, the pilot flies the mission, and the pilot is the only person who would have to talk themselves out of continuing once it's underway. Nobody is named as Operations Supervisor independent of the person flying, because nothing requires it yet. Part 108 will require it. Part 107 never did.
It's a structural gap nobody has built a bridge for yet, not a character flaw in the operators working inside it.
Floor versus margin, applied to operational control itself
The floor: current rule does not force this. Part 107 is silent on operational control as a named, documented function, and nothing requires a program to build it before Part 108 does.
The margin: building a named authority, written criteria for stop/continue/abort, and a real handoff point between planning and execution is something only you can choose to build before a rule forces it. Every program that waits for Part 108 to make it mandatory will be building this from a standing start while the programs that did it early are already operating on it.
What skipping it costs you
An accountability gap the moment something goes wrong. If an incident happens and nobody can point to who had the authority to stop it, that gap becomes the story.
Insurance and liability exposure. When a policy or a plaintiff's attorney goes looking for who was accountable for the decision to fly, an informal arrangement gives them nothing to point to, and that absence gets read against the operator.
No defensible record. If a regulator, an insurer, or a plaintiff's attorney asks who decided this flight was a go, "the pilot, informally" is not an answer that holds up.
Where this is going
Naming Operations Supervisor and Flight Coordinator is the easy part. Who actually holds that authority in your program, exactly where the handoff happens, and what gets written down to make the split real instead of theoretical: that's a deeper build than one issue can cover, and it's coming.
If you cannot name, right now, who has the authority to stop your next mission, you do not have operational control yet. You have a pilot exercising good judgment, and hoping it holds.
Who holds that authority on your team today? Reply and tell me.