FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00GA297 · Bell 412

13 Aug 2000 · Cold Springs, NV, United States

US Department of Interior Bell 412 · Accident: partial loss of engine power (mechanical failure) while maneuvering

From Cold Springs, NV to an unrecorded destination

Report a problem

Event

NTSB case
LAX00GA297
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
1 · all aircraft and ground
Ground fatalities
0
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
Government
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 412

Aircraft type
Bell 412
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
N174EH
Onboard fatalities
Unknown
Route
From Cold Springs, NVTo 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
Public Aircraft
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
Maneuvering · aerial application
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
Destroyed

Cause areas

  • Turbine assembly, turbine blade › Fatigue
  • Turbine assembly, turbine blade › Overtemperature
  • Unknown › Throttle/power control, improper use of

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

NTSB narrative

While flying along a mountain ridgeline to make a water drop on a wild fire, the helicopter lost power in one engine and collided with terrain as the pilot turned downslope toward a landing area. Ground crews watching the helicopter make its drop run observed smoke emanating from the right engine, then the helicopter made a left descending turn and impacted the downsloping mountainous terrain. A trailing pilot saw the helicopter about 150 feet above the ridgeline, then it made a sudden left descending turn. He did not see the pilot jettison either the water or the bucket. A teardown inspection and metallurgical examination of the No. 1 and No. 2 power sections was conducted. The examination of the No. 1 power section CT disc revealed that the firtree serrations adjacent to the No.s 24 and 25 blade positions were fractured above the blade retaining rivet hole, and that the No.s 27-29 firtree serrations were fractured at the blade roots. During the metallurgical examination, the failure of the CT disc was attributed to cyclic stress rupture due to extended and repeated operation of the engine at, near, or above its temperature/power limits. Dimensional measurements of the blades showed growth and deformation to the disk in the areas of the fractures. There were no material, manufacture, or design deficiencies identified during the metallurgical examination of the CT disc. The examination of the No. 2 power section revealed that the intermediate drive shaft fractured in a counterclockwise direction due to sudden stoppage of the left engine while it was at a high power level. Due to the degree of destruction and lack of dispatch records, the investigation was not able to accurately determine the operating weight of the helicopter at the time of the accident; however, for the 9,500-foot density altitude, it is believed that the helicopter's weight with the water load was at a point that resulted in marginal single engine capability at best. The accident helicopter had been modified with the installation of a water bucket and long line system. The long line and water bucket circuit breakers, and the emergency electrical release, were connected to the nonessential bus. This system was installed on a Form 337 field approval. According to the helicopter manufacturer, the electrical system is designed so that if one generator and/or engine failed both of the nonessential buses would automatically drop offline. Thus the emergency electrical release of the water bucket and long line would have been rendered inoperable in the event of a generator and/or engine failure. An override switch on the electrical panel can restore power to the nonessential buses; however, based on the event timeline reported by the witnesses, it is unlikely that the pilot could have restored power to the nonessential busses in time to prevent a collision with the ground.

Probable cause

failure of the compressor turbine disc due to cyclic fatigue brought about by repeated operation near or above the engines' temperature/power limits by company personnel over an extended period of time. Factors in the accident were: 1) the high density altitude, mountainous terrain, and the helicopter's resulting marginal single engine performance capability; 2) the design, fabrication, and installation of the emergency external load release system, which had the power supply wired to the nonessential bus that would automatically drop offline during an engine or generator failure; and 3) the pilot's resulting inability to electrically release the water load, bucket, or line while dealing with the engine failure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00GA297
Event ID
20001212X21760
Case number
LAX00GA297
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: d0ec93c8e60dca31e3b42ab4eb3b0a902341a40d3f83526629ca41aac3eba030; retrieved 2026-09-18T14:36:33.196Z.