A pilot was given holding instructions at the FAF but the aircraft's garmin 430 would not recognize ...

Narrative:

I requested the RNAV 14 approach into cxo and had been given clearance direct to cekru intersection. The controller told me that he would probably have to hold me at alibi for one turn. I told him that alibi wasn't on the RNAV 14 approach; and he then said it was the same as fobna; the FAF. I have a garmin 430 which is IFR approved; but I didn't realize that the garmin GPS doesn't allow a hold at the FAF. They must be accomplished prior to the FAF. After turning inbound to fobna from axtep; the controller told me to make one turn in the holding pattern at fobna. When I pressed the obs button to suspend the approach for the hold; instead of getting a susp message; I got an 'approach not active' message. I immediately pressed the obs button again; and the approach was once again active. I entered the hold just before fobna to keep the GPS from sequencing to the next leg of the approach; and was relieved after turning back inbound to fobna to see that the GPS was still 'happy.' had the GPS sequenced to the next leg; I would have had to abandon the approach and reprogram the GPS. I plan on studying this phase of the GPS approach very thoroughly; and feel that the TRACON's need to make sure controllers know the limitations of the GPS and not to assign a hold at the FAF.

Original NASA ASRS Text

Title: A pilot was given holding instructions at the FAF but the aircraft's Garmin 430 would not recognize FAF holding so the pilot commenced holding prior to the FAF which kept approach active for the inbound turn.

Narrative: I requested the RNAV 14 approach into CXO and had been given clearance direct to CEKRU Intersection. The Controller told me that he would probably have to hold me at ALIBI for one turn. I told him that ALIBI wasn't on the RNAV 14 approach; and he then said it was the same as FOBNA; the FAF. I have a Garmin 430 which is IFR approved; but I didn't realize that the Garmin GPS doesn't allow a hold at the FAF. They must be accomplished prior to the FAF. After turning inbound to FOBNA from AXTEP; the Controller told me to make one turn in the holding pattern at FOBNA. When I pressed the OBS button to suspend the approach for the hold; instead of getting a SUSP message; I got an 'Approach not Active' message. I immediately pressed the OBS button again; and the approach was once again active. I entered the hold just before FOBNA to keep the GPS from sequencing to the next leg of the approach; and was relieved after turning back inbound to FOBNA to see that the GPS was still 'happy.' Had the GPS sequenced to the next leg; I would have had to abandon the approach and reprogram the GPS. I plan on studying this phase of the GPS approach very thoroughly; and feel that the TRACON's need to make sure controllers know the limitations of the GPS and not to assign a hold at the FAF.

Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

Attributes
ACN	980402
Time
Date	201111
Local Time Of Day	0601-1200
Place
Locale Reference	CXO.Airport
State Reference	TX
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft Low Wing 1 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
Flight Plan	IFR
Component
Aircraft Component	GPS & Other Satellite Navigation
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 20 Flight Crew Total 3700 Flight Crew Type 2000
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe

A pilot was given holding instructions at the FAF but the aircraft's garmin 430 would not recognize FAF holding so the pilot commenced holding prior to the FAF which kept approach active for the inbound turn.