# Incident 20210621008559I: Amazon Logistics Inc MK27, Pendleton, OR, June 21, 2021 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: June 21, 2021, 11:55 local time - Place: Pendleton, OR - Airport: Eastern Oregon Regional At Pendlet - Damage: Destroyed - Phase of flight: Climb - 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: N579PA, a cancelled registration (https://openairdocs.org/deregistered/N579PA-2022-02-15) (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: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Commercial pilot, flight instructor - Pilot flight hours: 1,035 total - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20210621008559I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. N579PA, AN ^PRIVACY DATA OMITTED^ MK27, S/N 355, WAS OPERATING FROM PDT AIRPORT ON 06/21/2021 UNDER A SPECIAL EXPERIMENTAL AIRWORTHINESS CERTIFICATE FOR R&D PURPOSES WHEN IT EXPERIENCED A LOSS OF POWER TO THE NUMBER ONE MOTOR. THIS OCCURRED JUST AFTER COMPLETING THE OUTBOUND LEG OF A MAINTENANCE CHECK FLIGHT FROM THE ^PRIVACY DATA OMITTED^ LAUNCH AREA NEAR THEIR HANGAR AT THE PDT AIRPORT. AFTER THE UAS TOOK OFF FROM THE DROP OFF LOCATION ABOUT 1/2 MILE NW FROM THE PDT AIRPORT, IT CLIMBED VERTICALLY TO ABOUT 180 FEET AND BEGAN A TRANSITION FROM VTOL MODE TO FORWARD HORIZONTAL CRUISE FLIGHT MODE FOR THE RETURN LEG TO THE PDT BASE. THE SAFETY OFFICER (SO) ONSITE AT THE DROP OFF LOCATION REPORTED SEEING THE UAS CLIMB WITHOUT INCIDENT TO 180 FEET, BUT WHEN THE UAS BEGAN ITS ATTITUDE ROTATION FOR FORWARD FLIGHT, THE SO REPORTED SEEING THE AIRCRAFT ROTATE TO THE RIGHT AND THEN DROP VERTICALLY 10 TO 20 FEET IN A FULLY INVERTED POSITION. THE GROUND STATION OPERATOR (GSO) AND THE PIC (OIC) MONITORING THIS FLIGHT REPORTED SEEING A PROPULSION WARNING LIGHT IN THE GROUND CONTROL STATION, AND AT THE SAME TIME, THE UAS AUTOMATIC ONBOARD HEALTH MONITORING SYSTEM DETECTED A FAILURE IN THE #1 ELECTRONIC SPEED CONTROL (ESC) AND INITIATED AN IMMEDIATE "URGENT LAND" COMMAND. THE SO STATED THAT AS SOON AS HE SAW THE UAS FLIP INVERTED HE HIT THE FLIGHT TERMINATION SYSTEM (FTS) EMERGENCY STOP BUTTON. THIS BUTTON CAUSES ALL ESCS TO GO TO ZERO RPM AND FLIGHT SERVOS TO GO TO A PRE-COMMANDED POSITION TO LIMIT GLIDE OF THE UAS. THE SO STATED THE UAS FELL VERTICALLY FROM ABOUT 160 FEET IN A STRAIGHT DOWN TRAJECTORY. REVIEW OF VIDEO TAKEN BY THE SO OF THIS EVENT SHOWED THE UAS TUMBLING IN UNCONTROLLED FREE FALL UNTIL IT CONTACTED THE GROUND ABOUT 400 FEET FROM THE SO?S POSITION. AFTER IMPACT, SECTIONS OF THE FLIGHT CONTROLS AND STRUCTURE BROKE OFF, AND THE SO REPORTED SEEING SMOKE AND THEN FLAMES WITHIN ABOUT 5 SECONDS. THE SO ASKED THE OIC TO CALL THE FIRE DEPARTMENT TO REPORT THE FIRE THAT HAD BROKEN OUT IN A WHEAT STUBBLE FIELD, AS AN INTENSE LITHIUM BATTERY FIRE QUICKLY CONSUMED THE AIRCRAFT. SEVERAL ACRES OF WHEAT STUBBLE FIELD WERE SOON ON FIRE, WHICH THE FIRE DEPARTMENT EXTINGUISHED AFTER ARRIVING ABOUT 5-10 MINUTES AFTER GETTING THE EMERGENCY CALL. ON-SITE INSPECTION OF THE UAS REMAINS BY IIC VIA ^PRIVACY DATA OMITTED^ LATER THAT DAY FOUND NOTHING RECOGNIZABLE LEFT OF THE AIRCRAFT AFTER THE FIRE EXCEPT FOR THE BURNED REMAINS AND MELTED METAL COMPONENTS. ^PRIVACY DATA OMITTED^ REPRESENTATIVES REPORTED THAT THIS SERIAL NUMBER UAS HAD EXPERIENCED CONTROLLER AREA NETWORK (CAN) ISSUES JUST BEFORE THIS FLIGHT, AND THAT THE NUMBER ONE MOTOR HAD STOPPED DURING LAUNCH TWO DAYS BEFORE THIS EVENT. THEY REPORTED THE NUMBER ONE ESC AND NUMBER ONE MOTOR HAD BEEN CHANGED JUST BEFORE THE FLIGHT ON JUNE 21, AND THAT THE PURPOSE OF THIS FLIGHT WAS A POST MAINTENANCE CHECK AFTER SUCCESSFUL TETHER FLIGHT TESTS. 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.