14 CFR Part 107 Commercial Drone Operations

Regulatory Context

14 CFR Part 107, codified at 81 Fed. Reg. 42064 (June 28, 2016), is the FAA's foundational small-UAS operating rule. It applies to civil aircraft weighing under 55 pounds and prescribes operating limitations including 400-foot above-ground-level altitude, daylight or civil-twilight operation absent waiver, 100-mph maximum groundspeed, and visual-line-of-sight contact between the remote pilot in command and the aircraft at all times under §107.31. Section 107.39 prohibits operations over human beings absent a categorical compliance pathway, and §107.41 prohibits operations in controlled airspace without prior Air Traffic Organization authorization, typically delivered through the Low Altitude Authorization and Notification Capability (LAANC).

The 2021 Operations Over People final rule (86 Fed. Reg. 4314) established four categories of permissible overflight, ranging from sub-0.55-ounce Category 1 micro aircraft to Category 4 vehicles holding airworthiness certificates under Part 21. The same rulemaking introduced 14 CFR Part 89 Remote ID, which since September 16, 2023 has required nearly all registered sUAS to broadcast a unique identifier, position, velocity, and control-station location at one-second intervals. Operators flying under a Section 333 grandfathered exemption, the predecessor framework that authorized commercial UAS operations between 2014 and the Part 107 effective date in August 2016, retain narrow legacy authority but receive no relief from Remote ID or operations-over-people obligations.

Beyond-visual-line-of-sight (BVLOS) operations remain available only under §107.205 waivers or §107.200 certificates of waiver, with the FAA's BVLOS Aviation Rulemaking Committee final report (March 2022) and the proposed Part 108 framework signaling a structured transition toward routine BVLOS authority for package delivery, infrastructure inspection, and public-safety missions. Agricultural applicators operating under 14 CFR Part 137 face an overlapping rule set covering dispensing of economic poisons, while public-aircraft operators rely on certificates of authorization issued under 49 U.S.C. §40102. Each pathway adds operator-intent declarations, mission-scope limits, and post-flight reporting obligations that current command stacks satisfy through paperwork rather than structure.

Architectural Requirement

Each commanded sUAS actuation, takeoff, waypoint commit, payload release, and return-to-launch, occurs against a layered authority stack: the remote pilot's §107.12 certificate, the registration record under Part 47 or Part 48, the airspace authorization (Class B/C/D/E surface via LAANC or §107.41 ATO approval), any §107.205 waiver, the Part 89 Remote ID broadcast obligation, and applicable state or local restrictions preserved by the FAA Reauthorization Act of 2018. A compliant architecture must capture the operator's declared intent, the precise authority claimed for each segment, and the actuation outcome in a form that survives later FAA enforcement review under 49 U.S.C. §44701 or NTSB accident investigation under 49 CFR Part 830.

The architecture must also handle graduated outcomes. Wind exceedance, geofence intrusion, lost-link events, and detect-and-avoid alerts rarely admit a binary continue-or-abort decision; the operator's Part 107 obligation is to maintain control and avoid hazard to people and property, which often calls for partial execution, deferral to a holding pattern, or refusal of the next planned segment while completing the current one safely. The substrate must therefore expose actuation modes that map to those operational realities and record which mode was selected and why.

Why Procedural Compliance Fails

Current Part 107 compliance leans on pilot attestation, paper preflight checklists, and post-incident reconstruction from disparate logs: ground-control-station telemetry, autopilot black box, LAANC authorization receipts, and the pilot's recollection. When the FAA Office of Investigations opens a §44709 certificate action or when an NTSB investigator arrives after a §107.39 overflight injury, the operator must reconstruct the authority chain that justified each commanded movement. The 2021 Philadelphia Eagles parade incident and the 2024 Lionel Messi Inter Miami match overflight enforcement actions both turned on the operator's inability to produce a contemporaneous, structured record of which authority covered which segment.

BVLOS waivers compound the problem. A §107.205 waiver typically conditions authority on specific aircraft, specific pilots, specific operating volumes, and specific contingency procedures; the waiver is void the moment any condition lapses. Procedural compliance treats the waiver as a static document on file, but the actual operating envelope shifts second by second as winds change, ADS-B traffic enters the volume, or ground-risk populations move. Without a structural substrate that evaluates each commanded actuation against the live authority envelope, operators routinely fly outside their waiver without knowing it until enforcement arrives.

