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 |
#11
|
|||
|
|||
CFII_ASC wrote:
Matt, There are *no* GPS approaches that are authorized to be flown in the OBS mode. In order for you to fly a GPS approach, it is required that you approach the final approach fix in the LEG mode, and the TERM or ARM annunciator light lit on your external control panel. As you hit 2nm outside the FAF, the annunciators should change from ARM to ACTV (known as the approach mode on some other mfgs boxes). IT IS ILLEGAL TO CONTINUE (DESCEND) inside the FAF if you do not get the ACTV light--and you will never get it in the OBS mode. That is what I thought, but I couldn't figure out why it wouldn't sequence. The common problem with getting a GPS approach to work is that you miss one of the nine or so conditions that are required to be true at the FAF-2nm point to allow the box to switch into ACTV. Look in the manual on your KLN89B, and you will see a list of those required by your box, but they are all pretty similar since they are written into the TSO under which all of the approach-certified boxes are approved. Typically, to get it to go into the ACTV mode, these things must be true: 1. In LEG mode (not OBS) 2. In ARM mode (this comes up when you have a valid approach loaded, and you are within 30nm) 3. Valid RAIM now, and predicted at FAF and MAP 4. Outside FAF (110 degree arc each side of FAF) 5. Distance to FAF decreasing 6. Within 2nm of FAF, but not past (inside) FAF 7. NAV/GPS switch must be in the GPS position 8. No localizer frequency may be loaded into NAV 1 (some boxes) You probably had one of these conditions not met. Yes, obviously, I'm just not sure which one. I know that 1, 3, 4, 5, 6 and 7 were satisfied. I don't remember if I checked the ARM annunciator. I had flown the LOC 28 prior to the GPS 28 and still had that frequency tuned, however, it was in the #2 NAV as the #1 NAV is removed for repairs. I didn't realize that the GPS interfaced to the NAVs, so that may be it. I'll check the King manual shortly to see if that might be the problem. I later flew a GPS at N38 with no problem, but by then I'd tuned the NAV to a non-localizer frequency. The approach plate shows a procedure turn type approach. Assuming you did this approach without ATC vectors to final, it should run something like this: Clear the flight plan I didn't clear the flight plan, so that may have been the problem. I flew a flight plan from ELM to N38, but simply did a DIRECT to ELZ and therefore FP 0 would have still had ELM to N38. That may have been my error. Check Nav 1, and make sure no valid localizer freq is in that radio. Didn't have a NAV 1 that day! Set the GPS/NAV switch to GPS I don't recall our club plan having such a switch. Is this required for all IFR installations? This wasn't mentioned during my ICC either. Load the approach (APT 8 page); select the version of the approach that uses the LOM as the IAF. On this approach it is also the FAF, and in the 89B they are the same waypoint, which can be a point of confusion. Activate the approach, or put the cursor on the FAF waypoint in the flight plan and hit direct-enter-enter (proceed direct to the IAF/FAF) I believe I did the normal approach activation such that it asks you if you want to insert the approach waypoints into the flight plan. I said yes thinking that my "flight plan" was the direct to ELZ, however, I'll bet it added the approach to my FP 0 which was ELM to N38. That very well would confused the GPS royally, and me in rapid succession. :-) Now, heres the trick: push the OBS button on the external control panel; this puts your system into the OBS mode and DISABLES AUTOMATIC WAYPOINT SEQUENCING. We have to do this (temporarily), because we are going to cross the waypoint twice (once outbound to the PT, and then again inbound established on final) and we do NOT want the box to sequence down the flight plan to the next waypoint (in this case the MAP) at the first crossing; we need the box to keep the FAF as the active waypoint until we are established inbound from the PT. Yes, I did learn this during the ICC for both course reversals and holds after a missed. At 30 nm out, check that you get an ARM light on your external display. Cross the FAF, and turn outbound towards the PT; set the obs on your #1 vor indicator to the outbound course (098). Intercept it and track outbound until you are ready to do the PT (1 min, 2min or so) Once you start the PT (left turn to 053) reset the obs on #1 indicator to the inbound intermediate course (from the PT to the FAF), in this case 278. Turn inbound in the PT and then intercept and track the 278 course towards the FAF. DANGER!!! DO NOT MISS THIS NEXT STEP OR ALL IS LOST!!! Once established inbound, but prior to 2nm from FAF, push the OBS button again on the external GPS display and VERIFY THAT THE OBS LIGHT GOES OUT!!! I did this and that is when things went nuts. However, it sounds from what you wrote above that I entered the approach into a flight plan to a different airport. I didn't realize that entering a direct to fix wouldn't replace flight plan 0. The box will now go back into the LEG mode (you should see LEG displayed in the left portion of the GPS display), which is necessary to get to ACTV mode. Watch the distance tick down; at 2nm from the FAF, the ARM light should go out, and the ACTV light should come on. If this does not happen, you have about 1:20 (2 nm at 90 kts) to figure out which of the nine items in the list you missed and correct it prior to crossing the FAF. If you do not get an ACTV light and pass the FAF, nothing you can do will get it from there on. You have to abandon the approach, go back out and start over. At the FAF the box should sequence to the MAP, and then automatically go into the suspend mode (waypoint sequencing disabled). At 0 dist to MAP, you must either have the runway in sight and land visuallly, or execute the missed. If you go missed, hit the OBS button again; the box will go back into the LEG mode just long enough for it to sequence to the MAHP, and then it will go back into suspend mode again. This is so you can do multiple turns in the hold at the MAHP without the box autosequencing to some other fix. I was taught to hit direct to at the MAP and then fly in leg more towards the holding fix and then switch to OBS mode to fly the hold. If you want to go back and do another approach, you have to hit the OBS button again (get it out of suspend mode and back into leg mode), and set it up to proceed direct to the IAF and start the procedure over as before. I've not heard of suspended mode before. I'll look this up. I only read about LEG and OBS mode, and missed suspend. Somewhere in there I think you will find a piece you missed. When you get back in front of the GPS again, try loading the approach and then scrolling down through the waypoints. There should be 3 for this approach: the first one should be XXXXXf (database name of the LOM, with a small f after it), the second one should be YYYYYm (database name of the MAP, probably RW28 or some such, with a little m after it), and then ZZZZZh (database name of the MAHP, with a little h after it.) If you dont have at least those three waypoints in the approach, time to contact your database provider and ask some questions. If at first you do not get an ACTV light, try, try again. Gene CFII, ASC Thanks, Gene, I appreciate the time you took to make this very detailed approach. A few more flights and I'll get a handle on GPS approaches. I still find them far more complicated than other approaches, even NDBs, however, that is just my newness to GPS. Matt |
#12
|
|||
|
|||
Jose wrote:
[GPS approach procedure snipped] Wow... and people say GPS makes life =simple=? I'll take an ILS over that any day! Jose Yes, I still feel that way, but I'm determined to learn GPS approaches for two reasons: 1. I'm a computer science graduate and no computer is going to get the best of me! 2. A lot of places that don't have an ILS do have a GPS. I'm sure once learned, the GPS seem trivial, it is just taking me a little while to get the hang of it. Then again, I've only flow about 6 GPS approaches so far, so I'm not too worried about my current ineptness. Matt |
#13
|
|||
|
|||
2. A lot of places that don't have an ILS do have a GPS.
Agreed. Got to know GPS approaches. 1. I'm a computer science graduate and no computer is going to get the best of me! Don't bet on it. A computer is a personal servant, to whom you give the keys to your house, your car, and your bank, who only speaks Swahili, who takes his orders from a high school student in Pakistan, and who invites its friends over for parties when you are out of the house. The only way around this is to program the raw chip yourself. (and yes, I also do programming) I'm sure once learned, the GPS seem trivial, it is just taking me a little while to get the hang of it. With steam gauges, you depend on the laws of physics. With GPS, you depend on the twisted logic of whoever had too much coffee the day the design was burned in ROM. The laws of physics have never failed me. I've yet to encounter a computer that didn't go belly up just for jollies. Jose -- Freedom. It seemed like a good idea at the time. for Email, make the obvious change in the address. |
#14
|
|||
|
|||
Jose wrote:
2. A lot of places that don't have an ILS do have a GPS. Agreed. Got to know GPS approaches. 1. I'm a computer science graduate and no computer is going to get the best of me! Don't bet on it. A computer is a personal servant, to whom you give the keys to your house, your car, and your bank, who only speaks Swahili, who takes his orders from a high school student in Pakistan, and who invites its friends over for parties when you are out of the house. The only way around this is to program the raw chip yourself. No, you can always turn off the power! :-) (and yes, I also do programming) I did programming, but I grew out of that phase. :-) I'm sure once learned, the GPS seem trivial, it is just taking me a little while to get the hang of it. With steam gauges, you depend on the laws of physics. With GPS, you depend on the twisted logic of whoever had too much coffee the day the design was burned in ROM. Yes, there is some truth to that. The laws of physics have never failed me. I've yet to encounter a computer that didn't go belly up just for jollies. Well, the first computer I worked on was a PDP-11/34 running RSX-llM and that sucker never crashed once in the five years we used it as a development host. The only downtime it saw was when we applied patches or did a sysgen to change its configuration. Matt |
#15
|
|||
|
|||
In article ,
Matt Whiting wrote: Jose wrote: 2. A lot of places that don't have an ILS do have a GPS. Agreed. Got to know GPS approaches. 1. I'm a computer science graduate and no computer is going to get the best of me! Don't bet on it. A computer is a personal servant, to whom you give the keys to your house, your car, and your bank, who only speaks Swahili, who takes his orders from a high school student in Pakistan, and who invites its friends over for parties when you are out of the house. The only way around this is to program the raw chip yourself. No, you can always turn off the power! :-) Actually, with a lot of devices these days, turning off the power is harder than it appears. It may have an on/off switch, but that usually just shuts down the display and leaves the processor running. Pulling the plug out may not even help, if it's got backup batteries. |
#16
|
|||
|
|||
Roy Smith wrote:
In article , Matt Whiting wrote: Jose wrote: 2. A lot of places that don't have an ILS do have a GPS. Agreed. Got to know GPS approaches. 1. I'm a computer science graduate and no computer is going to get the best of me! Don't bet on it. A computer is a personal servant, to whom you give the keys to your house, your car, and your bank, who only speaks Swahili, who takes his orders from a high school student in Pakistan, and who invites its friends over for parties when you are out of the house. The only way around this is to program the raw chip yourself. No, you can always turn off the power! :-) Actually, with a lot of devices these days, turning off the power is harder than it appears. It may have an on/off switch, but that usually just shuts down the display and leaves the processor running. Pulling the plug out may not even help, if it's got backup batteries. They only keep track of the date and a few other key settings, typically. Can't do much real processing for long on the backup battery. Matt |
#17
|
|||
|
|||
[battery backup only keeps track of] a few other key settings
Those may be the settings that prevent you from doing something you thought was reasonable under the circumstances, but the programmer didn't think of. You are always depending on the programmer to have thought of whatever situation you are in, =and= come up with the right answer. Jose -- Money: What you need when you run out of brains. for Email, make the obvious change in the address. |
#18
|
|||
|
|||
Roy Smith wrote:
"CFII_ASC" wrote: Typically, to get it to go into the ACTV mode, these things must be true: 1. In LEG mode (not OBS) 2. In ARM mode (this comes up when you have a valid approach loaded, and you are within 30nm) Within 30 nm of what? The IAF? The destination? The FAF, I think, but someone else will give a more authoritative answer. 3. Valid RAIM now, and predicted at FAF and MAP 4. Outside FAF (110 degree arc each side of FAF) 5. Distance to FAF decreasing 6. Within 2nm of FAF, but not past (inside) FAF 7. NAV/GPS switch must be in the GPS position 8. No localizer frequency may be loaded into NAV 1 (some boxes) Wow, that last one is pretty strange. I often have an ILS frequency loaded up, even if I'm not using it. The most frequent use I make of the NAV part of the GPS/NAV/COM is to fly an ILS, so the last ILS flown is usually what's left there. What is the logic behind requiring me to change it to something else? The GX50 I had installed in my old Archer worked that way. I've also seen a GX50 that didn't work that way. It must be an installation option. In the plane that wasn't installed that way, I've been safety pilot and seen a confused pilot when he tuned the localizer without switching the GPS/NAV switch to NAV, and couldn't figure out why the OBS wasn't behaving the way he thought it should. OTOH, I can imagine the inverse kind of confusion occurring if the OBS switched to NAV mode on its own when a localizer is tuned. You have to know your installation. What is the logic? Dunno. |
#19
|
|||
|
|||
On Tue, 04 Jan 2005 12:01:19 -0500, Dave Butler wrote:
Within 30 nm of what? The IAF? The destination? The FAF, I think, but someone else will give a more authoritative answer. the airport, if I am not mistaken. |
#20
|
|||
|
|||
Hah!
I looked it up. It is the ARP. Gene |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Another approach question | Andrew Sarangan | Instrument Flight Rules | 5 | November 7th 04 05:44 PM |
GPS approach question | Matt Whiting | Instrument Flight Rules | 8 | November 1st 04 10:51 PM |
VOR/DME Approach Question | Chip Jones | Instrument Flight Rules | 47 | August 29th 04 05:03 AM |
where to ask question about approach? | J Haggerty | Instrument Flight Rules | 1 | August 17th 04 06:30 AM |
Established on the approach - Checkride question | endre | Instrument Flight Rules | 59 | October 6th 03 04:36 PM |