LAX03LA050 · Anderson Rotorway EXEC 162F
Anderson Rotorway EXEC 162F · Accident: partial loss of engine power (mechanical failure) during landing
From Phoenix Deer Valley Airport (DVT) to an unrecorded destination
Event
- NTSB case
- LAX03LA050
- 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
Anderson Rotorway EXEC 162F
- Aircraft type
- Anderson Rotorway EXEC 162
- 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
- N30545
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Phoenix Deer Valley Airport (DVT), Phoenix, AZTo 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
- 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
- Landing · flare/touchdown
- 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
- Substantial
Cause areas
- Engine assembly, valve, exhaust › Separation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After takeoff on an instructional flight, the helicopter experienced engine problems. The instructor made a decision to execute a normal approach to land, and during the flare, a loud "growling" noise was heard. This was followed by a reduction in rotor rpm and power. The helicopter made ground contact with forward speed, tipped forward, and the nose and main rotor blades contacted the ground. The helicopter rolled over and came to rest on its left side. Post accident examination revealed that the exhaust valve stem in the number 1 cylinder had fractured and separated, and that extensive mechanical damage occured to the interior of the number 1 cylinder.
Probable cause
The separation of the exhaust valve stem in the number 1 cylinder, which resulted in a partial loss of engine power during the landing flare and a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03LA050
- Event ID
- 20021226X05637
- Case number
- LAX03LA050
- 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: 140c4d3f2c380b0cae55805adaee71249fb59fc9b1ae2050c770a7e89672bd01; retrieved 2026-09-22T09:48:21.130Z.