Fatal NTSB investigations, SC
12 cases where the first occurrence was “Loss of engine power(total) - nonmechanical”.
Cases per year
| 1990 | 1 |
|---|---|
| 1992 | 1 |
| 1995 | 2 |
| 1996 | 1 |
| 1997 | 2 |
| 1999 | 1 |
| 2000 | 2 |
| 2002 | 1 |
| 2005 | 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\" = 353)
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" = 353) 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 ATL05FA135Accident · 2 fatalField investigationFinal reportBeech V35B · Rock Hill, SCThe pilot's mismanagement of the fuel supply , which resulted in fuel starvation and subsequent loss of engine power.NTSB MIA02FA144Accident · 1 fatalField investigationFinal reportPiper PA-28-180 · Cheraw, SCThe misrouting of the fuel lines to the fuel selector, which resulted in the use of a fuel tank with inadequate fuel supply, fuel starvation, and the loss of engine power. Contributing was the pilot's inadequate remedial action for conducting an emergency…NTSB MIA00FA117Accident · 1 fatalField investigationFinal reportCessna 177RG · Columbia, SCThe PIC's inadequate planning and preparation resulting in refueling not being performed and the subsequent fuel exhaustion and forced landing into trees. A factor in the accident was the erratic operation of the right fuel tank quantity indicating system.NTSB ATL00FA021Accident · 2 fatalField investigationFinal reportPiper PA-24-180 · Cordesville, SCThe pilot's inadequate inflight planning that resulted in fuel exhaustion and the subsequent loss of engine power.NTSB MIA99FA232Accident · 1 fatalField investigationFinal reportBeech C24R · Pickens, SCThe pilot's failure to properly preflight plan and prepare for the flight's fuel consumption resulting in engine loss of power due to fuel exhaustion and the subsequent inflight collision with trees.NTSB ATL97FA134Accident · 2 fatalField investigationFinal reportNorth American T-6-SNJ5 · Camden, SCThe pilot's failure to take remedial action after a loss of engine power for undetermined reasons, leading to a spin. Factors were the pilot's use of unapproved medication, and the FAA's inadequate certification and standards for airman.NTSB ATL97FA090Accident · 1 fatalField investigationFinal reportBeech 35-C33A · Lugoff, SCimproper fuel management by the pilot by not positioning the fuel selector to the fullest tank for landing, which resulted in fuel starvation, loss of engine power, and a forced landing. Trees in the emergency landing area were a factor.NTSB ATL96FA049Accident · 2 fatalField investigationFinal reportPiper PA-28-181 · Johns Island, SCthe pilot's inadequate evaluation of the weather conditions and the continued flight into icing conditions which resulted in the loss of engine power. A factor was conditions favorable for the formation of carburetor icing.NTSB ATL96FA022Accident · 1 fatalField investigationFinal reportPiper PA-46-310P · Greenwood, SCthe loss of engine power for undetermined reason.NTSB MIA95FA183Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Hilton Head Isl, SCloss of engine power for undetermined reasons, and the unsuitable terrain encountered during the emergency landing. A factor in the accident was the pilot's extension of the downwind leg which prevented landing on the intended runway following loss of engine…NTSB ATL92FA040Accident · 2 fatalField investigationFinal reportCessna 140 · Columbia, SCThe pilot-in-command's failure to assure that an adequate supply of fuel was on board the airplane for the intended flight, and his failure to maintain adequate airspeed during the forced landing resulting in a stall/spin. A factor contributing to the…NTSB ATL90FA075Accident · 1 fatalField investigationFinal reportSikorsky HSS-1N · Cross, SCImproper planning/decision by the pilot, which resulted in fuel exhaustion due to an inadequate supply of fuel, and his failure to fly the helicopter in such a manner that would have assured sufficient rotor RPM for an autorotation.