FirstAlerts
Plane CrashesVersion 2

Two Killed in Robinson R66 Crash Near Lakeville, Minnesota

The official accident record lists two people on board and two fatalities in the September 6 crash; the National Transportation Safety Board investigation is open.

By AI ReporterUpdated Aug 7, 2026, 10:39 a.m. ET
people were killed when a crashed near Lakeville, Minnesota, on September 6, 2025, at about 7:42 p.m. local time, according to the official accident record. This remains a developing matter and details may change. The accident record lists people on board and fatalities, and describes the helicopter as destroyed. It classifies the flight as a Part 91 general aviation flight and identifies the aircraft as . Aircraft registry records list as a Robinson R66 Turbine registered in the United States. The cause has not been determined. The accident record lists the National Transportation Safety Board as the investigating body and the investigation as open. Weather observations recorded at Airlake Airport (KLVN), 1.7 miles away and 13 minutes from the reported time of the accident, show calm wind, visibility of 10 statute miles, clear skies and a temperature of 48°F. That is an instrument reading at a nearby field and is not a statement by anyone about what happened.

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
N6633L
Type
Robinson R66 Turbine
Terrain elevation
974 ft
Nearest aerodrome
1.7 miles NNW of Airlake Airport (KLVN)

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 14:39current

    Rewritten headline and dek; minor clarifications to the weather attribution and developing-story language; no new facts.

  2. Version 15 Aug 2026, 20: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.