KJFZ approach entry question

May a feeder route be located between the IAF and the IF on an IAP?
What would be the point? There is already an Initial Approach Segment there. Feeders connect you from Airways to the Approach Fixes.
 
Has anyone said anything about reporting the charting error, i.e., a NoPT note on a chart that doesn't have a PT depicted?
 
Has anyone said anything about reporting the charting error, i.e., a NoPT note on a chart that doesn't have a PT depicted?
Questioned, yes. But it's not a Chart Error. The official response is below and they basically say it needs to be two steps. First you'd get a Clearance to the published Hold, then once established there, ATC would give you another Clearance for the Approach. And the NoPT Note is valid. If you come from within that range, you just turn inbound and continue on with the Approach. Reality from the South I'm sure would be Radar Vectors to a Straight In, but it was a great theoretical question posed.

FAA Response:
When the procedure published with the note, there wasn't any 8260.19 guidance for arrival holding, so the HIL note was used.

There is guidance in the .19 now, and should the procedure be amended, that note should be changed to current format exampled in the .19:

Example: ?CHART PLANVIEW NOTE: PROCEDURE NA VIA V343 NORTHEAST BOUND WITHOUT HOLDING AT JOXIT. ATC CLEARANCE REQUIRED
 
Has anyone said anything about reporting the charting error, i.e., a NoPT note on a chart that doesn't have a PT depicted?

Questioned, yes. But it's not a Chart Error. <snip>
I.e., they wanted you to fly the hold from the very beginning so turning left isn't the "correct" answer after all. Some here must be feeling a little egg on the face now. :)

Bluefield is some 27 NM beyond the outer limit of the MSA but happily the published 7000 ft limit appears to work there too just the same because all the MEAs south of Bluefield are above 6000 feet.

Coming from the south shouldn't mean you're in a radar environment, AFAIK, as long as you're in service volume limits from Bluefield.

And where does the idea you need approved RNAV come from?

Good thread, though.
 
Last edited:
I.e., they wanted you to fly the hold from the very beginning so turning left isn't the "correct" answer after all. Some here must be feeling a little egg on the face now. :)
Sigh...sounds like you fell off the wagon somewhere. No, the clarified note proves they want you to obtain a holding clearance if you want to enter the hold. The approach clearance in the original scenario does not include a holding clearance, thus, you may not enter the hold. Turning left is the correct answer.
 
Oddly the RNAV (GPS) RWY 23 (same runway) has a hold-in-loo on it.
 
Sigh...sounds like you fell off the wagon somewhere. No, the clarified note proves they want you to obtain a holding clearance if you want to enter the hold. The approach clearance in the original scenario does not include a holding clearance, thus, you may not enter the hold. Turning left is the correct answer.
We'll have to agree to disagree. The FAA has admitted they threw in a substitute note because they had no criteria to write what they really mean — so they used the closest verbiage they had at the time. We agree a clearance for the approach should be settled in view of the ambiguous language, but what if you're lost comms? Since ATC wants you to do the hold they won't (hopefully) give you a clearance like stated in the OP, they'll include the hold. But you don't know that, so safety first.

EDIT: Put another way, the NOPT note is the exception that proves the rule. If a certain quadrant is allowed to come straight-in, the rest are not. We don't know WHY we aren't allowed, but does it matter? The hold is surveyed and is safe, that's all that matters.
 
Last edited:
I.e., they wanted you to fly the hold from the very beginning so turning left isn't the "correct" answer after all. Some here must be feeling a little egg on the face now. :)

Bluefield is some 27 NM beyond the outer limit of the MSA but happily the published 7000 ft limit appears to work there too just the same because all the MEAs south of Bluefield are above 6000 feet.

Coming from the south shouldn't mean you're in a radar environment, AFAIK, as long as you're in service volume limits from Bluefield.

And where does the idea you need approved RNAV come from?

