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

Bell 206L-3 accident near Eugene Is 192, July 25, 2002

On July 25, 2002 at about 5:55 pm local time, a Bell 206L-3 (helicopter), registered N3174Y, was substantially damaged in an accident near Eugene Is 192. It was flown under charter and air-taxi rules (Part 135). 2 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The loss of tail rotor control due to an in-flight collision with an object.

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

What the record shows

Date
July 25, 2002 · about 5:55 pm local time
Place
Eugene Is 192 · map
Type
Accident
Injuries
2 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Bell 206L-3 · all 206L-3s on the register
Registration
N3174Y · no longer on the register · serial 51038
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

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

While in cruise flight over open ocean water, the pilot of the air taxi helicopter heard a "bang," and the helicopter yawed. The pilot was unable to control the yaw, so he initiated an autorotation. Prior to water entry, the skid mounted floats were successfully deployed. After touchdown on the water, the helicopter rolled over inverted, and the pilot and passenger exited the helicopter and were rescued by a recovery boat. Examination of the wreckage revealed a main rotor blade contact mark just aft of the exhaust stack on a downward angle of approximately 45 degrees. Cyclic, collective, and tail rotor control continuity was established throughout the flight control system. Removal. of the tail rotor drive shaft cowling revealed that the #6 drive shaft (s/n VNMK-47448) twisted apart into two sections, with respective adjacent disc pack couplings deformed. The #8 drive shaft (s/n VNMKH-48083) was found twisted, but not separated, no deformity was noted on the adjacent disc pack couplings. One tail rotor blade (s/n CS-9003) showed damage to its leading edge, and was fractured along the chord in perpendicular to the leading edge. A "bluish", plastic appearing material was found smeared onto the damaged leading edge. The opposite tail rotor blade displayed no visible damage, however, some of the "bluish" coloration was found on its blade tip weight rivets. The tail boom showed evidence of scrapping along its left side, corresponding to the tip path plane of the tail rotor disc. Additional "bluish" coloration was present in the area of the scrapes, and on the tail rotor gearbox output shaft. All damage found was within the rotational arc of the tail rotor disc, with the exception of the exception the main rotor blade and the twisted #6 section of the tail rotor drive shaft. The baggage compartment door and latches were inspected for integrity. The door interior was not deformed and did not show visible evidence of impact marks and the latches were in good condition with no looseness when the door was in the closed & latched position. An electrical continuity check of the baggage door open warning system found no anomalies, and the caution panel bulbs were not damaged or burned. Additionally, neither the pilot or passenger reported noticing any warning lights being illuminated during the accident. All four passenger and crew doors were closed and latched, and would not open by normal means from inside the cabin. During recovery, examination, and interviews, some of the aircraft's standard on-board equipment and internal cargo that was loaded prior to take off were not found. Unoccupied Rear Cabin (5 seating positions): 3 personal flotation devices; 1 newspaper; 1 manila folder with contents. Baggage Compartment: 2 cardboard boxes, measuring 12 inches by 12 inches; 1 envelope; 1 plastic hard hat; 1 ice water cooler. Material analysis of the "bluish" marks on the tail rotor were not conclusive as to what type of object or material could have come into contact with the tail rotor during flight. No mechanical anomalies were discovered that could have contributed to the accident.

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

Pilot

  • Certificate: commercial pilot
  • Ratings: instrument: helicopter; rotorcraft: helicopter
  • Flight time: 9,173 hours in all; 557 in this make and model; 25 in the last 90 days; 25 in the last 30 days; 9,173 as pilot in command
  • Last flight review: September 17, 2001
  • Medical certificate: Class 2 (valid medical--w/ waivers/lim.)
  • Seat: rgt
  • Injury: minor injuries

The aircraft

  • Airframe total time: 11,483.4 hours
  • Last inspection: approved inspection programme, July 4, 2002; 106.5 hours since
  • Maximum gross weight: 4,150 lb
  • Seats: 7
  • Landing gear: fixed
  • Engine: Rolls-Royce 250C30P (turboshaft); 0 hours total

The flight

  • Departed from: Ship Shoal 149 GM at 5:48 pm
  • Destination: Eugene Isld 192 GM

Weather at the time

  • Light: daylight
  • Wind: from 225° at 10 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 90°F (32°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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.