# Incident 20251001018219I: Amazon Prime Air MK30 BLOCK 10, Tolleson, AZ, October 1, 2025

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 1, 2025, 09:58 local time
- Place: Tolleson, AZ
- Damage: Destroyed
- Phase of flight: Cruise/Level Flight
- Operating rules: Air taxi and commuter (Part 135)
- Operator: 4MZA
- Location: 33.4591° N, 112.2698° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.4591&lon=-112.2698&mi=10
- Aircraft: N791PA, registered now (https://openairdocs.org/aircraft/N791PA) (OpenAirDocs)
- Registry model: Amazon.Com Services MK30 (registry code 06102FK, https://openairdocs.org/model/amazon-com-services-mk30) (OpenAirDocs)
- Reported make and model: AMAZON PRIME AIR MK30 BLOCK 10
- People aboard: 0
- Fatal injuries: 0
- Other injuries: 0
- NTSB investigation: [NTSB WPR26LA002](https://openairdocs.org/ntsb/WPR26LA002) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20251001018219I

## Narrative

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

ON OCTOBER 1, 2025, AT APPROXIMATELY 0958 MST, A MK30 UNMANNED AIRCRAFT SYSTEM (UAS) WAS SUBSTANTIALLY DAMAGED IN AN INCIDENT NEAR TOLLESON, ARIZONA. THE UAS, OPERATED AS A NON-SCHEDULED CARGO FLIGHT UNDER TITLE 14 CFR PART 135, COLLIDED WITH A MOBILE CRANE. THERE WERE NO INJURIES REPORTED. FIRST RESPONDERS FOUND THAT TWO UASS HAD COLLIDED WITH THE CRANE, RESULTING IN A BATTERY FIRE.

THE CRANE INVOLVED WAS A LINK BELT ATC-3275, WHICH HAD BEEN ERECTED AT THE JOB SITE BETWEEN 0730 AND 0800. AT 0949, THERE WAS AN INITIAL IMPACT TO THE BOOM OF THE CRANE FROM A UAS AND THE CRANE OPERATOR TERMINATED OPERATIONS TO EVALUATE THE SITUATION. A SECOND UAS THEN IMPACTED THE STATIONARY CRANE BOOM APPROXIMATELY 9 MINUTES AFTER THE FIRST REPORTED IMPACT. THE CRANE WAS RETRACTED, LOWERED, AND INSPECTED, REVEALING NO STRUCTURAL DAMAGE BUT PAINT TRANSFER FROM THE UAS. THE CRANE WAS ESTIMATED TO BE EXTENDED TO ABOUT 197.3 FEET ABOVE GROUND LEVEL (AGL) AT AN ANGLE OF 25°. THE CRANE’S MAXIMUM HEIGHT WITH ITS BI-FOLDING LATTICE FLY IS 300.6 FEET.

THE UAS OPERATOR REPORTED THAT THE COLLISION OCCURRED ABOUT 1.25 MILES NORTHEAST OF THE DEPARTURE LOCATION DURING A COMMERCIAL FLIGHT UNDER FAA EXEMPTION. THE PLANNED FLIGHT ROUTE WAS AT AN ALTITUDE OF ABOUT 200 FEET AGL. GROUND SURVEILLANCE CREWS (GSC) CONDUCTED SCANS OF THE AREA TWICE ON THE DAY OF THE INCIDENT, AT 0658, WITHOUT IDENTIFYING OBSTRUCTIONS.

EXAMINATION AT THE SITE SHOWED THE UAS ON THE GROUND NEAR THE CRANE, WITH ITS BATTERY EJECTED AND ON FIRE, WHICH WAS CONTAINED BY THE FIRE DEPARTMENT WITHIN 5 MINUTES. THE FIRE DID NOT SPREAD BEYOND THE BATTERY’S LOCATION, THE BURN SCARING WAS LIMITED TO BENEATH THE BATTERY AND THE FIRE DID NOT REIGNITE AFTER BEING EXTINGUISHED.  THE UAS FUSELAGE AND WINGS WERE DAMAGED, BUT TWO ELECTRIC WING-MOUNTED MOTORS REMAINED ATTACHED. THE UAS WAS RECOVERED, AND FLIGHT DATA WAS DOWNLOADED. THE FLIGHT TRACK DATA REVEALED THAT THE UAS ACTIVATED AT 0940:10, ASCENDED TO ABOUT 1,014 FEET MEAN SEA LEVEL (MSL), AND CONDUCTED FLIGHT CHECKS. AT 0956:25, IT ASCENDED TO 1,154 FEET MSL AND DEPARTED THE DELIVERY CENTER HEADING NORTH. AT 0957:30, THE UAS TURNED EAST AT ABOUT 1,206 FEET MSL. AT 0958:04, WHILE ON AN EASTERLY HEADING, THE UAS DESCENDED FROM 1,218 FEET MSL (ABOUT 200 FEET AGL) TO 1,073 FEET MSL (ABOUT 60 FEET AGL) UNTIL CONTACT WAS LOST AT 0958:08, APPROXIMATELY 160 FEET EAST OF THE CRANE'S LOCATION.

THIS IS THE END OF THIS REPORT.

## 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 WPR26LA002](https://openairdocs.org/ntsb/WPR26LA002), Oct 1, 2025: Amazon.Com Services MK30 (N791PA), Tolleson, AZ, incident, substantial damage, investigation ongoing

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.