Fatal NTSB investigations, SC
12 cases where the first occurrence was “Airframe/component/system failure/malfunction”.
Cases per year
| 1983 | 1 |
|---|---|
| 1984 | 1 |
| 1987 | 2 |
| 1988 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 2001 | 1 |
| 2002 | 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\" = 'SC' AND c.\"eventCountry\" = 'USA'
AND c.\"highestInjuryLevel\" = 'Fatal'
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\" = 130)
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" = 'SC' AND c."eventCountry" = 'USA' AND c."highestInjuryLevel" = 'Fatal' 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" = 130) 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 ATL02FA101Accident · 2 fatalField investigationFinal reportLuscombe LL-8-E · Olar, SCThe in-flight separation of the elevator push-pull control tube that resulted in a loss of flight control and subsequent collision with the ground.NTSB MIA01FA206Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-35 · Hilton Head, SCImproper maintenance/installation and and inadequate inspection of the airplane's flap torque tube joints during routine maintenance by company maintenance personnel, which resulted in the right flap torque tube assembly coupler becoming detached and the…NTSB ATL98FA017Accident · 4 fatalField investigationFinal reportMark Ewart Velocity Standard RG · Florence, SCimproper maintenance procedures used by the pilot/repairman, which resulted in the loosening and eventual failure of the propeller. Factors relating to the accident were: the pilot's self-imposed pressure to hurry to the destination, and trees in the forced…NTSB MIA96FA130Accident · 1 fatalField investigationFinal reportHelio H-295 · Gaffney, SCfailure of the pilot to remove the control lock during the preflight, and his failure to check the flight controls before taking off.NTSB ATL95FA049Accident · 1 fatalField investigationFinal reportCessna 150J · Piedmont, SCThe pilot's inappropriate 'buzzing' that resulted in exceeding the airplane's design stress limits, the failure of the windshield, and the pilot's subsequent loss of control and impact with the ground.NTSB ATL91FA020Accident · 2 fatalField investigationFinal reportMooney M20F · Pageland, SCFailure of the pilot to maintain control of the aircraft, due to spatial disorientation. Factors related to the accident were: the weather conditions and the malfunction of a gyro instrument (probably the attitude indicator).NTSB ATL90FA100Accident · 1 fatalField investigationFinal reportBell 205A-1 · Moncks Corner, SCThe in-flight separation of the main rotor because of the failure of a pillow block bolt, and the failure of the operator/repair station to follow the overhaul procedures.NTSB ATL88FA186Accident · 1 fatalField investigationFinal reportCessna 402B · West Columbia, SCThe airplane used about 1/2 of the 8,602 ft rwy for the t/o roll. After t/o it pitched nose-down briefly over the rwy during init climb. The plt radioed that he was having a problem with the elevator which required 'full back pressure' to keep the nose up,…NTSB ATL88MA048Accident · 2 fatalMajor investigationFinal reportBeech C90 · Beaufort, SCAt 0938, while clbg thru 9000', the plt was clrd to clb to FL 210. Aprx 10 min later, the ATC ctlr noted the acft's mode c rtrn wasn't being displayed on his scope. He tried to adz the plt, but couldn't establish radio contact. The acftbroke up in flt & the…NTSB ATL87FA147Accident · 1 fatalField investigationFinal reportHiller UH-12D (H23) · Spartanburg, SCDuring a local pleasure flight above the treetops, the passenger reported that they heard a loud 'pop' over the sound of the engine. The plt told her that they were going down and she noticed the main rotor blades began to turn slower than usual before the…NTSB ATL84FA298Accident · 1 fatalField investigationFinal reportBeech V35B · Mc Cormick, SCN6740Z, a Beech V35B acft,separated in flt over mccormick, SC while operating in VFR conditions. The investigation failed to locate witnesses who observed the flt prior to & during the inflight separation. Witnesses on the ground heard the acft & observed…NTSB ATL83FA081Accident · 3 fatalField investigationFinal reportPiper PA-24-250 · Beaufort, SCWhile en route in IMC, the ATC controller noted that the acft began to reverse course & asked the plt if he was having a problem. The plt responded that the acft was in clouds, he was having problem with his artificial horizon & that he didn't realize he was…