Heading track deviation on a wrong runway approach.

Attributes
ACN	200298
Time
Date	199201
Day	Tue
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : rdu
State Reference	NC
Altitude	msl bound lower : 2000 msl bound upper : 3000
Environment
Flight Conditions	Mixed
Light	Night
Aircraft 1
Controlling Facilities	tracon : rdu
Operator	general aviation : corporate
Make Model Name	Small Transport, Low Wing, 2 Turboprop Eng
Flight Phase	descent : approach landing other
Route In Use	approach : visual enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 30 flight time total : 5000 flight time type : 1000
ASRS Report	200298
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

This was pretty much a standard 'you hear what you expect to hear' situation. I still don't know if I was cleared for a 23R ILS, which I executed until breaking out for a visual, or the 23L approach as the controller expected. I was on the bussy arrival (from the south) and was given vectors to final ending in a 'maintain 2000 until intercepting the final approach course.' I passed through the 23L final and established on the 23R final after a slight overshoot. The controller observed that I was lined up for the wrong runway and I was reclred for the 23R approach while breaking out for a visual. Landing was without incident. I have flown similar approachs to rdu before (crossing through one final for another) and was expecting to do it again. Having now had this happen to me, I plan to be much more vigilant in accepting and reading back a clearance. On the controller's part the readback should be insisted upon, and perhaps the landing runway should be mentioned in the approach clearance (I don't believe it was). For my own edification, if there is any further investigation, I would love to hear the tape.

Original NASA ASRS Text

Title: HDG TRACK DEV ON A WRONG RWY APCH.

Narrative: THIS WAS PRETTY MUCH A STANDARD 'YOU HEAR WHAT YOU EXPECT TO HEAR' SITUATION. I STILL DON'T KNOW IF I WAS CLRED FOR A 23R ILS, WHICH I EXECUTED UNTIL BREAKING OUT FOR A VISUAL, OR THE 23L APCH AS THE CTLR EXPECTED. I WAS ON THE BUSSY ARR (FROM THE S) AND WAS GIVEN VECTORS TO FINAL ENDING IN A 'MAINTAIN 2000 UNTIL INTERCEPTING THE FINAL APCH COURSE.' I PASSED THROUGH THE 23L FINAL AND ESTABLISHED ON THE 23R FINAL AFTER A SLIGHT OVERSHOOT. THE CTLR OBSERVED THAT I WAS LINED UP FOR THE WRONG RWY AND I WAS RECLRED FOR THE 23R APCH WHILE BREAKING OUT FOR A VISUAL. LNDG WAS WITHOUT INCIDENT. I HAVE FLOWN SIMILAR APCHS TO RDU BEFORE (XING THROUGH ONE FINAL FOR ANOTHER) AND WAS EXPECTING TO DO IT AGAIN. HAVING NOW HAD THIS HAPPEN TO ME, I PLAN TO BE MUCH MORE VIGILANT IN ACCEPTING AND READING BACK A CLRNC. ON THE CTLR'S PART THE READBACK SHOULD BE INSISTED UPON, AND PERHAPS THE LNDG RWY SHOULD BE MENTIONED IN THE APCH CLRNC (I DON'T BELIEVE IT WAS). FOR MY OWN EDIFICATION, IF THERE IS ANY FURTHER INVESTIGATION, I WOULD LOVE TO HEAR THE TAPE.

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.