# Accident 20240906013292A: Amazon.Com Services LLC MK30, Pendleton, OR, September 6, 2024

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 6, 2024, 10:52 local time
- Place: Pendleton, OR
- Airport: Eastern Oregon Regional At Pendlet
- Damage: Destroyed
- Collision: Midair collision
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 45.6909° N, 118.8391° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=45.6909&lon=-118.8391&mi=10
- Aircraft: N213PA, registered now (https://openairdocs.org/aircraft/N213PA) (OpenAirDocs)
- Registry model: Amazon.Com Services MK30 (registry code 06102FK, https://openairdocs.org/model/amazon-com-services-mk30) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: AMAZON.COM SERVICES LLC MK30
- Reported engine: AMA/EXPR UNKNOWN ENG
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 215 total, 155 in this make and model, 148 in the last 90 days
- NTSB investigation: [NTSB WPR24LA302](https://openairdocs.org/ntsb/WPR24LA302) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20240906013292A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON SEPTEMBER 6, 2024 THE SUBJECT TWO MK30 UAS WERE CONDUCTING PROBABLE FAILURE TESTING FLIGHTS UNDER A SAC-EC AND EXPERIMENTAL AUTHORITY AT THE PENDLETON, OREGON FLIGHT TEST FACILITY. THE SPECIFIC TEST BEING EXECUTED WAS THE MOTOR-ELECTONIC SPEED CONTROLLER-PROPELLER (MEP)-OUT SCENARIO DESCRIBED IN DOC-013784, MK30 CMD PROBABLE FAILURES AND FUNCTIONALITY DEMONSTRATION FLIGHT TEST PLAN. BOTH UAS WERE SEPARATELY LOADED WITH A MISSION THAT HAD AN INTENTIONALLY INJECTED MEP-OUT WHICH WOULD BE EXPECTED TO RESULT IN A RETURN HOME CONTINGENCY AND A LANDING AT THE DIVERT PAD NOT THE ROUTINE RETURN HOME LANDING PAD. THE NOMINAL PLAN WAS FOR THE SECOND FLIGHT TO BE LAUNCHED AFTER THE FIRST LANDED, BUT DUE TO AN ERROR THEY WERE LAUNCHED 9 MINUTES APART.

UAS 1 TOOK OFF FROM PAD 301, PERFORMED A NOMINAL DELIVERY, THE MEP-OUT FAULT WAS INJECTED FOLLOWING THE DELIVERY, AND WAS RETURNING TO THE DIVERT PAD VIA THE RETURN HOME PATH AS INTENDED. WHILE UAS 1 WAS RETURNING TO THE LANDING AREA, UAS 2 TOOK OFF FROM PAD 303, THE PLANNED MEP-OUT WAS INJECTED ON TAKEOFF ASCENT AND IT IMMEDIATELY PROCEEDED TO THE DIVERT PAD PER THE TEST PLAN. UAS 1 STARTED DESCENDING ONTO THE DIVERT PAD FROM APPROXIMATELY 60M WHILE UAS 2 WAS TRANSITIONING TO THE DIVERT PAD AT APPROXIMATELY 40M.  THE SHIFT LEAD/PROBLEMS SOLVER RECOGNIZED THE SOUND OF A UAS MOTOR FAILURE AND IMMEDIATELY SHOUTED TO EXECUTE AN SCL (SAFE CONGINCY LANDING) THIS COMMAND WAS RADIOED TO THE FLIGHT MONITOR (PIC) AT THE GROUND CONTROL STATION (THE SAME PIC WAS MONITORING BOTH FLIGHTS AND AN ADDITIONAL UAS ON HIS GROUND CONTROL STATION).  THE FLIGHT MONITOR COMMANDED SCL FOR UAS 2.  UAS 2 ENTERED THE DESCENT PATH OF UAS 1 WHEN DRONE 1 WAS AT APPROXIMATELY 40M ABOVE THE GROUND, UAS 1 DESCENDED ONTO UAS 2 IN MID-AIR AT APPROXIMATELY 40M ALTITUDE.   THE WINGS OF BOTH UAS INTERLOCKED. BOTH UAS SPIRLED TO THE GROUND AND IMPACTED ON THE GRAVEL SOUTH OF THE DIVERT PAD. THE ENTIRE EVENT WAS CONTAINED AT THE DIVERT PAD AREA, AND THERE WERE NO INJURIES OR DAMAGE TO THIRD PARTY PROPERTY.

## Other aircraft in the event

- N282PA, Amazon.Com Services LLC MK30: [Accident 20240906020911A](https://openairdocs.org/incident/20240906020911A)

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB WPR24LA302](https://openairdocs.org/ntsb/WPR24LA302), Sep 6, 2024: Amazon.Com Services MK30 (N213PA), Pendleton, OR, destroyed. Probable cause: The operator’s failure to maintain separation between two drones during dual simulated engine out recoveries, which resulted in a midair collision.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.