NTSB investigations: Enstrom Helicopter 280C
5 cases on aircraft the registry lists as Enstrom Helicopter 280C, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1983 | 3 |
|---|---|
| 1988 | 1 |
| 2006 | 1 |
Where
Latest 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 ('3300505')
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\" = 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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3300505')
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" = 130))
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 NYC06LA175Accident · Minor injuriesLimited investigationFinal reportEnstrom 280C · Danville, WVA partial failure of the override clutch assembly. A contributing factor to the accident was the manufacturer's inadequate inspection procedures of the override clutch assembly following a tail rotor strike.NTSB LAX88FA140Accident · No injuriesField investigationFinal reportEnstrom 280C · Fremont, CAFailure of the engine to main rotor drive system due to a drive belt slippage caused by a drive pulley worn beyond its service limit. Contributing to the accident was the inadequate factory maintenance manuals which did not provide the serviceable limits for…NTSB SEA83FA135Accident · Minor injuriesField investigationFinal reportEnstrom 280C · Kent, WADuring a traffic reporting flt for a radio station, the plt noted the onset of a severe vibration which he felt through the antitorque pedals. He stated that within seconds, the helicopter lost directional control & began a rapid, uncontrolled spin to the…NTSB FTW83LA287Accident · No injuriesLimited investigationFinal reportEnstrom 280C · Frisco, TXThe plt reported that during flt, the low pressure fuel light illuminated & the nose of the helicopter yawed to the left as if the eng had lost power. He made a precautionary landing in a soft, plowed field with a forward speed of about 10 to 15 mph. During…NTSB LAX83LA248Accident · Minor injuriesLimited investigationFinal reportEnstrom 280C · Goshen, CAAbout 5 min after taking off, the plt noticed a sudden loss of power to the tail rotor. He made an emergency landing in an alfalfa field. He reported that during an autorotative landing, he had insufficient collective to flare properly. Subsequently, the main…