Regulatory watch
The push toward standardizing Beyond Visual Line of Sight (BVLOS) operations under the anticipated Part 108 framework remains the primary focus for enterprise UAS programs. Regulators continue to focus on three core areas:
- Detect and Avoid (DAA) standards: Emphasis is placed on deterministic performance standards for both cooperative and non-cooperative traffic, moving away from subjective visual observer mitigations.
- Airworthiness and system safety: The FAA continues to evaluate right-sized airworthiness models for commercial off-the-shelf aircraft operating in low-risk airspace, balancing heavy certification requirements with practical operational risk.
- Third-party service providers: Discussions continue regarding how UTM services, supplemental data providers, and fleet management networks will be formally recognized within standard operational approvals.
Check the FAA UAS website and official Federal Register notices directly for the latest updates on rulemaking schedules and public comment periods.
Waivers and approvals
For operators currently flying under Part 107 waivers or specific exemptions, the FAA continues to raise the bar on quantitative risk evidence. Approval packages are scrutinized heavily on:
- Demonstrated containment: Proving that geofencing and flight termination systems function reliably under lost-link or degraded GPS conditions.
- Ground risk mitigations: Providing verified third-party kinetic energy impact assessments or parachute recovery data for operations over people or moving vehicles.
- Training and crew resource management: Documenting that remote pilots and visual observers undergo recurrent, scenario-based training for degraded navigation, uncrewed traffic conflicts, and emergency procedures.
Compliance risk
Enterprise drone programs rarely fail audits due to aircraft performance. They fail because of administrative and operational drift. The most frequent compliance blind spots include:
- Remote ID operational status: Operating aircraft without confirming that the standard Remote ID broadcast or broadcast module is transmitting valid data prior to launch.
- Firmware and configuration drift: Applying manufacturer firmware updates without documenting the changes or validating that custom flight limits and failsafes remain intact.
- Maintenance and flight hour tracking: Incomplete logs regarding component lifecycles, motor replacements, and battery cycles, which are required for audit trails during waiver renewals.
Three things to do this week
- Audit aircraft maintenance logs: Ensure every airframe has up-to-date flight hours, firmware version records, and battery health tracking aligned with manufacturer recommendations.
- Test Remote ID broadcasts: Use an independent Remote ID scanner application during pre-flight checks to verify your aircraft's signal is broadcasting proper location and identification data.
- Review emergency response procedures: Run a tabletop drill with your flight crews to test lost-link, flyaway, and airspace conflict procedures against your current SOPs.