C172 landing at luk follows wrong aircraft, over flies wrong runway and is issued go around.

Attributes
ACN	597360
Time
Date	200310
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : luk.airport
State Reference	OH
Altitude	msl single value : 1500
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : luk.tower
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Route In Use	approach : traffic pattern
Flight Plan	None
Aircraft 2
Controlling Facilities	tower : luk.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent : approach
Route In Use	approach : traffic pattern
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : private pilot : multi engine
Experience	flight time last 90 days : 74 flight time total : 170 flight time type : 101
ASRS Report	597360
Person 2
Function	oversight : pic
Events
Anomaly	conflict : airborne less severe non adherence : clearance other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : took precautionary avoidance action flight crew : executed go around flight crew : became reoriented
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While turning crosswind in the traffic pattern (for the left runway of 2 parallel runways), tower advised that an aircraft was on a 3 mi base and that I was #2 for landing. I continued with the pattern and saw what I believed was the #1 aircraft crossing the threshold for landing. I turned my left base and called tower. Tower immediately advised me that I had cut in front of the #1 aircraft. I continued on the base, not sure exactly what to do, but I called the tower to ask if I should continue straight on the base or continue the approach. Tower told me to continue the approach, but for a low approach only, no landing. I turned final and began the low approach. When over the field, tower called again asking if I was over the right runway. I looked to my left and saw that I had turned final for my low approach over the wrong runway. This incident occurred because I acknowledged that I was #2 for landing, but did not follow up on it with enough care. In retrospect, I realize that an aircraft on a 3 mi base could hardly have been crossing the threshold by the time I was ready to turn my base. I should have thought this through and then asked tower for the position of the #1 aircraft before turning my base. I also could have asked tower to call my base for me. Then by the time I figured out what I should do next after turning my base and asked tower what I should do, I had flown an abnormally long base which put me in position for a final on the right runway. Before turning final, I should have been more attentive to my position and not let the previous mistake cause additional mistakes.

Original NASA ASRS Text

Title: C172 LNDG AT LUK FOLLOWS WRONG ACFT, OVER FLIES WRONG RWY AND IS ISSUED GAR.

Narrative: WHILE TURNING XWIND IN THE TFC PATTERN (FOR THE L RWY OF 2 PARALLEL RWYS), TWR ADVISED THAT AN ACFT WAS ON A 3 MI BASE AND THAT I WAS #2 FOR LNDG. I CONTINUED WITH THE PATTERN AND SAW WHAT I BELIEVED WAS THE #1 ACFT XING THE THRESHOLD FOR LNDG. I TURNED MY L BASE AND CALLED TWR. TWR IMMEDIATELY ADVISED ME THAT I HAD CUT IN FRONT OF THE #1 ACFT. I CONTINUED ON THE BASE, NOT SURE EXACTLY WHAT TO DO, BUT I CALLED THE TWR TO ASK IF I SHOULD CONTINUE STRAIGHT ON THE BASE OR CONTINUE THE APCH. TWR TOLD ME TO CONTINUE THE APCH, BUT FOR A LOW APCH ONLY, NO LNDG. I TURNED FINAL AND BEGAN THE LOW APCH. WHEN OVER THE FIELD, TWR CALLED AGAIN ASKING IF I WAS OVER THE RIGHT RWY. I LOOKED TO MY L AND SAW THAT I HAD TURNED FINAL FOR MY LOW APCH OVER THE WRONG RWY. THIS INCIDENT OCCURRED BECAUSE I ACKNOWLEDGED THAT I WAS #2 FOR LNDG, BUT DID NOT FOLLOW UP ON IT WITH ENOUGH CARE. IN RETROSPECT, I REALIZE THAT AN ACFT ON A 3 MI BASE COULD HARDLY HAVE BEEN XING THE THRESHOLD BY THE TIME I WAS READY TO TURN MY BASE. I SHOULD HAVE THOUGHT THIS THROUGH AND THEN ASKED TWR FOR THE POS OF THE #1 ACFT BEFORE TURNING MY BASE. I ALSO COULD HAVE ASKED TWR TO CALL MY BASE FOR ME. THEN BY THE TIME I FIGURED OUT WHAT I SHOULD DO NEXT AFTER TURNING MY BASE AND ASKED TWR WHAT I SHOULD DO, I HAD FLOWN AN ABNORMALLY LONG BASE WHICH PUT ME IN POS FOR A FINAL ON THE RIGHT RWY. BEFORE TURNING FINAL, I SHOULD HAVE BEEN MORE ATTENTIVE TO MY POS AND NOT LET THE PREVIOUS MISTAKE CAUSE ADDITIONAL MISTAKES.

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.