Good thread, though.
None of the above applies to the hypothetical dilemma facing a pilot in the hypothetical scenario posed by the OP, a scenario which would not occur in the real world for reasons previously stated. Those who suggested a left turn were responding to the hypothetical dilemma with a hypothetical solution based on the hypothetical scenario.

All characters and events depicted in this film are entirely fictitious. Any similarity to actual persons, living or dead, or to actual events is purely coincidental. No eggs were harmed in the production of this film.
 
EDIT: Put another way, the NOPT note is the exception that proves the rule. If a certain quadrant is allowed to come straight-in, the rest are not. We don't know WHY we aren't allowed, but does it matter? The hold is surveyed and is safe, that's all that matters.
ATC clearances that allow you to skip part of the procedure are more common than not.
 
You need examples? How many procedure turns have you done?
A lot. Mostly during my IR training, flight reviews and IPC’s. Wasn’t keeping count but it’s easily more than 50. And I’ve issued a lot. That would be well into the hundreds, maybe thousands.
 
the hypothetical scenario posed by the OP, a scenario which would not occur in the real world for reasons previously stated.
I wouldn’t go that far. I see real world applications. Radar vectors to the final approach course are indeed common, but it's a mistake to think they are universal. I can see reasons why they might not be used for this approach.
 
Last edited:
None of the above applies to the hypothetical dilemma facing a pilot in the hypothetical scenario posed by the OP, a scenario which would not occur in the real world for reasons previously stated.
I think you've spent too much time at the top of the food chain. :) I can easily imagine "real-world", say, coming up from Charlotte direct to BLF on an off-airway routing, getting the clearance, descending and reviewing the chart. When I see the ambiguity, I try to call and get no answer because in the mountains down low, it happens sometimes. It's dark, it's raining, it's windy over the hills and I'm concerned. But I don't know what I don't know, so I'm playing it safe. I can't imagine what this "hypothetical-world" thing is of which you speak.
 
Last edited:
I think you've spent too much time at the top of the food chain. :)
Oh, if only that were true! Prior to my 121 career, I spent several thousand hours flying single-pilot IFR, a significant portion of which included operations in non-radar environments. And some of those non-radar environments were in the mountainous regions of the western states.
I can easily imagine "real-world", say, coming up from Charlotte direct to BLF on an off-airway routing, getting the clearance, descending and reviewing the chart. When I see the ambiguity, I try to call and get no answer because in the mountains down low, it happens sometimes. It's dark, it's raining, it's windy over the hills and I'm concerned. But I don't know what I don't know, so I'm playing it safe. I can't imagine what this "hypothetical-world" thing is of which you speak.
As you undoubtedly know, in the real world you would have obtained the latest wx at JZF, figured out what approach you want to fly, and coordinated your intentions with ATC 15-30 minutes before arrival. If not, ATC would query you. If you requested vectors to intercept the localizer, you would have asked to intercept at NAVIC, bypassing BLU altogether. The controller would then provide you a nice 30 degree intercept (or less). In no case would a competent controller have vectored you to BLU with an intercept angle greater than 90 degrees, as stipulated by the OP, and if such a clearance were issued to you, you would have keyed the mic and negotiated a better deal.

The OP does not represent a real-world scenario--at least, not in my real world. It's merely a hypothetical situation with no real answer.
 
What would be the point? There is already an Initial Approach Segment there. Feeders connect you from Airways to the Approach Fixes.

Isn’t a feeder route by definition between the enroute structure and an IAF?
Yes, and I didn’t understand how your post applied to the thread.
 
As you undoubtedly know, in the real world you would have obtained the latest wx at JZF, figured out what approach you want to fly, and coordinated your intentions with ATC 15-30 minutes before arrival. If not, ATC would query you. If you requested vectors to intercept the localizer, you would have asked to intercept at NAVIC, bypassing BLU altogether. The controller would then provide you a nice 30 degree intercept (or less). In no case would a competent controller have vectored you to BLU with an intercept angle greater than 90 degrees, as stipulated by the OP, and if such a clearance were issued to you, you would have keyed the mic and negotiated a better deal.

