Flying an ILS that requires ADF but not ADF (or IFR GPS) equipped

I got it, in IMC, on a missed approach, on a coastal mountain airport (KHAF, RWY 30 RNAV Z). Followed shortly by a loss of signal and a "DR" annunciation. Worse, out of communication with Approach due to terrain shadowing. I was on my own to 2000 feet with unusable primary nav....
That's interesting, because the one time I recall getting a RAIM warning was on approach to that same runway. (I think it was ten or more years ago.)
 
No real data to back this up, but having used both, between my ADF and my Stratus w/I-pad, my money is on the Stratus/I-pad.
There's nothing but anecdotal evidence on my part either. I remember being told that the (now former) NDB approach at Oakland was iffy due to scalloping. I flew the former NDB approach at Stockton many times. It was an off-field NDB, and it always seemed like I ended up a quarter- or half-mile off the center line. And correcting for crosswind on an NDB approach was always a challenge if I hadn't practiced it recently.

After an Air Force plane carrying Ron Brown crashed in Croatia, I had to laugh at the conspiracy theorists who thought that assuming someone moved one of the NDBs was necessary in order to explain how someone could screw up an NDB approach!
 
I was wondering what approach you were talking about and saw in your post #37 the airport was KMYR so I assume it was the ILS or LOC RWY 36. That Approach has an Alternate Missed Approach. It goes to CRE, a VOR. Tell Approach you ain't got ADF and will need the Alternate Missed Approach. Have your pencil handy. It doesn't look like it will be to complicated.
 
Thanks all for your replies. The first time this happened to me I really just sort of stumbled on it. I could have chosen another ILS approach in the opposite direction (no NDB fix) but I actually felt safer proceeding with the favored runway since the wind was really blowing from the other way and I didn't want to go roaring down the glideslope. I also had a VOR approach to choose from but it was nearly on top of me by the time I figured all that out. Yes, the plane was in front of me. I was really interested to see what kind of leeway others allowed themselves for such a condition. I'm not sure I got that but I did get a bit of a spanking so maybe I'll just have to find that $15K somehow for an IFR GPS receiver (at least that what my avionics shop wants). But it's going to be a while.

You survived it, but the prudent thing to do was abandon the approach as soon as you found out, asking for vectors to the VOR. Continuing is really only the best option in a lost comms scenario, and even then only with ceilings well above minimums. It's not a comfortable situation to be on final when you HAVE to land.

You don't always get vectors on the missed, particularly if there is some weather and Approach is getting really busy with diversions and deviations.
 
I was wondering what approach you were talking about and saw in your post #37 the airport was KMYR so I assume it was the ILS or LOC RWY 36. That Approach has an Alternate Missed Approach. It goes to CRE, a VOR. Tell Approach you ain't got ADF and will need the Alternate Missed Approach. Have your pencil handy. It doesn't look like it will be to complicated.

Wow, now that is an unforgivable oversight on my part. However, the plate still says "ADF required" however. Then that's not absolute? Anyway, you've given me a new way of "approaching" this kind of thing and I'm glad I brought it up. Yes, it wouldn't be complicated. Thanks.
 
Wow, now that is an unforgivable oversight on my part. However, the plate still says "ADF required" however. Then that's not absolute? Anyway, you've given me a new way of "approaching" this kind of thing and I'm glad I brought it up. Yes, it wouldn't be complicated. Thanks.

If the plate says "ADF required," it's required.
 
If the plate says "ADF required," it's required.

I'm not so sure. Along the way I've had several instances where a controller has "modified" approach altitudes (sometimes even lower than published) and other aspects of a published approach differing from the plate, for me to follow. So, unchangeable gospel it may not be.
 
Wow, now that is an unforgivable oversight on my part. However, the plate still says "ADF required" however. Then that's not absolute? Anyway, you've given me a new way of "approaching" this kind of thing and I'm glad I brought it up. Yes, it wouldn't be complicated. Thanks.
My understanding is that since that restriction appears in the notes box instead of on the plan view, it only applies to the published missed approach procedure. So if you get the alternate missed approach instructions from ATC, the restriction no longer applies.
 
