FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03GA244 · Bell 206L-3

26 Jul 2003 · Whiteriver, AZ, United States

U.S. Dept. of Interior Bell 206L-3 · Accident: loss of control in flight on approach

From Whiteriver Airport (E24) to an unrecorded destination

Report a problem

Event

NTSB case
LAX03GA244
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
2 · 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 206L-3

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
N6184D
Onboard fatalities
Unknown
Route
From Whiteriver Airport (E24), Whiteriver, AZTo not recorded
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
Approach · VFR pattern final
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Hovering turn, attempted
  • Pilot in command › In-flight planning/decision, inadequate
  • Pilot in command › Loss of tail rotor effectiveness, encountered
  • Pilot in command › Performance data, not verified
  • Pilot in command › Translational lift, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During a right turn to return to a mountain landing site, the helicopter began to spin and struck trees. The flight's mission was to insert a helicopter fire attack crew at the location of a wildfire. The landing zone (LZ) closest to the fire was in a small area surrounded by trees. The density altitude was calculated to be 11,968 feet. The pilot first landed at a meadow about a mile away and off-loaded two fire fighters, then proceeded to the LZ, and dropped off the one remaining fire fighter and tools. He returned to the meadow, where he picked up the additional crewmembers. The flight returned to the landing site, overflew the LZ and continued up the drainage before making a right turn back towards the LZ. One witness seated in the front left seat noted that on the first takeoff from the meadow the torque gauge was at 100 percent and the helicopter was "hard to get off the ground" and the climb out was slow and labored. On the return flight to the LZ, the first fire fighter dropped at the LZ saw that the helicopter was flying slowly about 20 feet above the tree line. He believed they would land with the wind; however, the pilot flew the helicopter past the LZ and continued up the drainage. A surviving witness in the left front seat noted that the torque gauge read 100 percent. As the pilot initiated the right turn to return the LZ, the torque reading went from 100 to 105 and then 110 percent. He asked the pilot if the tail rotor was going to stall, but received no response. The witness noted that the airspeed gauge read zero. At that point the pilot started to rapidly move the collective, cyclic, and "his feet." The helicopter then spun two times to the right. Both a ground witness and a rescue flight crew noted that the LZ had a slope to it and was located in very tight area, with reported winds southwesterly between 2-4 knots. During the on-scene investigation, investigators noted that the compressor blades in the engine were folded opposite the direction of rotation and that tree fibers had been ingested by the compressor impellor, a condition indicative an operational engine at high power at the time of impact. The engine teardown revealed that additional tree fibers were found throughout the gas path from the compressor section through to the combustion and exhaust sections. There were no other discrepancies noted with the airframe or engine that would have precluded normal operation.

Probable cause

The pilot's failure to maintain a minimum translational lift airspeed while maneuvering in high density altitude conditions at near maximum required torque and above the in ground effect hover altitude, that resulted in a loss of tail rotor effectiveness and a loss of control. The pilot's inadequate in flight planning in his failure to note and account for the power requirements necessary to conduct takeoffs and the slow maneuvering flight at the accident site were also causal.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03GA244
Event ID
20030807X01277
Case number
LAX03GA244
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, coordinates. 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: c54b26ef23c02489493ed56ea0ab14503ac5fec6f26e15e1230cfd41e4e1f056; retrieved 2026-09-20T19:01:29.905Z.