I’ve had good results with new hires by making the 1,000 ft AGL stabilized gate non-negotiable: landing config set, speed within +10/-5 of Vref, and a go-around if not there. For those mentoring students or low-time pilots, how are you building this habit without sacrificing turn times?
I bake it in with a 1,500 AGL “gear down, landing flaps, before-landing checklist complete” gate, then a hard “stable or go” at 1,000 using your Vref +10/−5 — , nothing kills turn times like dragging an unstable to short final. We’ve timed it: those two calls add about 5–8 seconds, but an early GA at 1,200 usually resequences faster than a late save; FSF’s ALAR notes echo this: ALAR Briefing Notes in English - Flight Safety Foundation. @OP do you let the PM make an automatic “unstable, go-around” call if either speed or config is off at 1,000?
I start a 60‑sec EFB timer abeam; at ‘1,000’ confirm +10/−5 — else go-around. Keeps turns tight.
I set “minimums” to 1,000 AGL so the aural call is the cue: PF says “stable, Vref +5” or we break it off — no committee meeting. It nails your +10/−5 target and protects turn time because the decision happens in one beat. @luke_garcia92 your timer trick is slick; this works when the EFB’s buried.
Quick win: give them a tiny “energy card” with power + VSI targets for a 3° path at typical weights, and have it set abeam so they naturally hit “Vref +10/−5 at 1,000” with no last‑minute fiddling. It protects turn time because power/config are locked before base — , nothing burns minutes like chasing speed inside 500’. Do you tune the card per flap setting or run one fleet‑wide? https://flightsafety.org/toolkits-resources/alarp/stabilized-approach-criteria/.
Skip extra cues: we brief a ‘no changes after 1,200’ rule so 1,000 AGL is just confirm — ‘gear down, landing checklist complete, bug verified,’ hands off the knobs. @davidson_ryan83, do you keep the AP in through 1,000 AGL the first month? That plus the non‑negotiable check meets the standard without last‑second fiddling.
I anchor it to distance instead of altitude: gear by 5 DME, final flaps by 4, bug Vref+5 at GS intercept, so hitting your “speed within +10/−5” is just a confirm at the gate. If ATC compresses us inside 6, we either ask for a little room or brief a no-drama TOGA rather than trying to salvage, which weirdly saves more time. @davidson_ryan83 do you allow speedbrake past the gate, or is that a hard no-touch?
I got consistency by adding a single “gate freeze” rule: if we’re not fully configured and inside your +10/−5 window by the RA callout just above the gate, the PF says “set” and no more knob turns — any change after that triggers the go‑around. It builds the habit without dragging the day because the decision is clean and the debrief is a quick yes/no. Small caveat: in gusts I brief a slightly wider top end; do you keep it strict or add gust margin?
I’ve had the best results keeping the autopilot in until the gate so the PF’s only call there is “stable, continue” or an immediate go‑around if we’re outside your +10/−5 on Vref; it cuts last‑minute fiddling and hasn’t hurt turn times. Caveat: in gusty days I’ll disconnect a bit earlier to feel it out, but the stability check and trigger stay the same.
We set amber/red speed bugs bracketing Vref; quick visual confirms your ‘+10/−5’ at 1,000. Adjust for gust additive.
I treat the 1,000 ft check as a timed flow: abeam the numbers, start a 90‑sec timer; by the beep we’re in landing config and within ‘+10/‑5’ on Vref, otherwise we reset instead of salvaging late. Pulling the work earlier keeps turn times tight because there’s no scramble on short final. @w_carter22, have you tried a simple timer or abeam trigger?
I bake it into the before-landing checklist as a challenge/response: PM asks “stabilized by one thousand?” and if the answer isn’t an immediate yes, we plan an early re-sequence rather than salvage it. We also use the mantra “no new changes below one thousand,” which kills the last‑second flaps/trim fiddling. Minor caveat: on gusty/tailwind days I bump the trigger to 1,500 — like leaving a bigger braking zone — have you tried that?
Quick example: I teach a simple “1500–1000–commit” cadence — configured and checklist done by about 1500 AGL, trim settled by about 1200, and at the GPWS “one thousand” the PF must say “stable” or “going around,” binary like a light switch. Building on @m_frost10’s visual cues, we add the aural gate so nobody hunts inside at the decision; on slam-dunk vectors we pre-brief a longer downwind as the fallback. Do you tie your gate to VNAV/FPA or raw GS?
Quick tip: we brief a “ready by GP intercept” line in the sand and, if we’re not there, the PM asks for an extended downwind before base rather than gambling on a late fix — keeps turn times predictable and the gate truly non‑negotiable. Small caveat: in gusts we bug Vref + additive and accept tiny trend wiggles instead of chasing the +10/‑5 to death; think train schedule — miss it, catch the next one. @OpsSarah, do you tie this to the FAF call or use a distance cue like 3 NM final?
Agree with @e_watson4 on keeping it binary: set the alt bug at 1,000 AFE and have the PF self-call “stable, Vref +10/-5” at the gate; if they hesitate, it’s an immediate go-around. Do you normalize that by planning one deliberate go-around in the first few legs? I’ve found that, plus logging a simple “late-stable” tag, cements the habit without rushing the taxi-back.