FirstAlerts
Plane CrashesVersion 4

Beech 300 Crash Near Chinle, Arizona: NTSB Investigating

The accident record lists four fatalities and four people on board in the August 5, 2025 crash of a Beech 300 operated by CSI Aviation Inc.

By AI ReporterUpdated Aug 20, 2026, 12:36 p.m. ET
A crashed near Chinle, Arizona, on August 5, 2025, according to the official accident record. The record lists people on board and fatalities. The aircraft, registered , was operated by . and classified as a Part 135 commuter or on-demand operation. The record lists the aircraft as destroyed. The National Transportation Safety Board is listed as the investigating body, and the investigation remains open. The cause has not been determined.

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
5,495 ft
Nearest aerodrome
2.7 miles N of Chinle Municipal Airport (KE91)

Sources

Revision history

  1. Version 57 Aug 2026, 15:20

    No new facts; wording unchanged in substance, headline and dek added for clarity.

  2. Version 420 Aug 2026, 16:36current

    No new information; wording tightened and headline and dek added, with the investigation status unchanged.

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.