FTW03FA120 · Piper PA-32-300
Piper PA-32-300 · Accident: total loss of engine power (mechanical failure) en route
From Tulsa Riverside Airport (RVS) to Tulsa Riverside Airport (RVS)
Event
- NTSB case
- FTW03FA120
- 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
- 3 · 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-32-300
- Aircraft type
- Piper PA-32
- 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
- N70NZ
- Operator
- Travis Lee Butts
- Onboard fatalities
- Unknown
- Route
- From Tulsa Riverside Airport (RVS), Tulsa, OKTo Tulsa Riverside Airport (RVS), Tulsa, OK
- 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 · descent
- 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)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Engine assembly, connecting rod cap › Failure, total
- Engine assembly, piston › Eroded
- Fluid, oil › Starvation/exhaustion
- Pilot in command › Airspeed, not maintained
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 stalled the airplane, which impacted terrain in a nose down pitch attitude after the engine experienced a total loss of power. Numerous witnesses observed smoke trailing from the airplane; one of which observed the smoke up to nine minutes prior to the accident. The pilot reported a loss of oil pressure and subsequent loss of engine power. Some witnesses observed the airplane stall, roll to the right, and descend vertically. The airplane exploded upon impact with the terrain. Post-accident examination of the engine revealed the number six connecting rod end cap failed due to oil starvation. The oil starvation resulted from a piston blow-by condition that formed in the number six cylinder. The blow-by condition resulted in crankcase pressurization and the loss of the oil through the breather tube. The blow-by condition also resulted in the burning of oil in the number six cylinder, which resulted in the smoke observed by the witnesses. The cause of the blow-by situation was not determined.
Probable cause
Failure of the engine due to the blow-by condition in the number six cylinder for undetermined reasons, which resulted in oil starvation and eventual failure of the associated connecting rod end cap. Also causal was the pilot's failure to maintain airspeed during the forced landing, which resulted in an inadvertent stall and subsequent collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW03FA120
- Event ID
- 20030403X00425
- Case number
- FTW03FA120
- 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: 8056dfad594748179a596b342e2b8ed2ff1503aa8681aba88b7c417afa0598a6; retrieved 2026-09-20T19:20:44.779Z.