Part 108 Operations Supervisor: Role, Authority, and Requirements

The person watching one drone is not the person the FAA proposal makes responsible for the whole operation.

That is the cleanest way to understand the proposed Part 108 Operations Supervisor. The role would sit above individual flights, hold operational control across an assigned operation, and carry final authority for safe and secure operations. It is closer to a director of operations than a renamed remote pilot.

This article explains the proposal as written in the FAA’s August 2025 notice of proposed rulemaking. Part 108 is not final, and no operator can claim compliance with a rule that does not yet exist. For the broader status, scope, permits, certificates, and BVLOS framework, start with our Part 108 BVLOS guide.

What is a Part 108 Operations Supervisor?

Under proposed 14 CFR 108.305, every Part 108 operator would need at least one Operations Supervisor. The FAA describes this person as directly responsible for, and the final authority over, the operation of the unmanned aircraft under that person’s assigned responsibility.

The proposal gives the role four connected jobs:

• Maintain operational control at the company or assigned-area level.
• Make sure operations follow Part 108, the operator’s FAA authorization, and its company operations manual.
• Make sure required personnel are trained and knowledgeable before operations begin.
• Serve as a primary company contact for FAA oversight.

Those duties make this an accountable management role, not a shift label. A company could delegate individual tasks, but it could not delegate away the Operations Supervisor’s final responsibility for the operation under that supervisor’s control.

Operations Supervisor vs. Flight Coordinator

The proposed rule separates strategic operational control from tactical aircraft oversight.

Question	Operations Supervisor	Flight Coordinator
Primary scope	The operator’s whole operation, or a clearly assigned portion of it	One aircraft or an approved group of aircraft during flight
Type of oversight	Strategic and organizational	Tactical and real time
Core responsibility	Operational control, compliance, personnel readiness, and final safety authority	Monitor the flight and intervene when needed to maintain safe conditions
Required for every operator?	Yes, at least one under the proposal	Only when required by the aircraft design and manufacturer’s operating instructions
FAA relationship	Named management contact; changes would be reported to FAA	Assigned to flights by the operator

A Flight Coordinator could respond to a lost-link alert, unexpected traffic, or an aircraft that leaves its route. The Operations Supervisor would be responsible for whether the company had a sound lost-link procedure, whether coordinators were trained to use it, whether staffing and aircraft ratios were acceptable, and whether the operation should continue after a pattern of failures.

The same person might be qualified to fill both roles in a small organization, but the duties do not become interchangeable. During a demanding flight, tactical monitoring cannot quietly disappear because that person is also handling company-level decisions.

What operational control means here

Operational control is more than the ability to touch the controls. It is the authority to initiate, conduct, continue, divert, pause, or terminate an operation within the operator’s approved system.

In practical terms, the Operations Supervisor should have the authority to say:

• “Do not launch. The weather, staffing, or system status is outside our limits.”
• “Pause this route while we investigate repeated command-and-control interruptions.”
• “Reduce the number of aircraft assigned to each Flight Coordinator.”
• “This procedure no longer matches the operations manual. We stop until it is corrected.”

If a commercial manager can overrule those decisions to protect a delivery target, the title alone would not create meaningful operational control. Authority, escalation paths, and stop-work protection would need to exist in the company’s procedures and daily practice.

Proposed qualifications and knowledge

The FAA does not propose a new airman certificate for the role. Instead, the person would need to be qualified through training, experience, or other expertise. The notice gives UAS military experience and an academic background as examples, not exclusive routes.

The proposed knowledge standard is broad. An Operations Supervisor would need to know:

• The company’s policies and procedures.
• Aviation safety standards and safe operating practices.
• Practices for maintaining secure facilities and operations.
• The regulatory requirements of Part 108.
• The aircraft, associated elements, flight plans, and other operational roles well enough to oversee the system.

The proposal compares the position to a director of operations under Parts 121 and 135. That does not mean a Part 108 operator would inherit every airline requirement. It signals the level of company-wide awareness and authority the FAA expects.

One supervisor or several?

The proposal would allow an operator to use multiple Operations Supervisors. Each could be responsible only for the aircraft and operations within an assigned area of responsibility.

That flexibility can support round-the-clock or multi-state fleets, but it creates a boundary problem. A useful assignment should answer five questions:

1. Which aircraft, routes, sites, and time periods are under this supervisor?
2. When does responsibility transfer, and how is the handoff recorded?
3. Who has final authority during an overlapping or abnormal event?
4. What operating picture must be shared across regions or shifts?
5. Who can ground the broader fleet when a common system fails?

