Engine Failure on Initial Climb — Brooksville
Partial power loss at 400 ft AGL over residential development. No clear forced-landing site ahead. Decision window: seconds.
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 03, initial climb on a 026° heading. Field elevation 76 ft MSL. You are a Private pilot with 180 hours total, current and proficient. This is your first flight from KBKV; you arrived yesterday for a business meeting.
It is a warm, humid Florida morning in late summer: OAT 31°C, dew point 24°C, altimeter 29.91. Scattered clouds at 3,500 ft, visibility 10 SM. A typical Gulf Coast day — warm, moist air, high density altitude. The tower is open (part-time 0700–2200 local); you are in Class D airspace.
You are cleared for takeoff on Runway 03 at 0830 local. The runway is 4,200 ft long; you rotate at 51 KIAS and lift off cleanly at 57 KIAS. Climb is normal. At 400 ft AGL, heading 026°, climbing through 79 KIAS (Vy), the engine begins to lose power. The tachometer is unwinding. The airplane is no longer climbing — it is maintaining altitude at best.
Ahead and to the left (north and west of the runway), the off-field environment is residential development — single-family homes, trees, power lines, and some open pasture mixed in. Behind you is the runway. To the right (east) is more development. There is no clear, unobstructed field ahead. The decision window is measured in seconds.
Aircraft: Cessna 172R, solo, 40 gallons usable fuel (full tanks), within limits. Fuel selector BOTH. Mixture set for field elevation (76 ft). Boost pump OFF (normal for takeoff). The airplane was airworthy at departure; nothing was written up. Engine instruments show the power loss — manifold pressure and RPM are both dropping.
Pilot: you — Private pilot, 180 hours, current. You did not fly from KBKV yesterday; this is your first departure from this field. You did not review the off-field environment in detail before takeoff. You are focused on the climb and the departure procedure.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about engine failure on initial climb in a C172R? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN14CA023 (2013): A Cessna 172R student pilot touched down too far down a narrow runway during a touch-and-go landing and delayed aborting the takeoff, resulting in collision with trees at the runway end. The probable cause was the student pilot's delay in aborting the takeoff. The lesson: at low altitude with an engine anomaly, commit early to the best available landing site rather than attempting to stretch the climb or maneuver.
NTSB WPR12LA092 (2012): A Piper PA-28R-201T experienced partial engine power loss between 300 and 500 feet AGL after takeoff from Kalispell, Montana, and made a forced landing on a residential street. The probable cause was magneto malfunction. The contributing factor was the pilot's attempt to maneuver over a congested area rather than committing immediately to the safest available landing site.
NTSB CHI92DER01 (1992): A Goehring Quickie lost engine power during initial climb after a touch-and-go landing and made a forced landing in a residential area after descending through trees and a house. The probable cause was carburetor ice. The lesson: recognize early that return-to-runway is not feasible and commit to the best available forced-landing site rather than attempting to 'milk it around' over populated areas.
The local environment at KBKV Runway 03 makes this scenario particularly unforgiving: the climb-out environment (heading 026°) is residential development with pasture mixed in — no clear, unobstructed field. An engine failure on the Runway 03 departure at low altitude leaves no good forced-landing option ahead. The only viable option is return to the runway or a forced landing in the available development (pasture, park, or open area). This is not hypothetical; it is the USGS NLCD ground cover off that runway end.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport. KBKV has its own accident history (see field dominant patterns: hard landings, forced landings, runway excursions), but these specific events happened elsewhere. The scenario is localized to KBKV to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: engine failure or power loss at low altitude over congested terrain is survivable only if the pilot commits early to the best available landing site rather than attempting to stretch the glide, maneuver around obstacles, or return to the runway from an altitude where the turn is marginal. The C172R's fuel system can experience starvation at low altitude if the boost pump is OFF — a procedural issue, not a mechanical failure. Early recognition and immediate boost pump ON is the entire lesson.
Key lesson — In a C172R at low altitude with full tanks, fuel starvation can occur if the boost pump is OFF — the engine may be drawing fuel faster than the fuel pump can supply at low pressure. Apply boost pump ON immediately at the first sign of power loss on initial climb. Off Runway 03 at KBKV, the climb-out environment is residential development: a delayed response or failed recovery means a forced landing in available terrain, not a return to the runway.
Debrief — teaching points
Boost pump ON is required for climb at low altitude in the C172R.
The C172R's fuel system uses a mechanical fuel pump (engine-driven) and an electric boost pump. At low altitude during climb, especially with full tanks and high fuel demand, the mechanical pump alone may not supply adequate fuel flow. The boost pump is OFF for takeoff roll (to avoid vapor lock on the ground), but it should be ON during the climb. Many C172R pilots forget this step or do not understand the requirement. At 400 ft AGL with the boost pump OFF, fuel starvation is the most likely cause of power loss.
The first symptom of fuel starvation is a dropping tachometer and power loss — not roughness.
Unlike carburetor ice (which shows as roughness), fuel starvation in a fuel-injected engine shows as a smooth power loss — the tachometer unwinds, manifold pressure drops, and the airplane stops climbing. There is no roughness, no coughing. The symptom is clean but unmistakable: the engine is losing power. Scan the tachometer as part of your regular instrument scan during climb, especially at low altitude.
At 400 ft AGL over congested terrain, return-to-runway is marginal and depends on runway length, wind, and distance.
The 'impossible turn' is a real phenomenon. At 400 ft AGL in a C172R with partial power loss, a 180° turn back to the departure runway requires altitude and coordination you may not have. A 4,200 ft runway (Runway 03/21 at KBKV) gives you more room than a 3,000 ft runway, but the turn is still tight. Do not assume return-to-runway is feasible — assess it quickly, and if it is not, commit immediately to the best available forced-landing site ahead.
Off Runway 03 at KBKV, the climb-out environment is residential development — no clear forced-landing site.
The off-field environment off Runway 03's departure end (heading 026°) is residential development with pasture and open areas mixed in. There is no large, unobstructed field. A forced landing in this environment means landing in a pasture, park, or open area within the development — not a smooth grass field. This is the geographic reality. Know this before you line up on Runway 03.
Commit early to the best available forced-landing site rather than attempting to stretch the glide.
When return-to-runway is not feasible and the engine is failing at low altitude, the correct decision is to commit immediately to the best available forced-landing site — even if it is suboptimal. Attempting to 'milk it around' over power lines, trees, or populated areas to reach a better site often results in a stall/spin or impact with obstacles. The NTSB data is clear: early commitment to the best available site has better survival outcomes than attempting to stretch the glide.
Built from the real accident record
Scenario inspired by NTSB CEN14CA023 (2013 C172R aborted takeoff / tree strike), WPR12LA092 (2012 Piper PA-28R partial power loss over congested area), and CHI92DER01 (1992 engine failure over residential area). Real events occurred at other airports — NOT at Brooksville–Tampa Bay Regional (KBKV). Localized to KBKV's actual runway environment and off-field terrain.
NTSB reports: CEN14CA152 · CEN14CA023 · ERA12CA325 · ATL04CA170 · CHI92DER01 · CHI03LA083 · WPR12LA092 · FTW85LA278
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 KBKV