Engine Failure Over Tampa Bay

Departing Albert Whitted Airport (KSPG), St. Petersburg, FL — Runway 07, climbing out on a 062° heading over Tampa Bay. Elevation 7 ft MSL. It is a calm, clear morning; visibility 10 SM, OAT 22°C, altimeter 30.01. Winds calm. A textbook VFR day.

You are a Private pilot with roughly 250 hours total, current and proficient. You are flying a Cessna 172M — the carbureted, 150-hp variant with fixed gear and fixed-pitch prop. The airplane is within limits, full fuel, solo. The preflight was thorough; nothing was written up. The engine ran smoothly on the ground.

You line up on Runway 07, advance the throttle to full power, and rotate at 55 KIAS. The airplane climbs smoothly. At 400 ft AGL, heading 062°, climbing at 78 KIAS (Vy, best rate of climb), the engine suddenly loses ALL power. The tachometer drops to zero. No sputtering, no cough — total, immediate loss. You have roughly 30 seconds of useful altitude and a critical decision to make.

Off the Runway 07 departure end (heading 062°), the off-field environment is open water — Tampa Bay. There is no alternate landing surface ahead. Behind you is the airport, but you are 400 ft AGL, airspeed 78 KIAS, and the engine is dead. The 'impossible turn' back to Runway 25 (heading 242°) is a known trap: at 400 ft AGL with a dead engine, a 180° turn back to the departure runway is marginal at best and often ends in a stall/spin.

KSPG tower is part-time, open 0700–2100 local. You are in Class D airspace. The tower is aware of your departure. You are alone in the airplane. You have no time for lengthy deliberation. What do you do?

NTSB ERA15LA091 (2014): A Cessna 172M experienced total loss of engine power during cruise flight at 10,500 feet over the Atlantic Ocean and was ditched in the ocean about 5 miles from the nearest land mass. The accident resulted from total loss of engine power for reasons that could not be determined, as examination of the engine revealed no anomalies that would have precluded normal operation. The pilot executed a controlled ditching and survived.

NTSB ERA11LA429 (2011): A Cessna 172M experienced partial engine power loss during takeoff and made a controlled ditching in Lake Okeechobee after the pilot was unable to land on the intended runway. The accident resulted from separation of the No. 3 cylinder exhaust valve head. Contributing factor: the operator's exceedence of the engine manufacturer's recommended time between overhauls. The pilot's misjudgment of the airplane's position and airspeed relative to the runway during the return to the airport contributed to the accident.

NTSB ANC08LA007 (2007): A float-equipped Cessna 172M nosed over during a water landing on Rangeley Lake when the pilot's attention was diverted by military helicopters operating in close proximity to the landing area. The accident resulted from the pilot's failure to maintain aircraft control during the landing flare/touchdown, with diverted attention as a contributing factor. The lesson: maintain focus on the landing itself; external distractions can be fatal.

NTSB IAD02LA003 (2001): A Cessna 172M on a fish spotting flight over the Chesapeake Bay near White Stone, Virginia lost engine power at 2,500 feet and ditched in 50-foot deep water. The cause of the engine power loss could not be determined. The pilot survived the ditching.

NTSB LAX89LA222 (1989, FATAL): A Grumman AA-1C stalled on final approach over coastal water in gusting crosswind conditions and impacted the ocean short of the runway. The accident resulted from the pilot's failure to maintain sufficient airspeed to prevent a stall at an altitude too low for recovery. The mechanism — low altitude, low airspeed, steep turn, stall/spin — is the fatal outcome of the impossible turn trap.

NTSB ERA10CA300 (2010): A Piper PA-18-135 stalled and entered a spin during a climbing right turn on final approach when the pilot attempted to perform a 360-degree turn per ATC spacing request. The accident was attributed to the pilot's failure to maintain adequate airspeed during the climbing turn. The lesson: prioritize airspeed maintenance over ATC requests; recognize when a maneuver exceeds aircraft capability.

NTSB ATL92LA146 (1992): A Cessna 172D stalled 15 feet above ground during short final approach and crashed short of the runway surface. The accident resulted from the pilot's failure to maintain flying speed during final approach. The lesson: maintain flying speed throughout final approach; recognize stall warning signs early and execute go-around if airspeed decays below safe margin.

All of these real accidents occurred at other locations — NOT at Albert Whitted Airport (KSPG). However, KSPG's own accident history shows a dominant pattern of LOSS_OF_CONTROL_INFLIGHT (20%), FORCED_LANDING (16.4%), and DITCHING (12.7%) — the same mechanisms. The scenario is localized to KSPG to make the off-field environment real and consequential: Runway 07's departure end is open water. 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: at low altitude with a dead engine, the impossible turn back to the departure runway is a known trap. The turn requires altitude, airspeed, and coordination you are marginal on. Stall/spin risk is high. The safer, more survivable outcome is a controlled ditching — when you have time to prepare. Commit to the ditching early, when altitude allows you to complete the pre-impact checklist (doors unlatched, master off, flaps for slowest touchdown speed). The slowest possible touchdown speed is the priority — impact energy rises with the square of speed.