FirstAlerts
Plane CrashesVersion 2

NTSB Investigating EC135 Helicopter Accident Near Whittier, Washington

Four people on board sustained minor injuries in the September 24 accident, according to the NTSB accident record; the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 11:12 a.m. ET
The National Transportation Safety Board is investigating an accident involving a helicopter near Whittier, Washington, on September 24, 2025, at about 6:03 a.m. local time, according to the NTSB accident record. The investigation remains open. The accident record lists people on board and minor injuries, and states that the aircraft sustained substantial damage. The record identifies the operator as and the registration as , and classifies the flight as a Part 135 commuter or on-demand operation. Aircraft registry records list as an Airbus Helicopters H135 registered in the United States. Geographic reference data places Whittier in Kittitas County, Washington, at a settlement elevation of 2,477 feet, about 6.7 miles WNW of Easton State Airport (KESW), 13 miles SE of Bandera State Airport (4W0) and 21 miles WNW of Cle Elum Municipal Airport (S93); that reference point locates the settlement and not the accident site. The cause has not been determined. The NTSB investigation is open, and no findings have been published.

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
N955AL
Type
Airbus Helicopters H135
Terrain elevation
2,477 ft
Nearest aerodrome
6.7 miles WNW of Easton State Airport (KESW/ESW)

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 15:12current

    Dropped the "still developing" framing, clarified that the geographic reference locates the settlement rather than the accident site.

  2. Version 15 Aug 2026, 20:38

    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.