2025-03 · NASA ASRS report 2227334
Government UAS crew reported an engine positioning control issue caused the UAS to enter into an uncontrollable spin. Efforts to control the spin failed and the UAS crashed.
During the first flight of the day; the aircraft; a Censys Technologies Sentaero V2 BVLOS; experienced an unknown malfunction after launch; resulting in uncommanded aircraft movement away from the intended route of flight. During this time; the aircraft lost more than 100 feet of altitude before impacting the roadway on the eastern end of the road. No third-party property damage or injuries occurred as a result of the crash. However; the aircraft is damaged beyond the point of economical repair.The crew consisted of five individuals; four of whom have current FAA-issued Remote Pilot Certificates. All checklists were followed using the challenge and response methodology. The flight was programmed to depart from a small grass field off the NW corner of Location A (authorized by a port authority representative) using a VTOL functionality then fly an automated rectangular course south of the road over Location B. Some minor anomalies were noted and addressed during the preflight sequence. Namely motor servo positioning. However; this was later determined to normal behavior. Takeoff initially seemed uneventful; climbing to the expected transition altitude between vertical and horizontal flight. At the top of the climb; the aircraft began to rotate counterclockwise; which at first seemed like normal pre-transition behavior for the aircraft. However; during the third turn; the aircraft began to loose altitude and travel to the Northeast.Aircraft control was transferred to a more experienced remote pilot for the airframe; at which point he attempted to bring the aircraft to a hover; but the aircraft unexpectedly changed to a horizontal flight profile; climbed briefly; and then continued to descend; failing to respond to pilot control inputs. As the aircraft descended; one of the wings made contact with a street light pole; causing a final spin into the ground. At no point during the accident sequence were warning or error indicators present on GCS (Ground Control Station) equipment. All parts of the aircraft were recovered; with the exception of one propeller.Our team will conduct further inspections and investigation to isolate the cause of the malfunction next week.
The reporter suspected the issue occurred due one of the two operating motors changing modes. One motor remained in the position for vertical flight while the other motor changed toward a horizontal flying position.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.