Regulatory watch
The push toward a standardized Part 108 regulatory framework for Beyond Visual Line of Sight (BVLOS) operations remains the central focus for enterprise programs. Rulemaking efforts continue to emphasize shifting the industry away from custom waiver packages and toward scalable, repeatable operational rules.
Key regulatory themes to track right now include:
- Detect and Avoid (DAA) standards: Regulators are prioritizing performance-based standards for both onboard and ground-based DAA architectures. Programs should monitor how the FAA distinguishes between cooperative and non-cooperative traffic mitigations.
- Airworthiness and system safety: Expect increased scrutiny on manufacturer declarations of compliance, especially for medium-risk enterprise platforms operating over higher-density areas.
- Operator credentialing: Future frameworks are evaluating new supervisory roles for remote pilots managing automated fleets and multiple aircraft simultaneously.
Always verify current rulemaking statuses, open comment windows, and formal announcements directly on official FAA portals.
Waivers and approvals
While broad BVLOS rules progress, the FAA continues to process operational waivers under Part 107. Approval trends show that reviewers expect quantitative evidence rather than theoretical safety claims.
Enterprise applicants are consistently being asked to demonstrate:
- Rigorous ground risk mitigations: Clear data showing how population density along flight corridors is calculated, monitored, and avoided.
- Validated containment systems: Evidence of reliable geofencing, lost-link procedures, and automated return-to-home behavior under degraded GPS conditions.
- System reliability data: Detailed testing hours and failure mode analyses for both the airframe and critical command-and-control links.
Compliance risk
As enterprise drone fleets grow, compliance failures rarely stem from intentional violations. They usually happen due to administrative drift across decentralized field teams.
The most common compliance gaps include:
- Inconsistent maintenance logs: Missing component lifecycles, unrecorded motor swaps, and unmonitored battery retirement schedules.
- Currency and credential tracking: Lapsed pilot currencies, missed recurrent training windows, or unlogged operational hours for complex flight profiles.
- Firmware update drift: Flying platforms on modified firmware versions that have not been formally evaluated against active waiver requirements.
Three things to do this week
- Audit active waiver constraints: Pull flight logs from your last five operational deployments and verify that altitude limits, buffer zones, and observer roles matched your approved waiver documentation exactly.
- Review battery and airframe logs: Ensure all maintenance tracking across remote sites reflects physical component hours, firmware versions, and inspection schedules.
- Align internal SOPs with emerging BVLOS concepts: Review your team's standard lost-link and emergency response procedures to ensure they align with performance-based safety requirements.