Hi, all,
I took a very educational IFR flight yesterday, and learned a lot, so I thought I'd share some of the particulars here. One of those stream-of-little-things kind of stories.
I trained in the fleet of 172SP's at my flight school which are all /G. They've all got the GPS, MFD, and autopilot. They differ only slightly from one another. Here in the Northeast, you need /G to go most places, since just about every non-GPS approach in these parts says "ADF required" or "DME required" in big (or small) letters on the plate. So we did a lot of GPS approaches during training. My school has a couple of planes with ADF, but they don't always work. None have a separate DME. So when I reserved my 172SP plane for yesterday, I filed /G from KBED to KRUT like I am accostomed to.
The weather was great. There were some scattered clouds at 5000 and it was clear-and-a-million at Rutland, so this was to be an "IFR, just to keep my hand in the system" kind of flight.
I hop in the plane and fire up the engine. The GPS comes alive and says "FOR VFR USE ONLY. ACKNOWLEGDE?" in big letters. The database expired in 2001. Dammit! Okay, okay... calm down. Let's re-think this a little. First of all, tell ATC about it. What equipment code are we now? Well, looks like I've got an ADF in here... what is the code for that again? Do I even know if the ADF works? Aw, hell, I'll just file /U and fly it that way. (Arrrrrggg! This is what sucks about renting!)
Me: "Hanscom clearance, Skyhawk xxxxx is IFR to Rutland. I filed /G, but I'm actually /U."
Clearance: "Okay, I'll pass that along. You're cleared to Rutland via radar vectors, Manchester, direct..."
I read back the clearance and started taxiing. Halfway to the runup area, I realized I wasn't sure I could accept the clearance they'd given me. I mean, how am I supposed to go direct Rutland without the GPS? Arrrrrrgg!! Okay, okay, calm down, you'll sort it out after the runup.
Runup complete. Okay, let's re-think this from the beginning. I dig out the enroute chart, and realize, hey, Rutland has a VOR on the field! It's not part of the enroute structure, but it's there. So I CAN go "direct Rutland". Hot damn! Okay, that problem is solved. What about approaches? I dig through the approach plates and scan their titles. LOC Z Rwy 19, okay I can do that one. VOR/DME Rwy 1, nope. VOR/DME Rwy 19, nope. LOC/DME Rwy 19, nope. RNAV Rwy 19, nope. Dammit! I can only do one out of five of these things! Oh well, at least I can do one. It's clear and unlimited at KRUT and so I'll be cancelling IFR before doing any approaches anyway.
So I launch. Approach gives me vectors to MHT. Approach gives me direct MHT. I have a flight plan loaded in the GPS as a backup, but I keep the HSI set to "NAV" so as to do the whole thing by the book. Yay, I remembered that little rule! Good Kath! Doing great! I pop through a thin scattered cloud layer and rejoice!
Getting closer to Manchester. I tune in the Rutland VOR and turn up its volume. All I hear is <dit dit dit dit dit dit dit dit> and the needle is centered on North. Somebody's VOT signal? Sooooo... what do I do when I reach MHT? Approach is expecting me to go direct Rutland. Well, I could use the GPS, but this has to be "by the book", remember?
Me: "Approach, Skyhawk xxxxx is approaching Manchester, unable to receive Rutland VOR at this time, request vectors."
Approach: "Fly heading 320, direct Rutland when able."
There. That was easy! Hey, this isn't so bad. I've got the GPS as backup and everything's going smoothly. Miles slip happily under the nose. The clouds below are thinning. Approach occasionally asks me whether I'm able direct Rutland yet, and I check (dit dit dit dit dit!) and tell them no. I use the time to try to figure out whether the ADF works. I tune in a few NDB's and receive nothing. Of course, I am like 30 miles away from the thing. What is the range of your typical NDB anyway? I've completely forgotten. Oh well, we'll not depend on the ADF for this trip. Check Rutland VOR again, aha! There are those happy dits and dahs! I tell ATC that I'm receiving the VOR and proceeding direct. Hmmm... how about that approach, the LOC Z Rwy 19 at Rutland? Let's go over that thing. Not that I'll fly it, of course... I'll cancel first. But let's have a look just for practice. Frequencies, blah blah, localizer, blah, okay.... ADF required? Aw, HELL!! <insert some swear words here> G**da*n fine print! Well, now I'm down to zero approaches out of five that I can legally fly!
Suddenly my brain goes crazy with thoughts. A stream of consciousness kind of like this: I obviously should have looked at these details before takeoff. Well, Kath, you'd have paid more attention if it weren't a beautiful VFR day today! Is it legal to file IFR to an airport that you can't legally do any approaches at? Probably not. Come to think of it, there are airports with no IAP's at all... can you fly IFR there? I suppose you just have a clearance limit that is someplace other than your destination, past which you're on your own and had better be VMC. I suppose the Rutland VOR (not the airport) could have been (should have been?) my clearance limit. Maybe it is, since they're co-located. Sort of. Or are these musing just artifacts of my panicked brain? Don't panic. Does ATC know that I can't do any approaches here? Now, now, now, Kath, that's not their responsibility, is it, no, it's YOURS. Dammit, stupid Niner Mike Echo! Why did I have to get stuck with you? The only plane in the fleet without the IFR-certified-GPS! Come to think of it, I haven't checked your logbooks, how do I know you've even had your required pitot-static checks and transponder checks and.... AAaaack! Calm down, Kath. There's the airport, clear as day! "Boston Center, Skyhawk xxxxx, field in sight, cancel IFR."
There. *sigh* Problem solved. Man, /U sucks in the Northeast! You can't do approaches hardly anywhere it seems. Is it this bad everywhere? Why is this approach "ADF required" anyway? SMUTO is the only NDB on here, and you can identify it with the localizer and a cross-radial from Lebanon! Something in the missed approach? No, the missed says nothing about SMUTO or the NDB. MSA reference? Nope. It all looks doable without the ADF. I don't get it. Now, Kath, you can figure it out later, you should focus on flying the plane. You can ask the PoA board about it later.
So I landed, feeling a little stupid and a lot drained... and sure I was going to be VFR for the return trip! You definately can't do anything at KBED without a GPS or ADF.
Now that I'm back on the ground and in front of my computer, the mystery deepens.
Here's the NOS version of the approach:
http://download.aopa.org/iap/20050609/NE-1/rut_loc_z_rwy_19.pdf
I don't see any "ADF required" statement on here. Yet on the Jepp version of the plate (can anyone post it?), note #2 below the missed approach instructions says "ADF required". What gives with this approach?
--Kath
P.S. Radio exchange of the day (heard at Hanscom):
Tower: "Experimental xxxx, nice S-turns, thanks for the help."
Pilot: (laughing while speaking) Actually, I'm not doing S-turns. I am fighting the sea breeze!"
I took a very educational IFR flight yesterday, and learned a lot, so I thought I'd share some of the particulars here. One of those stream-of-little-things kind of stories.
I trained in the fleet of 172SP's at my flight school which are all /G. They've all got the GPS, MFD, and autopilot. They differ only slightly from one another. Here in the Northeast, you need /G to go most places, since just about every non-GPS approach in these parts says "ADF required" or "DME required" in big (or small) letters on the plate. So we did a lot of GPS approaches during training. My school has a couple of planes with ADF, but they don't always work. None have a separate DME. So when I reserved my 172SP plane for yesterday, I filed /G from KBED to KRUT like I am accostomed to.
The weather was great. There were some scattered clouds at 5000 and it was clear-and-a-million at Rutland, so this was to be an "IFR, just to keep my hand in the system" kind of flight.
I hop in the plane and fire up the engine. The GPS comes alive and says "FOR VFR USE ONLY. ACKNOWLEGDE?" in big letters. The database expired in 2001. Dammit! Okay, okay... calm down. Let's re-think this a little. First of all, tell ATC about it. What equipment code are we now? Well, looks like I've got an ADF in here... what is the code for that again? Do I even know if the ADF works? Aw, hell, I'll just file /U and fly it that way. (Arrrrrggg! This is what sucks about renting!)
Me: "Hanscom clearance, Skyhawk xxxxx is IFR to Rutland. I filed /G, but I'm actually /U."
Clearance: "Okay, I'll pass that along. You're cleared to Rutland via radar vectors, Manchester, direct..."
I read back the clearance and started taxiing. Halfway to the runup area, I realized I wasn't sure I could accept the clearance they'd given me. I mean, how am I supposed to go direct Rutland without the GPS? Arrrrrrgg!! Okay, okay, calm down, you'll sort it out after the runup.
Runup complete. Okay, let's re-think this from the beginning. I dig out the enroute chart, and realize, hey, Rutland has a VOR on the field! It's not part of the enroute structure, but it's there. So I CAN go "direct Rutland". Hot damn! Okay, that problem is solved. What about approaches? I dig through the approach plates and scan their titles. LOC Z Rwy 19, okay I can do that one. VOR/DME Rwy 1, nope. VOR/DME Rwy 19, nope. LOC/DME Rwy 19, nope. RNAV Rwy 19, nope. Dammit! I can only do one out of five of these things! Oh well, at least I can do one. It's clear and unlimited at KRUT and so I'll be cancelling IFR before doing any approaches anyway.
So I launch. Approach gives me vectors to MHT. Approach gives me direct MHT. I have a flight plan loaded in the GPS as a backup, but I keep the HSI set to "NAV" so as to do the whole thing by the book. Yay, I remembered that little rule! Good Kath! Doing great! I pop through a thin scattered cloud layer and rejoice!
Getting closer to Manchester. I tune in the Rutland VOR and turn up its volume. All I hear is <dit dit dit dit dit dit dit dit> and the needle is centered on North. Somebody's VOT signal? Sooooo... what do I do when I reach MHT? Approach is expecting me to go direct Rutland. Well, I could use the GPS, but this has to be "by the book", remember?
Me: "Approach, Skyhawk xxxxx is approaching Manchester, unable to receive Rutland VOR at this time, request vectors."
Approach: "Fly heading 320, direct Rutland when able."
There. That was easy! Hey, this isn't so bad. I've got the GPS as backup and everything's going smoothly. Miles slip happily under the nose. The clouds below are thinning. Approach occasionally asks me whether I'm able direct Rutland yet, and I check (dit dit dit dit dit!) and tell them no. I use the time to try to figure out whether the ADF works. I tune in a few NDB's and receive nothing. Of course, I am like 30 miles away from the thing. What is the range of your typical NDB anyway? I've completely forgotten. Oh well, we'll not depend on the ADF for this trip. Check Rutland VOR again, aha! There are those happy dits and dahs! I tell ATC that I'm receiving the VOR and proceeding direct. Hmmm... how about that approach, the LOC Z Rwy 19 at Rutland? Let's go over that thing. Not that I'll fly it, of course... I'll cancel first. But let's have a look just for practice. Frequencies, blah blah, localizer, blah, okay.... ADF required? Aw, HELL!! <insert some swear words here> G**da*n fine print! Well, now I'm down to zero approaches out of five that I can legally fly!
Suddenly my brain goes crazy with thoughts. A stream of consciousness kind of like this: I obviously should have looked at these details before takeoff. Well, Kath, you'd have paid more attention if it weren't a beautiful VFR day today! Is it legal to file IFR to an airport that you can't legally do any approaches at? Probably not. Come to think of it, there are airports with no IAP's at all... can you fly IFR there? I suppose you just have a clearance limit that is someplace other than your destination, past which you're on your own and had better be VMC. I suppose the Rutland VOR (not the airport) could have been (should have been?) my clearance limit. Maybe it is, since they're co-located. Sort of. Or are these musing just artifacts of my panicked brain? Don't panic. Does ATC know that I can't do any approaches here? Now, now, now, Kath, that's not their responsibility, is it, no, it's YOURS. Dammit, stupid Niner Mike Echo! Why did I have to get stuck with you? The only plane in the fleet without the IFR-certified-GPS! Come to think of it, I haven't checked your logbooks, how do I know you've even had your required pitot-static checks and transponder checks and.... AAaaack! Calm down, Kath. There's the airport, clear as day! "Boston Center, Skyhawk xxxxx, field in sight, cancel IFR."
There. *sigh* Problem solved. Man, /U sucks in the Northeast! You can't do approaches hardly anywhere it seems. Is it this bad everywhere? Why is this approach "ADF required" anyway? SMUTO is the only NDB on here, and you can identify it with the localizer and a cross-radial from Lebanon! Something in the missed approach? No, the missed says nothing about SMUTO or the NDB. MSA reference? Nope. It all looks doable without the ADF. I don't get it. Now, Kath, you can figure it out later, you should focus on flying the plane. You can ask the PoA board about it later.
So I landed, feeling a little stupid and a lot drained... and sure I was going to be VFR for the return trip! You definately can't do anything at KBED without a GPS or ADF.
Now that I'm back on the ground and in front of my computer, the mystery deepens.
Here's the NOS version of the approach:
http://download.aopa.org/iap/20050609/NE-1/rut_loc_z_rwy_19.pdf
I don't see any "ADF required" statement on here. Yet on the Jepp version of the plate (can anyone post it?), note #2 below the missed approach instructions says "ADF required". What gives with this approach?
--Kath
P.S. Radio exchange of the day (heard at Hanscom):
Tower: "Experimental xxxx, nice S-turns, thanks for the help."
Pilot: (laughing while speaking) Actually, I'm not doing S-turns. I am fighting the sea breeze!"
Last edited: