NTSB investigations: Lycoming HIO-360 series
19 cases on aircraft whose registry engine model is Lycoming HIO-360 series, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1982 | 1 |
|---|---|
| 1985 | 1 |
| 1986 | 2 |
| 1988 | 2 |
| 1993 | 1 |
| 1996 | 1 |
| 1998 | 2 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 2 |
| 2005 | 2 |
| 2006 | 1 |
| 2007 | 1 |
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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41524')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 130))
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 c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41524')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130))
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 LAX07LA106Accident · No injuriesLimited investigationFinal reportEnstrom F-28F · Monmouth, ORThe failure of the main drive belt tension assembly shaft due to high cycle, low stress fatigue.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 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 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.NTSB CHI04LA032Accident · Serious injuriesLimited investigationFinal reportHughes TH-55A · West Lafayette, INThe fractured cluster fitting resulting in a loss of directional control during initial climb and the improper repair of cluster fitting by unknown personnel. The night conditions were a contributing factor.NTSB CHI04IA018Incident · No injuriesIncident investigationFinal reportEnstrom F-28C · Lapeer, MIComplete failure of the right anti-torque cable while on final approach for landing. A factor was the diminished tail rotor control resulting from the broken cable.NTSB CHI02LA293Accident · No injuriesLimited investigationFinal reportHughes 269A · Council Bluffs, IAThe premature fracture of the cyclic/mixture bracket resulting in the inability to conduct a landing flare.NTSB DEN02LA098Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Broomfield, COmaintenance personnel's failure to secure the landing skid oleo strut bolt during the last 50-hour inspection, causing the left rear skid to collapse and the tail rotor to strike the ground.NTSB NYC01LA167Accident · Minor injuriesLimited investigationFinal reportHughes 269A · Clay, NYFailure of the left aft cluster fitting due to a fatigue crack. Factors in the accident were the mechanic's failure to identify the crack at the last annual inspection, and the pilot's failure to identify the crack during the last daily inspectionNTSB 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 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 FTW96LA095Accident · No injuriesLimited investigationFinal reportSchweizer 269C · San Ygnacio, TXFailure of the rotor drive system clutch assembly (separation of the swedge ball from the end of the clutch control cable), which resulted in disengagement of the rotor drive system, while the helicopter was in lateral movement at low altitude.NTSB CHI94LA013Accident · No injuriesLimited investigationFinal reportHughes 269A · Coldwater, MIthe fatigue failure of the tailboom support strut attachment lug.NTSB FTW89LA010Accident · No injuriesLimited investigationFinal reportHughes 269C · Dickens, TXThe pilot was inspecting a herd of cattle when he thought the helicopter was developing a problem with the engine and main rotor. He started an autorotation, lost tail rotor control, and went into a left spin which continued to contact with the ground.…NTSB SEA88LA073Accident · No injuriesLimited investigationFinal reportHughes 269C · Sitka, AKDuring sling operations, the long line became separated and entangled in the tail rotor at about 300 feet AGL. The pilot landed the helicopter onto a beach area where it rolled over onto its left side striking the main rotor. No accident report has been filed…NTSB NYC87MA024Accident · 1 fatalMajor investigationFinal reportEnstrom F-28F · Manhattan, NYThe aircraft was contracted by nbc to make daily highway traffic observations in the new york city area. The pilot and passenger, an nbc radio traffic reporter, were flying in a northerly direction along Manhattan's west side at an altitude of about 75 feet.…NTSB CHI86LA127Accident · Minor injuriesLimited investigationFinal reportHughes 269A · Ft. Wayne, INApprox 10-15 minutes after takeoff the student pilot lost control of the helicopter and crash landed into trees. Following the accident, the only unusual thing FAA personnel could locate was a failed horizontal stabilizer spar. Post-crash examination of the…NTSB SEA85LA079Accident · No injuriesLimited investigationFinal reportHughes 269C · Elma, WAJust prior to lift-off a vibration accompanied by lateral rocking occurred. Although the plt brought the power to idle. The helicopter had already started to come apart. During engine examination it was found that the ground resonance occurred due to under to…NTSB LAX82DA283Accident · No injuriesFinal reportEnstrom F28C · Phoenix, AZThe helicopter made a forced landing in a cotton field after tail rotor driveshaft failure. Examination showed a ductileshear overload failure. No evidence of fatigue was reported.