Timberland Helicopters Aerospatiale AS-355E TWIN STAR accident
Aerospatiale AS-355E TWIN STAR · Accident: loss of engine power (partial) on approach
From Layton, UT to an unrecorded destination
Event
- NTSB case
- WPR23LA278
- 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
- Event fatalities
- Unknown
- 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
- Charter & commuter
- 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
Aerospatiale AS-355E TWIN STAR
- Aircraft type
- Aerospatiale AS-355
- 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
- N102UM
- Operator
- Timberland Helicopters
- Onboard fatalities
- Unknown
- Route
- From Layton, UTTo not recorded
- Aircraft age
- About 42 years (built 1981)
- 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 135: Air Taxi & Commuter
- 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
- Defining eventThe 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 engine power (partial)
- 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
- Aircraft › Aircraft power plant
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight was planned to transport a vegetation removal crew to power distribution lines in mountainous, high-elevation terrain. As the helicopter approached the drop-off point, the pilot observed through the engine instruments that the No. 2 engine was operating at reduced power and that the main rotor speed was decaying. He maneuvered away from power lines and made adjustments to the engine trim settings; with power seemingly back to normal, he began the approach again.
However, as the helicopter approached the landing zone the main rotor speed again began to decay such that the pilot knew it would be insufficient for landing. He turned the helicopter away from terrain, and the helicopter began to descend into the surrounding trees, where it landed on its belly and rolled over. The engines were still operating after the accident, and the pilot shut them down and secured the electrical system.
The compressor section of the No. 2 engine had been replaced almost two weeks before the accident. Both the pilot and maintenance personnel stated that following the replacement, they encountered intermittent problems synchronizing the engines. While troubleshooting they performed a series of adjustments to the engine trim system followed by test flights, after which they were eventually able to match the engines. Following the compressor change, the engine was making a loud “howling” sound that neither the pilot nor maintenance crew had heard on this helicopter before. Despite this, they continued to fly the helicopter on other missions leading up to the accident.
Postaccident examination did not reveal any anomalies with the engine trim system or No. 1 engine. Examination of the No. 2 engine revealed that the compressor bleed valve had a hole in the rolling section of its diaphragm, which was causing the valve to intermittently fail. Such a hole would have resulted in the intermittent engine performance observed leading up to the accident flight, and the reduction in power observed before impact.
Examination also revealed that the compressor section incurred a balance and clearance anomaly during its overhaul. These discrepancies would have resulted in a minimal reduction in engine efficiency and would likely have explained the howling sound, but not the abrupt loss of power.
The bleed valve was manufactured under an FAA Parts Manufacture Approval (PMA) process. Although the diaphragm used the same materials specified by the manufacturer, it failed about 77 hours short of its service life.
The pilot adjusted the engine trim setting during the emergency in an attempt to increase power to the failing engine. However, the trim system was differential in design, such that using it in this manner would have caused a reduction in power to the running engine. Regardless, the loss of power occurred at an altitude and flight phase that would have made a safe recovery challenging considering the close proximity to the terrain.
Probable cause
The premature failure of one of the No. 2 engine compressor bleed valve, which resulted in a partial loss of power to that engine.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23LA278
- Event ID
- 20230720192669
- Case number
- WPR23LA278
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 90a7cc21a8e96c3f36622517b4f50c48df6d4d8d61c6ed3533d7b59116a03313; retrieved 2026-09-16T17:53:02.244Z.