FirstAlerts
Plane CrashesVersion 2

NTSB Investigating Amazon MK30 Accident Near Tolleson, Arizona

An accident record lists an Amazon.com Services LLC MK30, registration N791PA, as substantially damaged near Tolleson on October 1, 2025.

By AI ReporterUpdated Aug 7, 2026, 10:22 a.m. ET
The National Transportation Safety Board is investigating an accident involving an aircraft near Tolleson, Arizona, on October 1, 2025, at about 4:58 p.m. local time. The event is still developing and the accident record remains at an early stage. The accident record identifies the aircraft as an , registration , operated by , and lists it as having sustained substantial damage. The record classifies the flight as a Part 135 commuter or on-demand operation. It does not list injury counts, which is usual for a preliminary filing. The cause has not been determined. The record lists the National Transportation Safety Board as the investigating body, and the investigation is open. Geographic reference data places Tolleson in Maricopa County, Arizona, at a terrain elevation of 1,014 feet, about 5.7 miles south-southeast of Glendale Municipal Airport (KGEU), 6.1 miles south-southwest of Airscrew Performance Flightpark Ultralightport (AZ79) and 7.0 miles east-northeast of Phoenix Goodyear Airport (KGYR). Weather observations recorded at Glendale Municipal Airport, 5.7 miles away and eight minutes from the reported time, showed calm wind, visibility of 10 statute miles, clear skies and a temperature of 95°F. Those are instrument readings at a nearby field and say nothing about what happened.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Terrain elevation
1,014 ft
Nearest aerodrome
5.7 miles SSE of Glendale Municipal Airport (KGEU)

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 14:22current

    Corrected the bearings from Tolleson to Airscrew Performance Flightpark Ultralightport and Phoenix Goodyear Airport to match the geographic reference data.

  2. Version 15 Aug 2026, 20:24

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.