NTSB investigations: Lycoming HIO-360 series, 2006
9 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\") = 2006
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") = 2006
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 DFW07CA037Accident · No injuriesData collectionFinal reportHughes 269B · Houma, LAA partial loss of engine power as a result of a cracked engine cylinder and broken spark plug which resulted in a hard landing. A factor was that it was not possible to attain proper rotor RPM.NTSB LAX06LA290Accident · No injuriesLimited investigationFinal reportSchweizer 269C-1 · Van Nuys, CAInadequate maintenance adjustment and missing mixture spring, which resulted in a loss of engine power during approach.NTSB CHI06CA168Accident · No injuriesData collectionFinal reportSchweizer 269C · Grand Forks, NDThe dual student's failure to maintain rotor speed during the recovery from the intentional autorotation and the flight instructor's delayed remedial action. Contributing factors were the flight crew's intentional autorotation and dual student's misjudged…NTSB CHI06TA148Accident · Minor injuriesFinal reportSchweizer 269C · Schererville, INThe pilot's improper autorotation following an actual loss of engine power during a practice autorotation, which resulted in a hard landing. A factor associated with the accident was the loss of engine power at the beginning of the practice autorotation for…NTSB CHI06LA138Accident · 1 fatalLimited investigationFinal reportHughes 269A · Berlin Center, OHThe pilot flew at a low altitude and failed to maintain clearance from the wire. A factor was the wire.NTSB ATL06LA085Accident · No injuriesLimited investigationFinal reportHughes 269A · Concord, NCThe loss of engine power for undetermined reasons while maneuvering, resulting in a forced landing to uneven terrain and a roll over.NTSB SEA06LA096Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Boise, IDThe reduction of the throttle to idle at a high density altitude during a practice autorotation, which resulted in the engine stoppage. Factors contributing to the accident included the instructor pilot's improper planning by not adhering to the flight…NTSB CHI06CA131Accident · No injuriesData collectionFinal reportSchweizer 269C · Lees Summit, MOThe flight instructor's delay in taking remedial action which led to the hard landing during the practice autorotation. The misjudged glide path, the dual student restricting the throttle control, and the trees were factors in the accident.NTSB NYC06LA106Accident · Minor injuriesLimited investigationFinal reportSchweizer 269C · Kings Park, NYLoss of engine power due to the failure of the number 3 connecting rod bearing. A contributing factor was the lack of suitable terrain for the emrgency landing.