My understanding is that since that restriction appears in the notes box instead of on the plan view, it only applies to the published missed approach procedure. So if you get the alternate missed approach instructions from ATC, the restriction no longer applies.

I posted a similar question about DME. In other words, if it says DME required notes box, can you ask for alternate missed instructions that doesn't require that equipment and legally fly the approach? One poster suggested it was ok, and another said it was not.
 
I posted a similar question about DME. In other words, if it says DME required notes box, can you ask for alternate missed instructions that doesn't require that equipment and legally fly the approach?

My understanding is yes, but only if there is an alternate missed approach fix that doesn't require DME depicted on the chart.

One poster suggested it was ok, and another said it was not.
My recollection is that the information was posted by someone who is knowledgeable in such matters, but I don't remember specifically whom. If I find my source, I'll post it.
 
Last edited:
(1) Where certain equipment is required for procedure entry from the en route environment, enter the following in Additional Flight Data: “Chart planview note: ADF REQUIRED”; or, “ADF OR DME REQUIRED.”

(2) Where other navigation equipment is required to complete the approach; e.g., VOR, ILS, or other non-ADF approaches requiring ADF or DME for missed approach, use: “Chart note: ADF required”, or “Chart note: DME required.” When radar vectoring is also available, use: “Chart note: ADF or Radar required.”

From https://www.faa.gov/about/office_or...0/afs420/acfipg/media/open/Hist_13-02-312.pdf
 
Thanks. Also, from AIM 5-4-5a3(b):

In some cases, other types of navigation
systems including radar may be required to execute
other portions of the approach or to navigate to the
IAF (e.g., an NDB procedure turn to an ILS, an NDB
in the missed approach, or radar required to join the
procedure or identify a fix). When radar or other
equipment is required for procedure entry from the
en route environment, a note will be charted in the
planview of the approach procedure chart
(e.g., RADAR REQUIRED or ADF REQUIRED).
When radar or other equipment is required on
portions of the procedure outside the final approach
segment, including the missed approach, a note will
be charted in the notes box of the pilot briefing
portion of the approach chart (e.g., RADAR
REQUIRED or DME REQUIRED). Notes are not
charted when VOR is required outside the final
approach segment. Pilots should ensure that the
aircraft is equipped with the required NAVAID(s) in
order to execute the approach, including the missed
approach.

NOTE−
Some military (i.e., U.S. Air Force and U.S. Navy)
IAPs have these “additional equipment required”
notes charted only in the planview of the approach
procedure and do not conform to the same application
standards used by the FAA.
 
I really wasn't trolling. And, if I'm breaking a rule I generally do it reluctantly, infrequently and with some thought. And, I'm not likely to break more than one at a time with plenty of margin for downsides. I know that doesn't help the religious but I'm sure at least half of them do the same.
I'm hardly one of the religious about much of anything. And I have very little doubt a 10 year old obsolete handheld GPS will get you to that NDB waypoint more accurately than an ADF receiver. I'll even go as far as to say, if I had both and the two tracks disagreed, I'd follow the GPS unless they were so different as to indicate something was very wrong.

But I see what you are describing as being willing to forego following an official procedure as designed (which includes a requirement for certain equipment) in exchange for some minor convenience and guessing it will probably be ok. And yes, it's a matter of degree rather than kind, but to continue the driving analogy, I see this more as deciding it will be ok to go the wrong way down a one way street than 7 mph over the speed limit.
 
I'm hardly one of the religious about much of anything. And I have very little doubt a 10 year old obsolete handheld GPS will get you to that NDB waypoint more accurately than an ADF receiver. I'll even go as far as to say, if I had both and the two tracks disagreed, I'd follow the GPS unless they were so different as to indicate something was very wrong.

But I see what you are describing as being willing to forego following an official procedure as designed (which includes a requirement for certain equipment) in exchange for some minor convenience and guessing it will probably be ok. And yes, it's a matter of degree rather than kind, but to continue the driving analogy, I see this more as deciding it will be ok to go the wrong way down a one way street than 7 mph over the speed limit.

