NTSB investigations: Lycoming HIO-360 series, 1998
14 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
Latest 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\") = 1998
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") = 1998
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 CHI99LA006Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Oshkosh, NEthe pilot's failure to maintain control of the helicopter. Factors associated with the accident were the high winds, low altitude at which the pilot was maneuvering and the uneven terrain which the helicopter contacted.NTSB CHI98LA332Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Decker, INThe pilot's failure to maintain obstacle clearance resulting in a collision with a fence.NTSB FTW98LA362Accident · Minor injuriesLimited investigationFinal reportHughes 269C · Houston, TXThe pilot's failure to refuel the helicopter which resulted in the loss of engine power due to fuel exhaustion. A factor was the lack of suitable terrain for the forced landing.NTSB MIA98LA221Accident · No injuriesLimited investigationFinal reportEnstrom F-28F · Marco Island, FLThe pilot's inadequate fuel management which led to fuel exhaustion. A related factor was the pilot's improper use of the flight controls during autorotation.NTSB ANC98LA109Accident · No injuriesLimited investigationFinal reportEnstrom F-28F · Skwentna, AKA loss of engine power due to a fractured number three cylinder intake manifold flange, and the pilot's inability to maintain the proper rate of descent during the autorotation flare. A contributing factor associated with the accident was the downwind…NTSB FTW98LA279Accident · No injuriesLimited investigationFinal reportSchweizer 269C · San Angelo, TXThe improper touchdown executed by the flight instructor, which resulted in the tail rotor impacting the ground.NTSB CHI98LA166Accident · No injuriesLimited investigationFinal reportEnstrom F28 · West Chicago, ILthe student pilot attempting a tailwind landing and improper compensation for the wind resulting in too high of a sink rate and the hard landing.NTSB ATL98LA065Accident · No injuriesLimited investigationFinal reportSchweizer 269C · San Juan, PRThe pilot's failure to adequately secure the cargo strap which became entangled in the tail rotor, leading to a loss of the tail rotor control. This was followed by an improperly executed emergency procedure and an in-flight collision with the ground. A…NTSB ANC98LA037Accident · Minor injuriesLimited investigationFinal reportEnstrom F-28F · Haines, AKThe pilot flaring too low during an improper practice autorotation.NTSB MIA98LA127Accident · No injuriesLimited investigationFinal reportSchweizer 269-C · Ormond Beach, FLThe CFI's inadequate supervision and poor communication which led the rated student pilot to roll the throttle off, and the CFI's subsequent failure to apply forward cyclic to increase airspeed which resulted in the subsequent hard landing and roll over.NTSB SEA98FA055Accident · No injuriesField investigationFinal reportEnstrom F28F · Baker, ORFatigue failure of the steel tubing pylon structure. Factors include inadequate inspection by maintenance personnel of damage after a previous accident.NTSB FTW98LA129Accident · No injuriesLimited investigationFinal reportEnstrom F-28C-2 · Broomfield, COwater contamination in the fuel, which resulted in loss of engine power and a forced (autorotative) landing. Factors relating to the accident were: darkness; and a high obstruction in the emergency landing area.NTSB FTW98TA104Accident · Minor injuriesFinal reportHughes 269C · Brackettville, TXfailure of splines on the drive shaft coupling after separation of the forward bubber boot and loss of lubrication (grease), which resulted in a disconnect of the rotor drive system and an autorotation/forced landing. Lack of suitable terrain in the forced…NTSB FTW98LA084Accident · No injuriesLimited investigationFinal reportHughes 269C · Riviera, TXThe total loss of engine power due to a fatigue failure of the crankshaft for undetermined reason. A factor was the lack of suitable terrain for the forced landing.