A aviation & planes forum. AviationBanter

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.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Instrument Flight Rules
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Garmin 430 "Approach Not Active"



 
 
Thread Tools Display Modes
  #1  
Old June 5th 04, 04:38 AM
David
external usenet poster
 
Posts: n/a
Default 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  
Old June 5th 04, 11:55 AM
Rip
external usenet poster
 
Posts: n/a
Default

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  
Old June 5th 04, 04:45 PM
external usenet poster
 
Posts: n/a
Default



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.



  #7  
Old June 6th 04, 07:56 PM
Jerry Kurata
external usenet poster
 
Posts: n/a
Default

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  
Old June 7th 04, 03:18 AM
fly low
external usenet poster
 
Posts: n/a
Default

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  
Old June 7th 04, 07:47 PM
Marco Leon
external usenet poster
 
Posts: n/a
Default

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
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

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 05: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


All times are GMT +1. The time now is 01:29 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 AviationBanter.
The comments are property of their posters.