GA pilot intending 1n9 at night lands in error at abe instead.

Attributes
ACN	155563
Time
Date	199008
Day	Mon
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : abe
State Reference	PA
Altitude	agl bound lower : 0 agl bound upper : 1500
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : abe tower : abe
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	cruise other descent : approach landing other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 40 flight time total : 800 flight time type : 80
ASRS Report	155356
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	incursion : landing without clearance non adherence : far other anomaly other
Independent Detector	other controllera
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:

Arrived VFR, early morning hours at abe after 2 4-HR legs from lwc. Planned to identify and land at 1n9. Calls to altoona FSS and abe approach received no response. Did receive abe ATIS. Decided to remain clear of arsa, and land at 1n9 using VOR bearings from abe etx. While communicating on unicom (122.7) watching for other traffic (there was none), and using dual VOR's for a fix, I idented an airport and landed. Upon landing I noticed a green light directed at me from a control tower and realized that I had landed at the wrong airport (1n9 has no tower). I penetrated the arsa west/O prior 2-WAY communication and landed at abe. The beacon at 1n9 had not been turned on. (1n9 has pilot controlled lighting but the director of maintenance there explained that the beacon is controled by a switch and had not been turned on that night.) misinterp of confusing low altitude en route map (I had previously calculated a VOR fix for 1n9 from the low altitude map, but misidented abe for 1n9--see labeling on map). There were difficulties reaching approach control. Fatigue was also a factor. Finally, airports and hospital helipad very close together.

Original NASA ASRS Text

Title: GA PLT INTENDING 1N9 AT NIGHT LANDS IN ERROR AT ABE INSTEAD.

Narrative: ARRIVED VFR, EARLY MORNING HRS AT ABE AFTER 2 4-HR LEGS FROM LWC. PLANNED TO IDENT AND LAND AT 1N9. CALLS TO ALTOONA FSS AND ABE APCH RECEIVED NO RESPONSE. DID RECEIVE ABE ATIS. DECIDED TO REMAIN CLR OF ARSA, AND LAND AT 1N9 USING VOR BEARINGS FROM ABE ETX. WHILE COMMUNICATING ON UNICOM (122.7) WATCHING FOR OTHER TFC (THERE WAS NONE), AND USING DUAL VOR'S FOR A FIX, I IDENTED AN ARPT AND LANDED. UPON LNDG I NOTICED A GREEN LIGHT DIRECTED AT ME FROM A CTL TWR AND REALIZED THAT I HAD LANDED AT THE WRONG ARPT (1N9 HAS NO TWR). I PENETRATED THE ARSA W/O PRIOR 2-WAY COM AND LANDED AT ABE. THE BEACON AT 1N9 HAD NOT BEEN TURNED ON. (1N9 HAS PCL BUT THE DIRECTOR OF MAINT THERE EXPLAINED THAT THE BEACON IS CTLED BY A SWITCH AND HAD NOT BEEN TURNED ON THAT NIGHT.) MISINTERP OF CONFUSING LOW ALT ENRTE MAP (I HAD PREVIOUSLY CALCULATED A VOR FIX FOR 1N9 FROM THE LOW ALT MAP, BUT MISIDENTED ABE FOR 1N9--SEE LABELING ON MAP). THERE WERE DIFFICULTIES REACHING APCH CTL. FATIGUE WAS ALSO A FACTOR. FINALLY, ARPTS AND HOSPITAL HELIPAD VERY CLOSE TOGETHER.

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.