ERA14LA374 · Cessna 172 RG
C.A.M.S Flight School Cessna 172 RG · Accident: loss of engine power (total) on approach
From Apalachicola Regional Airport (AAF) to Apalachicola Regional Airport (AAF)
Event
- NTSB case
- ERA14LA374
- 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 172 RG
- Aircraft type
- Cessna 172
- 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
- N5276U
- Operator
- C.A.M.S Flight School
- Onboard fatalities
- Unknown
- Route
- From Apalachicola Regional Airport (AAF), Apalachicola, FLTo Apalachicola Regional Airport (AAF), Apalachicola, FL
- Aircraft age
- About 34 years (built 1980)
- 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 go-around
- 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
- 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
The commercial pilot reported that the accident flight was the first flight since maintenance was performed after water was found in the fuel system. The pilot performed a preflight, sumped the fuel tanks with no water noted, and conducted an engine run-up with no anomalies noted. After takeoff, the pilot performed one circuit in the traffic pattern, and, during the final approach, he chose to perform a go-around. He applied full throttle, and the airplane began to climb, but the engine then lost total power. He subsequently turned the fuel pump on, applied carburetor heat, and began to "pump" the throttle. The engine started but then lost total power again. The pilot restarted the engine two more times, but, after it lost power again, he chose to perform a forced landing to a marsh, which resulted in substantial damage to the fuselage.
A postaccident examination of the engine confirmed engine continuity from the propeller flange to the engine's accessory section, and an engine test run was performed with no anomalies noted. The left tank fuel line to the engine was found partially blocked with "fresh" sealant-type material. However, a review of the maintenance records found no entries indicating when the sealant was applied to the fuel tank. The fuel selector was found in the "both" position. Given that the sealant was only partially blocking the fuel line and that both fuel tanks were feeding the engine, the blockage likely would not have affected the engine power.
Although the weather conditions were conducive to the accumulation of serious carburetor icing at glide power at the time of the accident and the total loss of engine power occurred after the engine had been operating at a low-power setting for the descent on final approach, the investigation could not determine whether carburetor ice caused the total loss of engine power.
Probable cause
A total loss of engine power for reasons that could not be determined during postaccident examination and testing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA374
- Event ID
- 20140803X92843
- Case number
- ERA14LA374
- 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. 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: a903d8eb42ed2df923c736861ff554528eeeef4fa19b236a3c9067cf49fc3210; retrieved 2026-09-16T01:35:45.642Z.