FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02LA181 · Bell 206B

6 Jul 2002 · Three Rivers, MI, United States

Phoenix Precision Air Bell 206B · Accident: loss of control in flight during initial climb

From Three Rivers, MI to Goshen Municipal Airport (GSH)

Report a problem

Event

NTSB case
CHI02LA181
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
0 · 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

Bell 206B

Aircraft type
Bell 206
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
N60EA
Onboard fatalities
Unknown
Route
From Three Rivers, MITo Goshen Municipal Airport (GSH), Goshen, IN
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 91: General Aviation
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
Initial climb
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
Loss of control in flight
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 › Aircraft control, not maintained
  • Pilot in command › Loss of tail rotor effectiveness, encountered

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The helicopter sustained substantial damage during an emergency landing after liftoff. The pilot reported that a normal takeoff was made to the southwest, and upon reaching an altitude of 75 feet, he began a turn to the south and noticed that the aircraft was not responding to the turn. When the helicopter began to accelerate forward it started to spin to the right and the tail rotor lost all effectiveness. The helicopter spun 3 and 1/2 revolutions and the pilot then maneuvered it to an open pasture for the emergency landing. He lowered the collective bringing the aircraft to the ground for a level touchdown with no forward motion. The pilot stated that a local airport reported a wind from the southeast at 4 knots, and prior to the departure the wind was "non existent." No anomalies were found with the helicopter or its flight control systems that were determined to exist prior to impact. According to the FAA, a loss of tail rotor effectiveness (LTE) is "not related to an equipment or maintenance malfunction and may occur in all single-rotor helicopters at airspeeds less than 30 knots. It is the result of the tail rotor not providing adequate thrust to maintain directional control, and is usually caused by either certain wind azimuths (directions) while hovering, or by an insufficient tail rotor thrust for a given power setting at higher altitudes."

Probable cause

A loss of tail rotor effectiveness.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02LA181
Event ID
20020710X01089
Case number
CHI02LA181
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: 663ff69a16786f589b439d59d94fe65236bc7f850ec0cc2c31034bfb468ab048; retrieved 2026-09-22T10:45:36.354Z.