Remote ID enforcement under 14 CFR §89.110 introduces a third failure mode. The broadcast obligation is continuous, but procedural stacks treat it as a configuration item set at boot. When a Remote ID transmitter fails mid-flight, the procedural stack continues commanding actuations the aircraft is no longer legally permitted to perform, and the operator learns of the violation only when the FAA Law Enforcement Assistance Program receives a citizen report.

What Governed Actuation Provides

Governed actuation, as an Adaptive Query primitive, treats every commanded sUAS movement as a query against a published authority graph and exposes four graduated outcomes: continue, defer, partial, and refuse. Continue records the claimed authority and proceeds. Defer holds the actuation pending an authority refresh, useful when a LAANC authorization is approaching expiration or a Remote ID heartbeat is delayed. Partial executes a safe subset, climb to loiter altitude but withhold the planned waypoint advance, when the authority envelope covers some but not all of the commanded movement. Refuse declines the actuation entirely and records the refusal as a first-class observation, not a silent failure.

Harm minimization is built into the refusal path. A refused takeoff into degraded conditions returns the aircraft to a powered-off state on the ramp; a refused waypoint advance during a Part 137 agricultural application returns the aircraft to a holding pattern over previously treated ground rather than untreated population areas. Post-actuation verification closes the loop: each commanded movement is followed by a structured observation comparing intended state to achieved state, with deviations recorded against the authority that covered the command. This produces the contemporaneous, structured record that §44709 enforcement and Part 830 investigation both require.

The primitive composes naturally with multi-authority operations. A Part 137 applicator operating under a §107.205 BVLOS waiver in Class E surface airspace claims authority from four sources simultaneously; governed actuation evaluates each commanded actuation against all four and records the composite admission or the specific authority that refused.

Compliance Mapping

The mapping from Part 107 obligations to governed-actuation primitives is direct. Section 107.31 visual-line-of-sight becomes a continuous authority predicate evaluated against pilot-station telemetry; loss of VLOS triggers refuse on any actuation that would extend the aircraft beyond the recoverable envelope. Section 107.39 operations-over-people categories become geofenced authority overlays keyed to the airworthiness category of the specific aircraft, with the substrate refusing waypoint commits that would carry a Category 2 vehicle over a Category 4 population. Section 107.49 preflight familiarization becomes a structured intent declaration captured at mission start and referenced by every subsequent actuation.

Part 89 Remote ID maps to a continuous broadcast-health predicate; transmitter failure converts continue to defer or refuse depending on whether the aircraft can be safely recovered before the broadcast obligation lapses. Part 137 agricultural-applicator obligations, including the §137.19 commercial certificate and §137.41 personnel requirements, map to authority claims that gate dispense actuations specifically rather than flight actuations generally. Section 333 grandfather authority, where it remains operative for legacy operators, maps to a narrowly scoped authority that the substrate refuses to extend beyond its statutory boundaries.

Adoption Pathway

Adoption begins at the ground control station rather than the airframe. Existing autopilots already expose the command surface; the substrate sits between mission-planning software and the autopilot link, evaluating each commanded actuation against the operator's declared authority graph before the command reaches the aircraft. Initial deployments target high-stakes operations, BVLOS waiver holders, Part 137 applicators, and public-safety operators flying under certificates of authorization, where the cost of an enforcement action or accident materially exceeds the integration cost.

The second adoption wave follows Part 108 rulemaking. The proposed framework conditions routine BVLOS authority on demonstrated safety case, and a structural governed-actuation substrate produces exactly the evidence the FAA Aircraft Certification Service needs to evaluate a type design or operational approval. Operators arriving at the Part 108 application desk with reconstructable records of every commanded actuation, the authority claimed, and the post-actuation verification result hold a material advantage over operators who arrive with attestations and disparate logs. As Remote ID enforcement, UTM integration under the FAA's UAS Traffic Management framework, and emerging detect-and-avoid standards mature, the structural substrate becomes the precondition for participation rather than a competitive feature.