Bell 206L accident near Vernal, Utah, June 15, 2006
On June 15, 2006 at about 11:15 pm local time, a Bell 206L (helicopter), registered N265SH, was substantially damaged in an accident near Vernal, Utah. It was flown under charter and air-taxi rules (Part 135). 6 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The loss of tail rotor effectiveness during an attempted precationary landing after a takeoff over uneven, sloping, brush-covered terrain. Factors include the pilot using the wrong performance chart while completing his preflight performance calculations, the uneven, sloping, brush-covered terrain, and a high density altitude.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 15, 2006 · about 11:15 pm local time
- Place
- Vernal, Utah · map
- Type
- Accident
- Injuries
- 6 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Bell 206L · all 206Ls on the register
- Registration
- N265SH · registry record · serial 51447
- Damage
- Substantial damage
- Flight
- Flight · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
Prior to takeoff in conditions that resulted in a density altitude of over 10,000 feet, the pilot figured his takeoff/hover performance using the Hover Ceiling In Ground Effect chart, which indicated the helicopter could safely depart the landing zone (LZ). Because he was taking off over uneven, sloping, brush-covered terrain, he should have used the Hover Ceiling Out of Ground Effect chart, which indicated the helicopter did not have the performance to safely depart the LZ. After liftoff, the pilot started moving the aircraft forward, but it could not out-climb the up-sloping terrain, so he elected to make a precautionary landing on a nearby road. During the landing attempt, the helicopter's tail rotor lost its effectiveness, and the aircraft spun around once and descended into the terrain.
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: flight instructor, commercial pilot
- Ratings: instructor: helicopter; rotorcraft: helicopter
- Flight time: 1,607 hours in all; 557 in this make and model; 134 in the last 90 days; 53 in the last 30 days; 1,537 as pilot in command; 430 on instruments
- Last flight review: December 1, 2005
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: frt
- Injury: minor injuries
The aircraft
- Airframe total time: 5,227 hours
- Last inspection: 100-hour inspection, May 1, 2006
- Maximum gross weight: 4,150 lb
- Seats: 7
- Landing gear: fixed
- Engine: Lycoming 250-C30P (turboshaft); 0 hours total
The flight
- Departed from: Vernal UT
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: overcast at 10,000 ft; clear
- Temperature: 75°F (24°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 5 |
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.