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