LAX97LA137 · Piper PA-28R-200
Piper PA-28R-200 · Accident: total loss of engine power (mechanical failure) en route
From Tucson International Airport (TUS) to an unrecorded destination
Event
- NTSB case
- LAX97LA137
- 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
- 0
- 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
- N2226T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tucson International Airport (TUS), Tucson, 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
- 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
- Total 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, bearing › Failure
- Engine assembly, connecting rod bolt › Seized
- Engine assembly, cylinder › Overtemperature
- Lubricating system, oil port/passage, internal › Restricted
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane lost engine oil pressure followed by seizure of the engine. The flight instructor attempted to glide to a nearby private strip but had insufficient altitude and elected to land gear up on rough level terrain. Evidence of detonation was found in the number 2 cylinder. The number 2 piston was damaged and aluminum from the piston restricted the flow of oil. The number 2 piston rod bearing failed as a result of loss of lubrication. One of the bolts to the number 2 piston rod cap broke, jamming the rotation of the crankshaft. The reason for the detonation in the number 2 cylinder could not be determined.
Probable cause
loss of engine power as a result of detonation in the number 2 cylinder for undetermined reasons. A factor in the accident was the unsuitable nature of the forced landing area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX97LA137
- Event ID
- 20001208X07589
- Case number
- LAX97LA137
- 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. 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: 20152762e03551330abbb2c9bd3cdefa216defdb2325690bfc230bce40f643c9; retrieved 2026-09-21T12:11:48.272Z.