FirstAlerts
Plane CrashesVersion 2

NTSB Investigating Amazon MK30 Accident Near Tolleson, Arizona

An accident record lists substantial damage to the aircraft, registration N579PA, in the October 1 event; the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 11:13 a.m. ET
The National Transportation Safety Board is investigating an accident involving an near Tolleson, Arizona, on October 1, 2025, at about 4:49 p.m. local time, according to the accident record. The matter is developing and the investigation remains open. The accident record lists the aircraft as having sustained substantial damage and identifies it as . Aircraft registry records list that registration as registered in the United States. The record classifies the flight as a Part 135 commuter or on-demand operation and lists the operator as . No injury counts appear in the record, which is usual for a preliminary filing. A weather observation recorded at Glendale Municipal Airport (KGEU), 5.7 miles away and one minute from the reported time, showed calm wind, visibility of 10 statute miles, clear skies and a temperature of 95°F. The observation is an instrument reading at a nearby field and is not stated to have any bearing on the event. Geographic reference data places Tolleson in Maricopa County, Arizona, at a settlement elevation of 1,014 feet, about 5.7 miles south-southeast of Glendale Municipal Airport, 6.1 miles south-southwest of Airscrew Performance Flightpark Ultralightport (AZ79) and 7.0 miles east-northeast of Phoenix Goodyear Airport (KGYR). The cause has not been determined. The National Transportation Safety Board investigation is open.

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.

Registration
N579PA
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, 15:13current

    Reordered to place the weather observation ahead of the geographic reference data and added a note that the reading is not tied to the event; no new facts.

  2. Version 15 Aug 2026, 20:25

    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.