Power Loss on Initial Climb
Engine failure shortly after takeoff at Tampa Executive — decision-rich forced landing with runway-dependent off-field options
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 05, initial climb on a heading of 042° true. Field elevation 22 ft MSL. It is a clear, calm morning; OAT 22°C, light winds from the northeast. Visibility 10+ SM. A routine local flight — you are climbing out after a touch-and-go landing, heading back to the pattern for another circuit.
Aircraft: Cessna 172R, solo, full fuel, within limits. Lycoming IO-360-L2A, fuel-injected, 160 hp, fixed-pitch prop, steam panel with vacuum-driven instruments. The airplane was airworthy at preflight; nothing was written up. Engine run-up was normal — mag check good, engine temps and pressures in the green, mixture set for the field elevation.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have 40 hours in the C172R. This is a local training flight; you are familiar with KVDF and the surrounding area. You are climbing at 79 KIAS (Vy, best rate of climb), gear down (fixed), flaps up, heading 042° true.
At 400 ft AGL, passing through 300 ft MSL, the engine begins to lose power. The tachometer is unwinding. The engine is not running rough — it is simply producing less power. You have roughly 30 seconds of useful decision time before altitude becomes critical. The runway is behind you. Ahead and to your left (northwest) is wooded wetland and medium development. Ahead and to your right (northeast) is pasture, hay fields, and scattered development. To your right rear is open water — the bay.
This is a real forced-landing scenario. The decision you make in the next 30 seconds will determine the outcome.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before the decision tree — what do you know about engine failure on initial climb in the C172R? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN14LA333 (2014): A Cessna 172R on an instructional cross-country flight experienced partial loss of engine power during initial climb after a touch-and-go landing. The pilot made a forced landing short of the runway. The probable cause was partial loss of engine power for reasons that could not be determined — postaccident engine testing revealed no anomalies that would have precluded normal operation. The engine failure was real, but the root cause (mechanical fatigue, maintenance error, or undiscovered defect) was never identified.
NTSB ANC18LA013 (2017): A Cessna 172R on a personal flight experienced total engine power loss shortly after takeoff during initial climb. The probable cause was total loss of engine power for reasons that could not be determined — postaccident examination and testing revealed no preimpact mechanical malfunctions or failures. The engine quit completely, but why remains a mystery.
NTSB WPR18LA039 (2017): A Cessna 172R experienced total engine power loss due to crankshaft fatigue fracture during climb. The instructor performed a forced landing to a field past the runway. The crankshaft separated due to fatigue — a structural failure that could not have been predicted by preflight inspection. The engine simply quit.
NTSB ERA14LA142 (2014): A Cessna 172R experienced rapid oil pressure loss during climb, returned to the departure airport, and lost all engine power during an ILS approach. The probable cause was total loss of engine power due to maintenance personnel's improper installation of the lower vacuum pump. A maintenance error — not a pilot error, not a design flaw — caused the failure.
The common thread: engine failures on initial climb in the C172R happen. Sometimes the cause is mechanical (crankshaft fatigue, pump failure, maintenance error). Sometimes the cause is never determined. The preflight cannot always catch them. The decision that matters is what you do in the first 30 seconds after the power loss — establish best glide, evaluate your options, and commit to the best available landing site.
The real accidents cited above occurred at other airports — NOT at Tampa Executive Airport (KVDF). KVDF has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_GROUND 18.4%, HARD_LANDING 18.4%, FORCED_LANDING 15.8%), but these specific NTSB events happened elsewhere. The scenario is localized to KVDF to make the off-field environment real and consequential for you as a student here.
Off Runway 05's departure end (heading 042°), the off-field environment is wooded wetland and medium development — not ideal for a forced landing, but better than open water. Off Runway 36's departure end (heading 360°), the off-field environment is open water — a ditching. The runway you depart on determines your forced-landing options. Know your field.
Key lesson — Engine failure on initial climb is survivable if you establish best glide immediately (65 KIAS in the C172R), evaluate your options, and commit to the best available landing site. The decision window is 30 seconds. The first action is to lower the nose and establish best glide — not to diagnose, not to turn back, not to climb. Glide distance and time are your assets. Spend them wisely. Off Runway 05 at KVDF, the pasture and hay fields to the northeast are your best forced-landing option. Off Runway 36, the open water means a ditching — know which runway you are departing before you line up.
Debrief — teaching points
Best glide is the first action — not diagnosis, not turning back.
The moment you recognize engine power loss on initial climb, lower the nose to establish best glide speed (65 KIAS in the C172R). This is not optional. Best glide maximizes your glide distance and time to evaluate options. Every second you spend in a climb attitude or at a non-optimal speed is altitude and distance you lose. The preflight and run-up cannot always catch mechanical failures — crankshaft fatigue, pump failures, and maintenance errors can happen without warning. Your response is what matters.
Impact energy rises with the square of touchdown speed — full flaps is the standard.
In a forced landing, the dominant value of full flaps is the slowest possible touchdown speed. Full flaps (30°) in the C172R reduces stall speed to 33 KIAS (Vs0). Partial flaps (10°) leaves you at roughly 50 KIAS. No flaps leaves you at 65 KIAS (best glide). Impact energy rises with the square of speed — the difference between 33 KIAS and 65 KIAS is a factor of 4 in impact energy. Full flaps is always the goal in a forced landing.
The C172R is fuel-injected — there is no carburetor heat.
The C172R has a Lycoming IO-360-L2A fuel-injected engine. There is no carburetor, no carburetor heat, and no carb-ice risk. Engine roughness or power loss in the C172R is not a carb-ice problem. It is a mechanical, fuel-system, or electrical issue. The boost pump should be on for takeoff and climb. The mixture should be set for the field elevation (at KVDF's 22 ft MSL, full rich or near-full rich). If power is lost despite these settings, it is a mechanical failure — not a fuel-system management issue.
Off-field environment is runway-dependent — know your field.
Off Runway 05's departure end (heading 042°) at KVDF, the off-field environment is wooded wetland and medium development — not ideal, but better than open water. Off Runway 36's departure end (heading 360°), the off-field environment is open water — a ditching. Off Runway 23's departure end (heading 222°), the environment is pasture, hay, and scattered development — good. Off Runway 18's departure end (heading 180°), the environment is low-density development and wooded wetland — marginal. The runway you depart on determines your forced-landing options. Know your field before you line up.
A straight-in approach is the correct emergency approach — shortest path, no unnecessary turns.
When you are returning to the airport with an engine failure at low altitude, fly a straight-in approach to the runway. The shortest path to the runway is the goal. At 300 ft AGL with a sick engine, a full pattern is a luxury you may not have. Advise CTAF (KVDF is non-towered) of the emergency and your straight-in approach. Fly the approach at best glide speed (65 KIAS), add flaps as the runway is made, and land. This is the correct execution of an engine-failure approach.
Built from the real accident record
Scenario built from NTSB CEN14LA333 (2014 C172R partial power loss on initial climb), ANC18LA013 (2017 C172R total engine power loss shortly after takeoff), WPR18LA039 (2017 C172R crankshaft fatigue fracture during climb), and ERA14LA142 (2014 C172R oil pressure loss during climb). Real events occurred at other airports — NOT at Tampa Executive Airport (KVDF).
NTSB reports: CEN14LA333 · ANC18LA013 · WPR18LA039 · ERA14LA142
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors · PA.II.B — Engine Starting / Systems Preflight
Relevant FARs: §91.3 · §91.13 · §91.185
Step through the full decision tree, make the calls, and see where each choice leads — then debrief it with your CFI.
Open the interactive scenario →All sample scenarios · More Cessna 172R scenarios · More scenarios at KVDF