SEA97LA126 · Garlick UH-1H
Garlick UH-1H · Accident: airframe, component or system failure while maneuvering
From WA to an unrecorded destination
Event
- NTSB case
- SEA97LA126
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Garlick UH-1H
- Aircraft type
- Garlick UH-1
- Category
- Helicopter
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N85NW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From WATo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 133: Rotorcraft Ext. Load
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Terrain condition › None suitable
- Turboshaft engine, power output shaft › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While returning to pick up another log, the pilot heard a high-speed shredding sound' accompanied by high-frequency vibrations. As the noise and vibration increased, the pilot turned downhill and looked for a location where he could make an emergency landing. He then heard a second loud noise, and the rotor RPM immediately began to decay. He stretched his glide over the 130 foot high trees and managed to maneuver the helicopter so that it 'fell into' a switchback on an old dirt logging road. A post accident examination of the K-FLEX drive shaft, which runs between the engine and the transmission, revealed that one of its flex band legs had experienced an inflight fatigue fracture. A review of the records revealed that the shaft had accumulated 459 hours while being used by the United States Army, and had accumulated an additional 432 hours during civilian logging operations.
Probable cause
The inflight failure of the K-FLEX engine-to-gear box drive shaft and no suitable site in which to make a forced/emergency landing. A factor was the mountainous/hilly terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA97LA126
- Event ID
- 20001208X08244
- Case number
- SEA97LA126
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: a4e15aa4a8d2562eed5aa6bd20518eec32f02fe62fc5e16fafac3af84f9ca6e7; retrieved 2026-09-22T19:31:20.658Z.