NTSB investigations: Lycoming HIO-360 series, 1997
12 cases on aircraft whose registry engine model is Lycoming HIO-360 series. 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
| 1964 | 2 |
|---|---|
| 1965 | 1 |
| 1966 | 1 |
| 1967 | 2 |
| 1968 | 1 |
| 1969 | 2 |
| 1971 | 3 |
| 1972 | 2 |
| 1973 | 4 |
| 1974 | 3 |
| 1975 | 2 |
| 1976 | 5 |
| 1977 | 6 |
| 1978 | 6 |
| 1979 | 10 |
| 1980 | 12 |
| 1981 | 9 |
| 1982 | 6 |
| 1983 | 6 |
| 1984 | 3 |
| 1985 | 8 |
| 1986 | 9 |
| 1987 | 6 |
| 1988 | 10 |
| 1989 | 14 |
| 1990 | 5 |
| 1991 | 3 |
| 1992 | 3 |
| 1993 | 15 |
| 1994 | 10 |
| 1995 | 4 |
| 1996 | 6 |
| 1997 | 12 |
| 1998 | 14 |
| 1999 | 7 |
| 2000 | 12 |
| 2001 | 10 |
| 2002 | 13 |
| 2003 | 15 |
| 2004 | 8 |
| 2005 | 11 |
| 2006 | 9 |
| 2007 | 9 |
| 2008 | 7 |
| 2009 | 3 |
| 2010 | 5 |
| 2011 | 9 |
| 2012 | 9 |
| 2013 | 9 |
| 2014 | 3 |
| 2015 | 11 |
| 2016 | 6 |
| 2017 | 1 |
| 2018 | 5 |
| 2019 | 4 |
| 2020 | 4 |
| 2021 | 4 |
| 2022 | 3 |
| 2023 | 3 |
| 2024 | 1 |
| 2025 | 2 |
| 2026 | 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 year(c.\"eventDate\") = 1997
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41524'))
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 year(c."eventDate") = 1997
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41524'))
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 ATL98LA021Accident · No injuriesLimited investigationFinal reportHughes TH-55 · Bushnell, FLThe pilot's failure to maintain clearance from the trees during a hover. A factor was the pilot's diverted attention.NTSB SEA98LA021Accident · No injuriesLimited investigationFinal reportEnstrom F-28F · John Day, ORa loss of engine power for undetermined reasons.NTSB NYC98LA025Accident · No injuriesLimited investigationFinal reportHughes 269B · Cleveland, OHthe pilot's failure to recover from settling-with-power. Factors relating to the accident were: the pilot's downwind approach and low airspeed.NTSB NYC98FA018Accident · No injuriesField investigationFinal reportEnstrom F-28C · Fairview, PAinadequate maintenance, which led to detonation and a melted piston, and subsequent power loss.NTSB CHI98LA021Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Grand Forks, NDthe pilot's inadequate preflight planning which resulted in a low fuel state, and his inability to see the wire which the helicopter contacted. Factors associated to the accident were the precautionary landing, the dark night conditions, and the wire which…NTSB ATL97LA114Accident · No injuriesLimited investigationFinal reportHughes 269A · Dandridge, TNthe pilot's failure to properly plan the approach for landing, which led to a loss of tail rotor authority and directional control, while close to the ground. The tailwind was a related factor.NTSB LAX97LA224Accident · Minor injuriesLimited investigationFinal reportEnstrom F-28-F · Riverside, CAfailure by unknown maintenance personnel to retorque the nuts on the retainer cover.NTSB ATL97LA067Accident · No injuriesLimited investigationFinal reportHughes 269A · Lake Wales, FLloss of engine power for undetermined reason(s); and the flight instructor's improper flare and improper use of the flight controls, while flaring for an autorotative landing.NTSB CHI97LA118Accident · No injuriesLimited investigationFinal reportHughes 269A · Council Bluffs, IAfailure of the student pilot to maintain directional control, inadequate supervision by the flight instructor (CFI), and subsequent failure of the pilot(s) to properly flare the helicopter during a hover autorotation.NTSB MIA97LA103Accident · Serious injuriesLimited investigationFinal reportHughes TH-55 · Cullman, ALa loss of engine power for undetermined reasons and the pilot-in-command's failure to maintain control of the helicopter. Factors in this accident were: an improper autorotation as a result of improper collective use and resulting failure to maintain main…NTSB IAD97GA054Accident · No injuriesFinal reportSchweizer 269C · Cleveland, OHThe engine failure from the rod cap bolt being sheared and the separation of the number two cylinder separating from the crankcase.NTSB MIA97LA084Accident · No injuriesLimited investigationFinal reportHughes 269A · Homosassa, FLthe unqualified person's poor judgment, by taking the helicopter without the owner's permission and attempting an unauthorized flight at night; and his failure (or inability) to maintain control the helicopter. Darkness was a related factor.