Engine Failure on Initial Climb — Runway 05 at Lakeland
Total power loss at 400 ft AGL over congested residential development. No good forced-landing site ahead. The decision window is seconds.
The scenario
Departing Lakeland Linder International Airport (KLAL), Lakeland, FL — Runway 05, initial climb on a 045° heading. Field elevation 142 ft MSL. You are a visiting pilot, renting a Piper Warrior (PA-28-161) for a personal flight to a nearby field. This is your first time at KLAL; you flew in yesterday and spent the night.
It is a warm Florida morning in late spring: OAT 26°C, dew point 20°C, altimeter 29.94. Clear skies, light winds from 080°. Visibility 10 SM. Density altitude is approximately 1,800 ft — the field is performing as if it were 1,800 ft higher than its true elevation of 142 ft. The Warrior is loaded near gross weight (2,440 lb): you, one passenger, full fuel (36 gal usable), and baggage. Weight and balance are within limits, but you are at the high end of the envelope.
You have completed a thorough preflight, including a full-power magneto check at 1,700 RPM. Both mags checked within limits (max 150 RPM differential, max 50 RPM drop on each mag). The engine started normally and is running smoothly at idle. Carburetor heat is OFF (you will apply it only if needed). You are cleared for takeoff on Runway 05.
The off-field environment off Runway 05's departure end (heading 045°) is low-density residential development, wooded wetland, and scattered open lots — not ideal, but workable. There is no water, no major obstacles immediately visible. The terrain rises slightly to the northeast. You are confident in the airplane and the departure.
You advance the throttle to full power. The Warrior accelerates normally. Airspeed alive at 30 KIAS, rotation at 50 KIAS. You rotate and lift off at 55 KIAS. The airplane climbs out cleanly. You are at 200 ft AGL, climbing at 79 KIAS (Vy, best rate of climb), heading 045°, when the engine begins to lose power. The tachometer is unwinding. The engine is running rough.
Aircraft: Piper Warrior PA-28-161, solo + one passenger, full fuel, within limits. Lycoming O-320-D, 160 hp, carbureted, fixed-pitch prop, fixed gear, LEFT/RIGHT fuel selector (no BOTH position). Steam gauges. Nothing was written up; the airplane was airworthy at preflight.
Pilot: you — a Private pilot, current, roughly 250 hours total. You are not familiar with KLAL. 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 focused on the climb and the rough engine came as a surprise.
- {'label': 'Field', 'value': 'KLAL · Lakeland Linder'}
- {'label': 'Runways', 'value': '5/23 · 10/28'}
- {'label': 'Elevation', 'value': '142 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'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 in a Piper Warrior? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB NYC07CA181 (2007): A Piper PA-28 on a personal flight attempted takeoff from a 1,500-foot turf airstrip with rising terrain and struck trees during initial climb. The probable cause was the pilot's inadequate preflight planning regarding weight and balance, combined with a right magneto malfunction that reduced available power. The airplane was at or near gross weight; the field was short; the terrain rose ahead. The combination was fatal.
NTSB ERA21LA079 (2020): A Piper PA-28 on a personal flight struck a construction barricade on a closed taxiway during a go-around after the pilot was momentarily blinded by sun glare on final approach. The accident was attributed to the pilot's failure to maintain adequate clearance from obstacles during the go-around. The lesson: when obstacles are present and visibility is compromised, commit to a safe landing area immediately rather than attempting recovery maneuvers.
NTSB CHI92DER01 (1992): A Quickie homebuilt 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 accident was attributed to carburetor ice, with lack of suitable terrain for forced landing as a contributing factor. The pilot did not commit to the forced landing early enough; the result was a collision with obstacles.
NTSB MIA91LA128 (1991, fatal): A Sonerai-II homebuilt 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 the pilot's improper adjustment of the carburetor mixture control. The lesson: ensure proper engine setup before takeoff; when engine fails on initial climb, commit to the best available landing site immediately.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KLAL. KLAL has its own accident history (dominant pattern: loss of control inflight 23.7%, loss of control ground 19.4%, forced landing 17.2%), but these specific events happened elsewhere. The scenario is localized to KLAL 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 developed area is survivable only if the pilot commits to a forced landing in the best available area immediately, without attempting to stretch the glide or turn back to the runway. The Warrior's best glide is 73 KIAS; at 200 ft AGL, you have roughly 30–45 seconds of glide time. Use it to find the safest landing area, not to try to make the runway. Off Runway 05 at KLAL, that area is the park or open lot — not the residential streets.
Key lesson — In warm, moist Florida air, the Warrior's carbureted O-320 can accumulate serious carburetor ice even at cruise power and above-freezing temperatures. Apply full carburetor heat at the first sign of engine roughness or unexplained RPM loss. At low altitude over developed area, the decision window is measured in seconds — not minutes. Off Runway 05 at KLAL, the off-field environment is low-density residential development and wooded wetland: a delayed response means a forced landing in a park or open lot, not a return to the runway. Commit early, fly best glide, and land in the safest available area.
Debrief — teaching points
Carburetor ice forms in conditions you would not expect.
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 morning conditions at KLAL. You do not need visible ice, freezing temperatures, or IMC. Warm, moist air at reduced power is the classic carb-ice environment. The Warrior's Lycoming O-320 is carbureted; it has no fuel injection or alternate air system. Carburetor heat is the only tool.
The first symptom is subtle — a dropping tachometer and engine roughness.
In a fixed-pitch airplane like the Warrior, 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.
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 KLAL Runway 05, an engine failure on departure is a forced landing in development.
The off-field environment off Runway 05's departure end (heading 045°) is low-density residential development, wooded wetland, and scattered open lots. There is no water, but there are obstacles. If the engine quits on the Runway 05 departure and altitude is insufficient to return to the airport, the outcome is a forced landing in the best available area — a park, open lot, or field. This is not a worst-case scenario; it is the geographic reality. Best glide is 73 KIAS. Doors unlatched before landing. Master off just before impact. Flaps for slowest possible touchdown speed — impact energy rises with the square of touchdown speed, so the slowest possible speed matters most. Know this before you line up on Runway 05.
The Warrior has LEFT/RIGHT fuel selector — no BOTH position. Tank management is your job.
Unlike some Cessnas, the Warrior's fuel selector has only LEFT, RIGHT, and OFF positions — no BOTH. This means you must actively manage fuel by switching tanks during flight. Fuel starvation from forgetting to switch tanks is a real risk. Before takeoff, verify the fuel selector is on the tank you intend to use (typically the fullest tank or the left tank first). During cruise, switch tanks every 30 minutes or as recommended by the POH. On initial climb, the selector should be on the tank you verified as full during preflight.
Proactive carb heat use in conducive conditions is not optional.
The Warrior 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 morning departure with OAT near 26°C and dew point near 20°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 200 ft AGL over development is waiting too long.
When engine fails on initial climb over developed area, commit to a forced landing immediately.
At 200 ft AGL with best glide of 73 KIAS, you have roughly 30–45 seconds of glide time. That is not enough time to troubleshoot, attempt recovery, AND return to the runway. The NTSB precedents (CHI92DER01, MIA91LA128) show that pilots who delay the forced-landing decision and try to stretch the glide to the runway end up stalling into obstacles. The correct response is: (1) recognize the power loss immediately, (2) establish best glide (73 KIAS), (3) scan for the safest landing area ahead, (4) commit to it, and (5) execute the landing. Off Runway 05 at KLAL, that area is the park or open lot — not the residential streets or trees.
Built from the real accident record
Scenario built from NTSB NYC07CA181 (2007 PA-28-161 engine failure on initial climb over rising terrain and trees), ERA21LA079 (2020 PA-28 obstacle strike during go-around), and regional precedents CHI92DER01, MIA91LA128, ERA13FA325, CHI92DEM03 (engine failure on initial climb over congested/developed areas). Anonymized and localized to KLAL.
NTSB reports: NYC07CA181 · ERA21LA079 · CHI92DER01 · MIA91LA128 · ERA13FA325 · CHI92DEM03
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 Piper Warrior scenarios · More scenarios at KLAL