NTSB investigations: Lycoming HIO-360 series, 2005
11 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\") = 2005
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") = 2005
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 CHI06TA033Accident · No injuriesFinal reportSchweizer 269C · Manhattan, KSThe binding of the main rotor blade's tachometer cable during cruise flight resulting in an observed split tachometer indication/aural alarm and perceived mechanical emergency and the unsuitable terrain the pilot encountered during the emergency landing. A…NTSB MIA06CA013Accident · No injuriesData collectionFinal reportSchweizer 269C-1 · Titusville, FLThe pilot-in-command's improper flare during a practice autorotative landing, which resulted in a hard landing.NTSB NYC06CA008Accident · No injuriesData collectionFinal reportEnstrom F-28C · Smoketown, PAThe student pilot's failure to maintain aircraft control while performing pedal turns at a hover, resulting in a collision with terrain.NTSB SEA05CA149Accident · Minor injuriesData collectionFinal reportHughes 269A · Laurel, MTthe pilot's failure to maintain rotor rpm while executing a pinnacle approach, which resulted in a loss of control and collision with terrain.NTSB DFW05CA168Accident · No injuriesData collectionFinal reportHughes 269C · Bruceville, TXThe flight instructor's improper flare during autorotation, which resulted in a hard landing. Contributing factor was, the lack of suitable terrain.NTSB DEN05FA080Accident · Serious injuriesField investigationFinal reportSchweizer 269C · Pueblo, COthe flight instructor's failure to maintain control of the helicopter during the attempted autorotation after the loss of engine power for reasons undetermined. Contributing factors include the flight instructor's improper preflight planning, the high density…NTSB IAD05LA075Accident · Minor injuriesLimited investigationFinal reportHughes TH-55 · Paintsville, KYthe pilot's inadvertent encounter with ground resonance which resulted in destruction of the helicopter.NTSB DEN05CA079Accident · No injuriesData collectionFinal reportSchweizer 269C · Pueblo, COthe student pilot's failure to maintain control of the helicopter during the landing. Contributing to the accident was the flight instructor's inadequate supervision of the student pilot.NTSB SEA05CA083Accident · No injuriesData collectionFinal reportHughes 269A · Whitefish, MTThe student pilot's failure to maintain control of the helicopter while hovering resulting in an in-flight collision with terrain. Gusting winds and the student pilot's inadequate compensation for the wind conditions were contributing factors.NTSB DEN05LA068Accident · No injuriesLimited investigationFinal reportEnstrom F-28C · Morrison, COthe pilot's failure to maintain rotor RPM during the approach which resulted in a landing short of the helipad.NTSB IAD05LA046Accident · Serious injuriesLimited investigationFinal reportSchweizer 269C · Leet, WVA fatigue fracture of the main transmission drive pinion. Also causal was the manufacturer's failure to remove the affected pinions from service during the period that transpired between the initial failures and the accident flight.