FlightEdge
Sample scenario-based training
SAMPLE SBTLanding / Go-Around

Destabilized on Short Final

A go-around decision at low altitude in a DA40 — energy management, crosswind control, and the cost of delay

Diamond DA40 · Brooksville–Tampa Bay Regional Airport (KBKV) · Commercial · Landing / Go-Around

The scenario

Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, on an instructional flight with a commercial-certificate student. Elevation 76 ft MSL. The runway is 7,001 ft long, plenty of room for a normal landing.

It is a hot, humid Florida afternoon in late July: OAT 34°C, dew point 26°C, altimeter 29.89. Density altitude is approximately 2,800 ft — the airplane will perform as if it is at 2,800 ft elevation, not 76 ft. Scattered clouds at 3,500 ft, visibility 10 SM. Light and variable winds, but a crosswind component of 8–10 knots from the right (Runway 09 heading is 90°; the wind is roughly 120°).

You are on short final to Runway 09, 400 ft AGL, descending at 70 KIAS (Vref, approach speed). The student is flying. The approach has been unstable from 1,000 ft: the descent rate is inconsistent, the airplane is drifting right of centerline, and the student is correcting with left bank and forward pressure. The airplane is floating — it is not descending as expected. At 300 ft AGL, you are still 0.8 nm from the runway threshold. The student is fixated on landing.

Aircraft: Diamond DA40, dual controls, full fuel, within limits. Lycoming IO-360-M1A (fuel-injected), constant-speed prop, fixed gear, G1000 glass panel. Fuel selector is on LEFT tank (the right tank is full and available). Nothing was written up; the airplane is airworthy.

Pilot: You are the CFI. The student is a commercial-certificate applicant with roughly 180 hours total, 40 hours in the DA40. The student has logged 12 hours of dual instruction in crosswind landings but has not yet demonstrated consistent crosswind control. This is a training flight; you are evaluating the student's go-around decision-making and crosswind technique.

The decision

Before we get into the decision tree — what do you know about go-around decision-making in the DA40? (Pick all that apply; this records your baseline.)

What the record shows

What the NTSB files show

NTSB GAA19CA582 (2019): A Diamond DA40 on an instructional flight experienced a loss of control during an aborted go-around when the pilot cut power and applied brakes with insufficient runway remaining. The pilot had delayed the go-around decision, landed long, and then attempted to abort by cutting power and applying full brakes at high ground speed. The airplane veered off the runway and struck a concrete barrier. The probable cause was the pilot's decision to abort a go-around with insufficient runway remaining, which resulted in loss of control and runway excursion.

NTSB GAA19CA409 (2019): A Diamond DA40 on an instructional flight drifted left of the runway during landing in crosswind conditions and struck a runway edge light during a go-around. The pilot receiving instruction failed to maintain runway heading and bank control in crosswind conditions. The probable cause was the pilot's failure to maintain runway heading and bank control during landing in crosswind conditions, which resulted in a go-around and subsequent collision with a runway light.

NTSB GAA19CA431 (2019): A Diamond DA40 stalled during a go-around attempt on a short grass runway in high-density altitude conditions after the pilot delayed the go-around decision and the aircraft floated. The pilot exceeded the airplane's critical angle of attack in high-temperature, high-density altitude conditions. The probable cause was the pilot's delayed decision to go around in high-temperature and high-density altitude conditions and his exceedance of the airplane's critical angle of attack, which resulted in an aerodynamic stall.

The consistent thread across all three accidents: the go-around decision was delayed. In GAA19CA582, the pilot landed long and then tried to abort — too late. In GAA19CA409, the pilot was drifting off the runway and struck an edge light — the go-around was forced, not chosen. In GAA19CA431, the pilot floated in high-density altitude and stalled trying to land — the go-around was delayed until the airplane was in a critical configuration.

At KBKV, the off-field environment off Runway 09 (heading 90°) is mostly open developed land (parks, large lots), pasture, and medium development — not as unforgiving as water, but still a forced landing if the engine fails. The runway is 7,001 ft long — plenty of room for a normal landing, but not for a long landing followed by an abort. The density altitude on a hot July afternoon is 2,800 ft; the airplane performs as if it is at 2,800 ft elevation. The DA40 floats in high-density altitude. A stabilized approach is not optional — it is the only way to land safely in these conditions.

