FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW96LA178 · Cessna 152

23 Apr 1996 · Bullard, TX, United States

Cessna 152 · Accident: total loss of engine power (mechanical failure) on approach

From Tyler Pounds Regional Airport (TYR) to 6XS5

Report a problem

Event

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

Cessna 152

Aircraft type
Cessna 152
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
N46748
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tyler Pounds Regional Airport (TYR), Tyler, TXTo 6XS5
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
Approach · VFR pattern downwind
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, valve, exhaust › Failure

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During a dual instructional flight, the engine lost power, while the airplane was at 600 feet AGL, on a downwind leg for landing on runway 30. The flight instructor elected to land downwind on runway 12, which was a 2,700 foot grass runway. The airplane touched down past the midfield point. Braking on the wet grass was minimal, and the airplane overran the end of the runway, went through two fences and nosed over, coming to rest in the inverted position. Examination of the engine revealed that an exhaust valve had failed.

Probable cause

failure of an engine exhaust valve, which resulted in a loss of engine power, a forced landing, and subsequent damage to the airplane. Factors relating to the accident were: the tailwind, and the wet grass runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW96LA178
Event ID
20001208X05566
Case number
FTW96LA178
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: 88514c2aad3431179bf80d20bbe9b0479b5068f971426ad85662c04650d7d20f; retrieved 2026-09-22T22:35:52.513Z.