Regulatory watch
The push toward standardized Part 108 rules for Beyond Visual Line of Sight (BVLOS) operations is centering on low-altitude airspace segregation and shielded flight profiles. Regulators are evaluating how physical structures can safely shield uncrewed aircraft from crewed traffic.
Key regulatory themes to track across federal policy updates include:
- Shielded airspace definitions: The FAA is assessing operational envelopes within close proximity to structures, evaluating how natural or man-made obstacles reduce mid-air collision risk with crewed aircraft.
- Supplemental Data Service Providers (SDSPs): Rulemaking discussions continue to formalize the role of third-party digital services, specifically how micro-weather feeds and dynamic obstacle databases integrate into flight authorization pipelines.
- Automated contingency execution: Expectations are shifting from manual pilot intervention toward pre-programmed, deterministic vehicle behavior when entering degraded operational states.
Verify all draft language, formal announcements, and open public comment windows directly through official FAA channels.
Waivers and approvals
Safety assurance offices are demanding verifiable evidence for low-altitude containment and complex site waivers. Current approval packages must demonstrate clear technical competence in three specific areas:
- Containment buffer math: Reviewers require documented calculations showing spatial safety buffers between the flight boundary, structural shielding, and adjacent public airspace.
- Micro-weather integration: Applicants must show how ground control stations ingest real-time localized weather data, such as microburst or wind shear alerts, rather than relying solely on regional airport forecasts.
- Pilot workload and supervisory ratios: For multi-vehicle or dock-based operations, safety cases must quantify remote pilot cognitive load, proving the operator can safely handle unexpected vehicle handoffs or simultaneous alerts.
Compliance risk
Enterprise UAS programs often manage hardware effectively but fail audits due to operational boundary drift and unmonitored digital changes:
- Launch point migration: Field teams relocating launch pads slightly outside approved operational volume coordinates without updating their formal flight safety risk assessments.
- Automated background software updates: Ground control software or mission planning apps updating automatically, which can quietly reset custom geofencing thresholds or lost-link return altitudes.
- Pilot duty-time tracking gaps: Overlooking remote operator fatigue by failing to log active screen time and supervisory duty hours during high-cadence automated operations.
Three things to do this week
- Verify operational boundaries: Review last week's flight coordinates against approved waiver boundaries to confirm field teams launched and operated strictly inside authorized operational volumes.
- Lock down automatic software updates: Check all field ground control stations and tablets to disable automatic background updates for flight control and mission planning software.
- Establish screen-time tracking: Add remote pilot duty and rest tracking to your standard flight logging workflow to ensure operators maintain focus during complex supervisory shifts.