GA pilot enroute redlands airport makes wrong airport landing at norton AFB.

Attributes
ACN	177337
Time
Date	199105
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : l12 airport : sbd
State Reference	CA
Altitude	agl bound lower : 0 agl bound upper : 500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	military facility : sbd
Operator	general aviation : personal
Make Model Name	Small Aircraft, Low Wing, 1 Eng, Retractable Gear
Flight Phase	cruise other landing other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 25 flight time total : 2388 flight time type : 1343
ASRS Report	177337
Person 2
Affiliation	government : military
Function	controller : local
Qualification	controller : military
Events
Anomaly	incursion : landing without clearance non adherence : far other anomaly other
Independent Detector	other controllera other other : unspecified
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was on a business flight from montgomery field, san diego to redlands, ca. This was my first flight to the redlands area. In the vicinity of hemet, I contacted ont approach control for advisories/vectors. Approach furnished altitude and heading assignments until approximately 4 or 5 mi from the airport, at which time he advised me to squawk VFR and contact unicom. Just prior to that, I had informed him that I did not have the airport in sight, but I went ahead and complied with his instructions. Shortly thereafter, I observed an airport with an east/west runway and I set up for a landing to the west. On short final, I observed conflicting runway #south with those at redlands and realized I was set up for the wrong airport. Since no visibility traffic was apparent and I had already intruded in the airport traffic pattern, I decided it would be safer to continue the landing. Base personnel informed me where I was and had me fill out an information sheet. They were extremely courteous and after a brief period had me taxi out and takeoff for redlands. This incident probably could have been averted if ont approach control had stayed with me until I had the airport in sight. Contributing factors were reduced visibility, turbulence and a lazy dg.

Original NASA ASRS Text

Title: GA PLT ENROUTE REDLANDS ARPT MAKES WRONG ARPT LNDG AT NORTON AFB.

Narrative: I WAS ON A BUSINESS FLT FROM MONTGOMERY FIELD, SAN DIEGO TO REDLANDS, CA. THIS WAS MY FIRST FLT TO THE REDLANDS AREA. IN THE VICINITY OF HEMET, I CONTACTED ONT APCH CTL FOR ADVISORIES/VECTORS. APCH FURNISHED ALT AND HDG ASSIGNMENTS UNTIL APPROX 4 OR 5 MI FROM THE ARPT, AT WHICH TIME HE ADVISED ME TO SQUAWK VFR AND CONTACT UNICOM. JUST PRIOR TO THAT, I HAD INFORMED HIM THAT I DID NOT HAVE THE ARPT IN SIGHT, BUT I WENT AHEAD AND COMPLIED WITH HIS INSTRUCTIONS. SHORTLY THEREAFTER, I OBSERVED AN ARPT WITH AN E/W RWY AND I SET UP FOR A LNDG TO THE W. ON SHORT FINAL, I OBSERVED CONFLICTING RWY #S WITH THOSE AT REDLANDS AND REALIZED I WAS SET UP FOR THE WRONG ARPT. SINCE NO VIS TFC WAS APPARENT AND I HAD ALREADY INTRUDED IN THE ARPT TFC PATTERN, I DECIDED IT WOULD BE SAFER TO CONTINUE THE LNDG. BASE PERSONNEL INFORMED ME WHERE I WAS AND HAD ME FILL OUT AN INFO SHEET. THEY WERE EXTREMELY COURTEOUS AND AFTER A BRIEF PERIOD HAD ME TAXI OUT AND TKOF FOR REDLANDS. THIS INCIDENT PROBABLY COULD HAVE BEEN AVERTED IF ONT APCH CTL HAD STAYED WITH ME UNTIL I HAD THE ARPT IN SIGHT. CONTRIBUTING FACTORS WERE REDUCED VISIBILITY, TURB AND A LAZY DG.

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.