SEA95LA110 · Garlick TH-1L
Garlick TH-1L · Accident: in flight collision with object while maneuvering
From Myrtle Creek Municipal Airport (16S) to an unrecorded destination
Event
- NTSB case
- SEA95LA110
- 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
- 1 · 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 TH-1L
- Aircraft type
- Garlick TH-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
- N27FL
- Operator
- Schuyler, Sid · private individual
- Onboard fatalities
- Unknown
- Route
- From Myrtle Creek Municipal Airport (16S), Myrtle Creek, ORTo 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Pilot in command › Clearance, not maintained
- Rotor system, tail rotor blade › Blade strike
- Rotor system, tail rotor › Disabled
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WITNESSES SAW THE HELICOPTER STRIKE ITS TAIL ROTOR ON A TREE WHILE ATTEMPTING TO LIFT A 3,000 POUND LOG SECTION USING A 150-FOOT LIFT LINE. THE TREE STRIKE DISABLED THE TAIL ROTOR, RESULTING IN LOSS OF DIRECTIONAL CONTROL. THE HELICOPTER SUBSEQUENTLY IMPACTED AT THE TOP OF A 150-FOOT-HIGH ROCK BLUFF, THEN SLID OFF THE BLUFF, COMING TO REST IN AN INVERTED ATTITUDE ON A 50 TO 60 PERCENT SLOPE ABOUT 250 FEET BELOW THE INITIAL IMPACT POINT.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN CLEARANCE WITH A TREE, RESULTING IN A TAIL ROTOR BLADE STRIKE ON THE TREE WHICH DISABLED THE TAIL ROTOR. CONTRIBUTING TO THE ACCIDENT WAS THE 150-FOOT-HIGH ROCK BLUFF.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA95LA110
- Event ID
- 20001207X03807
- Case number
- SEA95LA110
- 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: 73eecb43a4699ee2b1df8486dbcb823df45d39b1a66cfef644df52330050b144; retrieved 2026-09-20T23:45:20.306Z.