Fatal NTSB investigations: Enstrom F-28C
5 cases on aircraft the registry lists as Enstrom F-28C. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1990 | 1 |
|---|---|
| 1993 | 1 |
| 1995 | 1 |
| 1999 | 1 |
| 2013 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3300407'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3300407'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun 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 ERA13LA433Accident · 1 fatalLimited investigationFinal reportEnstrom F-28C · Bloomsburg, PAThe relieved pilot’s failure to maintain clearance from the rotating main rotor blades after he exited the helicopter.NTSB SEA00FA014Accident · 1 fatalField investigationFinal reportEnstrom F28C · Pendleton, ORFailure to maintain clearance from the runway surface while maneuvering at low altitude, and inadequate remedial action after the tail rotor struck the surface.NTSB LAX95LA332Accident · 1 fatalLimited investigationFinal reportEnstrom F-28C · Livermore, CAthe pilot's inadequate preflight fuel load determination procedures which resulted in fuel exhaustion. In addition, the pilot's delayed and improper use of the collective and cyclic flight controls following the engine failure led to his failure to maintain…NTSB NYC93FA115Accident · 1 fatalField investigationFinal reportEnstrom F28C · Gordon, KYThe pilot's failure to see and avoid the wire.NTSB FTW91FA002Accident · 1 fatalField investigationFinal reportEnstrom F28-C · Mesquite, TXInstallation error of company maintenance personnel. Factors were the unsuitable terrain, the tailwind, the inability of the pilot to maintain main rotor RPM, and the inadequate annual inspection by company maintenance personnel.