FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA025 · Eurocopter AS350B3

2 Nov 2004 · Sierra Vista, AZ, United States

Eurocopter AS350B3 · Accident: partial loss of engine power (mechanical failure) during initial climb

From Sierra Vista Community Hospital Heliport (AZ89) to Portal, AZ

Report a problem

Event

NTSB case
LAX05LA025
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

Eurocopter AS350B3

Aircraft type
Eurocopter AS350
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
N106LN
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sierra Vista Community Hospital Heliport (AZ89), Sierra Vista, AZTo Portal, AZ
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
Partial loss of engine power (mechanical failure)
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

  • Fuel system, fuel control › Failure, partial
  • Pilot in command › Procedures/directives, not performed

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

NTSB narrative

The helicopter experienced a partial loss of power during the transition from an out of ground effect hover to forward flight, and collided with the ground in a parking lot. About 10 seconds after the transition to forward flight, at 35 knots and between 150 to 200 feet above ground level, the pilot sensed the engine turbine start to spool down towards idle. He saw a red 'GOV' light illuminated on the instrument panel. The pilot did not disengage the flight notch on the collective twist grip to manually control the fuel flow to the engine and proceeded to fly the helicopter about 1/8 mile towards the parking lot, working the collective to try to keep the helicopter above the trees and the roofs of the houses. He used all the available rotor rpm in an attempt to arrest the landing. The helicopter landed hard, collapsing the landing skids, and the ship slid about 100 feet. After the helicopter came to rest, the main rotor was still rotating at a slower rpm, and the engine was operating at what seemed like a low idle speed. The partial loss of engine power was initiated by an inconsistency of greater than 3 percent between the two N2 (free turbine speed) sensors on the engine. This inconsistency resulted in the fuel control entering a fixed mode that freezes the fuel flow at the level it was at when the inconsistency was detected, and the illumination of a red 'GOV' light in the cockpit. The power required for forward flight is less than the power required to hover. The fixed fuel flow to the engine provided insufficient power to fly and land the helicopter at speeds below 35 knots, which resulted in low rotor rpm and a high rate of decent prior to the hard landing. In the event of a red 'GOV' light the pilot is to disengage the flight notch and control the fuel manually with the collective twist grip, which would allow the pilot to regain the full power range of the engine. At an altitude of 150 to 200 feet and airspeed of 35 knots, the pilot was operating in the avoidance zone of the documented height-velocity diagram, and therefore, may not have had enough time to fully respond to the partial loss of power by selecting an emergency landing site, disengaging the twist grip flight notch, and exercising manual control of the engine.

Probable cause

An inconsistency between the engines' two N2 sensor signals caused the fuel control to enter a fixed mode, which limited the power available. Contributing to the accident was the lack of altitude and airspeed available to give the pilot time to select a landing zone, disengage the flight notch, and exercise manual control of the engine after the illumination of the red 'GOV' light.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA025
Event ID
20041104X01758
Case number
LAX05LA025
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: 05bec931a09a2ec632be907612e07c664a6400ab1f0ea3b48f8bbfea539adb88; retrieved 2026-09-22T06:33:07.395Z.