NTSB investigations, SD
7 cases where the first occurrence was “Overrun”.
Cases per year
| 1982 | 1 |
|---|---|
| 1985 | 1 |
| 1988 | 1 |
| 1993 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2004 | 1 |
Where
Open the mapLatest 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\" = 'SD' 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" = 'SD' 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 CHI04LA201Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Custer, SDThe pilot's poor preflight planning/preparation and the pilot used improper aborted takeoff procedures by not reducing the throttle. Factors associated with the accident were the high density altitude and the tailwind.NTSB CHI00LA192Accident · No injuriesLimited investigationFinal reportCreed Lancair 235 · Hot Springs, SDthe failure of the pilot to select the correct runway for takeoff. Factors to the accident were the inadequate preflight planning/preparation, the aborted takeoff not performed, and the tailwind.NTSB CHI00LA013Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Custer, SDthe pilot's inadequate preflight planning and decision to perform an intersection takeoff, and the improper short field, rolling, intersection takeoff. A factor relating to this accident was the trees.NTSB CHI93DTK01Accident · 1 fatalFinal reportCrowser Avid MK 3.75 · Philip, SDThe pilot's selection of unsuitable terrain for takeoff, and the pilot inadvertently stalling the airplane.NTSB DEN88LA208Accident · No injuriesLimited investigationFinal reportCessna 421B · Winner, SDThe private plt and 4 pax were attempting takeoff on rwy 13, a 3,900 x 30 ft asphalt rwy. The plt said the acft accelerated to 100 knots but he could not raise the nose for lift off. The plt said he aborted the takeoff and intentionally ground looped to the…NTSB DEN86LA043Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Hayes, SDThe plt stated that during the uphill ldg on snow covered terrain, the acft crested the hill, then started downhill on the opposite side. According to the plt he was unable to stop the acft before reaching a cliff. The plt egressed the acft prior to it going…NTSB DEN82DA070Accident · No injuriesFinal reportBellanca 7ECA · Spearfish, SDThe student pilot departed on runway 30 to practice touch and go landings. He immediately entered the traffic pattern for runway 26. He said he made a power on, soft field landing, touching down at 65 knots IAS, and then immediately started a takeoff.…