General aviation pilot reports attempting localizer 30 approach at erv to discover it OTS. NOTAM ind...

Narrative:

I asked for and was given clearance for the localizer 30 approach at erv. When I turned onto the approach course using GPS navigation; I switched to CDI mode (previously loaded localizer frequency in #1 navigation). I did not get an indication of picking up localizer signal. I went missed; returned to the hold for localizer 30 and rechecked all settings. I was not able to identify localizer signal; immediately switched to GPS mode for GPS approach and landed. I planned the trip using duats. The new duats format for route briefing lists all notams at the beginning of the briefing (or so I thought). There were two runway associated notams; one for runway 30 for approach path indicator and one for displaced threshold. Later in the briefing; there are notams grouped by type for all airports enroute as well as destination. Nothing was listed for erv localizer 30. After landing; I later rechecked the duats route briefing info and found; buried deep in the fdc notams; NOTAM #8/3837 stating 'localizer runway 30 amdt 4 .procedure not available.' I learned several lessons -- call flight service for additional briefing to make sure nothing was missed in reviewing duats; identify localizer signal sooner; don't expect ARTCC to have all the relevant information about various approaches at the many airports and sectors they handle.

Original NASA ASRS Text

Title: General aviation pilot reports attempting LOC 30 approach at ERV to discover it OTS. NOTAM indicating this approach not available is discovered after the fact buried in DUATS briefing.

Narrative: I asked for and was given clearance for the LOC 30 approach at ERV. When I turned onto the approach course using GPS navigation; I switched to CDI mode (previously loaded LOC frequency in #1 navigation). I did not get an indication of picking up LOC signal. I went missed; returned to the hold for LOC 30 and rechecked all settings. I was not able to identify LOC signal; immediately switched to GPS mode for GPS approach and landed. I planned the trip using DUATS. The new DUATS format for route briefing lists all NOTAMs at the beginning of the briefing (or so I thought). There were two runway associated NOTAMs; one for Runway 30 for approach path indicator and one for displaced threshold. Later in the briefing; there are NOTAMs grouped by type for all airports enroute as well as destination. Nothing was listed for ERV LOC 30. After landing; I later rechecked the DUATS route briefing info and found; buried deep in the FDC NOTAMs; NOTAM #8/3837 stating 'LOC Runway 30 AMDT 4 .Procedure not available.' I learned several lessons -- call flight service for additional briefing to make sure nothing was missed in reviewing DUATS; identify LOC signal sooner; don't expect ARTCC to have all the relevant information about various approaches at the many airports and sectors they handle.

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	823921
Time
Date	200902
Local Time Of Day	1801-2400
Place
Locale Reference	ERV.Airport
State Reference	TX
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
Flight Plan	IFR
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Instrument Flight Crew Private
Experience	Flight Crew Last 90 Days 40 Flight Crew Total 1450 Flight Crew Type 1000
Events
Anomaly	Deviation - Procedural FAR

General aviation pilot reports attempting localizer 30 approach at erv to discover it OTS. NOTAM indicating this approach not available is discovered after the fact buried in duats briefing.