Final NTSB investigations: Enstrom 280
7 cases on aircraft the registry lists as Enstrom 280. 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
| 1975 | 1 |
|---|---|
| 1976 | 1 |
| 1982 | 3 |
| 1990 | 1 |
| 2016 | 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.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3300502'))
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."completionStatus" = 'Completed'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3300502'))
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 WPR16LA057Accident · Minor injuriesLimited investigationFinal reportEnstrom 280 · Phoenix, AZA total loss of engine power for reasons that could not be determined because postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation.NTSB NYC90LA090Accident · No injuriesLimited investigationFinal reportEnstrom 280 · Thornton, PAFailure to attain a proper climb rate after takeoff from a confined area. Factors include gusty winds and high obstructions.NTSB SEA82DA139Accident · No injuriesFinal reportEnstrom F280 · Seattle, WAHelicopter made an emergency forced landing after power loss aircraft landed heavily in loose dirt and damaged skids and rotors. Post-accident exam found "throttle activating arm was improperly engaged to throttle stop."NTSB DEN82FA148Accident · 1 fatalField investigationFinal reportEnstrom F-280 · Medora, NDDuring flt the plt noticed that eng RPM was about 500 over rotor RPM. The acft crashed during an unsuccessful autorotation. The overrunning clutch linkage & clutch was found in the disengaed position. A successful autorotation requires that the collective…NTSB CHI82DA199Accident · Serious injuriesFinal reportEnstrom 280 · Rayland, OHAbout three minutes after takeoff, the engine lost power and the helicopter crashed in a wooded area. No preimpact failures of the aircraft or engine were found.NTSB SEA76FYG48Accident · Serious injuriesClosedEnstrom F-28A · White Bird, IDNTSB NYC76FHM06Accident · Minor injuriesClosedEnstrom 280 · Mahwah, NJ