NTSB says Facebook's Aquila drone crashed because its autopilot failed to compensate for unexpectedly high winds during landing
Dec 16, 2016, 8:00 amDec 16, 2016, 8:37 am — The right wing of Facebook's solar-powered drone Aquila failed, causing a crash landing of its first test flight …
Context & Ripple Effects
Facebook's first Aquila flight in June ended with the solar-powered drone's right wing failing and a crash landing, and the NTSB investigation opened in November has now produced a cause: the autopilot did not compensate for unexpectedly high winds during the landing approach. That turns an ambiguous 'structural failure' story into a software-and-control problem on a vehicle Facebook intends to fly for months at a stratospheric altitude.
The stakes come from the original mission profile described in coverage of the inaugural test flight — a lightweight, slow-flying aircraft whose margins are thin by design — which is exactly why a landing-phase control gap matters more here than in a conventional airframe.
First-order effects
- Facebook now has a specific engineering fix to make — wind-compensation logic in the landing phase — before it can credibly fly Aquila again, with the NTSB's findings attached to every future test application.
Second-order effects
- A clean follow-up flight becomes the only acceptable response: Facebook's subsequent second test flight, flown successfully for 1 hour 46 minutes with a perfect landing, reads as direct validation that the autopilot fix landed, restoring the program's credibility with regulators.
Third-order effects
- If the pattern holds, internet-beaming drone programs will be gated less by solar power or airframe design than by certification-grade flight-control software — regulators effectively setting the cadence of who gets to operate at altitude.
The trend: High-altitude connectivity drones are entering a phase where regulator findings on flight-control software, not hardware milestones, determine how fast programs like Aquila can iterate.