NTSB investigations: Lycoming HIO-360 series, 1994
10 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\") = 1994
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") = 1994
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 FTW95LA039Accident · No injuriesLimited investigationFinal reportHughes 269A · Monticello, ARThe loss of engine power due to a fatigued rod end bolt. A factor was the lack of suitable terrain for landing.NTSB CHI94LA316Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Grand Forks, NDthe pilot-in-command's (CFI) delayed recovery from a practice autorotation. A factor associated with the accident was the student pilot's improper autorotation.NTSB ANC94LA132Accident · No injuriesLimited investigationFinal reportJames Chisum CHISUM-SCRAPS · Fairbanks, AKThe failure of the pilot to maintain directional control of the airplane. Factors in the accident were the soft terrain and inadequate remedial action.NTSB FTW94LA253Accident · No injuriesLimited investigationFinal reportHughes 269A · Leander, LAInadequate maintenance and a fatigue failure of a #1 cylinder connecting rod bolt. A factor was the lack of suitable terrain available to the pilot for a forced landing.NTSB SEA94LA153Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Hillsboro, ORThe improper servicing of the skid shock struts.NTSB FTW94GA204Accident · Minor injuriesFinal reportHughes 269C · London, TXThe partial power loss due to a sticking valve. Factors were the remaining worn lobes on the camshaft and the lack of suitable terrain onto which a successful forced landing could be executed.NTSB ATL94LA100Accident · Serious injuriesLimited investigationFinal reportSchweizer 269C · Hiram, GAThe inadvertent flight from VMC conditions to IMC conditions by the pilot. A factor in the accident was the ground fog in the area.NTSB ATL94LA095Accident · Serious injuriesLimited investigationFinal reportSchweizer 300C · Randleman, NCThe pilot's failure to adequately preflight the helicopter which resulted in a complete loss of engine power. A factor was water in the fuel supply.NTSB CHI94LA138Accident · Minor injuriesLimited investigationFinal reportSchweizer 269C · Fargo, NDthe pilot in command's improper autorotation technique. A factor associated with the accident is the FAA Inspector's delayed remedial action.NTSB LAX94LA201Accident · No injuriesLimited investigationFinal reportSchweizer 300C · Pacific Ocean (Pacific Ocean)The low altitude of the aircraft when the engine lost power and the pilot's misjudgement of the flare point during the autorotation. Factors in the accident were the loss of engine power and the sunglare.