Tap what just happened: ask, try, say. CFM Rev 12 TR 26-02 · v2.1 · Refs verified: 2026-10-31 · instructor use only
Or pick it by phase. Tap one.
For talk-through mode: say the lines as the approach happens. Drop lines as the student takes them over.
CFM 7-3, 7-7, 7-84, 7-85
CFM 7-8, 7-84, 7-86 NOTE; Briefings Card; FOM 8-70 (idle by the 10 call)
CFM 7-86 (Table 7-23), 7-88, 7-89 · 200–300 fpm target is technique, not CFM [verify]
CFM 7-87, 7-88
Tiers. First rep: ask, talk-through, one correction. If it repeats: cover, shadow, freeze. If it persists: reposition reps, their phone. Every option in Try one is instruction, so Validation mode greys out the whole list. Find out, Show in debrief, Source and the session log stay active for the debrief.
Thrust: start at fifty, idle by ten. Not 100; the 100-ft REF call is information. CFM 7-8, 7-84; FOM 8-70.
Flare 30–20 ft; hold constant pitch from 20. Pitch 1° on approach, 3–5° at touchdown (4–6° reduced VREF). CFM 7-86.
Flare height ≈ sink ÷ 30 (700 fpm → ~23 ft). Briefings Card; guidance, not a limit.
Hard landing = over 600 fpm at or below MLW. CFM 7-89. A 300-fpm arrival is a normal landing.
Touchdown zone = first 3,000 ft or first third, whichever is less, starting 500 ft past the threshold. FOM 2-12.
Spoilers deploy with both levers at idle plus two of: main WOW, wheel speed > 16 kt, RA < 10 ft. Systems 9-32.
11° pitch = tailstrike, 11° bank = wingtip, gear near the runway. CFM 7-89.
Crosswind: crab wings-level on final; rudder and aileron together at the flare; aileron in until clear. CFM 7-88.
Rollout: nose down, then reverse, then brakes. 90 kt: stow; idle by 60. CFM 7-87.
The aim point tells you where you're going, not how high you are.
The flare is a rate, not a height: turn 700 into 200–300 and hold.
Rudder and aileron are one word, and the landing ends at the taxiway.
Set one of these in the visual on purpose once the normal picture is solid. Source: FAA AIM 8-1-5, illusions leading to landing errors [verify]. Not in company manuals.
Your reference clips (your phone). Phone on the CB panel over your shoulder, framed on the windscreen, the PFD and your hand on the levers. One approach per error, 20–30 seconds, narrate only what you’re doing: “Fifty. Eyes long. Levers coming back. Thirty. Flare. Hold.” Trim the ends, no other editing. These are yours; they go into these cards as “watch” clips.
The student’s clip (their phone). Offer it: “Want me to put your phone up so you can see your own landing?” Same mount, same spot, every student. Play it back on their phone in the debrief, not on the big screen. Nothing is ever on your device, and the consent is built in because they handed you the phone. One error per session, not every approach.
Why it works. They flared on the “fifty” and believe they flared at thirty. You don’t argue; the clip shows the nose coming up as the voice says fifty. And a camera behind them shows the head tilt toward the numbers at 50 ft, which is the eye-position answer you can’t get from the IOS.
Setup. A clip mount that attaches to the CB panel in a few seconds. Test one clip: can you hear the RA callouts, can you see the lever position? If the windscreen blows out the exposure, lock exposure on the panel. Check with training on recording in the sim before the first session; the student-owns-the-clip approach keeps it clean.
The full perception-vs-reality write-up (why each error happens, technique reconciliation, sim fidelity, source log) is the companion doc CRJ-900 Landing: Perception vs Reality — Instructor Deep Dive. Use it to build briefs; use this page in the bay.