Four Dead After Small Plane Crashes Into Water Near Seldovia, Alaska
A Piper PA-24-260 crashed into shallow water near Seldovia, Alaska, on August 26, 2026, killing all four people aboard, according to multiple outlets.
This report went out within minutes of the first account of it. Early reports are provisional and are frequently revised; where sources disagree, both readings are given.
We last searched for new coverage of this at Aug 27, 2026, 5:08 a.m. ET — checked 39 min ago.
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
- 46 ft
- Nearest aerodrome
- 0.4 miles SW of Seldovia Airport (PASO/SOV)
Sources
- Another Alaska plane crash: Four dead as aircraft falls into watertimesofindia.indiatimes.com
- Map Shows Where Four Killed In Alaska Plane Crashbiztoc.com
- Small plane crashes in water next to remote Alaska coastal town, killing all 4 on boardabcnews.com
- Alaska Plane Crash Kills Fourathens-times.com
- Small plane crashes in water next to remote Alaska coastal town, killing 4economictimes.indiatimes.com
- Small plane crashes in water next to remote Alaska coastal town, killing all 4 on boardmymotherlode.com
- Small plane crashes in water next to remote Alaska coastal town, killing all 4 on board | CNNcnn.com
- Four dead after small plane crashes in water next to Alaska towndailymail.com
- Small plane crashes into shallow water near remote Alaska town, killing all 4 people aboardfoxnews.com
- Small plane crashes into shallow water near remote Alaska town, killing all 4 people aboardkotaradio.com
Revision history
- Version 727 Aug 2026, 09:25current
Updated to reflect the latest reporting, including the aircraft type, the time discrepancy, and the phase of flight discrepancy.
- Version 627 Aug 2026, 09:00
No changes from previous version.
- Version 527 Aug 2026, 08:22
Updated to reflect the latest reporting, including the aircraft type, the date, and the investigation status.
- Version 427 Aug 2026, 07:22
Added conflict on time and phase of flight; attributed figures to sources.
- Version 327 Aug 2026, 05:53
Updated to reflect the latest reporting; no material changes from previous version.
- Version 227 Aug 2026, 05:23
Updated to include the Times of India as a source and to note the developing status.
- Version 127 Aug 2026, 04:56
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.