# Incident 20211201022679I: Amazon Logistics Inc MK27, Pendleton, OR, December 1, 2021

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 1, 2021, 12:07 local time
- Place: Pendleton, OR
- Airport: Eastern Oregon Regional At Pendlet
- Damage: Destroyed
- Phase of flight: Hover/Holding
- Operating rules: General operating rules (Part 91)
- Location: 45.6951° N, 118.8434° W: Placed by OpenAirDocs at EASTERN OREGON RGNL AT PENDLETON (PDT), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=45.6951&lon=-118.8434&mi=10
- Aircraft: N239PA, a cancelled registration (https://openairdocs.org/deregistered/N239PA-2022-11-10) (OpenAirDocs)
- Registry model: Amazon Logistics MK27 (registry code 061011S, https://openairdocs.org/model/amazon-logistics-mk27) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: AMAZON LOGISTICS INC MK27
- Reported engine: AMA/EXPR UNKNOWN ENG
- People aboard: 7
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 2,767 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20211201022679I

## Narrative

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

THIS TEST FLIGHT WAS A VTOL-ONLY FLIGHT CONDUCTED ABOVE THE PDT10 SOUTH PAD. THE MISSION PROFILE WAS TO CLIMB TO 100M AGL, PERFORM A 3 SEC HOVER, FOLLOWED BY A GPS LANDING. AFTER TAKEOFF, AT AN ALTITUDE OF 35M, THE AIRCRAFT LOST ALL POWER, AND DESCENDED STRAIGHT DOWN, IMPACTING THE TAKEOFF/LANDING PAD.  DURING THE IMPACT THE BATTERY WAS EJECTED AND LANDED ONE METER FROM THE AIRCRAFT AND CAUGHT FIRE.  THE BATTERY FIRE WAS ISOLATED TO ITSELF AND DID NOT CAUSE ANY ADDITIONAL DAMAGE TO THE AIRCRAFT OR SURROUNDING AREA.  THERE WERE NO PERSONAL INJURIES AND NO THIRD-PARTY PROPERTY DAMAGE. PRELIMINARY DATA INDICATES THERE WAS A DISRUPTION IN THE COMMUNICATION LINK BETWEEN THE GSR AND THE AIRCRAFT WHICH RESULTED IN A FAILSAFE TERMINATION COMMAND.

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.