Amazon.Com Services LLC MK30 and Amazon.Com Services LLC MK30 mid-air collision near Pendleton, Oregon, September 6, 2024
On September 6, 2024 at about 5:52 pm local time, 2 aircraft, Amazon.Com Services LLC MK30 (N213PA) and Amazon.Com Services LLC MK30 (N282PA), were involved in a mid-air collision near Pendleton, Oregon (Eastern Oregon Rgnl At Pendlet airport). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The operator’s failure to maintain separation between two drones during dual simulated engine out recoveries, which resulted in a midair collision.
The operator’s failure to maintain separation between two drones during dual simulated engine out recoveries, which resulted in a midair collision.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 6, 2024 · about 5:52 pm local time · cases in 2024
- Place
- Pendleton, Oregon · Eastern Oregon Rgnl At Pendlet · cases near this airport · map
- Type
- Accident · mid-air collision
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Amazon.Com Services LLC MK30, built 2024
- Registration
- N213PA · registry record · serial 178650100H
- Damage
- Destroyed
- Flight
- Flight test · general aviation rules (Part 91)
- Aircraft 2
- Amazon.Com Services LLC MK30, built 2024
- Registration
- N282PA · registry record · serial 178650100X
- Damage
- Substantial damage
- Flight
- Flight test · general aviation rules (Part 91)
The NTSB's narrative for the Amazon.Com Services LLC MK30 final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The NTSB's narrative for the Amazon.Com Services LLC MK30 final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record for the Amazon.Com Services LLC MK30 from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during enroute (cruise) defining event
The NTSB's findings
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Environmental issues › Physical environment › Object/animal/substance › Aircraft › Effect on equipment
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; rotorcraft: unmanned (suas)
- Flight time: 215 hours in all; 155 in this make and model; 215 as pilot in command
- Last flight review: May 23, 2024
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: none
- Injury: no injuries
The aircraft
- Last inspection: continuous airworthiness programme
- Maximum gross weight: 82 lb
- Seats: 0
- Landing gear: fixed
- Engine 1: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Engine 2: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Engine 3: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Engine 4: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Engine 5: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Engine 6: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Operator: Amazon.Com Services LLC
The flight
- Departed from: PDT Pendleton OR at 7:56 pm
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 86°F (30°C), dew point 45°F (7°C)
- Altimeter: 30.09 inHg
- Observation at 10:53 am from KPDT
Weather report (METAR): KPDT 061753Z VRB03KT 10SM CLR 30/07 A3009 RMK AO2 SLP170 T03000072 10300 20172 58002 $
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
The factual record for the Amazon.Com Services LLC MK30 from the NTSB's investigation tables, in plain English
What happened, in order
- Collision during takeoff/land during takeoff defining event
The NTSB's findings
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
Pilot
- Certificate: private, remote
- Ratings: single-engine land; rotorcraft: unmanned (suas)
- Flight time: 215 hours in all; 155 in this make and model; 215 as pilot in command
- Last flight review: May 23, 2024
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: none
- Injury: no injuries
The aircraft
- Airframe total time: 33 hours
- Last inspection: continuous airworthiness programme, September 6, 2024
- Maximum gross weight: 82 lb
- Seats: 0
- Landing gear: fixed
- Engine 1: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Engine 2: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Engine 3: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Engine 4: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Engine 5: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Engine 6: Ama/Expr UNKNOWN ENG (electric); 0 hours total
- Operator: Amazon.Com Services LLC
The flight
- Departed from: PDT Pendleton OR at 7:56 pm
- Flight plan: none
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
1 document, released by the NTSB on March 13, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N213PA on the register today · the tail number may have moved to another aircraft since
- N282PA on the register today · the tail number may have moved to another aircraft since
- Engine: Ama/Expr UNKNOWN ENG · as the NTSB recorded it
- Engine: Ama/Expr UNKNOWN ENG · as the NTSB recorded it
- Eastern Oregon Regional AT Pendleton · nearest airport
- Accidents and incidents in Oregon 1,864 since 1982 · 279 in the last ten years
- Oregon 7,002 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR24LA302.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