OK, I can live (or not) with your characterization of what I'm doing and understand its seriousness. Perhaps I will rethink this. However "luvflyin" has given me a way to do nearly the same thing using an alternate miss that I believe turns that one way sign around.

On a minor technical point my Garmin 250XL VFR GPS is an in-panel unit with visual display and an external antenna, a current Jepp database and a unit I never had any signaling problems (or any other problem) with in 20 years of use. I guess it is why all the rest of my panel is now Garmin saving one lonely very obsolete but usable Narco VOR. But I know that's not the point.

Thanks.
 
Wow, now that is an unforgivable oversight on my part. However, the plate still says "ADF required" however. Then that's not absolute? Anyway, you've given me a new way of "approaching" this kind of thing and I'm glad I brought it up. Yes, it wouldn't be complicated. Thanks.

It's "Cimb to 500 then climbing right turn to 3000 direct CRE VORTAC and hold". That's the Alternate Missed Approach published on the Approach Data Worksheet. Ya never know for sure if the controller is going to get creative and make something up even though their not supposed to, but that's what you can expect to get.
 
Basically in VMC, no harm done. If you have a chart and an iPad, just do it. Real IMC? 'Fess up so the controller doesn't have to watch you wander about while you get organized - tell 'em you need help or vectors, or lie, and tell 'em your ADF just died while doing the missed.

It's along shot, but it can happen - protect yourself, do the right thing. . .
 
It's "Cimb to 500 then climbing right turn to 3000 direct CRE VORTAC and hold". That's the Alternate Missed Approach published on the Approach Data Worksheet. Ya never know for sure if the controller is going to get creative and make something up even though their not supposed to, but that's what you can expect to get.
There is a theory floating around that certain "required" notations are waivable, especiallybwhere radar coverage is widespread. And the alternative missed kind of fits into it.

There are indications that the charting workgroup is at least considering a change to the way requirements are noted. In addition to making the reason for "required" cleared, perhaps it will also lead to a change to the current position that "required" means "required" regardless of the reason for it.
 
After an Air Force plane carrying Ron Brown crashed in Croatia, I had to laugh at the conspiracy theorists who thought that assuming someone moved one of the NDBs was necessary in order to explain how someone could screw up an NDB approach!

There was a discussion about the accident here long ago that included the interesting info that the Russians built a lot of dual-ADF approaches that required two ADFs to line up two beacons that were off of the approach and departure ends of the runway.

Seemed like a smart solution to not have to install much more expensive to maintain ILS gear at both ends. Simple transmitters, simple vertical antennas, provided exact runway orientation by overlaying two lines of navigation simultaneously, and on an HSI or similar, it could be on the same instrument with two ADFs feeding the needles.

I don't recall if that sort of approach was actually in the Brown accident, but I recall it being discussed as at least a side thread in that one.

You really would have to move one of the transmitters to sabotage that sort of ADF approach.

If the plate says "ADF required," it's required.

Or approved substitute. ;) e.g., IFR certified GPS. :)
 
My plate that I access via Airnav doesn't show that alternate missed approach procedure, just the missed approach point. Where are the approach worksheets you mention? It the logical procedure but I just see the standard miss procedure.
 
Well, I have another argument besides the slippery slope, and it has to do with the impact on the rest of us. When I ask for a popup IFR clearance, ATC rarely ask the formal question: "Confirm you are IFR rated and equipped" (or whatever). I appreciate that, because it means they trust me, or "us" (GA pilots), to act professionally and play by the rules, and treat us accordingly. Every time you have some misfit cheating the system, e.g. by lying about their credentials or equipment, they erode the trust that ATC has in us, collectively. This is similar to the effect a single GA accident has on the entire community, not just the immediate victims. So I resent losing that trust, which helps getting clearances (and flying in the system) faster and easier, due to those who lie and cut corners at the expense of the rest of us.
And BTW, getting the popup clearance quicker often makes a big difference, e.g. when you are flying into a cloud bank and need to start making evasive maneuvers while ATC is processing your clearance.
To my knowledge, whether you get asked that question has nothing to do with "trust" (unless the controller knows you personally and your qualifications). They're not acting out of suspicion that someone is breaking the law when they ask it; they want to know if they need to be handling the situation as an emergency. Unless the controller knows you, from what controllers have told me s/he is supposed to ask the question any time a pilot finds themselves in deteriorating conditions while operating VFR and the controller suspects the pilot may be a VFR-only getting in over their head and trying to bluff their way out of declaring. Again, not to bust them, but to give them priority handling if it's appropriate.

