Narrative:

I picked up the aircraft in mcallen, tx, and flew it, VFR, to del rio, navigating with a cg 23 WAC chart and an AOPA airport directory. I was unfamiliar with the area but expected to find the airport closed, not lit, and on the mexico border. I expected to land on runway 13. Upon arrival I attempted to contact ATC on the published frequencys but received no response. I also expected to identify the air force base in close proximity to del rio international, but observed no rotating beacon. Since the airport was idented to be on the border, I was concerned about making an illegal border crossing. Having idented an 'international' looking airport, with runway '13' and no identifiable lighting, 'no rotating beacon,' I proceeded to make a landing. Once on the ground, I observed the jets that were tied down and realized the error. If I had been able to accomplish any of the following, the above error would not have occurred. Observed a 'white, white, green' beacon. Raised anybody on the published frequencys. Been able to skirt the area to the opposite side of del rio international without concern for illegal border crossing. All of my charts were current. Visibility was clear but dusk lighting and a 3500 ft overcast impaired my ability to perhaps get a view from 'higher up.' these factors may have played a less important role in this scenario.

Google
 

Original NASA ASRS Text

Title: UNAUTH PENETRATION OF AIRSPACE AFTER WRONG ARPT APCH AND LNDG.

Narrative: I PICKED UP THE ACFT IN MCALLEN, TX, AND FLEW IT, VFR, TO DEL RIO, NAVIGATING WITH A CG 23 WAC CHART AND AN AOPA ARPT DIRECTORY. I WAS UNFAMILIAR WITH THE AREA BUT EXPECTED TO FIND THE ARPT CLOSED, NOT LIT, AND ON THE MEXICO BORDER. I EXPECTED TO LAND ON RWY 13. UPON ARR I ATTEMPTED TO CONTACT ATC ON THE PUBLISHED FREQS BUT RECEIVED NO RESPONSE. I ALSO EXPECTED TO IDENT THE AIR FORCE BASE IN CLOSE PROX TO DEL RIO INTL, BUT OBSERVED NO ROTATING BEACON. SINCE THE ARPT WAS IDENTED TO BE ON THE BORDER, I WAS CONCERNED ABOUT MAKING AN ILLEGAL BORDER XING. HAVING IDENTED AN 'INTL' LOOKING ARPT, WITH RWY '13' AND NO IDENTIFIABLE LIGHTING, 'NO ROTATING BEACON,' I PROCEEDED TO MAKE A LNDG. ONCE ON THE GND, I OBSERVED THE JETS THAT WERE TIED DOWN AND REALIZED THE ERROR. IF I HAD BEEN ABLE TO ACCOMPLISH ANY OF THE FOLLOWING, THE ABOVE ERROR WOULD NOT HAVE OCCURRED. OBSERVED A 'WHITE, WHITE, GREEN' BEACON. RAISED ANYBODY ON THE PUBLISHED FREQS. BEEN ABLE TO SKIRT THE AREA TO THE OPPOSITE SIDE OF DEL RIO INTL WITHOUT CONCERN FOR ILLEGAL BORDER XING. ALL OF MY CHARTS WERE CURRENT. VISIBILITY WAS CLR BUT DUSK LIGHTING AND A 3500 FT OVCST IMPAIRED MY ABILITY TO PERHAPS GET A VIEW FROM 'HIGHER UP.' THESE FACTORS MAY HAVE PLAYED A LESS IMPORTANT ROLE IN THIS SCENARIO.

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.