NTSB investigations: Lycoming HIO-360 series, 1993
15 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\") = 1993
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") = 1993
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 CHI94LA013Accident · No injuriesLimited investigationFinal reportHughes 269A · Coldwater, MIthe fatigue failure of the tailboom support strut attachment lug.NTSB MIA94LA002Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Opa-Locka, FLImproper servicing of three of the four main landing gear dampers by company maintenance personnel, and innadequate remedial action by the pilot as ground resonance began.NTSB ATL94LA002Accident · No injuriesLimited investigationFinal reportHughes 269B · Linville, NCThe pilot's failure to maintain airspeed that would have avoided a loss of tail rotor effectiveness (lte), and his improper compensation for tailwind condition. A factor was the lack of information in the pilot's operating handbook regarding the conditions…NTSB SEA93FA178Accident · No injuriesField investigationFinal reportEnstrom F-28C · Seattle, WAShorted magneto condensers. Factors include a hidden obstruction in the landing area, and a reduction in rotor RPM from attempting to avoid the obstruction.NTSB MIA93LA177Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Punta Gorda, FLThe pilot-in-command's improper use of the flight controls (cyclic and collective pitch) during a simulated autorotation with turn, resulting in an in flight collision with terrain with the tail skid and tailrotor blades.NTSB NYC93GA151Accident · Serious injuriesFinal reportEnstrom F-28C · Gallipolis, OHThe pilot's improper use of the collective and throttle which resulted in a low rotor rpm condition and a loss of control, and an inflight collision with the terrain.NTSB DEN93LA070Accident · No injuriesLimited investigationFinal reportEnstrom F-28C · Boulder, COA failure by the pilot flying to adequately compensate for wind conditions which led to a loss of tail rotor control. A factor was: inadequate supervision by the pilot in command.NTSB LAX93FA260Accident · 1 fatalField investigationFinal reportHughes 269A · Henderson, NVthe pilot's improper use of the collective control and his failure to maintain adequate RPM during an autorotative descent during a practice power off landing. A factor which contributed to the accident related to the pilot's lack of recent experience…NTSB NYC93FA115Accident · 1 fatalField investigationFinal reportEnstrom F28C · Gordon, KYThe pilot's failure to see and avoid the wire.NTSB CHI93LA208Accident · No injuriesLimited investigationFinal reportHughes 269 · Valley City, NDthe pilot-in-command's failure to maintain clearance from a tree during an aerial application manuever.NTSB CHI93DEE01Accident · No injuriesFinal reportMark Streitz Skybolt · Joliet, ILthe failure of the number two connecting rod bolt.NTSB LAX93LA227Accident · No injuriesLimited investigationFinal reportHughes 269C · Van Nuys, CAthe student pilot's failure to maintain the altitude while maneuvering toward the parking area. The student pilot's lack of total experience was a factor in this accident.NTSB MIA93LA061Accident · No injuriesLimited investigationFinal reportHughes 269A · Jacksonville, FLThe failure of the pilot-in-command to monitor fuel quantity due to inattentiveness. Contributing to the accident was the improper use of the collective flight control during the soft field autorotation.NTSB BFO93FA019Accident · 2 fatalField investigationFinal reportHughes 269C · Tonawanda, NYImproper inflight planning/decision by the pilot and his failure to maintain clearance from an obstacle during flight. Factors related to the accident include poor visibility and weather conditions at dusk, and the pilot's excessive airspeed for the…NTSB LAX93LA087Accident · Serious injuriesLimited investigationFinal reportHughes 269C · Folsom, CAThe pilot failing to maintain an adequate visual lookout resulting in the helicopter colliding with electrical transmission wires.