That said, generally I agree with you. I don't have a lot of sympathy for pilots that bust regs and get into trouble because of it. That does give GA a bad name and is one reason I would never advise someone to break a law. The fact is, though, that people do, and usually get away with it, and as long as they don't endanger anyone in the process (themselves included), I tend to look the other way.
 
Well, let see ... I have a GPS receiver (Garmin 250XL) that says it has internal RAIM checking. The manual, published in 1997, states that RAIM will be available "nearly 100% of the time" - that usually means something like 99.999%. With the airport I'm talking about (KMYR) along the flat east coast it's probably never had a RAIM issue. In all the years I've had the GPS (since 1998) I've never received a RAIM warning. Now, with my ADS-B receiver with WAAS it is my understanding that RAIM is not an issue at least for my transponder/iPad combo. (I do carry 2 iPads). I think it really is a non-issue for me and my flying (east coast, non-mountain).
RAIM is not an issue as long as WAAS is available. If integrity limits for WAAS are exceeded, or is not available because of gov't testing or something, you have to revert to relying on RAIM even if your unit is WAAS-capable. So you should definitely know how to do a RAIM check.
 
There are indications that the charting workgroup is at least considering a change to the way requirements are noted.

I just read in IFR magazine that an additional line was going to be added just below the current header that includes what equipment is required. I think this is a good idea rather than scattering the info around on the plate. Based on what I have read here and elsewhere, scattering the information around is confusing to a lot of pilots.
 
I don't think anyone is confused here about equipment. The discussion has been more about the interpretation of the requirements.
 
To my knowledge, whether you get asked that question has nothing to do with "trust" (unless the controller knows you personally and your qualifications). They're not acting out of suspicion that someone is breaking the law when they ask it; they want to know if they need to be handling the situation as an emergency. Unless the controller knows you, from what controllers have told me s/he is supposed to ask the question any time a pilot finds themselves in deteriorating conditions while operating VFR and the controller suspects the pilot may be a VFR-only getting in over their head and trying to bluff their way out of declaring. Again, not to bust them, but to give them priority handling if it's appropriate.

That said, generally I agree with you. I don't have a lot of sympathy for pilots that bust regs and get into trouble because of it. That does give GA a bad name and is one reason I would never advise someone to break a law. The fact is, though, that people do, and usually get away with it, and as long as they don't endanger anyone in the process (themselves included), I tend to look the other way.

Azure, your experience (or information) is different from mine regarding being asked about qualifications. Normally when I ask for popup IFR it has nothing to do with "deteriorating conditions", or being in a bind. What normally happens is that I try to get from A to B in the most efficient (and safe) manner, so when IFR routing is circuitous, I go VFR direct wherever possible, and switch to IFR (and back to VFR) when conditions dictate. In general, when asking for IFR I can continue VFR indefinitely, though perhaps not to my original destination.
So when asking for the popup I am not stressed, just eager to fly straight and not start circling or weaving around clouds, change altitude, or turn back. I am generally already on Flight Following, so switching to IFR is not much more than a formality. ATC in that situation sometimes comes back with the "are you qualified" question, though quite rarely. I have noticed that in Canada they do that much more than here, perhaps because I am a "foreigner" with that N number (and no "Eh?" :)). So I don't see it as an issue of being under duress, it seems to depend on the specific controller.

Regarding busting regs, I would say it depends. If you drive a bit faster than the speed limit under good road and visibility conditions, I'd consider that "normal". If you go, as Mark said above, wrong way down a one way street because it's more convenient, I'd consider that bad form. In general, if you lie or cheat authorities regarding safety, or otherwise circumvent safety related laws or regs for convenience, I'd consider that anti-social behavior. Flying IFR without the proper qualifications or equipment would be in the latter category IMO.
 
I don't think anyone is confused here about equipment. The discussion has been more about the interpretation of the requirements.

