The U.S. aircraft register, updated daily
Accidents · NTSB WPR20LA283 · Final report

Kaman K 1200 accident near Pine Grove, Oregon, August 25, 2020

On August 25, 2020 at about 1:00 am local time, a 2001 Kaman K 1200 (helicopter), registered N314, was substantially damaged in an accident during approach near Pine Grove, Oregon. It was a firefighting flight under external-load helicopter rules (Part 133). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 25, 2020 · about 1:00 am local time
Place
Pine Grove, Oregon · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Kaman K 1200 No Series, built 2001
Registration
N314 · registry record · serial A94-0032
Damage
Substantial damage
Flight
Firefighting flight · external-load helicopter rules (Part 133)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Aircraft structural failure during approach defining event

The NTSB's findings

  • Aircraft › Aircraft propeller/rotor › Main rotor system › Main rotor blade system › Failure

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land; rotorcraft: helicopter
  • Flight time: 4,425 hours in all; 2,086 in this make and model
  • Last flight review: July 16, 2020
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: sngl
  • Injury: fatal

The aircraft

  • Airframe total time: 5,287 hours
  • Last inspection: 100-hour inspection, February 25, 2020
  • Maximum gross weight: 12,000 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Honeywell T5317A-1 (turboshaft); 12,612 hours total
  • Operator: Central Copters Inc

The flight

  • Departed from: 4S2 Hood River OR at 11:30 am
  • Destination: 4S2 Hood River OR
  • Flight plan: VFR

Weather at the time

  • Light: daylight
  • Wind: from 290° at 18 knots, gusting 24
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 88°F (31°C), dew point 39°F (4°C)
  • Altimeter: 29.80 inHg
  • Observation at 11:53 pm from KDLS, 31 miles away

Weather report (METAR): METAR KDLS 252353Z AUTO 29018G24KT 10SM CLR 31/04 A2980 RMK AO2 PK WND 28026/2303 SLP090 T03110039 10317 20250 56007=

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

18 documents, released by the NTSB on April 26, 2023. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.