Touch and Go Landings What Student Pilots Get Wrong

Touch and Go Landings — What Student Pilots Get Wrong

Touch and go landings have gotten complicated with all the conflicting advice flying around. As someone who logged over 60 hours of pattern work at three different training airports, I learned everything there is to know about what goes wrong — and why it keeps going wrong. Today, I will share it all with you.

But what is a touch and go, really? In essence, it’s a landing where you don’t stop — you reconfigure and depart again from the runway. But it’s much more than that. It’s a compressed sequence of high-workload tasks crammed into a moving aircraft, and the margin for procedural sloppiness is smaller than most students realize. Your CFI isn’t repeating the same correction because you’re hopeless. The sequence itself creates decision points that feel natural but are procedurally backwards. That’s what makes touch and goes so humbling to us student pilots.

So, without further ado, let’s dive in.

Flap Reconfiguration at the Wrong Moment

Probably should have opened with this section, honestly. This mistake haunted my first 20 hours of pattern work — and I didn’t even realize I was making it.

Here’s what it looks like from inside the cockpit. The mains kiss the pavement. Your brain immediately registers “landing complete” and fires the next command: reconfigure flaps. In a Cessna 172, that means pulling from 40 degrees back down to 5 degrees for takeoff. Sounds simple. Except your feet are still making rudder corrections, the nose wheel hasn’t settled, and you’re maybe 800 feet into your rollout. You reach for the flap handle anyway.

I’m apparently a chronic multitasker and this habit works against me in the cockpit while single-task sequencing never feels fast enough. Don’t make my mistake.

Moving the flaps mid-rollout — say, stopping at 20 degrees instead of reaching 5 — suddenly reduces drag and shifts pitch attitude at the exact moment you need to be tracking straight and building speed. The aircraft balloons slightly. You overcorrect. Your CFI grabs the yoke. You hear about it. You land again. You do the same thing.

The fix is a verbal callout sequence. “Stabilized. Centerline. Flaps to takeoff.” Call it out loud every single time — at least if you want the habit to actually stick under pressure. This isn’t a cute mnemonic. It’s a procedural lock. Those five extra seconds of discipline buy you a clean departure instead of a developing control problem.

Power Application Timing on Departure

Rushed by false confidence, student pilots advance the throttle before the airplane is actually ready for it. This one nearly bit me at a 2,500-foot strip outside Redding — a narrow runway with a slight crosswind and zero room for error.

My instructor grabbed the yoke on my fourth consecutive attempt. “You’re pushing the throttle while you’re still fighting for the centerline,” he said. “You’ve got maybe 15 degrees of wind correction in, and now you’re fighting two problems instead of one.” That was the last time I rushed the power application.

In a standard Cessna 172S, adding full power while the nose wheel is still settling and your flaps aren’t fully configured creates a yaw right that compounds any existing alignment problem. On a wide runway with no crosswind, you might recover cleanly. On a 40-foot-wide strip with 10 knots off the left, you won’t.

The correct sequence is blunt: confirm configuration complete, confirm alignment, confirm you have directional control — then advance throttle smoothly to full. The half-second delay feels agonizing. It is not wasted time. It’s the difference between a clean departure and a runway excursion that ends your flying for a while.

In taildraggers or anything with a constant-speed prop, this timing is even more critical. More power means more pronounced pitch and yaw effects. The discipline required at 160 horsepower scales poorly to 300.

Runway Remaining Awareness Gets Ignored

Frustrated by the mental workload of pattern work, most students fall into a rhythm — land, take off, bank for downwind, base, final, repeat. It becomes meditative. That’s the problem.

The runway remaining isn’t constant. Where you touch down changes everything. Land 300 feet farther down the pavement than normal because you floated slightly, and your available departure distance just shrank — quietly, without any warning light or callout. A crosswind that forced a longer flare, a slightly high approach that added float, a gust that dropped you flat instead of letting you round out — any of these push your touchdown point forward.

At a 3,800-foot runway, this feels academic. At a 2,600-foot runway in summer density altitude — say, 4,500 feet MSL, temperature 95°F, full fuel — it absolutely is not.

Make a habit of noting your touchdown point every single landing. It should take two seconds. Then ask yourself one yes-or-no question: Do I have enough runway to safely configure, accelerate, and climb out clean? If the answer isn’t an immediate yes, full stop. No second-guessing, no optimistic math.

The Stabilized Approach That Falls Apart at the Threshold

You’ve flown a solid approach all the way down final. Descent rate locked in. Speed stable at 65 knots. Power set. Then something shifts inside the last 50 feet — you flare a beat too early, or too aggressively, and suddenly you’re floating four feet above the numbers burning through runway you didn’t plan to use.

These aren’t isolated errors. They have downstream consequences. A fast landing means a longer rollout and a rushed reconfiguration. A late touchdown means less runway remaining and tighter math on the departure. A hard landing — the kind where you bounced and called it fine — means you’re now transitioning into a takeoff reconfiguration while your brain is still processing what just happened to your spine.

That’s what makes the stabilized approach so fundamental to us student pilots doing pattern work. It’s not just about safety on a full stop. It’s about arriving at the flare in a position where the touch and go can be a clean procedure — not damage control for a chaotic final.

Fix the approach first. The touch and go problems downstream often solve themselves.

When Your CFI Says Do a Full Stop Instead

Listen. Just listen.

Your CFI is not ending the session because you’re failing. They’re offering a reset before a building error chain becomes a bent airplane. High workload, configuration confusion, a crosswind that’s eating your attention, or honestly just fatigue after an hour in the pattern — these are all legitimate reasons to roll out, exit at Charlie, and sit quietly for two minutes.

Full stops during touch and go training feel like admissions of defeat. They’re not. They’re judgment calls — at least if you’re the kind of pilot who wants a long career. The best pilots I’ve flown with know exactly when to stop and recalibrate instead of grinding through a mistake sequence that keeps compounding.

Take the full stop. Breathe. Start fresh. The pattern will still be there.