NTSB investigations: Lycoming HIO-360 series, 2002

13 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

19642026
NTSB investigations: Lycoming HIO-360 series, 2002 per year, 1964–2026: 390 cases
19642
19651
19661
19672
19681
19692
19713
19722
19734
19743
19752
19765
19776
19786
197910
198012
19819
19826
19836
19843
19858
19869
19876
198810
198914
19905
19913
19923
199315
199410
19954
19966
199712
199814
19997
200012
200110
200213
200315
20048
200511
20069
20079
20087
20093
20105
20119
20129
20139
20143
201511
20166
20171
20185
20194
20204
20214
20223
20233
20241
20252
20262

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\") = 2002
    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.

NTSB LAX03LA052Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Los Banos, CAThe improper engine overhaul by other maintenance personnel, which resulted in an exhaust valve failure and a total loss of engine power while in maneuvering flight.Dec 18, 2002 · N642KC · Substantial damageNTSB DEN03LA018Accident · Minor injuriesLimited investigationFinal reportEnstrom F-28C · Morrison, COthe pilot not maintaining clearance from the telephone lines during landing. Factors contributing to the accident were the pilot not being able to see the telephone lines, the low altitude, and the dark night.Nov 23, 2002 · N552CS · Substantial damageNTSB 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.Sep 24, 2002 · N1040S · Substantial damageNTSB 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.Aug 20, 2002 · N7508L · Substantial damageNTSB ATL02LA159Accident · Serious injuriesLimited investigationFinal reportSchweizer 300C · Haleyville, ALThe failure of maintenance personnel to perform an adequate inspection of loose intake components, which resulted in a total loss of engine power and subsequent emergency descent, forced landing, and collision with terrain in dark night conditions.Aug 17, 2002 · N269FW · Substantial damageNTSB SEA02LA150Accident · No injuriesLimited investigationFinal reportHughes 269A · Covington, WAAircraft control not maintained while hovering.Aug 10, 2002 · N90271 · Substantial damageNTSB ATL02LA141Accident · No injuriesLimited investigationFinal reportHughes HU-269-A · Hamilton, ALThe pilot's improper use of flight controls that resulted in an improper flare and a hard landing during a practice autorotation. A factor was the loss of rotor rpm.Jul 12, 2002 · N911LH · Substantial damageNTSB LAX02LA169Accident · Serious injuriesLimited investigationFinal reportEnstrom F-28C · Stockton, CAThe pilot's failure to maintain an adequate clearance from the water tower during takeoff. Also causal was the pilot's selection of a confined area for the landing and subsequent takeoff.May 20, 2002 · N51716 · Substantial damageNTSB LAX02LA161Accident · Minor injuriesLimited investigationFinal reportSchweizer 269C · Phoenix, AZthe CFI's failure to maintain an adequate airspeed resulted in a settling with power, and the CFI's failure to take remedial action. A factor in the accident was the high density altitude.May 13, 2002 · N577TA · Substantial damageNTSB SEA02LA075Accident · No injuriesLimited investigationFinal reportEnstrom F-28C · Hot Springs, MTThe pilot's failure to adequately compensate for unfavorable wind conditions. Factors include unfavorable/shifting winds, and a tailwind gust.Apr 20, 2002 · N51769 · Substantial damageNTSB LAX02LA137Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Scottsdale, AZThe flight instructor's inadequate remedial action following the onset of ground resonance.Apr 14, 2002 · N324PH · Substantial damageNTSB FTW02LA104Accident · No injuriesLimited investigationFinal reportHughes 269A-1 · Fort Collins, COthe flight instructor's failure to maintain control of the helicopter while hovering. Contributing factors were the tailwind and gusty wind conditions.Mar 27, 2002 · N8942F · Substantial damageNTSB MIA02LA070Accident · No injuriesLimited investigationFinal reportHughes 269C · Bessemer, ALThe failure of the flight instructor to adequately monitor the student's rotorcraft control, resulting in an abrupt cyclic input causing a tail rotor strike of the terrain while entering a hover, and the resulting rollover during an uncontrolled descent.Mar 24, 2002 · N7490F · Substantial damage