ATL03LA003 · Cessna 172N
Cessna 172N · Accident: loss of engine power during initial climb
From Pompano Beach Airpark (PMP) to Sarasota Bradenton International Airport (SRQ)
Event
- NTSB case
- ATL03LA003
- 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 172N
- 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
- N6542J
- Operator
- American Flyers
- Onboard fatalities
- Unknown
- Route
- From Pompano Beach Airpark (PMP), Pompano Beach, FLTo Sarasota Bradenton International Airport (SRQ), Sarasota, FL
- 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
- Initial climb
- 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
- Loss of engine power
- 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
- Powerplant › Undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
As the airplane climbed through 90 feet, the pilot noticed a loss of engine power. The pilot elected to shut down the engine by reducing the power and mixture levers. The airplane touched down on the runway and bounced about three times. Efforts by the pilot to stop airplane on the runway surface were unsuccessful. The airplane continued off the departure end of the runway and overrun, and collided with a fence. During the post-accident engine test run, the engine developed normal takeoff power without hesitation or roughness. The post-engine inspection disclosed no oil leaks or further discrepancies. According to the pilot, there were 40 gallons of fuel onboard the airplane at the time of the attempted takeoff. Review of weather data disclosed that conditions were favorable for the formation of carburetor ice.
Probable cause
The loss of engine power for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL03LA003
- Event ID
- 20021018X05333
- Case number
- ATL03LA003
- 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: a82373cdb861ca63f58ffb9f4bb0b0f63b65cbaf934c6254058fe9a44ce9c5e0; retrieved 2026-09-22T10:04:58.269Z.