FlightEdge
Sample scenario-based training
SAMPLE SBTTakeoff / Initial Climb

Engine Failure on Initial Climb — Runway 05

Total power loss at 400 ft AGL over congested development. No good forced-landing site ahead. Decision time is measured in seconds.

Piper Arrow · Tampa Executive Airport (KVDF) · Commercial · Takeoff / Initial Climb

The scenario

Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 05, initial climb on a 042° heading. Elevation 22 ft MSL. Non-towered field; you are on CTAF 122.8.

It is a clear, VFR morning: OAT 22°C, light winds from 080° at 4 kt, altimeter 29.98. Visibility 10 SM. A routine local flight — you are familiar with KVDF and have 800 hours total time in the Piper Arrow. The airplane was released from maintenance yesterday after an avionics upgrade (a new glass panel and associated vacuum pump work). You performed a standard preflight this morning; nothing was written up. The engine ran smoothly on the ground.

You are 400 ft AGL, climbing through 85 KIAS (Vy), heading 042°, when the engine suddenly loses all power. The propeller is still turning (windmilling), but there is no thrust. The tachometer has dropped to zero. You have no restart options at this altitude. Off the Runway 05 departure end (heading 042°), the terrain is medium-density development — houses, small commercial buildings, trees. There is no open field, no park, no road wide enough for a safe landing. The nearest open water is 1.5 nm to the east (Tampa Bay). The nearest airport is KVDF behind you, but you are already past the runway.

Aircraft: Piper PA-28R-201, solo, full fuel (48 gal usable), within limits. Lycoming IO-360 fuel-injected engine, constant-speed prop, retractable gear. The engine was running normally on the ground. No mechanical issues were apparent during preflight.

Pilot: you — a Commercial pilot, current, 800 hours total time. You have 120 hours in the Arrow. You are familiar with KVDF. You did not notice any engine anomalies during the preflight or ground run. The maintenance work was routine avionics; you did not inspect the engine bay in detail after the work was completed.

The decision

