A BE35 pilot in contact with foe makes an approach to top airport in error.

Attributes
ACN	349090
Time
Date	199608
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : top
State Reference	KS
Altitude	msl bound lower : 3000 msl bound upper : 3000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tower : foe tower : top
Operator	general aviation : personal
Make Model Name	Bonanza 35
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Route In Use	approach : visual
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : private
Experience	flight time last 90 days : 79 flight time total : 357 flight time type : 357
ASRS Report	349090
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	non adherence : published procedure non adherence : far other anomaly other other anomaly other
Independent Detector	other controllera
Resolutory Action	flight crew : became reoriented other other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was flying at the MEA (3000 ft) planning a VOR approach to forbes field. Cloud bases were ragged at my altitude. I spotted what I believed to be forbes field and canceled my IFR flight plan. I then contacted the tower at forbes and returned position-intent. The tower controller did not have visual contact and told me to report a 2 mi final. When I did, I estimated 2 mi out 'over the river.' this was their clue that I was at the wrong field. They told me I was probably at billard field and gave me the tower frequency there. I immediately turned away and contacted the billard tower, got landing clearance, and landed. Of course, I could have been better prepared, but I think the controllers could be made aware of the potential for a mix-up. Both fields have runways which are approximately aligned (runway 13 versus runway 12) which further lulled me into believing I was at the right field. When I reported the field in sight, the controller could have challenged me, or at least asked if I might be looking at the wrong airport (billard) since I was too far away from forbes to see it.

Original NASA ASRS Text

Title: A BE35 PLT IN CONTACT WITH FOE MAKES AN APCH TO TOP ARPT IN ERROR.

Narrative: I WAS FLYING AT THE MEA (3000 FT) PLANNING A VOR APCH TO FORBES FIELD. CLOUD BASES WERE RAGGED AT MY ALT. I SPOTTED WHAT I BELIEVED TO BE FORBES FIELD AND CANCELED MY IFR FLT PLAN. I THEN CONTACTED THE TWR AT FORBES AND RETURNED POS-INTENT. THE TWR CTLR DID NOT HAVE VISUAL CONTACT AND TOLD ME TO RPT A 2 MI FINAL. WHEN I DID, I ESTIMATED 2 MI OUT 'OVER THE RIVER.' THIS WAS THEIR CLUE THAT I WAS AT THE WRONG FIELD. THEY TOLD ME I WAS PROBABLY AT BILLARD FIELD AND GAVE ME THE TWR FREQ THERE. I IMMEDIATELY TURNED AWAY AND CONTACTED THE BILLARD TWR, GOT LNDG CLRNC, AND LANDED. OF COURSE, I COULD HAVE BEEN BETTER PREPARED, BUT I THINK THE CTLRS COULD BE MADE AWARE OF THE POTENTIAL FOR A MIX-UP. BOTH FIELDS HAVE RWYS WHICH ARE APPROX ALIGNED (RWY 13 VERSUS RWY 12) WHICH FURTHER LULLED ME INTO BELIEVING I WAS AT THE RIGHT FIELD. WHEN I RPTED THE FIELD IN SIGHT, THE CTLR COULD HAVE CHALLENGED ME, OR AT LEAST ASKED IF I MIGHT BE LOOKING AT THE WRONG ARPT (BILLARD) SINCE I WAS TOO FAR AWAY FROM FORBES TO SEE IT.

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.