The real accidents cited above occurred at other airports and in other aircraft — NOT at KBKV. The scenario is localized to KBKV to make the off-field environment and the density altitude real and consequential for you as a student here. The lesson is universal: a go-around is not a failure — it is the correct decision when the approach is unstable. The cost of waiting is damage to the airplane, injury to the occupants, and a failed training flight.

Key lesson — In high-density altitude conditions, the DA40 floats and is slippery. An unstable approach — drifting off centerline, inconsistent descent rate, floating — is a go-around trigger, not a 'fix it on short final' problem. Call the go-around at 400 ft AGL or higher, when you have altitude and options. Waiting until 150 ft AGL forces you into a choice between a dangerous landing and a dangerous abort. A go-around is not a failure — it is airmanship.

Debrief — teaching points

Density altitude reduces runway performance and climb performance.

At KBKV on a hot July afternoon, the density altitude is approximately 2,800 ft. The airplane performs as if it is at 2,800 ft elevation, not 76 ft. The landing distance increases, the climb performance decreases, and the airplane floats more in high-density altitude. A stabilized approach is not optional — it is the only way to land safely. An unstable approach in high-density altitude is a go-around trigger.

An unstable approach is a go-around trigger, not a 'fix it on short final' problem.

If the approach is unstable at 1,000 ft AGL (drifting off centerline, inconsistent descent rate, floating), call the go-around. Do not wait until 500 ft AGL, 300 ft AGL, or 150 ft AGL. The earlier you call the go-around, the more altitude and options you have. Waiting until 150 ft AGL forces you into a choice between a dangerous landing and a dangerous abort. A go-around is not a failure — it is the correct decision.

Crosswind control in the DA40 requires smooth, shallow bank corrections.

The DA40 is a slippery airplane. In crosswind conditions, use shallow bank angles (5–10°) and smooth, coordinated corrections. Avoid steep banks and aggressive rudder inputs at low altitude. If the approach is unstable in crosswind conditions, change the runway (request the reciprocal with a headwind component) or call the go-around. Do not try to force a crosswind landing in high-density altitude.

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

The DA40 has no BOTH position on the fuel selector. You must manage LEFT and RIGHT tanks actively. On a go-around, ensure the fuel selector is on the tank with fuel (in this scenario, the right tank is full and available). A mis-set fuel selector on go-around, when power is critical, is a starvation risk. Brief the student on fuel management before the flight.

Full power on go-around means full throttle AND full RPM (prop control forward).

The DA40 has a constant-speed prop. On a go-around, advance the throttle to full power AND push the prop control forward to full RPM. The prop control is not optional — it is part of the go-around procedure. Failure to advance the prop control will result in insufficient power and a sluggish climb.

Aborting a go-around (cutting power and applying brakes) is a last-resort emergency maneuver.

NTSB GAA19CA582 documents a pilot who aborted a go-around by cutting power and applying full brakes with insufficient runway remaining. The airplane veered off the runway and struck a concrete barrier. Aborting a go-around is not a normal procedure — it is a last-resort emergency maneuver used only when the go-around is not possible and a landing is the only option. If you are committed to a go-around, commit fully. Do not land long and then try to abort.

Built from the real accident record

Scenario built from NTSB GAA19CA582 (2019 DA40 go-around abort with insufficient runway), GAA19CA409 (2019 DA40 crosswind loss of control during go-around), and GAA19CA431 (2019 DA40 stall during delayed go-around in high-density altitude). Localized to KBKV.

NTSB reports: GAA19CA582 · GAA19CA409 · GAA19CA431

ACS tasks: PA.II.F — Approach and Landing · PA.II.G — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.E — Descent Planning · PA.III.A — Preflight Preparation

Relevant FARs: §91.3 · §91.13 · §91.103

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 Diamond DA40 scenarios · More scenarios at KBKV