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
|
|||
|
|||
Garmin 430 "Approach Not Active"
Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03
at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430 reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO and HIBAN at ROA), and stopped sequencing. I am quite certain that I activated both approaches when I added them to the flight plan (not just "Loaded" them). It was VMC+ at each airport, so I just continued to landing both times. I didn't get any other warnings or messages from the 430. Any ideas on why the 430 may have stopped sequencing at the FAF on my approaches? I re-read the Pilot's Guide, but if there's something related there I didn't see it. Thanks, Dave |
#2
|
|||
|
|||
RAIM failure?
David wrote: Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03 at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430 reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO and HIBAN at ROA), and stopped sequencing. I am quite certain that I activated both approaches when I added them to the flight plan (not just "Loaded" them). It was VMC+ at each airport, so I just continued to landing both times. I didn't get any other warnings or messages from the 430. Any ideas on why the 430 may have stopped sequencing at the FAF on my approaches? I re-read the Pilot's Guide, but if there's something related there I didn't see it. Thanks, Dave |
#4
|
|||
|
|||
David wrote: Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03 at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430 reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO and HIBAN at ROA), and stopped sequencing. I am quite certain that I activated both approaches when I added them to the flight plan (not just "Loaded" them). It was VMC+ at each airport, so I just continued to landing both times. I didn't get any other warnings or messages from the 430. Any ideas on why the 430 may have stopped sequencing at the FAF on my approaches? The message means what it says. Go to the procedures page and activate the approach. This will activate any approach except for a RAIM failure and you would know that by a separate message. |
#5
|
|||
|
|||
|
#6
|
|||
|
|||
No vectors, I was on course, on the flight plan, each time.
The previous post questioning RAIM failure makes me think that is the likely suspect. I didn't think to check the status screen right at that time (too busy flying), but if this happens again I will take a closer look if at all possible. Dave wrote in message ... Were you being vectored to the final approach course? If so, you need to be established on the FAC at least two miles prior to the FAP. If you're not established two miles out from the FAP, the approach mode will not activate. That's somewhere in the book, and I've seen it myself. On 4 Jun 2004 20:38:57 -0700, (David) wrote: Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03 at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430 reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO and HIBAN at ROA), and stopped sequencing. I am quite certain that I activated both approaches when I added them to the flight plan (not just "Loaded" them). It was VMC+ at each airport, so I just continued to landing both times. I didn't get any other warnings or messages from the 430. Any ideas on why the 430 may have stopped sequencing at the FAF on my approaches? I re-read the Pilot's Guide, but if there's something related there I didn't see it. Thanks, Dave |
#7
|
|||
|
|||
Hi David,
There are couple of possibilities. One is a RAIM error. If a RAIM issue occurs at the FAF you will get that message, followed by another message saying that RAIM was not available. The second possibility is that your unit was in Suspend mode and no longer automatically sequencing waypoints. This would have occured back at the IAF. The chart shows that KENNI is the IAF for the approach at KCHO. It is also the holding fix. Therefore, when you arrived at KENNI the GNS 430 would have automatically gone into suspend mode, since the unit could not know whether you were going to hold or continue. The message "SUSP" should have been displayed above the OBS button. If you press the OBS button the automatic sequencing will continue from KENNI inbound. I have seen a number of people tripped up by the auto-suspend "feature" of the GNS radios. jerry "David" wrote in message om... Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03 at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430 reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO and HIBAN at ROA), and stopped sequencing. I am quite certain that I activated both approaches when I added them to the flight plan (not just "Loaded" them). It was VMC+ at each airport, so I just continued to landing both times. I didn't get any other warnings or messages from the 430. Any ideas on why the 430 may have stopped sequencing at the FAF on my approaches? I re-read the Pilot's Guide, but if there's something related there I didn't see it. Thanks, Dave |
#8
|
|||
|
|||
My 430 will ask me if I want to HOLD.
"Jerry Kurata" wrote in message ... Hi David, There are couple of possibilities. One is a RAIM error. If a RAIM issue occurs at the FAF you will get that message, followed by another message saying that RAIM was not available. The second possibility is that your unit was in Suspend mode and no longer automatically sequencing waypoints. This would have occured back at the IAF. The chart shows that KENNI is the IAF for the approach at KCHO. It is also the holding fix. Therefore, when you arrived at KENNI the GNS 430 would have automatically gone into suspend mode, since the unit could not know whether you were going to hold or continue. The message "SUSP" should have been displayed above the OBS button. If you press the OBS button the automatic sequencing will continue from KENNI inbound. I have seen a number of people tripped up by the auto-suspend "feature" of the GNS radios. jerry "David" wrote in message om... Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03 at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430 reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO and HIBAN at ROA), and stopped sequencing. I am quite certain that I activated both approaches when I added them to the flight plan (not just "Loaded" them). It was VMC+ at each airport, so I just continued to landing both times. I didn't get any other warnings or messages from the 430. Any ideas on why the 430 may have stopped sequencing at the FAF on my approaches? I re-read the Pilot's Guide, but if there's something related there I didn't see it. Thanks, Dave |
#9
|
|||
|
|||
I think Jerry's second possibility may be the cause. I was tripped up by
this too. I now include "Remove Hold......Consider" in my approach checklist as a result. Marco "Jerry Kurata" wrote in message ... Hi David, There are couple of possibilities. One is a RAIM error. If a RAIM issue occurs at the FAF you will get that message, followed by another message saying that RAIM was not available. The second possibility is that your unit was in Suspend mode and no longer automatically sequencing waypoints. This would have occured back at the IAF. The chart shows that KENNI is the IAF for the approach at KCHO. It is also the holding fix. Therefore, when you arrived at KENNI the GNS 430 would have automatically gone into suspend mode, since the unit could not know whether you were going to hold or continue. The message "SUSP" should have been displayed above the OBS button. If you press the OBS button the automatic sequencing will continue from KENNI inbound. I have seen a number of people tripped up by the auto-suspend "feature" of the GNS radios. jerry "David" wrote in message om... Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03 at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430 reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO and HIBAN at ROA), and stopped sequencing. I am quite certain that I activated both approaches when I added them to the flight plan (not just "Loaded" them). It was VMC+ at each airport, so I just continued to landing both times. I didn't get any other warnings or messages from the 430. Any ideas on why the 430 may have stopped sequencing at the FAF on my approaches? I re-read the Pilot's Guide, but if there's something related there I didn't see it. Thanks, Dave Posted Via Usenet.com Premium Usenet Newsgroup Services ---------------------------------------------------------- ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY ** ---------------------------------------------------------- http://www.usenet.com |
#10
|
|||
|
|||
|
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
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 |
Garmin 530 VOR Approach Using GPS or VLOC | Rich | Instrument Flight Rules | 3 | November 28th 03 04:08 AM |
Garmin DME arc weidnress | Dave Touretzky | Instrument Flight Rules | 5 | October 2nd 03 02:04 AM |
Garmin Behind the Curve on WAAS GPS VNAV Approaches | Richard Kaplan | Instrument Flight Rules | 24 | July 18th 03 01:43 PM |