The Ride, Details, the flight portion

Bill

Touchdown! Greaser!
Joined
Mar 2, 2005
Messages
15,106
Location
Southeast Tennessee
Display Name

Display name:
This page intentionally left blank
I know I'm doing this backwards, and I hope to write up the oral in the next day or so. For now, those interested can look at my writeup of the flight portion of the IR checkride. WARNING: LOOONNNNGGGG.

I'm going to post an exact copy on the 'red' board for those over there.

Flight test


He tells me we will depart Chattanooga, and head for the NDB RWY 3 approach into Cleveland (HDI). So I call CD, get my clearance. Before starting the plane, I set up all the radio and nav frequencies I could, and ID’d both the VOR I’d use to help locate the NDB as well as the NDB itself. The NDB was left on softly in the background.


Once off, DEP starts to give me vectors to Hardwick, but the DE is wise to this game and tells me to tell DEP to cancel vectors, we’d be doing this one on our own. You see, this NDB APP has a mandatory hold, and the DE didn’t want me to get out of the hold by having vectors to the station.


Fairly easy, I home on the NDB, and once having station passage, do a direct entry into the pattern, and then fly my one minute outbound while getting my altimeter from McMinn County AWOS. I turn back inbound, and when I roll out, the needle is 20 degrees left. So, I turn 40 degrees left, and fly until I see my 40 degrees. Back to inbound, and the needle is right on the nose. It again starts to fall off to the left as I near the station, but I verbalize that I will maintain published inbound until station passage and I’m far enough past to get reliable information.


About 0.8 DME past station, I’m showing the needle 25 degrees left, so I turn 50 degrees left and fly until I see my 50 degrees. Back to inbound, and the needle is right on the tail. As I’ve been descending towards MDA, I seem to get out of the wind as the needle stays on the tail with very minor corrections. All the while, I was calling in my position reports. The DE says don’t even bother raising the foggles, as we’re never going to come out of the clouds and will have to fly the published miss. So, I fly until the stopwatch hits the missed time, and I go missed and do my position announcement. Climb straight ahead to 2100, then climbing right turn to 3000 back to the NDB.


As I pass the station, I would have to make a left turn to stay in the protected area, so I do a parallel entry, and fly outbound for 1 minute, then begin my turn to the left into the protected area. I then home towards the station for 15 seconds or so, and he says “good enough, turn to a north heading.”


I do so, and he covers the AI and DG, and asks me to turn right to a south heading. (Partial panel was the only thing I was really worried about) I start my turn and the stopwatch, and watch the whisky compass. As it passes thru east, I look at the stopwatch, 28 seconds, pretty good standard rate turn. After east, the compass starts to lead the turn, so I’m looking for 210 or so, and when I do, the watch still has 6 seconds to go. I split the difference, turn for another 3 seconds, and roll out. Right on, this is the best timed turn I’ve done!!! He then says turn left back to north, so I do, and roll out at 030, and again I was right at north. Amazing what you can do when the chips are down.

He then pulls the cover from the DG, and says we’ll do some unusual attitudes, and we do two moderately aggressive unusual attitude recoveries. He then pulls the cover from the AI, and says we’ll do two more. This time, aggressive ones, one pitch up about 25 degrees 30 degree bank, one pitch down 25 degrees, 45 degree bank. We then do steep turns left and right.


That done, he says call APP and get vectors to OSILY (IAF) for the VOR RWY 33 ARC approach. On the way there, I set up NAV 1 on the VOR, with the OBS set to inbound course, and NAV 2 to the VOR, and use the OBS to keep track of what radial I am crossing. ID both, and then set up DAISY on the NDB, as that is the published miss fix. ID the NDB, and keep it softly beeping in the background.


I fly around the arc without much trouble, using the OBS of NAV 2 to keep track of the radials. The instant the needle on the inbound VOR head lifts from full scale deflection, he covers the AI and DG, and I begin my turn in to inbound partial panel. Wanting 332 inbound; I figure maybe 20 degrees of lag at that heading, and roll out at 310. Not bad, once the compass settles, we’re in the ballpark. From then on, I make small corrections inbound, but the wind is pretty strong. From the FAF in to the missed, I’m flying about due north to stay on the 332 radial. ATC had given me a missed to fly, and 33 being the crosswind runway and lots of traffic, ATC called our miss about one mile before the published missed. I take a peek, and I’m lined right up with 33.


