Wrong runway approach landing. Unauthorized landing in a night operation.

Attributes
ACN	238457
Time
Date	199304
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : msn
State Reference	WI
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	general aviation : instructional
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	descent : approach landing other
Flight Plan	VFR
Person 1
Affiliation	Other
Function	instruction : instructor oversight : pic
Qualification	pilot : cfi pilot : instrument pilot : commercial
Experience	flight time last 90 days : 50 flight time total : 1950 flight time type : 200
ASRS Report	238457
Person 2
Affiliation	Other
Function	flight crew : single pilot instruction : trainee
Qualification	pilot : student
Events
Anomaly	incursion : landing without clearance non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We had flown from enw to msn and had been handed off from msn approach to msn tower. Prior to entering the left downwind for runway 13 as instructed, I asked the tower to turn up the lights for runway 13 since my student was uncertain of the runway's location. The tower complied and turned up both runway 13 and runway 18 lights. The wind was reported to be from the east and as we entered downwind, I made mention of this fact to the student and suggested widening out our pattern. The student was preoccupied with the before landing checklist and did not respond with any major corrective action. As we passed the end of the runway, the power was reduced and flaps set as normal. We began a standard left base (already cleared to land runway 13) and I was already anticipating the possibility of overshooting the runway on base due to our position and wind conditions. As we started to roll out on base I saw a lit up runway off to our left side. I immediately perceived this to be runway 13 and that we had in fact overshot the runway on base. I took over control of the aircraft at this point and made mention of our poor positioning to the student and that I was going to re-center us for a continued approach to runway 13. At approximately 1/4 - 1/8 mi out on final approach, I instructed the student to take control again, yet I stayed on the controls (stayed with the controls -- shadowed the student's controls) in case he needed help with the crosswind landing. The landing was completed successfully and as we rolled on the runway, I instructed the tower we were going to FBO. The tower replied that we had landed on the wrong runway, we were cleared for runway 13 but had landed on runway 18. The tower said something to the effect that 'but that is ok, just taxi off on C and contact ground on point 9.' we did as instructed. In the short time period in which all of this had occurred I let my preconceived notion of overshooting the runway interfere with my own orientation and visual positioning on base and final for runway 13. Having both runways lit up I unintentionally went for the first one I saw, runway 18.

Original NASA ASRS Text

Title: WRONG RWY APCH LNDG. UNAUTH LNDG IN A NIGHT OP.

Narrative: WE HAD FLOWN FROM ENW TO MSN AND HAD BEEN HANDED OFF FROM MSN APCH TO MSN TWR. PRIOR TO ENTERING THE L DOWNWIND FOR RWY 13 AS INSTRUCTED, I ASKED THE TWR TO TURN UP THE LIGHTS FOR RWY 13 SINCE MY STUDENT WAS UNCERTAIN OF THE RWY'S LOCATION. THE TWR COMPLIED AND TURNED UP BOTH RWY 13 AND RWY 18 LIGHTS. THE WIND WAS RPTED TO BE FROM THE E AND AS WE ENTERED DOWNWIND, I MADE MENTION OF THIS FACT TO THE STUDENT AND SUGGESTED WIDENING OUT OUR PATTERN. THE STUDENT WAS PREOCCUPIED WITH THE BEFORE LNDG CHKLIST AND DID NOT RESPOND WITH ANY MAJOR CORRECTIVE ACTION. AS WE PASSED THE END OF THE RWY, THE PWR WAS REDUCED AND FLAPS SET AS NORMAL. WE BEGAN A STANDARD L BASE (ALREADY CLRED TO LAND RWY 13) AND I WAS ALREADY ANTICIPATING THE POSSIBILITY OF OVERSHOOTING THE RWY ON BASE DUE TO OUR POS AND WIND CONDITIONS. AS WE STARTED TO ROLL OUT ON BASE I SAW A LIT UP RWY OFF TO OUR L SIDE. I IMMEDIATELY PERCEIVED THIS TO BE RWY 13 AND THAT WE HAD IN FACT OVERSHOT THE RWY ON BASE. I TOOK OVER CTL OF THE ACFT AT THIS POINT AND MADE MENTION OF OUR POOR POSITIONING TO THE STUDENT AND THAT I WAS GOING TO RE-CTR US FOR A CONTINUED APCH TO RWY 13. AT APPROX 1/4 - 1/8 MI OUT ON FINAL APCH, I INSTRUCTED THE STUDENT TO TAKE CTL AGAIN, YET I STAYED ON THE CTLS (STAYED WITH THE CTLS -- SHADOWED THE STUDENT'S CTLS) IN CASE HE NEEDED HELP WITH THE XWIND LNDG. THE LNDG WAS COMPLETED SUCCESSFULLY AND AS WE ROLLED ON THE RWY, I INSTRUCTED THE TWR WE WERE GOING TO FBO. THE TWR REPLIED THAT WE HAD LANDED ON THE WRONG RWY, WE WERE CLRED FOR RWY 13 BUT HAD LANDED ON RWY 18. THE TWR SAID SOMETHING TO THE EFFECT THAT 'BUT THAT IS OK, JUST TAXI OFF ON C AND CONTACT GND ON POINT 9.' WE DID AS INSTRUCTED. IN THE SHORT TIME PERIOD IN WHICH ALL OF THIS HAD OCCURRED I LET MY PRECONCEIVED NOTION OF OVERSHOOTING THE RWY INTERFERE WITH MY OWN ORIENTATION AND VISUAL POSITIONING ON BASE AND FINAL FOR RWY 13. HAVING BOTH RWYS LIT UP I UNINTENTIONALLY WENT FOR THE FIRST ONE I SAW, RWY 18.

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.