Engine Failure on Runway 07 Departure
Total power loss at 300 ft AGL over Tampa Bay — immediate ditching decision and execution
The scenario
Departing Albert Whitted Airport (KSPG), St. Petersburg, FL — Runway 07, local VFR flight. Elevation 7 ft MSL. The runway is essentially at sea level; off the Runway 07 departure end (heading 062°), the off-field environment is open water — Tampa Bay. There is no alternate landing surface ahead on the initial climb-out.
It is a clear, calm morning: OAT 22°C, winds calm, altimeter 29.92, visibility 10+ SM. The airplane is a Cessna 172N, solo, full fuel, within limits. You completed a normal preflight and run-up; the engine ran smoothly. The airplane was airworthy at departure. You are cleared for takeoff on Runway 07.
You roll down Runway 07, rotate at 55 KIAS (Vr), and climb out at 73 KIAS (Vy). At 300 ft AGL, heading 062° over Tampa Bay, the engine suddenly loses all power. The tachometer drops to zero. The propeller is windmilling. You have no engine thrust.
Pilot: you — a Private pilot, current, roughly 200 hours total. You have never experienced a total engine failure in flight. You have practiced forced-landing procedures in the simulator, but this is real. The water is ahead and below. The airport is behind you. You have seconds to decide.
Aircraft systems: Lycoming O-320, carbureted, fixed-pitch prop, fixed gear. Fuel selector on BOTH. No fuel contamination was noted during preflight. The throttle was full forward at takeoff. The engine failure is total and immediate — not a gradual power loss, but a complete loss of thrust.
- {'label': 'Field', 'value': 'KSPG · Albert Whitted'}
- {'label': 'Runways', 'value': '7/25 · 18/36'}
- {'label': 'Elevation', 'value': '7 ft'}
- {'label': 'Aircraft', 'value': 'C172N'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you already know about engine failure on initial climb and ditching? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB NYC06LA179 (2006, fatal): A Cessna 172N on a personal local flight experienced partial loss of engine power during cruise due to improper maintenance of the throttle shaft during the most recent annual inspection. The pilot made a forced landing that resulted in collision with trees. The probable cause was improper maintenance of the throttle shaft, which resulted in a partial loss of engine power during cruise flight.
NTSB CEN25LA168 (2025): A Cessna 172N on an instructional flight lost total engine power on final approach when the throttle cable was found disconnected from the carburetor. The pilot executed a forced landing to a field. The accident resulted from improper maintenance following carburetor replacement, with an apprentice's work not adequately inspected by the supervising mechanic.
NTSB CHI02FA247 (2002, fatal): A Cessna 172N on a night personal flight from Minnesota to Wisconsin experienced fuel exhaustion during final approach and was forced to land in a cornfield. The accident resulted from the pilot's failure to refuel before departure and inadequate fuel planning, with contributing factors including pilot fatigue and night conditions.
NTSB CEN25LA099 (2025): A Cessna 172N on a cross-country flight lost total engine power during a go-around after an aborted landing due to fuel exhaustion. The accident resulted from poor flight planning and the pilot's decision not to refuel at an intermediate stop despite instructor guidance.
Regional ditching precedents: NTSB BFO91LA069 (1991, C177RG): A pilot lost engine power at 300 ft AGL during initial climb and executed a controlled ditching in the Ohio River. The probable cause was total loss of engine power for undetermined reasons. The pilot recognized the engine failure early, assessed glide distance, and committed to ditching rather than attempting a marginal return to the runway. NTSB NYC03LA109 (2003, C175A): A pilot experienced partial loss of engine power during initial climb and ditched in shallow water near Ocean City, New Jersey. The pilot evaluated whether altitude and distance permitted safe return to the airport, recognized when ditching was the only safe option, and executed it promptly. NTSB ANC13LA048 (2013, PA-16): A pilot on a personal flight experienced total engine failure at 350 ft AGL shortly after takeoff. The pilot successfully ditched the aircraft in the ocean; both occupants evacuated safely and were rescued. NTSB ERA11LA405 (2011, C206G): A Part 135 air taxi flight lost engine power during initial climb due to fuel starvation. The pilot ditched the aircraft in the ocean near Matinicus Island, Maine, and all occupants were rescued.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Albert Whitted Airport (KSPG). KSPG has its own accident history dominated by loss-of-control inflight, forced landings, and ditching (12.7% of the field's corpus). The scenario is localized to KSPG to make the off-field environment real and consequential for you as a student here: Runway 07's departure end is open water — Tampa Bay. An engine failure on the Runway 07 departure at low altitude is a ditching, not a field landing.
The consistent thread across all these events: total engine failure on initial climb is rare, but when it happens, the decision window is measured in seconds. The pilot who recognizes the failure early, establishes best glide immediately, assesses whether the airport is reachable, and commits to ditching if it is not — that pilot survives. The pilot who delays, attempts a marginal turn back to the runway, or tries to restart the engine at low altitude — that pilot does not.
Key lesson — Total engine failure on initial climb over water is survivable if you respond decisively: establish 65 KIAS best glide immediately, assess altitude and distance to the airport, and commit to a controlled ditching if the airport is not reachable. At 300 ft AGL on the Runway 07 departure at KSPG, the off-field environment is Tampa Bay. A controlled ditching in calm water with proper configuration (doors unlatched, master switch off before impact, flaps for slowest touchdown speed) has a high survival rate. A stall/spin attempt to stretch the glide to the runway does not.
Debrief — teaching points
Establish best glide (65 KIAS) immediately after total engine failure.
The moment you recognize total engine power loss, lower the nose to establish 65 KIAS best glide. This is the speed that maximizes glide distance and gives you the most time to assess options. At 300 ft AGL, every second counts. Delay in establishing best glide costs altitude and options. The C172N's best glide speed is 65 KIAS at gross weight — use this number, not a guess.
Assess altitude and distance to the airport within the first 10–15 seconds.
At 300 ft AGL on the Runway 07 departure, the airport is 0.8 nm behind you. At 65 KIAS glide speed, that is roughly 45 seconds of glide time. Descent rate at best glide is roughly 500 ft/min. You have roughly 300 ft of altitude. The math is tight — you might make it, but the margin is thin. If you cannot reach the airport with a comfortable margin, commit to ditching. Do not attempt a marginal turn back to the runway at low altitude; the risk of a stall/spin is high.
A controlled ditching in calm water is survivable; an uncontrolled one or a stall/spin is not.
If the airport is not reachable, commit to a controlled ditching. Configure the airplane: unlatch the doors (so they open on impact and you can exit), keep the fuel selector on BOTH, position your hand on the master switch to turn it off just before water contact (to prevent fire), and add flaps incrementally to 20–30° for the slowest possible touchdown speed. Impact energy rises with the square of speed — minimizing touchdown speed is critical to survival. Maintain 65 KIAS approach speed. Aim for smooth water. Level wings, shallow descent angle. Survival rates in controlled ditchings are significantly higher than in uncontrolled ones.
Off Runway 07 at KSPG, the off-field environment is open water — Tampa Bay.
The USGS NLCD ground cover off Runway 07's departure end (heading 062°) is open water. There is no alternate landing surface ahead on the initial climb-out. An engine failure on the Runway 07 departure at low altitude is a ditching, not a field landing. This is not a worst-case scenario; it is the geographic reality of KSPG's Runway 07. Know this before you line up on Runway 07. If you are uncomfortable with the risk of a ditching off Runway 07, request Runway 25 for departure (heading 242°), where the off-field environment is dense development — not ideal, but not water.
A marginal turn back to the runway at low altitude risks a stall/spin.
At 300 ft AGL with total engine failure, a 180° turn back to the departure runway is marginal. The turn eats altitude rapidly. At low airspeed (approaching stall speed of 48 KIAS clean), a steep bank can result in a stall. A stall/spin at 300 ft AGL is unrecoverable. If you decide to turn back, keep the bank shallow (15° or less), maintain 65 KIAS best glide, and be prepared to abandon the turn and commit to ditching if altitude becomes critical. The safer decision at 300 ft AGL over water is often to commit to ditching rather than attempt a marginal return to the runway.
Built from the real accident record
Scenario built from NTSB NYC06LA179 (2006 C172N throttle-shaft failure / forced landing), CHI02FA247 (2002 C172N fuel exhaustion / forced landing), CEN25LA168 (2025 C172N throttle disconnection / forced landing), CEN25LA099 (2025 C172N fuel exhaustion / go-around failure), and regional ditching precedents BFO91LA069 (1991 C177RG engine failure / controlled ditching), NYC03LA109 (2003 C175A partial power loss / ditching), ANC13LA048 (2013 PA-16 engine failure / ocean ditching), ERA11LA405 (2011 C206G fuel starvation / ditching). Localized to KSPG.
NTSB reports: NYC06LA179 · CHI02FA247 · CEN25LA168 · CEN25LA099 · BFO91LA069 · NYC03LA109 · ANC13LA048 · ERA11LA405
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 · PA.II.C — Takeoff and Climb
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 172N scenarios · More scenarios at KSPG