BE58 pilot attempts to execute an ILS approach without charts or the proper frequency into cae.

Attributes
ACN	595867
Time
Date	200310
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : cae.vortac
State Reference	SC
Altitude	msl single value : 2100
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : cae.tracon
Operator	general aviation : corporate
Make Model Name	Baron 58/58TC
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : single pilot oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 5.5 flight time total : 6000 flight time type : 1800
ASRS Report	595867
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	non adherence : far
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I filed a flight plan and checked WX for a short trip, charlotte/columbia for an association meeting. I failed to remember to bring the instrument charts to the airplane the morning of the trip and did not catch my error until climb out at approximately 3000 ft. Since the WX at the destination, 25 mins away was essentially the same as the departure airport, I proceeded direct to the destination using GPS. I requested the parameters for the ILS runway 11 approach but the controller gave me (or I misheard) the frequency 110.35. The actual ILS runway 11 frequency is 110.3, but I read back only the initial approach altitude, decision ht, miss and lost communication procedures as the ATC was quite busy. I encountered flagged localizer's and GS's on beginning the approach but had a good audio identify on #1 navigation on the ILS (perhaps because the frequency bled over to 110.3?) the situation would have been prevented by: 1) carrying charts needed, 2) reading back ILS frequency despite ATC workload. Situation was resolved by a request and execution of ASR approach to runway 11.

Original NASA ASRS Text

Title: BE58 PLT ATTEMPTS TO EXECUTE AN ILS APCH WITHOUT CHARTS OR THE PROPER FREQ INTO CAE.

Narrative: I FILED A FLT PLAN AND CHKED WX FOR A SHORT TRIP, CHARLOTTE/COLUMBIA FOR AN ASSOCIATION MEETING. I FAILED TO REMEMBER TO BRING THE INST CHARTS TO THE AIRPLANE THE MORNING OF THE TRIP AND DID NOT CATCH MY ERROR UNTIL CLBOUT AT APPROX 3000 FT. SINCE THE WX AT THE DEST, 25 MINS AWAY WAS ESSENTIALLY THE SAME AS THE DEP ARPT, I PROCEEDED DIRECT TO THE DEST USING GPS. I REQUESTED THE PARAMETERS FOR THE ILS RWY 11 APCH BUT THE CTLR GAVE ME (OR I MISHEARD) THE FREQ 110.35. THE ACTUAL ILS RWY 11 FREQ IS 110.3, BUT I READ BACK ONLY THE INITIAL APCH ALT, DECISION HT, MISS AND LOST COM PROCS AS THE ATC WAS QUITE BUSY. I ENCOUNTERED FLAGGED LOC'S AND GS'S ON BEGINNING THE APCH BUT HAD A GOOD AUDIO IDENT ON #1 NAV ON THE ILS (PERHAPS BECAUSE THE FREQ BLED OVER TO 110.3?) THE SIT WOULD HAVE BEEN PREVENTED BY: 1) CARRYING CHARTS NEEDED, 2) READING BACK ILS FREQ DESPITE ATC WORKLOAD. SIT WAS RESOLVED BY A REQUEST AND EXECUTION OF ASR APCH TO RWY 11.

Data retrieved from NASA's ASRS site as of July 2007 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.