I know. I was just expanding a little on Mark's statement. Sorry for sort of hijacking the thread.
 
Azure, your experience (or information) is different from mine regarding being asked about qualifications. Normally when I ask for popup IFR it has nothing to do with "deteriorating conditions", or being in a bind. What normally happens is that I try to get from A to B in the most efficient (and safe) manner, so when IFR routing is circuitous, I go VFR direct wherever possible, and switch to IFR (and back to VFR) when conditions dictate. In general, when asking for IFR I can continue VFR indefinitely, though perhaps not to my original destination.
So when asking for the popup I am not stressed, just eager to fly straight and not start circling or weaving around clouds, change altitude, or turn back. I am generally already on Flight Following, so switching to IFR is not much more than a formality. ATC in that situation sometimes comes back with the "are you qualified" question, though quite rarely. I have noticed that in Canada they do that much more than here, perhaps because I am a "foreigner" with that N number (and no "Eh?" :)). So I don't see it as an issue of being under duress, it seems to depend on the specific controller.
Yeah, I don't know what the SOP for asking the question is for Canadian controllers. For all I know, Canadian controllers are always supposed to ask the question when a pilot asks for a pop-up. But it isn't a matter of my experience, at least not so much. My information comes from controllers working in the US. (I could be misremembering, but I think Steven was one. It was a couple years ago at least.) My only point is that you haven't really given any evidence that it's a matter of "trust" that would be intact if so many pilots didn't break the rules.

