Wrong runway approach and unauthorized landing without clearance coordination.

Attributes
ACN	192002
Time
Date	199110
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : luk
State Reference	OH
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	descent : approach landing other other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : instrument
Experience	flight time last 90 days : 16 flight time total : 1425 flight time type : 500
ASRS Report	192002
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	incursion : landing without clearance non adherence : clearance
Independent Detector	other flight crewa
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:

After being over to cvg tower on approach, I asked to do some stop and goes on runway 18L. I was advised that they were unable at the time, told to break off the approach, turn to heading 10, and contact approach. I did so and made the same request for luk. About 3 mi west of luk I was turned over to luk tower where I again made my request; I was cleared to land runway 20R. I lined up on the runway that was lit and visible from my position and landed, but it turned out to be runway 20L. From my position and altitude west of the field, I never saw the runway lights for the shorter 20R runway; the dimmer lights were not apparent in the sea of ground lights visible from my position. Perhaps if the runway lights had been brighter, I could have seen them. I was unfamiliar with the airport and the fact that I had very little time and distance for this abrupt change of plans also contributed to selecting the wrong runway. And perhaps the tower could have seen me line up on the wrong runway and mentioned before I had actually landed. Fortunately, traffic was very light and there were no conflicts either in the air or on the ground. I did 1 more stop and go on 20L and departed the field uneventfully.

Original NASA ASRS Text

Title: WRONG RWY APCH AND UNAUTH LNDG WITHOUT CLRNC COORD.

Narrative: AFTER BEING OVER TO CVG TWR ON APCH, I ASKED TO DO SOME STOP AND GOES ON RWY 18L. I WAS ADVISED THAT THEY WERE UNABLE AT THE TIME, TOLD TO BREAK OFF THE APCH, TURN TO HDG 10, AND CONTACT APCH. I DID SO AND MADE THE SAME REQUEST FOR LUK. ABOUT 3 MI W OF LUK I WAS TURNED OVER TO LUK TWR WHERE I AGAIN MADE MY REQUEST; I WAS CLRED TO LAND RWY 20R. I LINED UP ON THE RWY THAT WAS LIT AND VISIBLE FROM MY POS AND LANDED, BUT IT TURNED OUT TO BE RWY 20L. FROM MY POS AND ALT W OF THE FIELD, I NEVER SAW THE RWY LIGHTS FOR THE SHORTER 20R RWY; THE DIMMER LIGHTS WERE NOT APPARENT IN THE SEA OF GND LIGHTS VISIBLE FROM MY POS. PERHAPS IF THE RWY LIGHTS HAD BEEN BRIGHTER, I COULD HAVE SEEN THEM. I WAS UNFAMILIAR WITH THE ARPT AND THE FACT THAT I HAD VERY LITTLE TIME AND DISTANCE FOR THIS ABRUPT CHANGE OF PLANS ALSO CONTRIBUTED TO SELECTING THE WRONG RWY. AND PERHAPS THE TWR COULD HAVE SEEN ME LINE UP ON THE WRONG RWY AND MENTIONED BEFORE I HAD ACTUALLY LANDED. FORTUNATELY, TFC WAS VERY LIGHT AND THERE WERE NO CONFLICTS EITHER IN THE AIR OR ON THE GND. I DID 1 MORE STOP AND GO ON 20L AND DEPARTED THE FIELD UNEVENTFULLY.

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.