NTSB investigations: Lycoming HIO-360 series, 2010
5 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\") = 2010
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") = 2010
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 WPR10CA442Accident · No injuriesData collectionFinal reportSchweizer 269C · Caldwell, IDThe failure of both pilots to maintain adequate main rotor RPM, the flight instructor's delayed remedial actions, and inadequate supervision of the flight.NTSB ERA10CA432Accident · No injuriesData collectionFinal reportSchweizer 269C-1 · Titusville, FLThe instructor's delayed remedial action, which resulted in a loss of rotor rpm and a hard landing.NTSB ERA10CA399Accident · No injuriesData collectionFinal reportSchweizer 269C · Baldwin, FLA loss of tail rotor effectiveness during a hover.NTSB CEN10CA390Accident · No injuriesData collectionFinal reportSchweizer 269C · Santa Rosa, NMThe student pilot's failure to maintain control of the helicopter while landing in gusty surface winds conditions. Contributing to the accident was the flight instructor's inadequate monitoring of the flight.NTSB ERA10CA134Accident · No injuriesData collectionFinal reportEnstrom F-28C · Fort Pierce, FLThe pilot's inadvertent encounter with settling with power while hovering downwind.