Before we get into the decision tree — what do you already know about engine-out procedures in the PA-28R? (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 probable cause was a missing vacuum pump drive pad gasket that was not installed during recent avionics maintenance. The missing gasket caused oil exhaustion and catastrophic engine failure. The mechanic's failure to follow the maintenance manual and the Director of Maintenance's failure to verify the installation before returning the airplane to service were the direct causes. The pilot had no opportunity to recover.

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 that was improperly installed with a rigid line instead of flexible hose. The pilot did not perform an adequate preflight inspection to detect the improper installation. The maintenance personnel's failure to follow the avionics installation guidance and the pilot's failure to perform a detailed post-maintenance preflight inspection were contributing factors.

NTSB CHI92DER01 (1992): A Quickie aircraft lost engine power during initial climb and made a forced landing in a residential area after descending through trees and a house. The accident was attributed to carburetor ice, but the lack of suitable terrain for a forced landing was a critical contributing factor. The pilot did not commit to a landing site early and attempted to stretch the glide over congested development.

NTSB ERA13FA325 (2013): A Beech 23 lost total engine power at 250 feet AGL shortly after takeoff and struck a tree and houses during a forced landing. The accident was attributed to the pilot's inadequate preflight preparation and decision to operate an unairworthy aircraft with a compromised fuel system. The pilot did not recognize the marginal aircraft condition and did not commit to a landing site early.

The consistent thread across all these accidents: post-maintenance engine failures in complex aircraft (PA-28R, PA-28RT) are often caused by improper reinstallation of components — vacuum pump gaskets, oil sensor lines, ignition harnesses. A detailed post-maintenance inspection is critical. Additionally, when engine power is lost over congested development at low altitude, the pilot who commits to the best available landing site early (a parking lot, a road, open water) survives. The pilot who attempts to stretch the glide to a better site or turn back to the airport often does not.

At KVDF, the off-field environment off Runway 05 (heading 042°) is medium-density development — houses, trees, small commercial buildings. There is no open field, no park, no road wide enough for a safe landing. An engine failure on the Runway 05 departure at low altitude leaves you with three options: (1) turn back to the runway (marginal at 400 ft AGL), (2) land in a parking lot or on a road if one is available, or (3) ditch in Tampa Bay if you can reach it. The real accidents cited above occurred at other airports — NOT at KVDF. But the off-field environment at KVDF makes this scenario particularly unforgiving for a Runway 05 departure.

The lesson: (1) Post-maintenance engine failures are real — perform a detailed preflight after any maintenance, especially avionics work that involves vacuum pump or engine bay access. (2) When power is lost at low altitude over congested development, commit to the best available landing site immediately — do not attempt to stretch the glide or turn back to the runway. (3) Best glide speed (79 KIAS in the PA-28R) must be established immediately — it maximizes glide distance and gives you the most options.

Key lesson — In the PA-28R, post-maintenance engine failures are often caused by improper reinstallation of components. A detailed post-maintenance preflight is critical. When engine power is lost at low altitude over congested development, commit to the best available landing site (a parking lot, a road, open water) immediately. Do not attempt to stretch the glide or turn back to the runway — the margin is too thin. Best glide speed (79 KIAS) must be established immediately.

Debrief — teaching points

Post-maintenance engine failures in the PA-28R are often caused by improper component reinstallation.

NTSB CEN22FA419 and ERA22FA261 both involved PA-28R engine failures caused by improper reinstallation of components during maintenance — a missing vacuum pump gasket and an improperly installed oil sensor line. These failures occurred shortly after takeoff, during initial climb, when the pilot had minimal options. A detailed post-maintenance preflight inspection is not optional — it is critical. After any maintenance involving the engine bay, vacuum system, or ignition system, inspect those areas carefully. Look for loose fasteners, missing gaskets, improperly routed hoses, and any signs of improper installation. Do not rely on the mechanic's inspection alone.

Best glide speed (79 KIAS) must be established immediately when power is lost.

The PA-28R's best glide speed is 79 KIAS. This speed maximizes glide distance and gives you the most time and distance to find a landing site. At 400 ft AGL with a dead engine, every second and every foot of altitude matters. Establish 79 KIAS immediately — do not waste time trying to restart the engine, cycling the prop, or checking the fuel selector. Get the airplane into the best glide configuration first, then troubleshoot if altitude permits.

When power is lost over congested development, commit to the best available landing site immediately.

The off-field environment off Runway 05 at KVDF is medium-density development — houses, trees, small commercial buildings. There is no open field, no park, no road wide enough for a safe landing. When power is lost in this environment at low altitude, you have limited options: (1) turn back to the runway (marginal at 400 ft AGL), (2) land in a parking lot or on a road if one is available, or (3) ditch in open water if you can reach it. The key is to commit to one option early and execute it correctly. Do not attempt to stretch the glide to a better site — that is how pilots stall and spin into houses. The NTSB precedents (CHI92DER01, ERA13FA325) show that pilots who commit to the best available option early survive; pilots who attempt to stretch the glide do not.

Landing gear should be lowered only when the landing site is assured.

In the PA-28R, lowering the landing gear increases drag and reduces glide distance. In an engine-out emergency, keep the gear up until you are committed to a landing site and confident you can reach it. Once you have identified a parking lot, a road, or open water and are on final approach, then lower the gear. Lowering the gear too early wastes altitude and glide distance.

A controlled ditching in open water is survivable — and better than a crash in houses.

If you cannot reach a clear field, a parking lot, or a road, and you have enough glide distance to reach open water, a controlled ditching is a viable option. Execute the ditching checklist: fuel selector on BOTH, mixture rich, master switch off just before water contact, doors unlatched, flaps for slowest possible touchdown speed. Survival rates in controlled ditchings are significantly better than in uncontrolled crashes in houses and trees. At KVDF, Tampa Bay is 1.5 nm to the east of the Runway 05 departure end — it is reachable if you turn right and commit to the water early.

Built from the real accident record

Scenario built from NTSB CEN22FA419 (2022 PA-28R-201 post-maintenance engine failure / oil starvation), ERA22FA261 (2022 PA-28RT oil sensor line fatigue / inadequate preflight), ERA13LA111 (2013 PA-28R fuel exhaustion / missed approaches), WPR12FA058 (2011 PA-28R-200 unexplained power loss), and local-environment precedents CHI92DER01, ERA13FA325, CHI92DEM03, MIA91LA128 (forced landings in congested development). Anonymized and localized to KVDF.

NTSB reports: CEN22FA419 · ERA22FA261 · ERA13LA111 · WPR12FA058 · CHI92DER01 · ERA13FA325 · CHI92DEM03 · MIA91LA128

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.B — Engine Starting

Relevant FARs: §91.3 · §91.13 · §91.185 · §43.5

Run this scenario yourself

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 KVDF