Power Loss on Initial Climb — Congested Terrain

Engine failure at 300 ft AGL over medium development off Runway 14 at Tampa North Aero Park — no good landing site ahead, decision window is seconds

Diamond DA40 · Tampa North Aero Park Airport (X39) · Private · Takeoff / Initial Climb

The scenario

• {'label': 'Field', 'value': 'X39 · Tampa North Aero Park'}
• {'label': 'Runways', 'value': '14/32'}
• {'label': 'Elevation', 'value': '68 ft'}
• {'label': 'Aircraft', 'value': 'DA40'}
• {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}

The decision

Before we get into the decision tree — what do you already know about engine failure on initial climb in a DA40? (Pick all that apply; this records your baseline.)

What the record shows

What the NTSB files show

Key lesson — At 300 ft AGL over congested terrain with a failing engine, the decision window is measured in seconds. The correct response is to establish 73 KIAS best glide immediately, commit to the least-bad landing site ahead (a street, parking lot, or open area), and execute a controlled forced landing. Attempting to turn back toward the runway or stretch the glide at this altitude and power setting is a high-risk maneuver that often results in a stall/spin or a landing in a populated area. The runway is not a viable option — the least-bad site ahead is.

Debrief — teaching points

Engine failure on initial climb is survivable — but only if you commit to the landing site immediately.

At 300 ft AGL, you have roughly 20–30 seconds of useful decision time. The correct response is to establish 73 KIAS best glide, scan for the least-bad landing site ahead, and commit to it. The runway is behind you; attempting to turn back or stretch the glide at this altitude is a high-risk maneuver that often results in a stall/spin or a landing in a populated area. The NTSB data on initial-climb engine failures shows that pilots who commit early to the available landing site survive; pilots who attempt to 'make it back' do not.

The DA40 fuel selector has LEFT / RIGHT only — there is no BOTH position.

The DA40 requires active fuel management. The pilot must select LEFT or RIGHT and monitor fuel quantity in the selected tank. If the selected tank runs dry, the engine will quit — even if the other tank is full. This is a common cause of power loss on initial climb in the DA40. Always verify fuel selector position and fuel quantity during the preflight and engine-start checklist. On this flight, the fuel selector was set to LEFT and the boost pump was ON — both correct — so fuel starvation was not the cause. But the discipline of checking is non-negotiable.

The fuel boost pump must be ON during takeoff and initial climb.

The DA40's fuel boost pump ensures adequate fuel pressure during takeoff and climb. If the boost pump is OFF, fuel starvation can occur even with fuel in the selected tank. The engine-start checklist explicitly requires boost pump verification. NTSB MIA91LA214 (a Ryan Navion) shows the consequence of skipping this step: engine failure on initial climb due to inadequate fuel pressure. The DA40 is not immune. Verify boost pump status as part of the engine-start checklist, every time.

Best glide speed in the DA40 is 73 KIAS — establish it immediately if engine power is lost.

Best glide speed maximizes glide distance and gives the most time to manage the emergency. In the DA40, that speed is 73 KIAS at gross weight. If engine power is lost at 300 ft AGL, establish 73 KIAS within the first 5 seconds. This speed is your baseline for all subsequent decisions: turning back to the runway, committing to a landing site, or executing a slip to lose altitude. Deviating from best glide (pitching up to 'stretch' the glide, or pitching down to 'get down faster') reduces your options and increases risk.

Off Runway 14 at X39, the climb-out environment is medium-density residential development — there is no open field.

The USGS NLCD ground cover off Runway 14 (heading 141°) is medium-density residential development, low-density development, and wooded wetland. There are no open fields, parks, or clear landing areas. An engine failure on the Runway 14 departure at 300 ft AGL is a forced landing into congested terrain. This is not a worst-case scenario; it is the geographic reality. Know the off-field environment before you depart. If the climb-out environment is congested, consider using Runway 32 (heading 321°) instead, which has a similar environment but puts you over the airport longer before committing to a departure heading.

The constant-speed propeller requires active management — understand prop control.

The DA40's constant-speed prop adjusts blade pitch automatically to maintain the selected RPM. The prop control lever (in the cockpit) sets the target RPM; the prop governor maintains that RPM by adjusting pitch. If engine power is lost, the prop will feather (increase pitch) to reduce drag — but this happens automatically. You do not need to 'do something' with the prop control in an engine-failure scenario. The prop is not the cause of the power loss in this scenario, but understanding how it works prevents you from wasting time on incorrect troubleshooting.

Built from the real accident record

Scenario inspired by NTSB ERA23LA285 (2023 DA40 turbocharger housing fatigue / partial power loss), ERA19LA272 (2019 DA40 induction coupling failure on takeoff at 300 ft), ERA18LA241 (2018 DA40 total power loss on approach), and regional forced-landing precedents ATL90LA140, MIA91LA214, WPR18FA046, LAX88LA050. Real events occurred at other airports and aircraft — NOT at Tampa North Aero Park.

NTSB reports: ERA23LA285 · ERA19LA272 · ERA18LA241 · ATL90LA140 · MIA91LA214 · WPR18FA046 · LAX88LA050

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

All sample scenarios · More Diamond DA40 scenarios · More scenarios at X39