![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]() I think this is the problem. I'd expect MOVER to be the first fix once the approach is loaded and I expand the approach in the flight plan view. I could then go Direct-to EWTOF quite easily and still be in proper sequence. However, the first fix is UBBEP. I replicated this behavior on the 480 sim, as well. How do I load the approach such that at least all of the fixes from the IAF (in this case MOVER) are there and ready to go? I can't seem to find a way to make this happen. I'd like it to either magically be there when the approach is loaded or at least allow me to select the applicable transition. No dice. Thanks, --Chris Mike Adams wrote: Sam Spade wrote: This handling is now approved and is no problem whatsoever with a Garmin 400 or 500. Is it with the 480? It works much the same on the 480. You have to put in the approach transition from the applicable IAF, MOVER in this case, Execute it, and then do a Direct-to EWTOF as a separate action. The only problem, mentally, is that you have to look on the chart to find the applicable transition that contains the waypoint you're looking for, rather than being able to select it directly on the approach menu. Mike |
#2
|
|||
|
|||
![]()
Chris Quaintance wrote:
I think this is the problem. I'd expect MOVER to be the first fix once the approach is loaded and I expand the approach in the flight plan view. I could then go Direct-to EWTOF quite easily and still be in proper sequence. However, the first fix is UBBEP. I replicated this behavior on the 480 sim, as well. How do I load the approach such that at least all of the fixes from the IAF (in this case MOVER) are there and ready to go? I can't seem to find a way to make this happen. I'd like it to either magically be there when the approach is loaded or at least allow me to select the applicable transition. No dice. Huh, I get the choice of Vectors, MOVER, ISIFU, and SHOEY. Picking any other than VECTORS gives me the the EWTOF waypoint. Are you sure you selected something OTHER than vectors (and you did remember to EXEC it!) |
#3
|
|||
|
|||
![]()
Mike Adams wrote:
Sam Spade wrote: This handling is now approved and is no problem whatsoever with a Garmin 400 or 500. Is it with the 480? It works much the same on the 480. You have to put in the approach transition from the applicable IAF, MOVER in this case, Execute it, and then do a Direct-to EWTOF as a separate action. The only problem, mentally, is that you have to look on the chart to find the applicable transition that contains the waypoint you're looking for, rather than being able to select it directly on the approach menu. Well in this case, they all have it except for Vectors. There is only one IAF (which there are two additional transitions leading to). |
#4
|
|||
|
|||
![]()
In article ,
Sam Spade wrote: Roy Smith wrote: "Chris Quaintance" wrote: Hi Folks- Please forgive what is probably a simple question regarding GPS approaches. I am new the the /G world. I was out flying my 182P today to do some practice approaches. The airplane is equipped with a GNS480 and I have a Garmin 296 on the yolk. I was buzzing around NW of the Salinas airport on vectors and was told to expect the GPS13 approach as I requested. So far, so good. Fight plan entered into the 480 and the 296, approach loaded on both. Here's the approach: http://www.naco.faa.gov/d-tpp/0701/00363G13.PDF NorCal cleared me direct EWTOF at 3200, cleared for the approach. When looking at the approach on both the 480 and the 296, it seemed to commence at UBBEP rather than EWTOF. Yeah, right, you got a bum clearance. I had a similar experience not long ago and wrote about it here (http://tinyurl.com/yt8vkn). It's pretty common. The problem is that while from the point of view of somebody sitting in a dark room watching blips move around a screen, it's a perfectly reasonable thing to have you do, the software in the GPS wants you to either start the approach from an IAF, or get vectors to final. It would be nice if controllers gave clearances that were flyable, but the often don't, and then you're struggling to figure out how to tell the GPS to do something it doesn't want to do. Roy, This handling is now approved and is no problem whatsoever with a Garmin 400 or 500. Is it with the 480? At least with the software rev we've got, it is. When you select an approach, the only things that come up in the menu are Vectors and all the IAFs. I believe you can fake it out by looking on the approach plate, figuring out which IAF you can select that gives you a route including the specified IF, load that up, then go into FPL mode, scroll down to the IF, and do -D- to that. That's a lot of fumbling, looking, and button-pushing to do at a busy time of the flight. It ATC is allowed to send you direct to an IF, then the distinction between IF and IAF has, for all practical matters, been eliminated. If that's the case, then the databases and/or software needs to be updated to have the IFs show up in the menu. |
#5
|
|||
|
|||
![]()
Roy Smith wrote:
In article , Sam Spade wrote: Roy Smith wrote: "Chris Quaintance" wrote: Hi Folks- Please forgive what is probably a simple question regarding GPS approaches. I am new the the /G world. I was out flying my 182P today to do some practice approaches. The airplane is equipped with a GNS480 and I have a Garmin 296 on the yolk. I was buzzing around NW of the Salinas airport on vectors and was told to expect the GPS13 approach as I requested. So far, so good. Fight plan entered into the 480 and the 296, approach loaded on both. Here's the approach: http://www.naco.faa.gov/d-tpp/0701/00363G13.PDF NorCal cleared me direct EWTOF at 3200, cleared for the approach. When looking at the approach on both the 480 and the 296, it seemed to commence at UBBEP rather than EWTOF. Yeah, right, you got a bum clearance. I had a similar experience not long ago and wrote about it here (http://tinyurl.com/yt8vkn). It's pretty common. The problem is that while from the point of view of somebody sitting in a dark room watching blips move around a screen, it's a perfectly reasonable thing to have you do, the software in the GPS wants you to either start the approach from an IAF, or get vectors to final. It would be nice if controllers gave clearances that were flyable, but the often don't, and then you're struggling to figure out how to tell the GPS to do something it doesn't want to do. Roy, This handling is now approved and is no problem whatsoever with a Garmin 400 or 500. Is it with the 480? At least with the software rev we've got, it is. When you select an approach, the only things that come up in the menu are Vectors and all the IAFs. I believe you can fake it out by looking on the approach plate, figuring out which IAF you can select that gives you a route including the specified IF, load that up, then go into FPL mode, scroll down to the IF, and do -D- to that. That's a lot of fumbling, looking, and button-pushing to do at a busy time of the flight. Yes, but once you select one of the IAFs and it loads the approach into the active flight plan, aren't all of the waypoints then available for a direct-to operation? Matt |
#6
|
|||
|
|||
![]()
In article ,
Matt Whiting wrote: Yes, but once you select one of the IAFs and it loads the approach into the active flight plan, aren't all of the waypoints then available for a direct-to operation? Yes, but it would still be a lot simplier if the IF just showed up in the initial menu. |
#7
|
|||
|
|||
![]()
Roy Smith wrote:
It ATC is allowed to send you direct to an IF, then the distinction between IF and IAF has, for all practical matters, been eliminated. If that's the case, then the databases and/or software needs to be updated to have the IFs show up in the menu. It will take quite a few years for the FAA to identify all the IFs. Direct-to-the IF is not an "if" for RNAV IAPs. ;-) It's been in the AIM and 7110.65 for about a year now. |
#8
|
|||
|
|||
![]() "Sam Spade" wrote in message ... Roy Smith wrote: It ATC is allowed to send you direct to an IF, then the distinction between IF and IAF has, for all practical matters, been eliminated. If that's the case, then the databases and/or software needs to be updated to have the IFs show up in the menu. It will take quite a few years for the FAA to identify all the IFs. Direct-to-the IF is not an "if" for RNAV IAPs. ;-) It's been in the AIM and 7110.65 for about a year now. What's to identify? If it is not an IAF, and not the FAF, and is on an intermediate segment, it is an IF. Why does it need to be "identified"? PCG: INTERMEDIATE FIX- The fix that identifies the beginning of the intermediate approach segment of an instrument approach procedure. The fix is not normally identified on the instrument approach chart as an intermediate fix (IF). Intermediate Approach- The segment between the intermediate fix or point and the final approach fix. (Is that circular, or what?) |
#9
|
|||
|
|||
![]() rant mode Having earned my instrument rating and done all my flying behind panels that do NOT include an IFR GPS, I frequently find myself a little queasy when I read these posts about GPS approaches. I'm a young man (33) and am a professional in the computer industry (or was, until I decided to go back to grad school) and yet, I find the complexity of operating a GPS just plain outrageous. I've rented aircraft with panel GPS and fiddled with the simulators on my PC and I always come away with this feeling of "argggh!" this is way too hard. I think the people who invented these panel units (or set up the IFR certification for them) seriously screwed up by not fully appreciating what was good about the old nav radios. To me, the nice thing is that using a nav radio is NOT A NEGOTIATION. You set it and that's that. You can do it ahead of time. You can change it at any time, without updating a plan, etc. You can put a frequency in there long before what appears on the nav head will make sense -- and that's okay. You as the pilot get to decide when to look at the needle. With these GPS systems it seems like you are constantly dealing with the after-effects of some engineer/programmer who is not in the air with you. Oh, and here's another nice thing about nav radios. They look and work the same in a 737 and a 152. But god forbid you jump into an aircraft with a different GPS unit than the one you're familiar with. You're gonna be in trouble! I dunno. I get what's great about GPS. I have a handheld (196) and like it. (And it's flightplan logic is substantially easier than a 430/530, btw). Aviation used to represent the cutting edge in human factors research. What happened? /rant mode -- dave j |
|
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
R172K Approach Configuration | facpi | Instrument Flight Rules | 10 | January 5th 07 03:58 PM |
RNAV vectors | Dan Luke | Instrument Flight Rules | 74 | December 26th 06 10:31 PM |
Trust those Instruments.... Trust those Instruments..... | A Lieberman | Instrument Flight Rules | 1 | May 2nd 06 03:54 PM |
Approach Question- Published Missed Can't be flown? | Brad Z | Instrument Flight Rules | 8 | May 6th 04 04:19 AM |
Why is ADF or Radar Required on MFD ILS RWY 32 Approach Plate? | S. Ramirez | Instrument Flight Rules | 17 | April 2nd 04 11:13 AM |