Aerospatiale AS-355E TWIN STAR accident near Farmington, Utah, July 19, 2023
On July 19, 2023 at about 2:38 pm local time, a 1981 Aerospatiale AS-355E TWIN STAR (helicopter), registered N102UM, was substantially damaged in an accident during approach near Farmington, Utah. It was a positioning flight under charter and air-taxi rules (Part 135). No one was hurt; 5 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The premature failure of one of the No. 2 engine compressor bleed valve, which resulted in a partial loss of power to that engine.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 19, 2023 · about 2:38 pm local time
- Place
- Farmington, Utah · map
- Type
- Accident
- Injuries
- No one was hurt; 5 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Aerospatiale AS-355E TWIN STAR, built 1981 · all AS-355E TWIN STARs on the register
- Registration
- N102UM · registry record · serial 5075
- Damage
- Substantial damage
- Flight
- Positioning flight · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (partial) during approach defining event
- Collision with terrain or object (not controlled flight into terrain) during approach
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Compressor section › Failure
- Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Compressor section › Fatigue/wear/corrosion
Pilot
- Certificate: flight instructor, commercial pilot, private
- Ratings: single-engine land; instructor: helicopter; instrument: helicopter; rotorcraft: helicopter
- Flight time: 17,053 hours in all; 2,800 in this make and model; 135 in the last 90 days; 18 in the last 30 days; 16,950 as pilot in command; 3,200 on instruments
- Last flight review: November 22, 2022
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 11,625.1 hours
- Last inspection: continuous airworthiness programme, July 8, 2023; 12.1 hours since
- Maximum gross weight: 5,291 lb
- Seats: 7
- Landing gear: fixed
- Engine 1: Rolls-Royce Allison 250-CF (turboshaft); 11,430 hours total
- Engine 2: Rolls-Royce Allison 250-CF (turboshaft); 11,388 hours total
- Fire on the ground
- Operator: Timberland Helicopters INC
The flight
- Departed from: Layton UT at 2:30 pm
Weather at the time
- Light: daylight
- Wind: from 150° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 57°F (14°C)
- Altimeter: 30.21 inHg
- Observation at 8:55 am from KHIF, 7 miles away
Weather report (METAR): METAR KHIF 191455Z AUTO 15006KT 10SM CLR 24/14 A3021 RMK AO2 SLP165 T02400141 53008=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 4 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
10 documents, released by the NTSB on July 16, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
| 2 | Memorandum for Record A�� Pilot and Mechanic | PDF, 4 pages | View Download |
| 3 | Engine Exam Report | PDF, 10 pages | View Download |
| 4 | Materials Laboratory Factual Report 24-078 | PDF, 10 pages | View Download |
| 5 | Rolls-royce Compressor Exam Findings | PDF, 8 pages | View Download |
| 6 | Engine Trim System Design | PDF, 1 page | View Download |
| 7 | Flight Manual Excerpts | PDF, 3 pages | View Download |
| 8 | Evidence Control Forms | PDF, 4 pages | View Download |
| 9 | Statement of Party Representatives to NTSB Investigation | PDF, 2 pages | View Download |
| 10 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number WPR23LA278.
