ERA14FA428 · Cessna 172 K
Cessna 172 K · Accident: loss of engine power (total) during initial climb
From South Albany Airport (4B0) to South Albany Airport (4B0)
Event
- NTSB case
- ERA14FA428
- 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
- 2 · 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 K
- 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
- N79438
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From South Albany Airport (4B0), Selkirk, NYTo South Albany Airport (4B0), Selkirk, NY
- Aircraft age
- About 45 years (built 1969)
- 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
- 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, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The flight instructor and the light sport pilot, who was receiving training toward a private pilot certificate, were on an instructional flight in the airplane. Witnesses reported that, during takeoff, the airplane became airborne about 3/4 of the way down the 2,853-ft runway, and, when it was about 100 ft above the ground, the witnesses heard the engine lose power and subsequently regain it. One witness then heard the engine run "rough" and saw the airplane bank to the right and descend behind a treeline and out of view. Examination of the accident site indicated that the airplane impacted the side of a rail car parked on tracks beyond the end of the runway. The propeller blades displayed some leading edge damage and chordwise gouging, consistent with the engine producing partial power at the time of impact.
No preexisting mechanical anomalies were found that would have precluded normal airplane or engine operation. The airplane's fuel selector was found in the "both" position; however, it had been moved by a first responder who could not recall its original position. Both wing fuel tanks contained fuel that appeared to be 100 low lead aviation fuel and was absent of water and debris. The gascolator was destroyed, but the damaged carburetor contained a small amount of fuel, which was tested and found not to have water in it. The carburetor heat control was found in the "ON" position.
Fuel starvation due to an improperly positioned fuel selector could have resulted in the loss of engine power, and testing was conducted to determine if this was a possibility. There were no onboard recording devices, but airport security cameras captured segments of the airplane's start, taxi and takeoff roll. Using a similar airplane, the fuel selector was moved to the off position at various power settings, and the time it took for the engine to lose power was measured. Comparing these measurements to the times obtained from the security camera recordings indicated that the accident airplane's fuel selector could not have been turned to and remained in the off position during engine start or run-up. The timing comparisons did, however, indicate a possibility that the fuel selector could have been moved to the off position just before takeoff, which could have resulted in the loss of engine power. If this was the cause of the power loss, changing the position of the fuel selector in flight may have allowed the engine to regain at least partial power before impact.
Diminished airflow through the carburetor due to carburetor ice also could have resulted in the loss of engine power. Temperature and dew point values were conducive to carburetor icing at taxi power settings. If carburetor ice formed during the airplane's taxi with the carburetor heat off, the additional engine heat from the application of takeoff power could have caused the ice to break off and block air flow during the airplane's initial climb, resulting in the loss of engine power. The subsequent addition of carburetor heat could then have melted some or all of the remaining ice and allowed the engine to regain at least partial power before impact. Although no preexisting mechanical anomalies could be found, the amount of damage to the airplane and the lack of recording devices precluded a definitive determination of how the engine power was lost and at least partially recovered.
Probable cause
A loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14FA428
- Event ID
- 20140908X82336
- Case number
- ERA14FA428
- 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: 4f5714f77b30b614b8b9373e8a7dd9dbbcae6ee50e7cd47c900a5a49c8063d14; retrieved 2026-09-14T17:25:39.893Z.