Uncoordinated Turn at 400 Feet
A low-altitude slip in the DA20's light, responsive airframe — stall/spin recovery window is measured in seconds
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 04, climbing out on a 037° heading. Elevation 8 ft MSL. The runway is short (3,583 ft) and sits in the heart of Tampa's dense development. Off the Runway 04 departure end (heading 037°), the off-field environment is poor: dense development, medium development, low-density development — no open fields, no water, no roads. It is a built-up area. Off the Runway 22 departure end (heading 217°), by contrast, is open water — Tampa Bay and the Hillsborough River.
It is a clear, VFR afternoon: OAT 26°C, winds 080° at 8 knots gusting to 14 knots. Runway 04 is the active runway; the crosswind is 6–8 knots from the right. Visibility 10 SM, scattered clouds at 3,500 ft. A typical Tampa summer day — warm, light winds, but with enough gust that the DA20's light airframe and responsive controls demand attention.
You are 400 ft AGL, climbing through 73 KIAS (Vy, best rate of climb), heading 037°, when you decide to make a shallow left turn toward your first waypoint. The DA20 is a light, slippery airplane — it floats in ground effect, responds quickly to control inputs, and has a bubble canopy that gives excellent visibility. You are heads-down on the GPS for a moment, then look up to turn.
Aircraft: Diamond DA20-C1, solo, full fuel (18 gal usable), within limits. Fuel-injected Continental IO-240-B, fixed-pitch prop, fixed gear, steam panel (attitude indicator, turn coordinator, airspeed, altimeter). Nothing was written up; the airplane is airworthy at departure.
Pilot: you — a Private pilot, current, roughly 180 hours total. You have about 25 hours in the DA20. You are familiar with the airplane's light, responsive controls, but you have not practiced slow-flight or stall recovery in the DA20 in the past six months. Your last stall practice was in a Cessna 172. You did not brief the departure turn or review the DA20's stall characteristics before takeoff.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'DA20'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you already know about stall/spin risk in the DA20 at low altitude? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR09FA062 (2008, FATAL): A Diamond DA 20-C1 on a solo instructional flight near Alamo Lake State Park, Arizona, experienced loss of control and descended into terrain. The pilot was performing a maneuver (the exact maneuver is not fully documented, but the context suggests a turn at low altitude). The probable cause was the pilot's failure to maintain control during the maneuver and his failure to recover from the subsequent aerodynamic stall and spin. The pilot did not recover; the airplane impacted terrain.
NTSB GAA19CA527 (2019): A Diamond DA20 flown by a student pilot with a flight instructor on board experienced an aerodynamic stall during a soft-field takeoff. The student released back pressure and the instructor's corrective action was delayed. The probable cause was the student pilot's improper pitch attitude during the takeoff climb and the flight instructor's delayed remedial action, which resulted in an aerodynamic stall and ground impact. The airplane was damaged; both occupants survived.
The common thread: the DA20 is a light, responsive airplane. Control inputs are quick and sensitive. The stall speed in a turn is significantly higher than in straight flight. At low altitude (below 500 ft AGL), the recovery altitude for a stall or spin is marginal or non-existent. A loss of control in a turn — whether from an uncoordinated input, a steep bank, or a delayed recovery — can result in a stall/spin from which there is no recovery.
Peter O Knight Airport (KTPF) is in the heart of Tampa's dense development. Off Runway 04's departure end (heading 037°), the off-field environment is dense development, medium development, low-density development — no open fields, no water, no roads. A stall/spin at 400 ft AGL on the Runway 04 departure is a forced landing in a built-up area, with all the hazards that implies. Off Runway 22's departure end (heading 217°), by contrast, is open water — Tampa Bay and the Hillsborough River. A stall/spin on the Runway 22 departure would be a ditching.
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 (see field dominant patterns: FORCED_LANDING 19.4%, LOSS_OF_CONTROL_INFLIGHT 16.7%, LOSS_OF_CONTROL_GROUND 11.1%, DITCHING 11.1%, STALL_SPIN 8.3%), but these specific NTSB 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: the DA20's light, responsive airframe and quick control response can mask a loss of control until it is too late. An uncoordinated turn, a steep bank, or a delayed stall recovery at low altitude is a stall/spin from which there is no recovery. The decision window is measured in seconds — not minutes.
Key lesson — In the DA20 at low altitude, a shallow, coordinated turn at Vy (75 KIAS) is safe. An uncoordinated turn, a steep bank, or a failure to recognize an approaching stall is a stall/spin from which there is no recovery below 500 ft AGL. Brief every turn before takeoff. Maintain coordinated flight. Monitor the airspeed indicator and turn coordinator continuously. At 400 ft AGL on the Runway 04 departure at KTPF, the off-field environment is dense development — a forced landing there is survivable only if you find a clear area. Off Runway 22, it is open water — a ditching.
Debrief — teaching points
The DA20 is light and responsive — control inputs are quick and sensitive.
The Diamond DA20 is a composite two-seat trainer with a light airframe and responsive controls. A small aileron input produces a quick bank. A small pitch input produces a quick pitch change. This responsiveness is an asset in normal flight, but it can mask a loss of control at low altitude. An uncoordinated turn or a steep bank can develop into a stall/spin before the pilot realizes what is happening. Respect the DA20's responsiveness; do not treat it like a heavier trainer.
The stall speed in a turn is significantly higher than in straight flight.
The DA20's Vs0 (stall speed, landing flap) is 36 KIAS in straight flight. But in a 15° bank, the stall speed is roughly 37 KIAS; in a 30° bank, it is roughly 42 KIAS. At Vy (75 KIAS), you are close to the stall speed in a turn — a loss of airspeed or a steep bank can stall a wing. At 400 ft AGL, you do not have the altitude to recover from a stall/spin. Brief every turn before takeoff. Maintain a shallow bank (15° or less). Monitor the airspeed indicator continuously.
An uncoordinated turn (rudder not synchronized with aileron) can induce a stall in one wing.
When you roll into a turn with aileron but do not coordinate with rudder, the airplane slips — the nose yaws opposite to the bank. The slip increases drag and causes the airspeed to decay. In a slip at low altitude, the airspeed can decay to the stall speed in a turn before the pilot realizes what is happening. The result is a stall in one wing (typically the outside wing in a slip), which can lead to a spin. Coordinate every turn: aileron and rudder together, smooth and synchronized.
Spin recovery requires immediate opposite rudder, forward stick, and level wings.
The spin recovery procedure for the DA20 is: (1) opposite rudder (full rudder opposite to the direction of spin rotation), (2) forward stick (reduce back pressure to break the stall), and (3) level wings (use aileron to level the wings after the spin rotation stops). At 400 ft AGL, there is no altitude for a developed spin. Recovery must be immediate — within the first 1–2 turns of the spin. If the spin develops beyond 1–2 turns, recovery altitude is insufficient. Prevention (coordinated flight, shallow bank, maintain airspeed) is the only option.
At KTPF Runway 04, the off-field environment is dense development — no open fields or water.
The off-field environment off Runway 04's departure end (heading 037°) is dense development, medium development, low-density development — buildings, roads, obstacles. A stall/spin at 400 ft AGL on the Runway 04 departure is a forced landing in a built-up area. The DA20's light weight and low landing speed (Vref 55 KIAS, Vs0 36 KIAS) give you the best chance of a survivable landing, but the margin is thin. A forced landing in dense development is survivable only if you find a clear area (a park, a parking lot, a street). Off Runway 22's departure end (heading 217°), by contrast, is open water — a ditching.
Brief every turn before takeoff — do not turn heads-down on the GPS.
A heads-down turn on the GPS at 400 ft AGL is a loss of situational awareness. You are not monitoring the airspeed indicator, the turn coordinator, or the attitude indicator. You are flying by feel, not by instruments. In the DA20's responsive airframe, a turn by feel can quickly become an uncoordinated turn or a steep bank. Brief your first turn before takeoff: heading, bank angle, airspeed, instruments to monitor. After takeoff, establish a scan: airspeed, attitude, turn coordinator, altitude. Do not go heads-down until you are above 1,000 ft AGL and in stable, coordinated flight.
Built from the real accident record
Scenario built from NTSB WPR09FA062 (2008 DA20-C1 loss of control / stall-spin near Alamo Lake, AZ) and GAA19CA527 (2019 DA20 stall during soft-field takeoff, student/instructor). Anonymized and localized to KTPF.
NTSB reports: WPR09FA062 · GAA19CA527
ACS tasks: PA.II.A — Preflight Inspection · PA.II.C — Takeoff and Climb · PA.II.D — Attitude Instrument Flying · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
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 Diamond DA20-C1 scenarios · More scenarios at KTPF