Power Loss on the Climb-Out
Partial engine failure in a Piper Warrior over dense development — a low-altitude decision with no good off-field options
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 16, climbing out on a 155° heading. Elevation 71 ft MSL. You are in Class G airspace (non-towered, CTAF), but the overlying Tampa Class B begins at 3,000 ft MSL — you will need to stay below that or request clearance.
It is a warm, humid Florida morning in late spring: OAT 26°C, dew point 21°C, altimeter 29.94. Scattered clouds at 2,800 ft, light rain shower one mile to the northeast. Visibility 9 SM. The conditions are classic for carburetor icing in a carbureted engine at reduced power — warm, moist air, and the Lycoming O-320 in the Warrior is susceptible.
You are 350 ft AGL, climbing through 73 KIAS (Vy, best rate of climb), heading 155°, when the engine begins to run rough. Power is noticeably down — the tachometer is unwinding. The off-field environment ahead is dense development: low-density residential, medium-density residential, and scattered commercial. There is no open field, no park, no water. The only safe landing option is to return to KCLW.
Aircraft: Piper PA-28-161 Warrior, solo, full fuel (48 gal usable), within limits. Carbureted Lycoming O-320-D, fixed-pitch prop, steam panel, fuel selector on LEFT (the tank you selected for takeoff). Nothing was written up; the airplane was airworthy at departure.
Pilot: you — a Private pilot, current, roughly 180 hours total. 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 engine sounded fine at full power.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you already know about partial engine power loss in the PA-28-161 Warrior? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN12LA175 (2012): A Piper PA-28-161 on an instrument instructional flight encountered carburetor icing during climb through 6,500 feet. The engine lost power progressively. The probable cause was carburetor icing in conditions conducive to serious icing, with a contributing factor of limited carburetor heat valve travel from recent maintenance. The pilot did not apply carburetor heat early enough to prevent significant ice accumulation.
NTSB LAX03LA238 (2003): A Piper PA-28-161 experienced partial engine power loss during initial climb from Torrance, California, due to carburetor icing. During a go-around attempt, the pilot failed to maintain adequate airspeed, resulting in a stall and collision with power lines and terrain. The probable cause was carburetor icing and the pilot's failure to use carburetor heat. A secondary cause was the pilot's failure to maintain airspeed during the aborted landing, which resulted in a stall/mush.
NTSB CHI05LA226 (2005, FATAL): A Piper PA-28-161 on an instructional flight from Culver, Indiana, lost engine power due to partial left magneto failure during initial climb after takeoff and subsequently stalled. The accident resulted from improper maintenance, with contributing factors including the instructor's failure to maintain airspeed and follow emergency procedures. The pilot did not recognize the partial power loss as a magneto issue and did not maintain best-glide airspeed during the emergency.
NTSB ERA14LA141 (2014): A Piper PA-28-161 experienced partial engine power loss during takeoff from Atlantic City International Airport and the pilot executed a forced landing to the airport perimeter road. The accident resulted from a partial loss of engine power for reasons that could not be determined during postaccident examination or engine test run. The pilot's decision to land immediately, rather than attempt to climb out of the airport environment, was correct.
The local environment at KCLW makes this scenario particularly unforgiving: Runway 16's departure end (heading 155°) is surrounded by dense development — low-density residential, medium-density residential, and scattered commercial. There is no open field, no park, no water. An engine failure on the Runway 16 departure at low altitude is a forced landing in unsuitable terrain, not a field landing. This is not hypothetical; it is the NLCD ground cover off that runway end.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Clearwater Air Park. KCLW has its own accident history (see field dominant patterns: forced landing 22.2%, loss of control 18.5%, gear-up landing 18.5%), but these specific events happened elsewhere. The scenario is localized to KCLW to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: partial engine power loss in the PA-28-161 is insidious. It builds gradually, the first symptom is roughness and a dropping tachometer (not a dramatic power cut), and by the time it is obvious, it may be too late for a comfortable recovery. The fix — full carburetor heat, immediately, at the first sign of roughness in conducive conditions — is simple. The failure is always a delay, or a failure to maintain airspeed during the emergency maneuver.
Key lesson — In warm, moist Florida air, the PA-28-161'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 dense development, the decision window is measured in seconds — not minutes. Off Runway 16 at KCLW, the off-field environment is unsuitable terrain: a delayed response means a forced landing in development, not a field landing. Maintain best-glide airspeed (73 KIAS) during any emergency descent.
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 afternoon conditions at KCLW. You do not need visible ice, freezing temperatures, or IMC. Warm, moist air at reduced power is the classic carb-ice environment. The Lycoming O-320 in the PA-28-161 is carbureted; it has no fuel injection, no 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 PA-28-161, 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 KCLW Runway 16, an engine failure on departure is a forced landing in dense development.
The off-field environment off Runway 16's departure end (heading 155°) is dense development: low-density residential, medium-density residential, and scattered commercial. There is no alternate landing surface. If the engine quits on the Runway 16 departure and altitude is insufficient to return to the airport, the outcome is a forced landing in unsuitable terrain. This is not a worst-case scenario; it is the geographic reality. Best glide is 73 KIAS. 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 16.
Proactive carb heat use in conducive conditions is not optional.
The PA-28-161 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, with OAT near 26°C and dew point near 21°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 350 ft AGL over dense development is waiting too long.
The PA-28-161 has LEFT / RIGHT fuel selector — no BOTH position.
Unlike Cessnas, the Piper Warrior requires active tank management. You must select LEFT or RIGHT; there is no BOTH position. Fuel starvation from not switching tanks is a Piper-class accident. In this scenario, you selected LEFT for takeoff and remained on LEFT throughout. If the engine had quit from fuel starvation (not carb ice), switching to RIGHT would have been the recovery. Always know which tank you are on and plan your tank switches before flight.
Built from the real accident record
Scenario built from NTSB CEN12LA175 (2012 PA-28-161 carburetor ice / power loss during climb), LAX03LA238 (2003 PA-28-161 carb ice / stall on go-around), CHI05LA226 (2005 PA-28-161 magneto failure / stall, fatal), ERA14LA141 (2014 PA-28-161 partial power loss at takeoff), WPR10FA264 (2010 PA-28-161 in-flight fire / forced landing), CHI08LA197 (2008 PA-28-161 power loss / runway overrun), IAD05LA133 (2005 PA-28-161 total power loss / forced landing), and DEN03LA139 (2003 PA-28-161 density altitude / forced landing). Localized to KCLW.
NTSB reports: CEN12LA175 · LAX03LA238 · CHI05LA226 · ERA14LA141 · WPR10FA264 · CHI08LA197 · IAD05LA133 · DEN03LA139
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 Piper Warrior scenarios · More scenarios at KCLW