NTSB investigations: Enstrom Helicopter 280C, CA
7 cases on aircraft the registry lists as Enstrom Helicopter 280C. 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
| 1981 | 1 |
|---|---|
| 1983 | 2 |
| 1986 | 1 |
| 1988 | 1 |
| 1990 | 1 |
| 1994 | 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\" = 'CA' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3300505'))
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" = 'CA' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3300505'))
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 LAX94LA239Accident · No injuriesLimited investigationFinal reportEnstrom 280C · California City, CAthe pilot's inadequate compensation for the gusty wind conditions and his subsequent failure to maintain control of the helicopter.NTSB LAX90LA121Accident · No injuriesLimited investigationFinal reportEnstrom F-28C · Canyon Lake, CAThe pilot to maintain proper rotor RPM during a practice autorotation. Contributing to the accident was the uneven terrain selected by the pilot to conduct practice touch maneuvers.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 LAX86LA291Accident · No injuriesLimited investigationFinal reportEnstrom EN-280-C · Los Altos, CAThe instructor stated that during a practice auto rotative landing the helicopter lost rotor RPM and a hard landing followed. On ground contact, the main rotor blades struck the tail cone, resulting in substantial damage. The instructor further stated that…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…NTSB LAX83LA134Accident · Minor injuriesLimited investigationFinal reportEnstrom F280C · Concord, CAThe helicopter collided with a tree during a landing after a decay in rotor RPM during takeoff. According to the pilot the acft was facing southeast prior to departure and the pilot estimated that the wind was from the northwest at 8 KTS. Following a pedal…NTSB LAX81FA089Accident · No injuriesClosedEnstrom F-280C · Bridgeport, CA