Regarding busting regs, I would say it depends. If you drive a bit faster than the speed limit under good road and visibility conditions, I'd consider that "normal". If you go, as Mark said above, wrong way down a one way street because it's more convenient, I'd consider that bad form. In general, if you lie or cheat authorities regarding safety, or otherwise circumvent safety related laws or regs for convenience, I'd consider that anti-social behavior. Flying IFR without the proper qualifications or equipment would be in the latter category IMO.
I think we agree for the most part. I'd only add filing IFR without the necessary paper qualifications in CAVU weather to the list of activities I wouldn't get too upset about, as long as someone has had the training and is close to their checkride. (Which is not to say that *I* would do it, as I wouldn't. Just that I'd look the other way if someone 'fessed to having done that, under those circumstances.) I'd be a lot more upset if it was someone with no instrument training to speak of, and would, if I thought it could make any difference, try to have a Come To Jesus talk with them.

If you object to that, I think we're just going to have to agree to disagree.
 
Yeah, I don't know what the SOP for asking the question is for Canadian controllers. For all I know, Canadian controllers are always supposed to ask the question when a pilot asks for a pop-up. But it isn't a matter of my experience, at least not so much. My information comes from controllers working in the US. (I could be misremembering, but I think Steven was one. It was a couple years ago at least.) My only point is that you haven't really given any evidence that it's a matter of "trust" that would be intact if so many pilots didn't break the rules.


I think we agree for the most part. I'd only add filing IFR without the necessary paper qualifications in CAVU weather to the list of activities I wouldn't get too upset about, as long as someone has had the training and is close to their checkride. (Which is not to say that *I* would do it, as I wouldn't. Just that I'd look the other way if someone 'fessed to having done that, under those circumstances.) I'd be a lot more upset if it was someone with no instrument training to speak of, and would, if I thought it could make any difference, try to have a Come To Jesus talk with them.

If you object to that, I think we're just going to have to agree to disagree.

No, I can accept that. :)
 
Ask for alternate missed approach instructions.
 
RAIM is not an issue as long as WAAS is available. If integrity limits for WAAS are exceeded, or is not available because of gov't testing or something, you have to revert to relying on RAIM even if your unit is WAAS-capable. So you should definitely know how to do a RAIM check.

Very astute. Most people don't realize there's a difference, but part of that is that the GPS manufacturer may still call the annunciation that somehing is wrong, a "RAIM" indication on the screen, even if it's the WAAS data that the receiver used to determine something was amiss in the time signals being received. And the nomenclature in some of the manuals is even worse, or more mixed.

There's a pretty big hole in Non-Precision Approach airspace without barometric aiding in the SE US right now.

36764113c3c26befe1c7ca060868f902.jpg
 
Along the way I've had several instances where a controller has "modified" approach altitudes (sometimes even lower than published) and other aspects of a published approach differing from the plate, for me to follow.
In a radar environment ATC can, and routinely will, give you lower (down to the MVA in the area) than is published in the plate given that you maintain that altitude until you are established on segment of the approach.
To my knowledge, whether you get asked that question has nothing to do with "trust" (unless the controller knows you personally and your qualifications). They're not acting out of suspicion that someone is breaking the law when they ask it; they want to know if they need to be handling the situation as an emergency. Unless the controller knows you, from what controllers have told me s/he is supposed to ask the question any time a pilot finds themselves in deteriorating conditions while operating VFR and the controller suspects the pilot may be a VFR-only getting in over their head and trying to bluff their way out of declaring. Again, not to bust them, but to give them priority handling if it's appropriate.

What you said here is correct. While the controller is usually generally aware of the wx in their area of control, they are stuck in a dark room many miles away. If a VFR pilot on FF or not asks for a pop-up many controllers think its for deteriorating wx (and usually is). Below is from the .65

10−2−8. RADAR ASSISTANCE TO VFR
AIRCRAFT IN WEATHER DIFFICULTY
a. If a VFR aircraft requests radar assistance when
it encounters or is about to encounter IFR weather
conditions, ask the pilot if he/she is qualified for and
capable of conducting IFR flight.
b. If the pilot states he/she is qualified for and
capable of IFR flight, request him/her to file an IFR
flight plan and then issue clearance to destination
airport, as appropriate.
c. If the pilot states he/she is not qualified for or not
capable of conducting IFR flight, or if he/she refuses
to file an IFR flight plan, take whichever of the
following actions is appropriate......
 
ATC in that situation sometimes comes back with the "are you qualified" question, though quite rarely.
It may be because of the way you ask, (i.e. like to pick back up my IFR, etc) or it may be the area of the country you are in (rare IMC). If a controller does ask you the capable/qualified question it isn't a lack of trust. Unfortunately we live in a CYA world where if anything happens we are under a microscope.
 
It may be because of the way you ask, (i.e. like to pick back up my IFR, etc) or it may be the area of the country you are in (rare IMC). If a controller does ask you the capable/qualified question it isn't a lack of trust. Unfortunately we live in a CYA world where if anything happens we are under a microscope.

I've never had that question (that I recall) when trying to pick up an IFR flight plan already in the system, which I would not call "popup" anyway. For me popup IFR is when there is no filed IFR flight plan at all, just you asking for a clearance out of the blue (or gray :)). Of course, in many cases, since I am normally on FF, there might already be a computer record for the FF, but that's VFR only.
And when they do (very rarely) ask that question, I think it's because they want to be sure you are qualified and equipped. If there are incidents of unqualified pilots (or improperly equipped aircraft) flying the system, it affects their mindset, as does unprofessional sounding communication.
 
Here's a safety-related question to ponder: Which are more reliable, ADF receivers, or VFR GPS receivers? Does anyone have data on this?
In the world of the FAA's avionics experts who hold the certification of IFR avionics, the issue is integrity. The ADF has an identifier. That provides the required integrity. A VFR GPS has accuracy, but lacks integrity and has unknown continuity.
 
My plate that I access via Airnav doesn't show that alternate missed approach procedure, just the missed approach point. Where are the approach worksheets you mention? It the logical procedure but I just see the standard miss procedure.

When an alternate missed approach procedure is created the missed approach holding pattern is depicted on the plate but the procedure is not published to avoid confusion. When the alternate procedure is to be used it will appear in a NOTAM or be issued by ATC.
 
In the world of the FAA's avionics experts who hold the certification of IFR avionics, the issue is integrity. The ADF has an identifier. That provides the required integrity. A VFR GPS has accuracy, but lacks integrity and has unknown continuity.

Small nitpick. IDs are removed by automated monitors like VSWR monitors at the transmitter. It's transmitter integrity.

In the NDB / ADF integrity relationship ONLY the transmitter has "integrity". The integrity check on the receiver working properly is the pilot in the cockpit noticing if the needle is pointing the right way.

Only GPS has receiver integrity. NDB/ADF and VOR/ILS have none. They have transmitter integrity only -- provided by monitoring devices.

The ID itself doesn't technically provide any integrity. It provides an indication to the pilot that the ground based monitors aren't in alarm, as long as it is present. Even then, not always guaranteed.

"Not monitored" is a common FDC NOTAM issued on ground based gear, especially rural in mountainous terrain when the telecom circuit to the site fails in the dead of winter, but that is usually on enroute gear and not allowed on all pieces of an ILS approach. (The LOM being unmonitored I've seen quite a bit, I think.) And those transmitters have their IDs unless the local monitoring on site fails.

I'd have to look and see if there's any unmonitored NDBs in use for ADF approaches anywhere. I suspect not, but it wouldn't surprise me as NDBs die. Bunches of VORs that have that NOTAM issued against them.

Noticing an "unmonitored" NOTAM in the spew of FDC NOTAMs for nearly any XC these days, is a serious eyeball test unless you used software to help categorize the hundred or so that'll spit out for any particular flight plan. ;)
 
Okay, so what about this. ILS 19 KMKC, ADF or DME required. No ADF and my G430 has an exp DB. The ADF is used as the FAF at KENZY which also has a LOM. I don't have an ADF, nor do I have a updated G430, but I do have a beacon. Since I can identify the FAF using the beacon, am I legal?
 
Okay, so what about this. ILS 19 KMKC, ADF or DME required. No ADF and my G430 has an exp DB. The ADF is used as the FAF at KENZY which also has a LOM. I don't have an ADF, nor do I have a updated G430, but I do have a beacon. Since I can identify the FAF using the beacon, am I legal?

I doubt it with an expired database.
 
Okay, so what about this. ILS 19 KMKC, ADF or DME required. No ADF and my G430 has an exp DB. The ADF is used as the FAF at KENZY which also has a LOM. I don't have an ADF, nor do I have a updated G430, but I do have a beacon. Since I can identify the FAF using the beacon, am I legal?

IF you verify the lat/lon for the NDB (as well as all the other points on the approach) are correct, yes, that's legal. Rather labor intensive and not worth it IMO, but legal. Much easier to update the database....

If that airplane is a rental, squawk the expired database with a note "IFR not recommended" and that will get their attention. If it's not a rental, that's why you get DB subscriptions.
 
Small nitpick. IDs are removed by automated monitors like VSWR monitors at the transmitter. It's transmitter integrity.

In the NDB / ADF integrity relationship ONLY the transmitter has "integrity". The integrity check on the receiver working properly is the pilot in the cockpit noticing if the needle is pointing the right way.

Only GPS has receiver integrity. NDB/ADF and VOR/ILS have none. They have transmitter integrity only -- provided by monitoring devices.

The ID itself doesn't technically provide any integrity. It provides an indication to the pilot that the ground based monitors aren't in alarm, as long as it is present. Even then, not always guaranteed.

"Not monitored" is a common FDC NOTAM issued on ground based gear, especially rural in mountainous terrain when the telecom circuit to the site fails in the dead of winter, but that is usually on enroute gear and not allowed on all pieces of an ILS approach. (The LOM being unmonitored I've seen quite a bit, I think.) And those transmitters have their IDs unless the local monitoring on site fails.

I'd have to look and see if there's any unmonitored NDBs in use for ADF approaches anywhere. I suspect not, but it wouldn't surprise me as NDBs die. Bunches of VORs that have that NOTAM issued against them.

Noticing an "unmonitored" NOTAM in the spew of FDC NOTAMs for nearly any XC these days, is a serious eyeball test unless you used software to help categorize the hundred or so that'll spit out for any particular flight plan. ;)
All well and good. To keep it in pilot-speak "ADF Required" is FAR Part 97. The protected airspace for a conventional missed approach is quite large. ADF is lousy; it has no science behind it whatsoever. Nonetheless, hearing the identifier satisfies the FAA. Making sure the needle is pointed generally where it should is the pilot's responsibility, as you stated.
 
Back
Top