Cirrus Vision Jet Involved in Idaho Takeoff Collision Identified as N71KD
The aircraft that hit construction material during takeoff at Driggs, Idaho, has been identified as a Cirrus Vision Jet registered N71KD.
2 reports on this incident · first at Aug 21, 2026, 6:45 a.m. ET
Earlier reports
Aug 21, 2026, 6:45 a.m. ETFirst report
Cirrus Vision Jet Hits Construction Material During Takeoff in Idaho
A Cirrus Vision Jet collided with construction material during takeoff at Driggs/Reed Memorial Airport in Idaho on August 14, 2026, according to Flying. The incident occurred at approximately 6:30 a.m. MDT. One person was injured, Flying reported.
The aircraft, registered N71KD, attempted takeoff through a portion of runway under construction and hit gravel, causing the landing gear to collapse, Flying reported. The Federal Aviation Administration and the National Transportation Safety Board are investigating; the cause has not been determined.
Registry records list the aircraft as a Cirrus Design Corp SF50, serial number 0433, with Vision71 LLC as the registered owner of record; the owner of record is not necessarily the operator of the flight. The NTSB database lists 11 other cases involving the SF50 since 2008, none of which involved a fatality; that record says nothing about the cause of this accident.
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
- N71KD
- Type
- Cirrus Design Corp SF50 — single-engine jet landplane
- Registered owner
- Vision71 LlcThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
- Terrain elevation
- 6,115 ft
- Nearest aerodrome
- 1.5 miles SSW of Driggs/Reed Memorial Airport (KDIJ)
Sources
Revision history
- Version 121 Aug 2026, 10:52current
First published.
- Version 121 Aug 2026, 10:45current
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.