Re: Setting up for an approach

[C Kingsbury]

"Brad Z" > wrote in message news:<_uXRc.121125$eM2.105682@attbi_s51>...
> With my students, I do WIRE, along with CTMM

I've never heard those before, but my CFII taught me to do the "5 Ts"
as we cross the FAF:

Time: Start your timer no matter the type of approach
Turn: Make sure you're on the right course for the final segment
Twist: If on an ILS/LOC or VOR twist the #2 box to back up the #1
Throttle: Power back for descent to the minimum (and re-check the
minimum)
Talk: Let controller know you're on your way in from point XYZ.

-cwk.

[Brad Z]

I've heard WIRE before, but I'd never heard CTMM before I came up with it
trying to figure out how to teach approach briefings one day. I was
concerned that my students were not committing to memory important details
of the approach, and spent too much time reading the chart as we went along.
Mind you, heading bugs, altitude bugs and the like are useful in aiding
memory.

I use the Five T's as well, but they apply to crossing any fix, not just in
the approach environment. The five T's (or six, or seven, even) challenge
the pilot to ask themselves "what next?" CTMM is an acronym that helps to
answer those challenges in the approach environment, where such information
should be committed to memory. Looking down to read the chart while you're
descending to MDA is not a good practice.

Brad

"C Kingsbury" > wrote in message
om...
> "Brad Z" > wrote in message
news:<_uXRc.121125$eM2.105682@attbi_s51>...
> > With my students, I do WIRE, along with CTMM
>
> I've never heard those before, but my CFII taught me to do the "5 Ts"
> as we cross the FAF:
>
> Time: Start your timer no matter the type of approach
> Turn: Make sure you're on the right course for the final segment
> Twist: If on an ILS/LOC or VOR twist the #2 box to back up the #1
> Throttle: Power back for descent to the minimum (and re-check the
> minimum)
> Talk: Let controller know you're on your way in from point XYZ.
>
> -cwk.