Regulatory watch
The push toward a standardized beyond visual line of sight (BVLOS) framework remains the central focus for commercial operators. As the FAA progresses with rulemaking initiatives broadly associated with Part 108, enterprise programs should track several core regulatory themes:
- Detect and Avoid (DAA) criteria: Regulators continue to emphasize performance-based standards over prescriptive hardware mandates. Expect scrutiny around how systems mitigate risk with both cooperative and non-cooperative aircraft.
- Third-party service integration: The role of UTM (Unmanned Aircraft System Traffic Management) service suppliers, digital flight authorizations, and third-party data feeds is central to upcoming scalable BVLOS models.
- Airworthiness and system safety: The FAA is distinguishing between off-the-shelf light UAS operations in low-risk environments and heavier platforms operating over populated areas.
Check the Federal Register and official FAA channels regularly for the latest notices of proposed rulemaking and docket updates.
Waivers and approvals
While broad rulemaking continues, complex operations still rely heavily on Part 107 waivers and special approvals. The FAA safety assurance teams are focusing on clear, verifiable data:
- Quantitative ground risk mitigations: Broad claims of safety are routinely rejected. Regulators require exact population density estimates, sheltering factors, and kinetic energy calculations for operations over people or moving vehicles.
- C2 link reliability and lost-link logic: Applications must clearly demonstrate deterministic behavior during command-and-control interruptions, including predictable return-to-home profiles and obstacle-clearance routines.
- Operational containment: Chief pilots must show how the aircraft is reliably contained within the approved operational volume if primary navigation systems experience degraded performance.
Compliance risk
Enterprise flight departments rarely face enforcement from deliberate non-compliance. Violations typically occur due to administrative drift and operational scaling:
- Hardware drift against waiver terms: Upgrading payloads, altering aircraft geometry, or swapping critical flight components without confirming they match the exact configurations listed in your waiver safety case.
- Remote ID operational checks: Failing to log pre-flight Remote ID broadcast functionality checks as standard operating procedure. A functioning broadcast module is mandatory for every flight unless operating under an explicit exemption.
- Maintenance and pilot records: Incomplete tracking of component lifecycles, battery cycles, and pilot currency for specialized operations. Ensure your flight logs explicitly match airframe maintenance records.
Three things to do this week
- Audit active waiver parameters: Review your organization's active FAA waivers against your current aircraft fleet, firmware versions, and standard operating procedures to ensure you remain within authorized limits.
- Standardize pre-flight Remote ID verification: Confirm that pre-flight checklists require pilots in command to verify that the Remote ID broadcast is actively transmitting valid data before takeoff.
- Review maintenance log completeness: Inspect airframe and battery logs across all operating units to verify that flight hours, component replacements, and software updates are documented accurately.