LAX04TA202 · Bell OH-58A+
Bell OH-58A+ · Accident: total loss of engine power (mechanical failure) while maneuvering
From Meadows Field (BFL) to Meadows Field (BFL)
Event
- NTSB case
- LAX04TA202
- 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 OH-58A+
- Aircraft type
- Bell OH-58
- 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
- N397E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Meadows Field (BFL), Bakersfield, CATo Meadows Field (BFL)
- 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
- Maneuvering
- 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
- Total loss of engine power (mechanical failure)
- 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
- Wire, transmission
- 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
- Other maintenance personnel › Maintenance, overhaul, inadequate
- Turbine assembly, nozzle › Separation
- Turbine assembly, turbine wheel › Seized
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 collided with power lines and landed hard during a night autorotation following a loss of engine power. As the pilot initiated a turn, both he and the observer heard a loud boom. While they were discussing the origin of the boom, a second boom occurred followed by an immediate power loss. The pilot lowered the collective and entered an autorotation. During the flare, he realized he was going to overshoot the landing zone (LZ) and lined up with a street for landing. The pilot initiated a flare about 60 feet above the ground and felt a strong jolt with an increased rate of descent and a loss of main rotor rpm's as the helicopter collided with power lines. The helicopter landed hard from about 10 feet above the ground. Review of the maintenance logbooks revealed that the engine had been in service 5 months and 161 hours since a 1,750-hour inspection had been completed. An engine teardown was conducted. Various internal components had excessive heat damage, carbon deposits, and metal splatter. There was a partial loss of airfoils for the number 1 turbine wheel. The gas producer (GP) turbine could not be manually rotated and was locked in place, with the second-stage turbine nozzle diaphragm fractured into several pieces. Paperwork obtained from the engine overhaul facility indicated that the second-stage turbine nozzle diaphragm had been replaced by machining out the old diaphragm and brazing in a new diaphragm. A metallurgical examination of the diaphragm revealed that it had separated from the main portion of the nozzle at the braze joints and it was also fractured 360 degrees around the trailing edge side of the diaphragm. The fracture surface revealed no pre-existing cracks, and the damage was determined to be consistent with tensile overstress. Both the leading and trailing edges of the braze alloy fill were measured. The leading edge side had a fill between 10 and 50 percent of the joint width with an estimated average fill of 30 percent. The trailing edge side had a fill between 50 and 100 percent of the joint width with an estimated average fill of 75 percent. The diaphragm's manufacturer indicated that the braze alloy fill should fill the exposed extremities in a continuous line for the first 20 percent of the joint width, or 1.5 times the thickness of the thinnest member being joined, and have a minimum total coverage of 80 percent of the joint. The braze thickness of the accident diaphragm was measured to be at least 0.009-inch in one location. The manufacturer's specifications for the braze thickness was between 0.002 and 0.004-inches. Review of the overhaul facilities procedures for the repair of the diaphragm included requirements for visual and fluorescent penetrant inspection of the brazed joints after repair completion. The Safety Board metallurgist found that those methods of inspections were not capable of detecting internal voids, unless the voids were connected to the surface. The manufacturer and the overhaul facility reviewed the history and processing of the diaphragm. It was noted that normally the overhaul facility used the hydrogen fluoride cleaning method to clean the majority of the diaphragms prior to brazing. However, the accident diaphragm and seven others were cleaned using the vapor degreasing method. Other diaphragms that had undergone the vapor degreasing method were retrieved and destructively examined. The results showed that these diaphragms contained cracking along the brazed joints. Several diaphragms that had undergone the hydrogen fluoride cleaning method were retrieved and destructively examined. They contained no cracks; however, the braze thickness was noted to be as large as 0.020 inches. As a result of the accident, the manufacturer revised their Parts Repair Procedures Letter (PRPL 2-D004) to reflect changes in the procedures for brazing the second-stage turbine nozzle diaphragm, which included hydrogen fluoride cleaning, and immersion ultrasonic inspection and ultrasonic inspection during and after the brazing process. The overhaul facility rewrote their procedures to reflect the manufacturer's revised procedures.
Probable cause
loss of engine power due to the separation of the diaphragm portion of the repaired second-stage turbine nozzle from the rim portion due to the use of an inadequate cleaning method to clean the joint prior to the braze repair during overhaul by the manufacturer's authorized maintenance center. Contributing to the accident was the lack of an inspection procedure that could verify that the joint met the braze fill requirements.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04TA202
- Event ID
- 20040513X00599
- Case number
- LAX04TA202
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-05-04.
- API snapshot SHA-256: 044570f47f2231c1b2441456f1cfb26c93fd3e32ca17da7d27b2ac0294c94e1d; retrieved 2026-09-22T07:37:10.728Z.