WPR20LA283 · Kaman K 1200
Central Copters Kaman K 1200 · Accident: aircraft structural failure on approach
From Ken Jernstedt Airfield (4S2) to Ken Jernstedt Airfield (4S2)
Event
- NTSB case
- WPR20LA283
- 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
- Unknown
- 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
Kaman K 1200
- Aircraft type
- Kaman K-1200
- 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
- N314
- Operator
- Central Copters
- Onboard fatalities
- Unknown
- Route
- From Ken Jernstedt Airfield (4S2), Hood River, ORTo Ken Jernstedt Airfield (4S2), Hood River, OR
- Aircraft age
- About 19 years (built 2001)
- 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
- Approach
- Defining eventThe 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
- Aircraft structural 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
- Aircraft › Aircraft propeller/rotor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had been conducting fire suppression activities for the United States Forest Service using a water bucket suspended at the end of a 140-ft longline. The pilot informed the controller that he would need to return to the base for fuel after another bucket of water, which was the last communication between the controller and the pilot. The helicopter was subsequently located in a river at the dip site. No mayday call was received. Onboard global position system (GPS) data revealed that the helicopter had arrived at the dip site and was hovering at an altitude of 138 ft above the water, which would place the helicopter about 40 ft above the treetops. The water bucket would have been near or in the water. No evidence showed any signs of rotor system contact with the trees. However, evidence did show that the helicopter rolled to the left as it descended and the 140-ft longline wrapped around the fuselage during the descent. The helicopter then struck the river in an inverted position and continued to roll to the left until it came to rest on its right side. The lack of damage to the longline demonstrated that both rotor systems and pylons had separated from the fuselage while the helicopter was in flight. The left rotor blades were found 560 ft away from the main wreckage. Postaccident examination revealed that the damage observed on the right rotor blades, right hub, and right pylon occurred after they were struck by the left rotor blades while the helicopter was above the dip site. The damage observed on the left rotor system occurred when it hit the right rotor system while in flight. This intermeshing contact resulted in the in-flight separation and breakup of the left rotor blades. The failure of the left white blade servo flap started as a fracture of the lower skin at the spar-to-afterbody transition and peel separation of the upper skin before transitioning to fracture of both upper and lower skins at the transition. The transition between separation modes, onset of reverse bending damage at the outboard closeout, and the extent of damage to the left white blade servo flap compared to the servo flaps from the remaining three blades indicates that the left white blade servo flap was cracked at its inboard end prior to the collision between the left and right rotor systems. The inboard end crack grew progressively and compromised the structural integrity of the servo flap leading to the failure and eventual separation of the afterbody. Failure of the left white blade servo flap resulted in a loss of control of the left white blade. However, it could not be determined why the left white blade servo flap failure ultimately resulted in a collision between the left and right rotor systems in this accident. A past event involving a servo flap separation demonstrated that the loss of a servo flap does not always result in catastrophic consequences. It is likely that flight control inputs, including the pilot’s responses to an abnormal vibration in the rotor system, were a factor to the catastrophic outcome of the servo flap failure in this accident. The lack of flight data precluded analysis of the control inputs leading up to the collision between the left and right rotor systems.
Probable cause
An in-flight breakup resulting from contact of the left rotor system with the right rotor system after an in-flight failure of a servo flap from a left rotor blade.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20LA283
- Event ID
- 20200824X31000
- Case number
- WPR20LA283
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2020-08-25.
- API snapshot SHA-256: 694f15726a2d42f8fccd99e9ce81d5be3562dba471288508c5cc46b6a346646a; retrieved 2026-09-15T07:18:39.008Z.