Engine Failure on Climb — Open Water Ahead
Total power loss at 400 ft AGL off Runway 22 at Peter O Knight Airport — the decision window is measured in seconds
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22, climbing out on a 217° heading over open water. Field elevation 8 ft MSL. KTPF is non-towered (CTAF); you are in Class G airspace below 1,200 ft MSL, overlying Tampa Class B above that. The field's dominant accident pattern includes forced landings (19.4%) and ditchings (11.1%) — this is a water-surrounded airport.
It is a clear, calm morning in late spring: OAT 24°C, light winds from the east. Visibility 10 SM. You are climbing through 400 ft AGL at 90 KIAS (Vy, best rate of climb, gear up, prop in cruise), heading 217°. Runway 22's climb-out environment is open water — Tampa Bay and the Gulf of Mexico approach. There is no alternate landing surface ahead.
The engine is running smoothly. You are on schedule. Then, without warning, the engine loses all power. The propeller is still turning (windmilling), but there is no thrust. You are at 400 ft AGL, climbing at 90 KIAS, with open water ahead and the airport 0.8 nm behind you.
Aircraft: Piper PA-28R-201 Arrow, solo, full fuel (48 gal usable), within limits. Lycoming IO-360, fuel-injected, constant-speed prop, retractable gear. The airplane came out of a 100-hour inspection three weeks ago; a new avionics system was installed during that inspection. The preflight was normal; all engine instruments were green.
Pilot: you — a Commercial pilot, current, roughly 800 hours total, 200 hours in type. You are familiar with the Arrow's systems. You have practiced engine-out procedures, but never in a real emergency at 400 ft AGL over water.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you already know about engine failure in the Piper Arrow at low altitude? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN22FA419 (2022, FATAL): A Piper PA-28R-201 on a personal flight from Myrtle Beach, South Carolina experienced total engine failure during initial climb after departure. The accident resulted from a missing vacuum pump drive pad gasket installed during avionics maintenance. The mechanic failed to install the required gasket in accordance with the maintenance manual, which caused oil exhaustion and catastrophic engine failure. The Director of Maintenance failed to verify the installation before returning the airplane to service. The pilot did not perform an adequate preflight inspection that would have caught the low oil pressure.
NTSB ERA22FA261 (2022, FATAL): A Piper PA-28RT-201 on a personal flight lost engine power due to oil starvation caused by high-cycle fatigue failure of an oil pressure sensor line. The line was improperly installed with rigid tubing instead of flexible hose during avionics work. The pilot did not perform an adequate preflight inspection. Maintenance personnel failed to follow the avionics installation guidance. The result was total loss of engine power at low altitude.
NTSB ERA13LA111 (2013, FATAL): A Piper PA-28R on an IFR flight lost engine power due to fuel exhaustion after the pilot attempted multiple missed approaches at three different airports. The pilot failed to land at airports equipped with adequate instrument approaches while operating in low IMC and delayed declaring a fuel-related emergency. This is a different failure mode (fuel management, not mechanical), but it illustrates the PA-28R's vulnerability to total power loss at low altitude.
NTSB WPR12FA058 (2011, FATAL): A Piper PA-28R-200 on a personal flight experienced total loss of engine power during cruise. The pilot attempted a forced landing near Coupeville, Washington, but impacted terrain below a ridge line. Post-accident examination revealed no mechanical malfunctions that would have precluded normal operation. The cause was undetermined — but the outcome was fatal because the pilot did not execute a controlled landing procedure.
Regional water-landing precedents: NTSB ATL97LA099 (1997, Cessna P210N), NYC03LA109 (2003, Cessna 175A), BFO91LA069 (1991, Cessna 177RG), and ANC13LA048 (2013, Piper PA-16) all document engine failures at low altitude over water. In the cases where pilots executed controlled ditching procedures (ATL97LA099, BFO91LA069, ANC13LA048), survival rates were high. In cases where pilots attempted marginal glide-backs or uncontrolled landings, outcomes were worse.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Peter O Knight Airport. KTPF has its own accident history (dominant patterns: forced landings 19.4%, ditchings 11.1%), but these specific fatal events happened elsewhere. The scenario is localized to KTPF to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: total engine failure in the PA-28R at low altitude is survivable if the pilot (1) recognizes the failure immediately, (2) establishes best glide speed (79 KIAS) without delay, (3) evaluates the return-to-airport option realistically, and (4) commits decisively to either a return-to-land or a controlled ditching. The fatal accidents occur when pilots delay the decision, attempt marginal glide-backs, or fail to execute the ditching checklist properly. The decision window at 400 ft AGL is measured in seconds — not minutes.
Key lesson — In the PA-28R, total engine failure at low altitude over water is survivable if you recognize the failure immediately, establish 79 KIAS best glide, evaluate the return-to-airport option realistically (400 ft AGL, 0.8 nm to the airport = tight but possible), and commit decisively to either a return-to-land or a controlled ditching. Off Runway 22 at KTPF, the off-field environment is open water — a delayed response or a marginal glide-back attempt means a ditching. The post-maintenance engine failures documented in CEN22FA419 and ERA22FA261 underscore the importance of an adequate preflight inspection, especially after recent maintenance work. Check the oil pressure gauge and the engine instruments carefully before every flight.
Debrief — teaching points
Total engine failure in the PA-28R at low altitude is survivable if you act immediately.
The decision window at 400 ft AGL is measured in seconds — roughly 30–40 seconds of useful decision time before altitude becomes critical. The first action is to lower the nose to 79 KIAS best glide without delay. This establishes the maximum glide distance and gives you the best chance to evaluate your options. Hesitation, troubleshooting attempts, or climbing-speed turns all cost altitude and time. Establish best glide first; diagnose second.
At 400 ft AGL with a dead engine, the return-to-airport option is marginal but possible.
The PA-28R at 79 KIAS best glide loses roughly 500 ft per minute. At 400 ft AGL, you have roughly 48 seconds of glide time. The glide distance is roughly 2,000–2,200 ft (79 KIAS × 48 seconds ÷ 3,600 + some margin for turn). KTPF is 0.8 nm (4,200 ft) away. The math is tight — you will arrive at the airport at roughly 200 ft AGL — but it is doable. A direct descent to Runway 04 (heading 037°, reciprocal of your departure) is the fastest path. Do not attempt a full pattern; fly a straight-in descent.
If the return-to-airport option fails, commit to a controlled ditching early.
If you are below 300 ft AGL and more than 0.5 nm from the airport, the return is no longer reliable. Commit to a controlled ditching in open water. The ditching checklist is: (1) Fuel selector OFF — fire prevention. (2) Mixture to idle cutoff — engine stops cleanly. (3) Master switch off just before water contact — electrical safety. (4) Doors unlatched — escape route. (5) Flaps as needed for slowest possible touchdown speed — impact energy rises with the square of speed. A controlled ditching with proper checklist execution has significantly higher survival rates than an uncontrolled impact or a stall/spin trying to stretch the glide.
Post-maintenance engine failures in the PA-28R are a known risk.
NTSB CEN22FA419 and ERA22FA261 both document total engine failures in the PA-28R immediately after avionics maintenance. The failures were caused by improper installation of a vacuum pump gasket (CEN22FA419) and an oil pressure sensor line (ERA22FA261). Both were maintenance errors that should have been caught by an adequate preflight inspection. Before every flight, especially after recent maintenance, check the oil pressure gauge, the engine temperature, and the fuel pressure. Scan the engine instruments carefully during the run-up and the initial climb. An anomaly at 400 ft AGL is too late to catch a maintenance error.
Off Runway 22 at KTPF, the off-field environment is open water — there is no alternate landing surface.
KTPF's dominant accident pattern includes forced landings (19.4%) and ditchings (11.1%). The field is surrounded by water. Off Runway 22's climb-out (heading 217°), the environment is open water — Tampa Bay and the Gulf of Mexico. Off Runway 04's climb-out (heading 037°), the environment is dense development. Off Runway 18 and 36, the environment is also open water. If the engine fails on any departure from KTPF, the off-field options are limited. A controlled ditching in open water is often the only survivable outcome. Know this before you depart.
Built from the real accident record
Scenario built from NTSB CEN22FA419 (2022 PA-28R-201 engine failure post-maintenance), ERA22FA261 (2022 PA-28RT oil starvation from improper maintenance), ERA13LA111 (2013 PA-28R fuel exhaustion / missed approaches), WPR12FA058 (2011 PA-28R undetermined engine loss), and regional water-landing precedents ATL97LA099 (1997 P210N ditching), NYC03LA109 (2003 C175A ditching), BFO91LA069 (1991 C177RG ditching), ANC13LA048 (2013 PA-16 ditching). Real events occurred at other airports — NOT at KTPF.
NTSB reports: CEN22FA419 · ERA22FA261 · ERA13LA111 · WPR12FA058 · ATL97LA099 · NYC03LA109 · BFO91LA069 · ANC13LA048
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.V.A — Preflight Inspection · PA.V.C — Engine Starting · PA.VIII.A — Slow Flight
Relevant FARs: §91.3 · §91.13 · §91.185 · §91.207
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 Arrow scenarios · More scenarios at KTPF