Aerospatiale AS-355E TWIN STAR N102UM
19 July 2023 · Farmington, Utah, United States · No injuries
Summary
On 19 July 2023 at about 14:38 local time, a Aerospatiale AS-355E TWIN STAR registered N102UM, operated by Timberland Helicopters Inc, was involved in an accident near Farmington, Utah, United States. 5 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 14:38
- Classification
- Accident
- Location
- Farmington, Utah, United States
- Coordinates
- 41.0300, -111.8500
- Aircraft
- Aerospatiale AS-355E TWIN STAR
- Registration
- N102UM
- Category
- Helicopter
- Year built
- 1981
- Engines
- 2
- Operator
- Timberland Helicopters Inc
- Operating rule
- Part 135: Air Taxi & Commuter
- Purpose of flight
- Positioning
- Phase of flight
- Not recorded
- Route
- Layton → Unknown
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR23LA278
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 5 | 0 | 0 | 0 | 5 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Aerospatiale AS-355E accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 24 Aug 1984 | Aerospatiale AS-355E | Strawberry, California, United States | Rogers Helicopters Inc | No injuries | - |
| 18 Oct 1983 | Aerospatiale AS-355E | Corpus Christi, Texas, United States | Superior Helicopters | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 4 Jan 2023 | Piper PA-34-220T | New Harmony, Utah, United States | - | Fatal | 1 |
| 15 May 2023 | Robinson R22 | Spanish Fork, Utah, United States | Utah Helicopter | No injuries | - |
| 21 Sep 2023 | Cessna 180K | Monument Valley, Utah, United States | - | No injuries | - |
| 8 Aug 2023 | Piper PA-28-180 | Ritchfield, Utah, United States | - | No injuries | - |
| 11 Mar 2023 | Harris Robert W ZENITH CH 801 | Brigham City, Utah, United States | - | No injuries | - |
| 27 Sep 2023 | Cirrus SR20 | Salt Lake City, Utah, United States | Elevate Aviation | No injuries | - |