The OP does not represent a real-world scenario--at least, not in my real world. It's merely a hypothetical situation with no real answer.
Sorry, but if you think that, I think your "real world" is limited. I agree with the early part of your answer.
in the real world you would have obtained the latest wx at JZF, figured out what approach you want to fly, and coordinated your intentions with ATC 15-30 minutes before arrival. If not, ATC would query you.
But beyond that, I think there is a real answer and that it's a real-world scenario.
 
Yes, and I didn’t understand how your post applied to the thread.
I many have misstated something. But I don't understand what you didn't understand.

BTW
Can Atlanta Center provide Vectors for this approach? I suspect they can’t.
No one responded to this, but I agree with you. That's the question @Roger Wilco's real world pilot isn't asking himself.
 
No one responded to this, but I agree with you. That's the question @Roger Wilco's real world pilot isn't asking himself.
Well, you certainly have me there. I do not know whether radar services are available and shouldn’t have made the assumption. If radar vectors are not available, ATC would so advise and issue an appropriate clearance to join the requested approach. Should any ambiguity arise, resolve the issue with ATC prior to accepting the clearance (per my reply in #25, and replies by others).
 
I do not know whether radar services are available...
I asked Gemini! Here's what he/she says:

  • The Sector Map Constraint: On the official FAA ZTL chart, the grid sector containing NAYIC and KJFZ (TVAM15) mandates a strict MIA floor of 6,000 feet MSL. Below 6,000 feet, line-of-sight radar tracking is not guaranteed due to terrain masking. [1]
  • The Approach Profile Constraint: On the official KJFZ LOC/DME RWY 25 approach plate, the intermediate fix NAYIC dictates a minimum crossing altitude of 5,900 feet MSL.
  • The Trap: Because 5,900 feet is below the 6,000-foot radar floor, a controller cannot legally assign you a vectoring heading at the approach's required intercept altitude. To vector you, they would have to keep you at 6,000 feet, which puts you above the published intermediate segment altitude.
Here's how Gemini says ATC can get around it:

Much of the confusion in aviation circles stems from mixing up Radar Vectors (Chapter 5 of the 7110.65) with RNAV Routing (Chapter 4 of the 7110.65). [1]​
  • Vectors (Not Allowed): A controller cannot say: "Turn left heading 220, maintain 6,000 until advised, vectors to NAYIC." They lack the radar coverage floor to monitor your flight path off a published structure below 6,000 feet.
  • Direct To (Allowed): A controller can say: "Proceed direct NAYIC, maintain 6,000 until NAYIC, cleared straight-in LOC/DME Runway 25 approach."
Why is "Direct" allowed but "Vector" is not? Because when you are cleared direct to a fix, you are on a pilot-navigated RNAV flight path. The responsibility for terrain clearance shifts to your onboard certified GPS and the published approach segments.​
Once your GPS guides you to NAYIC on a direct track, you are officially established on a published portion of the approach, allowing you to legally descend to 5,900 feet without requiring the controller to have low-altitude radar visibility.​

Gemini is cool even if it turns out to be full of smoke.
 
Well, you certainly have me there. I do not know whether radar services are available and shouldn’t have made the assumption. If radar vectors are not available, ATC would so advise and issue an appropriate clearance to join the requested approach. Should any ambiguity arise, resolve the issue with ATC prior to accepting the clearance (per my reply in #25, and replies by others).
That's the part I agree with. You are going to resolve this well before you are cleared for the approach. It should not - and most likely will not - be a surprise.

FWIW, here's what I see when I look at the approach. As soon as I see an approach handled by Center rather than a TRACON, my first thought is, "is their MIA low enough for vectors to the final approach course?" Sometimes yes, sometimes no. Here, the fact that it's in mountainous terrain increases the likelihood the answer is "no" (although I happened to learn this one in some of the flattest terrain in the US - the Colorado plains). As usual, the enroute chart altitudes also provide a few hints.

I absolutely agree with you about the need for advance clarification. Just like pretty much every approach to a nontowered airport, ATC is going to ask, "say approach request." The pilot needs to be prepared for that and that's the time to get it all clarified. On this one, if my direction of flight is from the south, I'm definitely not assuming vectors. ATC might well offer wat they can do, but if not, I am going to ask whether they can vector me for a straight in. If not, it's simple to request the arrival hold to reverse course.
 
I asked Gemini! Here's what he/she says:

  • The Sector Map Constraint: On the official FAA ZTL chart, the grid sector containing NAYIC and KJFZ (TVAM15) mandates a strict MIA floor of 6,000 feet MSL. Below 6,000 feet, line-of-sight radar tracking is not guaranteed due to terrain masking. [1]
  • The Approach Profile Constraint: On the official KJFZ LOC/DME RWY 25 approach plate, the intermediate fix NAYIC dictates a minimum crossing altitude of 5,900 feet MSL.
  • The Trap: Because 5,900 feet is below the 6,000-foot radar floor, a controller cannot legally assign you a vectoring heading at the approach's required intercept altitude. To vector you, they would have to keep you at 6,000 feet, which puts you above the published intermediate segment altitude.
Here's how Gemini says ATC can get around it:

Much of the confusion in aviation circles stems from mixing up Radar Vectors (Chapter 5 of the 7110.65) with RNAV Routing (Chapter 4 of the 7110.65). [1]​
  • Vectors (Not Allowed): A controller cannot say: "Turn left heading 220, maintain 6,000 until advised, vectors to NAYIC." They lack the radar coverage floor to monitor your flight path off a published structure below 6,000 feet.
  • Direct To (Allowed): A controller can say: "Proceed direct NAYIC, maintain 6,000 until NAYIC, cleared straight-in LOC/DME Runway 25 approach."
Why is "Direct" allowed but "Vector" is not? Because when you are cleared direct to a fix, you are on a pilot-navigated RNAV flight path. The responsibility for terrain clearance shifts to your onboard certified GPS and the published approach segments.​
Once your GPS guides you to NAYIC on a direct track, you are officially established on a published portion of the approach, allowing you to legally descend to 5,900 feet without requiring the controller to have low-altitude radar visibility.​

Gemini is cool even if it turns out to be full of smoke.
Who/what is Gemini ?
 
I many have misstated something. But I don't understand what you didn't understand.

BTW

No one responded to this, but I agree with you. That's the question @Roger Wilco's real world pilot isn't asking himself.
It was responded to. We’re trying to figure out what their Radar coverage is there. After that we’ll need to know if they have the required Video Map
 
That's the part I agree with. You are going to resolve this well before you are cleared for the approach. It should not - and most likely will not - be a surprise.

FWIW, here's what I see when I look at the approach. As soon as I see an approach handled by Center rather than a TRACON, my first thought is, "is their MIA low enough for vectors to the final approach course?" Sometimes yes, sometimes no. Here, the fact that it's in mountainous terrain increases the likelihood the answer is "no" (although I happened to learn this one in some of the flattest terrain in the US - the Colorado plains). As usual, the enroute chart altitudes also provide a few hints.

I absolutely agree with you about the need for advance clarification. Just like pretty much every approach to a nontowered airport, ATC is going to ask, "say approach request." The pilot needs to be prepared for that and that's the time to get it all clarified. On this one, if my direction of flight is from the south, I'm definitely not assuming vectors. ATC might well offer wat they can do, but if not, I am going to ask whether they can vector me for a straight in. If not, it's simple to request the arrival hold to reverse course.
I do too. Flat lands maybe, areas with terrain is usually a certain no. ATC’s job is separation, not holding your hand into an approach. If you do much international flying, you will be shocked to learn there is no radar. I don’t believe most of the Caymans has radar service today. I know CYB still isn’t served by radar.
 
Last edited:
Who/what is Gemini ?
Google that question and see if it answers you in person. I just ask a plain language question in the Google search engine and more often than not their version of AI offers up an answer. From there you can ask subsequent questions and get into along conversation. But don't take everything as the Gospel. It makes many mistakes. Even still, you can point them out and eventually wind up with something pretty useful.
 
It was responded to. We’re trying to figure out what their Radar coverage is there. After that we’ll need to know if they have the required Video Map
If we're looking for that kind of stuff, might also look for their MIA.
 
Yeah. The coverage could be lower but unusable.
Here's the MIAs. I circled the sector Gemini claims (footnote [1] in the dialog I had with AI and posted above) applies to Tazewell County Airport. Gemini said it indicates 6000 ft.
 

Attachments

That's the part I agree with. You are going to resolve this well before you are cleared for the approach. It should not - and most likely will not - be a surprise.

FWIW, here's what I see when I look at the approach. As soon as I see an approach handled by Center rather than a TRACON, my first thought is, "is their MIA low enough for vectors to the final approach course?" Sometimes yes, sometimes no. Here, the fact that it's in mountainous terrain increases the likelihood the answer is "no" (although I happened to learn this one in some of the flattest terrain in the US - the Colorado plains). As usual, the enroute chart altitudes also provide a few hints.

I absolutely agree with you about the need for advance clarification. Just like pretty much every approach to a nontowered airport, ATC is going to ask, "say approach request." The pilot needs to be prepared for that and that's the time to get it all clarified. On this one, if my direction of flight is from the south, I'm definitely not assuming vectors. ATC might well offer wat they can do, but if not, I am going to ask whether they can vector me for a straight in. If not, it's simple to request the arrival hold to reverse course.
So much for the real world, then. Back to the OP…

In the realm of the hypothetical, the OP provided an approach plate and stipulated the following (hypothetically):

“…direct Bluefield, cross Bluefield at 6,000, cleared Localizer 25 approach." Upon reaching the VOR, what do you do?

With nothing more to go on, RussR supplied the best answer to this hypothetical situation way back in post #2. My only disagreement with his solution is in regard to the >120-degree intercept.
 
So much for the real world, then. Back to the OP…

In the realm of the hypothetical, the OP provided an approach plate and stipulated the following (hypothetically):

“…direct Bluefield, cross Bluefield at 6,000, cleared Localizer 25 approach." Upon reaching the VOR, what do you do?

With nothing more to go on, RussR supplied the best answer to this hypothetical situation way back in post #2. My only disagreement with his solution is in regard to the >120-degree intercept.
Unless things have changed very recently, 120 degrees is correct. For RNAV it’s 90. It used to be 120 also. When it change to 90 I don’t remember. I’ll take a guess about 15 years ago.
 
Unless things have changed very recently, 120 degrees is correct. For RNAV it’s 90. It used to be 120 also. When it change to 90 I don’t remember. I’ll take a guess about 15 years ago.
Reference, please?
 
With nothing more to go on, RussR supplied the best answer to this hypothetical situation way back in post #2. My only disagreement with his solution is in regard to the >120-degree intercept.

And that's a fair disagreement. The 120 deg limitation is a TERPS design standard, not a pilot regulation.

However, to go a little bit deeper on this scenario, we have to first pretend we're flying without GPS.

Old-school flying without GPS, you'd not turn inbound until you actually crossed the BLF VOR. Which means that you will cross well through the course centerline as you turn and will go well to the side of the course as you correct back. This is called "outside turn expansion" and is accounted for in Victor airway design - more airspace is evaluated for obstacles on the outside of a turn than on the inside (V-airway only, not applicable for most GPS routes). Although airways are 4 nm either side of centerline, a faster aircraft at cruise speed can easily take more than 4 nm to turn, and the greater the amount of turn, the more space it takes. Airway design is very generous with outside expansion for this reason.

However, that's for airways. While VOR-based initial segment on an approach procedure are also 4 nm either side of centerline, there is no outside turn expansion applied. This is (as far as I can tell) the main reason for the >120 deg turn prohibition. So if you ARE in the OP's scenario, making more than 120 deg of turn and waiting until you cross the VOR to begin that turn, it is "possible" you could go outside the protected area. Now, that's not very likely in typical light GA aircraft but in something in the 200+ kt range it gets pretty close, especially with strong wind from the "wrong" direction.

So, it's something to at least be aware of.

Now, on the flip side, say you're flying this with a modern GPS with turn anticipation. That potentially faces the opposite problem if you choose to just make the 120+ degree turn to the inbound course. Because in that scenario, the tighter the turn, the more it's going to have to lead the turn. At some combination of ground speed and amount of turn, that turn may have to be made so early that it's outside the protected airspace on the INSIDE of the turn. This is one of the reasons for the 90 deg turn limitation on GPS procedures.
 
Reference, please?

The 120/90 is a TERPS limitation, not a pilot limitation, but I'd say the change was some time around 2009 or 2010 (so pretty close to @luvflyin 's guess), around when we implemented the 8260.54 for RNAV procedure design, and got away from the 8260.38, which allowed 120 degrees. It would take some research to nail that down, but that's about what I remember from when I did that work. I think the ATC vectoring limitation came shortly thereafter.
 
And that's a fair disagreement. The 120 deg limitation is a TERPS design standard, not a pilot regulation.

However, to go a little bit deeper on this scenario, we have to first pretend we're flying without GPS.

Old-school flying without GPS, you'd not turn inbound until you actually crossed the BLF VOR. Which means that you will cross well through the course centerline as you turn and will go well to the side of the course as you correct back. This is called "outside turn expansion" and is accounted for in Victor airway design - more airspace is evaluated for obstacles on the outside of a turn than on the inside (V-airway only, not applicable for most GPS routes). Although airways are 4 nm either side of centerline, a faster aircraft at cruise speed can easily take more than 4 nm to turn, and the greater the amount of turn, the more space it takes. Airway design is very generous with outside expansion for this reason.

However, that's for airways. While VOR-based initial segment on an approach procedure are also 4 nm either side of centerline, there is no outside turn expansion applied. This is (as far as I can tell) the main reason for the >120 deg turn prohibition. So if you ARE in the OP's scenario, making more than 120 deg of turn and waiting until you cross the VOR to begin that turn, it is "possible" you could go outside the protected area. Now, that's not very likely in typical light GA aircraft but in something in the 200+ kt range it gets pretty close, especially with strong wind from the "wrong" direction.

So, it's something to at least be aware of.

Now, on the flip side, say you're flying this with a modern GPS with turn anticipation. That potentially faces the opposite problem if you choose to just make the 120+ degree turn to the inbound course. Because in that scenario, the tighter the turn, the more it's going to have to lead the turn. At some combination of ground speed and amount of turn, that turn may have to be made so early that it's outside the protected airspace on the INSIDE of the turn. This is one of the reasons for the 90 deg turn limitation on GPS procedures.
Very well-stated, and I completely agree. In this example the aircraft would have some additional relief due to the holding pattern, but such an obtuse intercept angle would be, shall we say, less than optimal, regardless.
 
The OP does not represent a real-world scenario--at least, not in my real world.
Nope... It was a "Checkride" scenario. So if the DPE had really posed that scenario, the answer would... er... should have been that you can't fly that clearance.
 
Nope... It was a "Checkride" scenario. So if the DPE had really posed that scenario, the answer would... er... should have been that you can't fly that clearance.
Where was this scenario that the OP said was making its way around social media? What exactly is the “…that clearance…” that would have been issued?
 
Back
Top