I do a climbing turn to 065, then vectored to 090, then 150, then 200, so we’re on the right downwind for ILS RWY 02. All I have to do now is fly a clean ILS, and we’re home free. I spend the time on downwind setting up NAV 1 to the LOC, NAV 2 to the VOR, with OBS set to the radial that helps ID the OM, check DAISY (missed fix) on the NDB, then ID everything, and return the NDB to softly beeping in the background. Set the beacon receiver to phones, low, and hit the test switch to test the beacon lights.


I get vectored to 230, and then am expecting a vector to west or so to take me towards the ILS course. I receive a vector from APP, but screw it up, “Bugsmasher 12345 turn right 350, maintain 2500 until established, cleared ILS RWY 02 approach.” I hear turn right 250, and readback as such. The controller does not catch my mistake, and chimes back with readback correct. I quickly think about that vector, and remember most of the time they give a 30 degree intercept vector when saying cleared for the approach.


Oh no, what to do? Normally, if I didn’t fully catch a call, I’d ask my safety pilot or instructor, but knew I couldn’t ask the DE. Oh crap, I’m gonna bust!!!


I did the only think I could think of, and punched the button, “Approach, Bugsmasher 12345 verify heading.” And he came back with the 350, so I continued my turn and read back the proper vector. Whew!


For added excitement, right as I rolled out on the inbound, approach asked for best forward speed due to traffic behind me. So, I dial up 2600rpm, and fly down the GS at 125kts (normal approach for the Skyhawk is 90kts). Work like the devil to keep everything in the donut on this fast approach, receive the OM and begin my timer, get to DH, flip up the foggles, pull power and carb heat, nose up, airspeed into the white arc, dump full flaps, trim for 60kts, and float down power off to a decent landing.


Tower had us taxi to the ramp with them, and it was done. I got out of the airplane and did a little Snoopy dance around the plane. About 1.6 total chock to chock.
 
Last edited:
I'll bet the DE caught the heading error on the last approach and just sat back waiting to see how you'd deal with the ensuing confusion. Then when you verified the number he had to be smiling, as it was exactly the right thing to do.
 
lancefisher said:
I'll bet the DE caught the heading error on the last approach and just sat back waiting to see how you'd deal with the ensuing confusion. Then when you verified the number he had to be smiling, as it was exactly the right thing to do.

Back on the ground, walking into the FBO, he said, "Good flight, by the book."

I was glad to think quickly enough to sort that out.
 
Funny thing, Bill: I knew you passed, and yet as I read your account, I flew it along with you. Good fun, all that, and I bet when you were done, you enjoyed it too.

I need to go out and practice NDB procedures... while there are still NDBs to do 'em with!
 
Congrats!
Great job and great post. I knew there was a reason I got rid of the ADF b/4 my IFR ride.
 
Awesome, Bill!

A few thoughts:

It was nice of the DPE not to make you fly the NDB partial panel!

Good catch on the wrong vector. I think you did exactly the right thing.

On the ILS I would not have gone so fast, even with the request. Just say, "roger," add a bit of power, and do your best. If you were really in the clouds, and you were doing something radically different for your aircraft, you increase the risk.

1.6 on the Hobbs sounds short for what you did!

Congratulations!
 
Last edited:
Good job Bill. I believe you said "It's amazing what you can do when the chips are down." That's so true...I found that the nerves during my checkride gave what I needed to nail every timed turn, approach, etc. Now you just have to continue flying that well without the DE sitting next to you. Congratulations...enjoy the ticket...we just need to get some warmer temps so we can build some actual time!
 
dang I always break into a sweat when I read these accounts! Good going Bill. (glad real life is not that tough)
 
The IFR ticket test passing grade is cool but, not as cool as your first solo APP in IMC as PIC, only pilot on board or with PAX.
That's when you actually get the IFR rating.
 
Wow, that read like a steamy novel. Especially the part about the misheard heading and how you corrected. Great job of staying ahead and great write-up.
 
Dave Krall CFII said:
The IFR ticket test passing grade is cool but, not as cool as your first solo APP in IMC as PIC, only pilot on board or with PAX.
That's when you actually get the IFR rating.
I completely agree. But they're both cool. Different types of cool!
 
Paul Allen said:
Congrats!
Great job and great post. I knew there was a reason I got rid of the ADF b/4 my IFR ride.

On the flip side, our other club plane has 430's and an S-Tec 55x. I thought it would be easier to demonstrate ADF approaches than demonstrate coupled approaches.

To each his own :cheerswine:

121Dispatch said:
Congratulations...enjoy the ticket...we just need to get some warmer temps so we can build some actual time!

