NYC00LA203 · Cessna 172M
Cessna 172M · Accident: partial loss of engine power (non-mechanical) during initial climb
From 0SU to 2I8 · Newark, OH
Event
- NTSB case
- NYC00LA203
- 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 172M
- 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
- N80624
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 0SUTo 2I8 · Newark, OH
- 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
- Partial loss of engine power (non-mechanical)
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed on Runway 9R, and when the airplane was about 500 feet above the ground, the engine started to sputter and lose power. The pilot initiated a right turn and landed long on runway 27R. The airplane departed the end of the runway and continued for about 500 feet before it struck a chain link fence, and stopped. The engine was run at the accident site by a FAA inspector, who reported it ran 'hesitantly.' The airplane was moved to a hanger. Examination found no contamination in the fuel or the carburetor. Some moisture was found in the foam air filter, and the carburetor heat was operative. The engine was run again, and a low power magneto check was performed satisfactorily. The weather report prior to departure indicated light rain. However the pilot reported it was not raining at the time of the accident.
Probable cause
a partial power loss for undetermined reason(s).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00LA203
- Event ID
- 20001212X21588
- Case number
- NYC00LA203
- 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: 8d2a74d7c1e9c0ee94b65d4bef575ec9db3390570989d2cfe62589d6eb3ca965; retrieved 2026-09-21T20:09:13.408Z.