Engine Failure Over Sarasota Development
Total power loss on initial climb off Runway 04 — no good forced-landing site ahead, marginal terrain behind
The scenario
Departing Sarasota Bradenton International Airport (KSRQ), Runway 04, climbing out on a 038° heading over the Sarasota/Bradenton development. Elevation 30 ft MSL; the runway is essentially at sea level. Runway 04 is 5,006 ft of asphalt, and the off-field environment on the climb-out (heading 038°) is marginal: mostly medium development, wooded wetland, and low-density residential. There are no open fields, no roads wide enough for a safe forced landing, and no water suitable for a ditching. Behind you (Runway 22 end) is open water and parks — but you are committed to the 04 departure.
It is a hot, humid Florida morning in late July: OAT 32°C, dew point 26°C, altimeter 29.89. Scattered clouds at 3,500 ft, visibility 10 SM. The density altitude is approximately 2,800 ft — the airplane will climb like it is at 2,800 ft elevation, not sea level. The C172M, with its 150 hp Lycoming O-320, is already marginal on climb performance in this heat. You are at gross weight (2,300 lb) with a full cabin and full fuel.
You are 300 ft AGL, climbing through 78 KIAS (Vy, best rate of climb), heading 038°, when the engine begins to run rough. Power is noticeably down — the tachometer is dropping. The development below is dense and unforgiving. KSRQ's tower is open (it operates 0600–0000 local) and is aware of your departure; you are in Class C airspace.
Aircraft: Cessna 172M, four souls on board, full fuel, within limits. Carbureted Lycoming O-320, fixed-pitch prop, steam panel, fuel selector on BOTH. The airplane was airworthy at departure; nothing was written up. You did not apply carburetor heat during the run-up because the engine ran smoothly. You did not apply it after takeoff because you were heads-down on the climb.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have never flown out of KSRQ before. You are not familiar with the terrain or the off-field options. You did not brief the forced-landing environment before departure. You are now at 300 ft AGL with a rough engine and no good landing site ahead.
- {'label': 'Field', 'value': 'KSRQ · Sarasota Bradenton'}
- {'label': 'Runways', 'value': '4/22 · 14/32'}
- {'label': 'Elevation', 'value': '30 ft'}
- {'label': 'Aircraft', 'value': 'C172M'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you already know about engine failure on initial climb in a C172M? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR09FA316 (2009, FATAL): A Cessna 172M on approach to Tieton State Airport in mountainous terrain failed to land and initiated a go-around at low altitude, striking trees at the runway end. The pilot lacked experience with turf airstrips and mountainous terrain; the go-around was initiated too late. The probable cause was the pilot's failure to maintain clearance from trees during the go-around, with contributing factors including inadequate experience and delayed decision-making.
NTSB GAA15CA088 (2015): A Cessna 172M struck trees during takeoff when the pilot attempted to abort after discovering the gust lock was still installed in the yoke. The accident resulted from the pilot's failure to remove the gust lock during preflight inspection, combined with crosswind conditions that pushed the aircraft off the runway. The lesson: a thorough preflight is not optional, and when an anomaly appears on the runway, the decision to abort must be immediate.
NTSB MIA91LA128 (1991, FATAL): A homebuilt aircraft experienced total engine failure shortly after takeoff and made a forced landing in an alley, where it touched down hard, bounced, and struck a telephone pole. The accident resulted from improper adjustment of the carburetor mixture control. The lesson: recognize engine performance degradation during takeoff and commit to a forced landing decision early; understand how improper mixture control can cause power loss on climb.
NTSB ERA13FA325 (2013): A Beech 23 lost total engine power at 250 feet AGL shortly after takeoff from Suburban Airport, Maryland, and struck a tree and houses during a forced landing. The accident was attributed to inadequate preflight preparation and decision to operate an unairworthy aircraft with a compromised fuel system. The lesson: thorough preflight inspection and airworthiness assessment before flight; recognize when an aircraft is unfit to fly and commit to not departing; decision-making when engine failure occurs over congested terrain.
NTSB NYC89DHM05 (1989): A Woods Formula Vee homebuilt experienced total engine failure at approximately 100 feet during initial climb and made a forced landing on an airport access road. The lesson: recognize engine roughness early and commit to landing straight ahead rather than attempting a turn back to runway when altitude is marginal; understand energy management during engine failure.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Sarasota Bradenton International Airport. KSRQ has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_GROUND 19.2%, FORCED_LANDING 15.4%, RUNWAY_EXCURSION 11.5%, HARD_LANDING 11.5%, LOSS_OF_CONTROL_INFLIGHT 11.5%), but these specific events happened elsewhere. The scenario is localized to KSRQ to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: engine failure on initial climb over congested terrain is unforgiving. There is no good landing site. The decision window is measured in seconds. The correct response is to recognize the problem early (carburetor ice, fuel selector, mixture, gust lock, preflight omission), apply the fix if there is one (carb heat, fuel selector, mixture, abort), and if the engine fails completely, commit to the best available forced-landing site straight ahead — not a turn back to the runway that risks a stall/spin at low altitude.
Key lesson — In warm, moist Florida summer air, the C172M's carbureted O-320 can accumulate serious carburetor ice even at sea level and above-freezing temperatures. Apply full carburetor heat at the first sign of engine roughness or unexplained RPM loss. At low altitude over development, the decision window is measured in seconds — not minutes. Off Runway 04 at KSRQ, the off-field environment is marginal: medium development, wooded wetland, low-density residential — no good forced-landing site. A delayed response means a forced landing in the worst possible terrain. Know the off-field environment before you depart.
Debrief — teaching points
Carburetor ice forms in conditions you would not expect — especially on takeoff and initial climb.
The FAA icing probability chart shows 'serious icing at glide power' at temperatures between roughly 20°C and 30°C when relative humidity is high — exactly the Florida summer afternoon conditions at KSRQ. You do not need visible ice, freezing temperatures, or IMC. Warm, moist air at reduced power is the classic carb-ice environment. The C172M's Lycoming O-320 is carbureted; it has no alternate air system. Carburetor heat is the only tool. On takeoff and initial climb, when the engine is at reduced power (Vy, best rate of climb), the conditions are perfect for ice formation.
The first symptom is subtle — a dropping tachometer and engine roughness.
In a fixed-pitch airplane like the C172M, carburetor ice first shows as engine roughness and an unexplained RPM decrease. There is no dramatic power cut. Pilots who are not actively monitoring the tachometer miss the early warning. By the time the roughness is obvious, significant ice has accumulated. Scan the tachometer as part of your regular instrument scan, especially in conducive conditions. On takeoff and initial climb, the tachometer should be steady or rising slightly; any unexplained drop is a red flag.
Apply full carburetor heat — not partial — and expect an initial RPM drop.
When you apply carb heat to an iced carburetor, the RPM will drop further before it rises. This is expected and normal: the heat is melting ice and the resulting water is briefly disrupting combustion. Do not remove carb heat when the RPM drops — that is the heat working. Hold it full on. The RPM will recover as the ice clears, typically within 15–30 seconds depending on ice accumulation. Partial carb heat can worsen the situation by partially melting ice into water ingestion without fully clearing the restriction.
At KSRQ Runway 04, an engine failure on departure is a forced landing in development — no good site.
The off-field environment off Runway 04's departure end (heading 038°) is marginal: medium development, wooded wetland, low-density residential. There is no open field, no road wide enough for a safe landing, and no water suitable for a ditching. If the engine quits on the Runway 04 departure and altitude is insufficient to return to the runway, the outcome is a forced landing in the worst possible terrain. Best glide is 65 KIAS. Commit to the best available site straight ahead — a parking lot, a wide street, a park — rather than attempting a turn back to the runway at low altitude, which risks a stall/spin. Know this before you line up on Runway 04.
Proactive carb heat use in conducive conditions is not optional.
The C172M POH and the FAA Pilot's Handbook of Aeronautical Knowledge both recommend applying carburetor heat when conditions are conducive to icing — before the symptom appears. In a Florida summer departure at KSRQ, with OAT near 32°C and dew point near 26°C, that means applying carb heat during the run-up check (and confirming the expected RPM drop, then recovery) and considering its use during climb in visible moisture or high humidity. Waiting for the roughness to appear at 300 ft AGL over development is waiting too long.
Brief the forced-landing environment before departure — it is part of your preflight.
Before you line up on any runway, you should know what the off-field environment looks like. Is it water? Is it development? Is it open field? Are there trees? Are there power lines? This is not optional — it is part of your preflight planning. At KSRQ, Runway 04 departs over marginal terrain; Runway 22 departs over water and parks. The choice of runway, and your decision-making if the engine fails, depends on knowing this. Spend 30 seconds looking at the terrain before you request takeoff clearance.
The C172M at gross weight in high density altitude is marginal on climb performance.
The C172M, with its 150 hp Lycoming O-320, is already marginal on climb performance at gross weight in heat and high density altitude. At KSRQ on a hot day (32°C, density altitude ~2,800 ft), the airplane will climb like it is at 2,800 ft elevation, not sea level. A full cabin and full fuel make it worse. Understand your airplane's performance limits before you depart. If the engine is rough or losing power, you may not have the altitude margin to recover — the window is narrow.
Built from the real accident record
Scenario built from NTSB WPR09FA316 (2009 C172M go-around / tree strike), GAA16CA011 (2015 C172M approach path loss), GAA15CA088 (2015 C172M gust lock / loss of control), ERA14CA430 (2014 C172M navigation error / off-airport landing), and regional precedents MIA91LA128, ERA13FA325, NYC89DHM05, CHI04CA108 (engine failure on initial climb over congested terrain). Anonymized and localized to KSRQ.
NTSB reports: WPR09FA316 · GAA16CA011 · GAA15CA088 · ERA14CA430 · MIA91LA128 · ERA13FA325 · NYC89DHM05 · CHI04CA108
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.A — Preflight Inspection · 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 172M scenarios · More scenarios at KSRQ