Roger that, freeze levels here in the southeast are not cooperating very well. In the mean time, I'm going to get instruction on using the 430 and 55x in the other plane for flying coupled approaches, etc.

wangmyers said:
1.6 on the Hobbs sounds short for what you did!

I guess we're lucky to have a variety of approaches in the area. There are 4 NDB apps within 20nm of my home airport, one VOR app, and two ILS apps.

So, for the checkride, the NDM app was about 20nm away, and between the NDB app and the beginning of VOR 33 (OSILY intersection) is our east practice area. So, no real lost downtime, the airwork was done on the transit from the NDB to the VOR. After the VOR approach, all I needed was vectors downwind to join ILS 02.

Nice compact practice area, during practice without the airwork, it was quite easy to get all three approaches in about an hour. (light traffic days, maybe 1.2 on a heavy traffic day)

Good controllers, they work really well with GA guys practicing approaches.
 
Last edited:
Bill Jennings said:
On the flip side, our other club plane has 430's and an S-Tec 55x. I thought it would be easier to demonstrate ADF approaches than demonstrate coupled approaches.

To each his own :cheerswine:

Once you work out a good relationship with the autopilot, coupled approaches are easier. You didn't ask but here's my advice WRT flying coupled approaches.

It's been said that the most common "conversations" with an autopilot almost always include the phrase "what's the d@mn thing doing now?", because the have a tendency to do what you program them to rather than what you want them to do. Since most problems with coupled approaches are setup errors, you can gain a lot of "free" practice by setting up for a coupled approach and then hand flying the final once the a/p has you established (and on GS if ILS). Try to learn all the nuances involved with your autopilot by reading the manual enough times that most of it actually sinks in, with particular emphasis on intercepting lateral and vertical course
guidance. Then verify your understanding in VFR flight (w/o foggles), preferrably with another pilot along to watch for traffic while you futz. Make sure you understand what's required to fly a course reversal with various nav sources as LOC, VOR, and GPS often require somewhat different methods. And speaking of GPS, I recommend learning that unit well before flying any approaches coupled to it or you'll end up wondering whether your "problem" came from the GPS setup or the autopilot.


There are a couple other caveats when flying a coupled approach though.
One is that it's very important to avoid applying any "help" in pitch if the a/p has autotrim or if like the new Chelton a/p it only controls trim. If you "argue" with george in pitch on that kind, he will call for trimming against your input and this is likely to lead to a very out of trim airplane that's going to be near impossible to control when you disconnect or the a/p kicks itself off. There is no such issue with roll on any GA a/p I've ever seen.

The other is that the a/p can mask anomalies that you would be likely to recognize sooner if hand flying. George will follow a defective gyro right into a death spiral without a complaint, so you need to pay close attention to the flight instruments when the a/p flies close to the ground. Things like ice accumulation and fuel imbalance cause similar problems with the a/p hiding the symptoms until they suprise you on short final, and again the answer is to pay close attention.

I've met way too many pilots so unfamilar with their autopilots that they are afraid to use it on any approach, as well as plenty who fear that using the autopilot will become a crutch that will kill them when it breaks. An autopilot is a very good tool that can make instrument flying safer by allowing the pilot to manage the airplane along with the other tasks of flight in IMC with less concentration on maintaining the correct attitude.
 
lancefisher said:
Once you work out a good relationship with the autopilot, coupled approaches are easier. You didn't ask but here's my advice WRT flying coupled approaches.

Thanks for the advice, Lance. I downloaded the POH's for both the GPS and Autopilot, now time for more studying. Ticket to learn...
 
Dave Krall CFII said:
The IFR ticket test passing grade is cool but, not as cool as your first solo APP in IMC as PIC, only pilot on board or with PAX.
That's when you actually get the IFR rating.

Nah, what REALLY makes you an IFR pilot is going 7600 while solo in IMC on your first flight after getting your IR ticket. :yes:
 
N2212R said:
Nah, what REALLY makes you an IFR pilot is going 7600 while solo in IMC on your first flight after getting your IR ticket. :yes:

Crikey you're evil ! :hairraise:
 
N2212R said:
Nah, what REALLY makes you an IFR pilot is going 7600 while solo in IMC on your first flight after getting your IR ticket. :yes:

I would think you'd have less work...
Gonna tell us the details of the flight ?
 
Dave Krall CFII said:
The IFR ticket test passing grade is cool but, not as cool as your first solo APP in IMC as PIC, only pilot on board or with PAX.
That's when you actually get the IFR rating.

Waiting for a good non-icing soupy day. Most of the IFR here lately has been in icing conditions.
 
Back
Top