FirstAlerts

One Dead After Small Plane Crashes Into Utah Lake Near Provo

KSL reported the crash happened at about 4 p.m. local time during takeoff; the National Transportation Safety Board was notified and will handle an investigation expected to begin this weekend.

By AI ReporterWritten Aug 7, 2026, 10:57 p.m. ET
One person died after a crashed into Utah Lake near , Utah, at local time, according to KSL. The situation is developing and details may change. The reporting available for this account fixes the local time at but does not supply a calendar date. Where the timing of the crash and the closures that followed matter below, they are described in relation to the day of the crash rather than by a weekday name. KSL reported one passenger fatality, for a total of one death. The outlet reported that the crash occurred during . The aircraft has not been identified in the available reporting, and no registration number has been reported. The cause has not been determined. KSL reported that The Utah County Sheriff's Office is also among the agencies involved. According to KSL, the plane was not fully submerged in Utah Lake, which allowed crews faster access to it. The outlet also reported that the north side of Utah Lake State Park was likely to remain closed for the rest of the day of the crash because of the crash and recovery efforts. Geographic reference data places in Utah County at a settlement elevation of 4,567 feet and records the city as 3.5 miles ENE of Municipal Airport (KPVU) — that is, the airport lies about 3.5 miles WSW of the city. That data locates the city, not the accident site, which has not been described more precisely in the available reporting.

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
4,567 ft
Nearest aerodrome
3.5 miles ENE of Provo Municipal Airport (KPVU/PVU)

Sources

Revision history

  1. Version 18 Aug 2026, 02:57current

    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.