CEN19LA232 · Cessna 152
Cessna 152 · Accident: loss of engine power (total) en route
From Gillespie County Airport (T82) to Georgetown Executive Airport at Johnny Gantt Field (GTU)
Event
- NTSB case
- CEN19LA232
- 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
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
- N48410
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gillespie County Airport (T82), Fredericksburg, TXTo Georgetown Executive Airport at Johnny Gantt Field (GTU), Georgetown, TX
- Aircraft age
- About 42 years (built 1977)
- 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
- Defining eventThe 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
- Loss of engine power (total)
- 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
- Environmental issues › Physical environment
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While in cruise flight at 3,500 ft, the pilot and flight instructor-rated passenger heard the engine begin to run rough. They completed the emergency checklist for a loss of engine power and chose to return to the departure airport; however, the engine continued to lose power and the pilots performed a forced landing to a field, during which the airplane impacted a barbed wire fence.
The atmospheric conditions at the time of the accident were conducive to the development of serious carburetor icing at descent power; however, the engine was operating at cruise power at the time of the accident. The airplane's engine was test run at the accident site; the engine started and ran with no anomalies noted. The reason for the loss of engine power could not be determined based on the available information.
Probable cause
A total loss of engine power for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19LA232
- Event ID
- 20190722X83356
- Case number
- CEN19LA232
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 62adecb1f9d8a07d6426fb84bdce105f95add46035c6ef939b6c157472f3c3f1; retrieved 2026-09-16T09:30:53.488Z.