“West region” may be too vague if an aircraft crosses the boundary, a network service supports both regions, or a supervisor’s shift ends during a diversion. The operations manual would need a specific answer before the edge case occurs.

Worked example: a multi-city delivery fleet

Imagine an operator conducting package delivery flights in three cities. Each city has Flight Coordinators monitoring aircraft. One Operations Supervisor covers the morning shift.

Before launch, the supervisor reviews staffing, weather, notices and airspace constraints, system availability, unresolved maintenance items, and any overnight safety reports. The supervisor confirms that each coordinator’s assigned aircraft load fits the approved procedures.

Thirty minutes later, coordinators in two cities report intermittent command-and-control latency. Each coordinator manages the aircraft in front of them, but the shared symptom suggests a fleet-level problem. The Operations Supervisor compares the reports, pauses new launches that rely on the same service, invokes the company’s escalation procedure, and decides whether aircraft already airborne should land at planned contingency sites.

That split is the point. Flight Coordinators protect individual flights in real time. The Operations Supervisor recognizes the common risk and controls the operation as a system.

Worked example: inspection routes after a storm

An infrastructure company plans BVLOS inspections after a major storm. Customers want immediate imagery, but weather cells remain nearby and temporary airspace restrictions are changing.

A field team verifies equipment and launch sites. Flight Coordinators monitor assigned aircraft. The Operations Supervisor checks that the latest restrictions have been incorporated, confirms which routes remain within the operator’s authorization, reviews emergency recovery locations, and sets conservative launch limits.

When a client asks the team to extend a route beyond the approved area, the supervisor has the authority to refuse. A sales promise does not change the operations manual or the operator’s FAA limitations.

Edge cases the operations manual should resolve

A Flight Coordinator calls out sick

The Operations Supervisor should not simply spread aircraft across the remaining coordinators. The operator would need to stay within its approved procedures and what each coordinator can safely manage. The right answer may be fewer flights.

An automated aircraft needs little attention

Automation can change the coordinator-to-aircraft ratio, but it does not erase accountability. The ratio would still depend on aircraft design, operating instructions, environment, procedures, and what a coordinator can reasonably handle.

The supervisor loses the common operating picture

If the tools needed to exercise operational control become unavailable, the company needs a defined degraded-mode response. Continuing because each aircraft still appears stable could leave no one able to see fleet-wide risk.

A handoff happens during an abnormal event

Responsibility should not transfer through an informal message that omits the active hazard. The outgoing and incoming supervisors need a positive handoff with aircraft status, open risks, restrictions, and pending decisions.

A small operator has one person in several roles

The proposal does not automatically require a large management team. It does require the duties to be performed. A small operator should show when one person can safely combine roles and when workload or conflicting responsibilities require another qualified person.

Changes in the role would be reportable

Proposed section 108.305(b) would require an operator to inform the FAA within 10 days after changing the person assigned as Operations Supervisor. That detail matters because the FAA expects this person to be a primary point of contact and part of its continuing oversight.

An operator should therefore treat succession as an operational issue, not just a human-resources update. Qualification records, access, authority, manual knowledge, and active-risk handoffs should be ready before the new assignment takes effect.

What operators can prepare now

No one needs to appoint a regulatory Part 108 Operations Supervisor today. The rule is still proposed. Operators can still use the proposal to test whether their management system is ready for scaled BVLOS work.

1. Draw the authority map. Identify who can approve, pause, divert, and terminate operations.
2. Define areas of responsibility. Tie each shift, site, route, aircraft, and shared service to an accountable owner.
3. Separate strategic and tactical workload. Do not assume the person monitoring flights can also manage every fleet-level decision.
4. Write handoff criteria. Specify what must be transferred and when responsibility changes.
5. Build evidence of qualification. Keep role-based training, experience, exercises, and competency records.
6. Test stop-work authority. Run scenarios where schedule pressure conflicts with safety limits.
7. Track the final rule. Recheck the regulatory text before changing job descriptions or compliance systems.

The takeaway

The proposed Operations Supervisor is the person who owns the safety and compliance picture above individual aircraft. Flight Coordinators would manage tactical flight risk. The Operations Supervisor would make sure the organization, people, procedures, and systems are fit to operate, then hold final authority over the operation within an assigned scope.

That distinction is central to the FAA’s proposed move from one pilot controlling one aircraft toward organizations supervising automated BVLOS fleets. It is also still a proposal. Job titles, qualifications, timelines, and duties may change before a final rule becomes effective.

Primary source

• FAA and TSA, Normalizing Unmanned Aircraft Systems Beyond Visual Line of Sight Operations, 90 FR 38212 (August 7, 2025), especially proposed sections 108.120, 108.305, and 108.310.