DEPLOYDatabase

Incident · Collision

Two Amazon Prime Air MK30 drones collide with construction crane in Tolleson, Arizona, prompting FAA and NTSB investigation

Two Amazon Prime Air MK30 delivery drones collided with the boom of a stationary construction crane in Tolleson, Arizona, approximately 1.25 miles northeast of the departure location. The crane was erected after the morning ground surveillance scan and was not detected by Amazon's rooftop scan procedures.

Both drones sustained substantial damage; the first drone's battery ejected and caught fire on impact. One person was evaluated at the scene for possible smoke inhalation. The FAA and NTSB launched investigations, and Amazon temporarily paused drone deliveries in the area. NTSB classified the incident as a Class 3 investigation.

Occurred 2025-10-01 · Amazon Prime Air MK30 · Amazon Prime Air · Drones · Investigated by FAA

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.
Track Two Amazon Prime Air MK30 drones collide with construction crane in Tolleson, Arizona, prompting FAA and NTSB investigation

Machine-readable surfaces

Sources (2)

  1. CNBC · https://www.cnbc.com/2025/10/02/amazon-drone-crash-faa-ntsb.html · 2025-10-02
  2. Unmanned Airspace · https://www.unmannedairspace.info/uncategorized/ntsb-releases-preliminary-findings-into-amazon-drone-collision-with-crane/ · 2025-10-15

Status history

  • Active · 2026-07-23 · agent:recon

Common questions

What happened in Two Amazon Prime Air MK30 drones collide with construction crane in Tolleson, Arizona, prompting FAA and NTSB investigation?
Two Amazon Prime Air MK30 delivery drones collided with the boom of a stationary construction crane in Tolleson, Arizona, approximately 1.25 miles northeast of the departure location. The crane was erected after the morning ground surveillance scan and was not detected by Amazon's rooftop scan procedures. Both drones sustained substantial damage; the first drone's battery ejected and caught fire on impact. One person was evaluated at the scene for possible smoke inhalation. The FAA and NTSB launched investigations, and Amazon temporarily paused drone deliveries in the area. NTSB classified the incident as a Class 3 investigation.
When did this incident occur?
The incident is recorded as occurring on October 1, 2025 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in Two Amazon Prime Air MK30 drones collide with construction crane in Tolleson, Arizona, prompting FAA and NTSB investigation?
Amazon Prime Air MK30 is the recorded robot involved in this incident.
Has anyone responded to Two Amazon Prime Air MK30 drones collide with construction crane in Tolleson, Arizona, prompting FAA and NTSB investigation?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of Two Amazon Prime Air MK30 drones collide with construction crane in Tolleson, Arizona, prompting FAA and NTSB investigation?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-08-09

Verification posture

Verified

Medium confidence

Review state

Stable

Last reviewed 2026-08-09

Sources by quality tier

1
secondary-established-publication
Established publication
1
unclassified
Unclassified source

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Two Amazon Prime Air MK30 drones collide with construction crane in Tolleson, Arizona, prompting FAA and NTSB investigation.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.

Canonical ID e37f66a2-46aa-4f90-9e63-75c90089d136