NTSB investigations, UT
14 cases where the first occurrence was “Overrun”.
Cases per year
| 1982 | 2 |
|---|---|
| 1983 | 1 |
| 1986 | 1 |
| 1989 | 2 |
| 1990 | 1 |
| 1992 | 2 |
| 1994 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 1999 | 1 |
| 2006 | 1 |
Where
Latest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"eventStateOrRegion\" = 'UT' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 340)
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1 WHERE c."eventStateOrRegion" = 'UT' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o."occurrenceNumber" = 1 AND o."occurrenceCode" = 340) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB SEA06LA075Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Bullfrog Basin, UTA high airspeed at touchdown resulting in a high ground speed during the landing roll. Downhill sloping runway, a tailwind, the pilot's delayed remedial action and rough terrain off the end of the runway were factors.NTSB DEN99LA118Accident · No injuriesLimited investigationFinal reportPiper PA-25-235 · Delta, UTThe pilot's delayed aborted takeoff. A factor was the high density altitude.NTSB FTW97LA360Accident · No injuriesLimited investigationFinal reportSchweizer SGS 1-34 · Heber City, UTThe pilot's improper use of spoilers during the landing sequence. Factors were the embankment and the fence.NTSB SEA96LA147Accident · Minor injuriesLimited investigationFinal reportSchleicher ASW-19 · Salem, UTThe pilot's failure to attain a proper touchdown point during an off-airport landing. Factors relating to the accident were: loss of thermal lift, high obstructions (transmission wires) near the edge of the field that the pilot chose to land, and a bale of…NTSB SEA94LA104Accident · No injuriesLimited investigationFinal reportCessna 182 · Hanksville, UTThe excess airspeed maintained by the pilot on final approach, and his failure to attain the proper touchdown point. Factors include loose gravel, and a berm off the end of the intended landing strip.NTSB SEA93LA028Accident · No injuriesLimited investigationFinal reportCessna A152 · Tremonton, UTDelayed remedial action. Factors include a tailwind.NTSB SEA92LA050Accident · No injuriesLimited investigationFinal reportCessna 182D · Monroe, UTAn aborted takeoff was not performed. The wet, soft runway was a factor.NTSB DEN90LA094Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Bountiful, UTThe flight instructor's inadequate supervision of the dual student. Factors in the accident were the premature lift-off by dual student, the rough terrain and the fence.NTSB DEN89LA169Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Salt Lake City, UTThe pilot's improper use of the parking brake and his delay in aborting the takeoff. Factors related to the accident were: the fence & vehicle.NTSB DEN89LA135Accident · No injuriesLimited investigationFinal reportCessna 210 · Halls Crossing, UTInadequate aircraft handling by the pilot, resulting in a runway overrun.NTSB DEN86LA191Accident · No injuriesLimited investigationFinal reportPiper PA-60-601P · Provo, UTPlt and three pax flew from el paso, TX to Provo, UT en route to Alaska vacation. Left main tire blew after acft touched down. Acft veered to left and went off rwy. Examination of tire revealed large hole but with good tread remaining. Acft damage was…NTSB DEN83LA126Accident · Minor injuriesLimited investigationFinal reportCessna 182Q · New Harmony, UTThe acft ran off the departure end of the rwy during landing after going through a fence/bushes and the acft nosed over. The pilot had made one go-around because of excessive airspeed. He said the windsock was limp as he obseved it. However,winds at cedar…NTSB DEN82DA145Accident · No injuriesFinal reportCessna 152 · Woods Cross, UTThe student pilot stated that during the takeoff roll, he discovered the airspeed indicator was not operating. Also, he said that he accumulated excessive ground speed and made a decision to abort the takeoff. The aircraft was damaged when the pilot was…NTSB DEN82DA053Accident · No injuriesFinal reportCessna T210G · Moab, UTThe aircraft was found on an abandoned dirt runway near deadhorse point. Investigation indicated that the aircraft touched down long on runway 21 and collided with an elevated dirt road that crosses the runway. Two impact marks were found on the instrument…