Probable cause
The operator’s failure to maintain separation between two drones during dual simulated engine out recoveries, which resulted in a midair collision.
NTSB analysis
The operator of the unmanned aircraft system (UAS) reported that during a test flight, N213PA was intentionally faulted by the UAS operator to simulate a “motor out recovery” and diverted to an alternate landing pad as the system was designed to do. The same fault was applied to N282PA as it was departing, which then diverted the UAS to the same alternate landing pad and into the flight path of N213PA, resulting in a mid-air collision. Both UAS sustained substantial damage throughout.
The operator reported that there were no preaccident mechanical failures or malfunctions with either UAS that would have precluded normal operation.
Text from the NTSB. Open the NTSB docket for WPR24LA302 for the full record.
Event
- Date
- Sep 6, 2024
- Type
- Accident
- Place
- Pendleton, Oregon
- Nearest airport
- Eastern Oregon Rgnl At Pendlet (PDT)
- Highest injury
- None
- Weather
- Visual (VMC)
- Light
- Day
Amazon.Com Services Llc MK30
- N-number
- N213PA
- Category
- Helicopter
- Year built
- 2024
- Damage
- Destroyed
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Flight test
Amazon.Com Services Llc MK30
- N-number
- N282PA
- Category
- Helicopter
- Year built
- 2024
- Damage
- Substantial
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Flight test
From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.