NTSB investigations: Enstrom F-28C
6 cases on aircraft the registry lists as Enstrom F-28C, where the first occurrence was “In flight collision with object”. 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
| 1993 | 1 |
|---|---|
| 1995 | 1 |
| 1997 | 1 |
| 1999 | 1 |
| 2002 | 2 |
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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3300407')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3300407')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 DEN03LA018Accident · Minor injuriesLimited investigationFinal reportEnstrom F-28C · Morrison, COthe pilot not maintaining clearance from the telephone lines during landing. Factors contributing to the accident were the pilot not being able to see the telephone lines, the low altitude, and the dark night.NTSB LAX02LA169Accident · Serious injuriesLimited investigationFinal reportEnstrom F-28C · Stockton, CAThe pilot's failure to maintain an adequate clearance from the water tower during takeoff. Also causal was the pilot's selection of a confined area for the landing and subsequent takeoff.NTSB LAX99LA226Accident · Minor injuriesLimited investigationFinal reportEnstrom F28C · Kaunakakai, HIThe pilot encountered a dust devil during the takeoff transition from a dirt and grass area resulting in a loss of vision, disorientation, and subsequent collision with trees.NTSB NYC97LA119Accident · Minor injuriesLimited investigationFinal reportEnstrom F-280C · Sharon, VTThe pilot's improper decision to descend and fly at 100 feet over a river and his failure to maintain adequate obstacle clearance, which resulted in the in-flight collision with wires.NTSB BFO96LA003Accident · No injuriesLimited investigationFinal reportEnstrom F28-280C · Blue Ash, OHthe commercial pilot's failure to maintain clearance from obstacles during hover-taxi operations. Related factors the tailwind, the nearby obstacle, and the misjudged maneuver to avoid obstacles.NTSB NYC93FA115Accident · 1 fatalField investigationFinal reportEnstrom F28C · Gordon, KYThe pilot's failure to see and avoid the wire.