Need for what, a minimum en route altitude? If it isn't charted you'll have to undertake the task yourself, as best you can using a VFR sectional instead of the IFR chart.
No, the tower comment is not inappropriate, it's exactly the point.
I assure you that we did not go to Goodland or MCJEF before turning for St. Francis. I filed for a fix and turn prior to Goodland and ATC gave the vector at the fix. A feeder route isn't required as long as there is radar coverage and comms.
It's becoming popular in contested areas to just stamp the plate RADAR REQUIRED and leave it to the controller and the MVA to get you to the FAF.
Kinda makes planning an alternate for lost comm suddenly important in some areas.
Be interesting to ask some controllers where they think a NORDO is going to go if it becomes NORDO in the enroute portion of the flight to a filed airport with no published feeder to get to it and a RADAR REQUIRED stamp on the plate, and no filed alternate. Obviously the usual choices for NORDO apply but what airspace are they really going to clear?
The sad part about direct routing is that it's breaking an integrated *system* designed to fail gracefully by removing the previously obvious options.
I bet the younger the controller the more likely to say the aircraft will continue to the original destination, assuming that most aircraft are /G or iPad /G-minus (minus being legal for navigation).
It's an interesting side effect for sure.
It's becoming popular in contested areas to just stamp the plate RADAR REQUIRED and leave it to the controller and the MVA to get you to the FAF.
Kinda makes planning an alternate for lost comm suddenly important in some areas.
Be interesting to ask some controllers where they think a NORDO is going to go if it becomes NORDO in the enroute portion of the flight to a filed airport with no published feeder to get to it and a RADAR REQUIRED stamp on the plate, and no filed alternate. Obviously the usual choices for NORDO apply but what airspace are they really going to clear?
The sad part about direct routing is that it's breaking an integrated *system* designed to fail gracefully by removing the previously obvious options.
I bet the younger the controller the more likely to say the aircraft will continue to the original destination, assuming that most aircraft are /G or iPad /G-minus (minus being legal for navigation).
It's an interesting side effect for sure.
It's becoming popular in contested areas to just stamp the plate RADAR REQUIRED and leave it to the controller and the MVA to get you to the FAF.
Kinda makes planning an alternate for lost comm suddenly important in some areas.
Be interesting to ask some controllers where they think a NORDO is going to go if it becomes NORDO in the enroute portion of the flight to a filed airport with no published feeder to get to it and a RADAR REQUIRED stamp on the plate, and no filed alternate. Obviously the usual choices for NORDO apply but what airspace are they really going to clear?
The sad part about direct routing is that it's breaking an integrated *system* designed to fail gracefully by removing the previously obvious options.
I bet the younger the controller the more likely to say the aircraft will continue to the original destination, assuming that most aircraft are /G or iPad /G-minus (minus being legal for navigation).
It's an interesting side effect for sure.
It shouldn't require going to a different airport as long as you can make use of the provided feeder(s) and related approaches:It's becoming popular in contested areas to just stamp the plate RADAR REQUIRED and leave it to the controller and the MVA to get you to the FAF.
Kinda makes planning an alternate for lost comm suddenly important in some areas.
This concept was recently shared with me. And wasn't emphasized by either of my instructors. Once I heard it and the logic behind doing it it, it make sense and will likely be something I'd add to my methods.Clark1961 said:I tend to file for an IAF and airport rather than just the airport.
It's hard to imagine where it wouldn't be practical to provide at least one feeder.
It seems there may be a growing disconnect between the way plates are built and the way they may be used. The NDB approaches are one example. Lost comms planning is low priority.
Feeder routes don't have to begin at a VOR.The Denver area and APA in particular has a problem since all the useable VORs are fairly close to DEN. Most of the IAPs used the Falcon VOR and that would totally screw up all of DEN's traffic. Of course in practice nobody ever went to Falcon...
While it may seem logical in one sense, it raises other questions. How do you know which IAF fix to file to? You don't know which approach will be in use at the time. Many times it depends on the winds. If you file a STAR, many of them end in radar vectors or a heading. I've also been given "direct destination" at times, from halfway across the country. This usually changes once you get closer, but there is always the chance you will lose coms during the portion you were direct to the airport.This concept was recently shared with me. And wasn't emphasized by either of my instructors. Once I heard it and the logic behind doing it it, it make sense and will likely be something I'd add to my methods.
Feeder routes don't have to begin at a VOR.
File to the one you want to use if NORDO.How do you know which IAF fix to file to?
"Direct destination" implies "via an SIAP", IMO. How else do you suppose you're going to get below the clouds? If it was meant only to the airport and no further, they'd have to give you holding instructions there with an EFC, which they can't because "airports" aren't authorized "holding fixes".I've also been given "direct destination" at times, from halfway across the country. This usually changes once you get closer, but there is always the chance you will lose coms during the portion you were direct to the airport.
"Direct destination" does not mean direct to the IAF. It means direct to the airport. I think they ATC sometimes says "direct destination" because they don't immediately recognize the identifier. Many other times I have been cleared direct to the airport specifically. If you lose coms then you do what you need to do.File to the one you want to use if NORDO.
"Direct destination" implies "via an SIAP", IMO. How else do you suppose you're going to get below the clouds? If it was meant only to the airport and no further, they'd have to give you holding instructions there with an EFC, which they can't because "airports" aren't authorized "holding fixes".
dtuuri
"Direct destination" does not mean direct to the IAF. It means direct to the airport. ... Many other times I have been cleared direct to the airport specifically. If you lose coms then you do what you need to do.
No, it does not. They say "direct destination".First of all, the word "airport" must follow "destination",
"Direct destination" does not mean via airways or fixes you filed. It means exactly what it sounds like. It does not matter what they did before RNAV was invented. It is available now.FWIW. Before RNAV was invented you could be cleared to the destination airport via airways--which go over VORs not over airports, so how would you have expected to get to the airport back in those days unless via an IAP? Why would the ability to find the geographic center of an airport with modern navigation equipment change the meaning of "cleared <destination> airport"? You can't hold there or actually reach the airport without the IAP, which begins at an IAF.
That's nice....and it doesn't explain why most of the IAPs included FQF...and why the solution is "via vectors" and "radar required"
I'm merely quoting from Order 7110.65.No, it does not. They say "direct destination".
I didn't say that."Direct destination" does not mean via airways or fixes you filed.
A controller half way across the country doesn't know or care what the SFO controllers want. Like you said, you'll be taken off that route long before you reach the airport--they can't even clear you for an approach until they do (again, from 7110.65). And if you lose comms, as per your scenario, YOU don't want to go over the airport either, you want to go to a point where an IAP begins, so you can commence your descent and get out of everybody's hair ASAP, not to mention to avoid running out of fuel after that long cross country trek into a stiff wind.It means exactly what it sounds like. It does not matter what they did before RNAV was invented. It is available now.
Sure, if you lose coms you will want to go to the IAF, and you find your way there, if you can, using whatever nav capability you have. But that doesn't mean that you need to file your flight plan that way. In any case, many times the original flight plan would be negated by subsequent clearances. As I said, this is an argument people have had over and over on this board, so file what you want and use common sense if you have a com failure.A controller half way across the country doesn't know or care what the SFO controllers want. Like you said, you'll be taken off that route long before you reach the airport--they can't even clear you for an approach until they do (again, from 7110.65). And if you lose comms, as per your scenario, YOU don't want to go over the airport either, you want to go to a point where an IAP begins, so you can commence your descent and get out of everybody's hair ASAP, not to mention to avoid running out of fuel after that long cross country trek into a stiff wind.
Sure, if you lose coms you will want to go to the IAF, and you find your way there, if you can, using whatever nav capability you have. But that doesn't mean that you need to file your flight plan that way.
Feeder routes don't have to begin at a VOR.
Clark1961 said he "tends to" file that way.
What would you recommend I use in a /A aircraft without an ADF?
You argue against me then you reference me? That is weird....weird to like the 12th power.
Try to humble yourself a little,./QUOTE]
That is my advise to you....in fact please never reference me again in one of your posts because you tried to use me as an authority and then deny me as an authority. In short, you are bat **** crazy.
No, but you were strongly suggesting it. At least that is what I got out of your posts. In case you haven't figured it out by now, I don't file to an IAF. But it really doesn't matter because, as I said, some do it one way and some do it the other.Clark1961 said he "tends to" file that way. AggieMike88 said he will add that technique to his "methods" (plural). Nobody said you "need" to file that way.
As I said before, you don't necessarily know what that will be, especially at airports with many runways and approaches. I also mentioned that subsequent clearances could negate what you filed anyway.Then you asked how to know which IAF to file to, so I said "File to the one you want to use if NORDO."
I'm sorry, I don't understand your question. Feeder routes exist or not, they aren't made up by the pilot. If radar is required because there are no feeder routes, then you need radar, period. Now if a user group or persistent letter writer were to lobby for some--maybe pilots won't have to land elsewhere the next time the radar goes tango uniform.
That is my advise to you....in fact please never reference me again in one of your posts because you tried to use me as an authority and then deny me as an authority. In short, you are bat **** crazy.
Nobody said you "need" to file that way.
Not. I simply answered your question, and am about to answer it once more...No, but you were strongly suggesting it.
It doesn't matter when you're planning for a NORDO arrival--the airspace is all yours. You might only be equipped for certain approaches or performance issues may dictate certain ones, so you want to know if you can still land there if radar goes out or you arrive with an engine inop and can only hold MEA along a certain route. It's a basic planning step I'm advocating, not that I'm saying you should "always" file to an IAF. You should have one you can rely on in the back of your mind.In case you haven't figured it out by now, I don't file to an IAF. ...
As I said before, you don't necessarily know what that will be, especially at airports with many runways and approaches. I also mentioned that subsequent clearances could negate what you filed anyway.
I'm trying to explain the "SYSTEM" to those who don't or should know better. That's why I quoted this reference earlier (w/my em):The point has been, and you know it, you're just arguing for no reason, that the SYSTEM was designed to have feeders off of the enroute structure to IAFs. The plates are slowly losing those and that forces pilots to have to decide how they're going to file vs what's going to happen in the real world.
You're preaching to the choir.Stamping the plate "RADAR Required" is a lazy cop-out and seems to indicate a distinct lack of understanding by the so-called experts who've forgotten why the regs and charts used to match up.
I checked all the published missed approaches at KFTG and saw none for a 110° heading. A glance at the Denver sectional didn't scare me, although maybe studying it closer might have, so I'm at a loss for what your concern there is. If there's a legit concern, again, you need to raise it with ATC. "Silence implies consent".That 110 heading they give for a missed at FTG is one of those that if you went NORDO right thereafter and didn't know it yet, you'd have been vectored right into the ground before you knew it, if you weren't careful to look at the VFR sectional and were unfamiliar with the terrain around FTG.
I checked all the published missed approaches at KFTG and saw none for a 110° heading. A glance at the Denver sectional didn't scare me, although maybe studying it closer might have, so I'm at a loss for what your concern there is. If there's a legit concern, again, you need to raise it with ATC. "Silence implies consent".
Clark: Wasn't that higher terrain they vectored us toward, just about where the Cirrus guy who got disoriented popped his chute in Actual at night?
That 110 heading they give for a missed at FTG is one of those that if you went NORDO right thereafter and didn't know it yet, you'd have been vectored right into the ground before you knew it, if you weren't careful to look at the VFR sectional and were unfamiliar with the terrain around FTG.
We were definitely a lot lower AGL out there than I'd ever want to go in IMC, that's for sure. I wasn't even that happy with how low they vectored us for VFR really. Definitely an interesting problem over there wedged up against DEN.
Oh my, imagine that. Welcome to insrument flying. For your information it's that way everywhere there's radar not just FTG. It's all the more reason to heed my advice at www.AvClicks.com re: an IFR pilot's mindset. Never rely solely on ATC for obstruction avoidance.Wake up! I've already pointed this out in this thread. The plates for FTG say one thing, ATC's practice is different. In IMC the missed approach is an instruction to fly southeast. Got it now?
Ok, what have you written them and what has been their response? There's two sides to everything and so far I know neither yours nor theirs (simply being radar vectored instead of flying the published missed approach is standard procedure for missed approaches and IFR departures). What are your specific concerns?Silence implies consent? You've typed this a couple times...and your insinuations are inappropriate each time. You don't know what has been communicated to ATC and are deliberately being rude.
Oh my, imagine that. Welcome to insrument flying. For your information it's that way everywhere there's radar not just FTG. It's all the more reason to heed my advice at www.AvClicks.com re: an IFR pilot's mindset. Never rely solely on ATC for obstruction avoidance.
Ok, what have you written them and what has been their response. There's two sides to everything and so far I know neither yours nor theirs (simply being radar vectored instead of flying the published missed approach is standard procedure for missed approaches and IFR departures). What are your specific concerns?
You're concerned that 91.185(c)(1)(ii) would be unsafe to comply with during comm loss on a missed approach at KFTG (you prefer to go to FQF)? What about radar vectors during an IFR departure then? Aren't they about the same?Drop the attitude and read the thread Dave. Denver approach doesn't want anyone to go to FQF but that's what most of the IAPs show. Think it through now and understand what a com loss means...and it's been that way since DEN opened...think about what that means. Only a delusional arrogant ass would think they can change it.
Right. I never said you shouldn't have one in the back of your mind but you were initially advocating filing it, even if you didn't "need" to file it. Those are two different things. I just pointed out scenarios where filing it wouldn't make any difference and you started arguing.It doesn't matter when you're planning for a NORDO arrival--the airspace is all yours. You might only be equipped for certain approaches or performance issues may dictate certain ones, so you want to know if you can still land there if radar goes out or you arrive with an engine inop and can only hold MEA along a certain route. It's a basic planning step I'm advocating, not that I'm saying you should "always" file to an IAF. You should have one you can rely on in the back of your mind.
No, ma'am. I never said I advocate always filing to an IAF. I only explained, in answer to your question, which IAF to file to if you were filing like Clark1961 and AggieMike88 proposed. And I'm not here to argue with anybody, just trying to set the record straight when I happen to see bad or confusing advice being dispensed to newbies by folks who don't or should know better--which is my modus operandi.Right. I never said you shouldn't have one in the back of your mind but you were initially advocating filing it, even if you didn't "need" to file it. Those are two different things. I just pointed out scenarios where filing it wouldn't make any difference and you started arguing.