FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA214 · Piper PA-28R-200

16 Jun 2005 · Happy Jack, AZ, United States

Piper PA-28R-200 · Accident: partial loss of engine power (mechanical failure) en route

From Gallup Municipal Airport (KGUP) to Needles Airport (KEED)

Report a problem

Event

NTSB case
LAX05LA214
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

Piper PA-28R-200

Aircraft type
Piper PA-28
Category
Airplane
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
N5229T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gallup Municipal Airport (KGUP), Gallup, NMTo Needles Airport (KEED), Needles, CA
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
En route · cruise
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, intake › Fractured
  • Engine assembly, valve, intake › Separation

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot landed on a rough dirt road and damaged the wings following a partial loss of power. The airplane was in cruise flight about 10,500 feet mean sea level (msl) when it began to slowly lose altitude. Efforts by the pilot to increase engine power and arrest the descent failed. The pilot determined that the engine was capable of producing only partial power. In order to avoid an uncontrolled descent into terrain, he landed on the dirt road. Examination of the engine revealed an intake leak on cylinder no. 3. A piece of the intake valve was missing, and the edges of the fracture surface were jagged.

Probable cause

The fracture/separation of an engine intake valve during cruise flight, which resulted in a partial loss of engine power and a forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA214
Event ID
20050705X00932
Case number
LAX05LA214
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: cb948b2500bd64a9b66700cae5c6d7ae74e12be363e60aec35ed789766f8a559; retrieved 2026-09-22T05:47:20.712Z.