Flight crew of B737-200 has runway change when being vectored onto localizer. They input new informa...

Attributes
ACN	385400
Time
Date	199711
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : rdu
State Reference	NC
Altitude	msl bound lower : 2400 msl bound upper : 2400
Environment
Flight Conditions	Marginal
Light	Dusk
Aircraft 1
Controlling Facilities	tracon : rdu tower : rdu tower : bos
Operator	common carrier : air carrier
Make Model Name	B737-200
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 11000 flight time type : 3000
ASRS Report	385400
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	other other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Upon initial contact with rdu approach, we were advised to expect vectors to ILS runway 5L (frequency 109.1). We had briefed ILS runway 5R for approach briefing (nearer to our gates), so we then briefed runway 5L. Approaching base leg on downwind, we were advised to expect ILS runway 5R (frequency 109.5). We acknowledged and rebriefed runway 5R. We were then vectored onto the localizer and turned over to tower, who advised us we were left of course. We acknowledged that we were showing on course, to which tower told us to turn right and climb to 3000 ft for missed approach. We complied, and then realized that when given runway 5R, we had not changed the localizer frequency from 109.1 to 109.5. We contacted the approach controller, who gave us the frequency at that point (109.5 for runway 5R) and we proceeded to shoot runway 5R ILS and land with no further incident. No conflict with any traffic occurred at any time. In the future, I will make sure to set new frequency with new expect clearance, immediately, or if I feel rushed to make the change, insist that we stay with original runway assignment.

Original NASA ASRS Text

Title: FLC OF B737-200 HAS RWY CHANGE WHEN BEING VECTORED ONTO LOC. THEY INPUT NEW INFO EXCEPT FOR THE NEW LOC FREQ. TWR ADVISES THEY ARE OFF COURSE AND GIVE THEM A MISSED APCH. NEXT APCH IS CORRECT.

Narrative: UPON INITIAL CONTACT WITH RDU APCH, WE WERE ADVISED TO EXPECT VECTORS TO ILS RWY 5L (FREQ 109.1). WE HAD BRIEFED ILS RWY 5R FOR APCH BRIEFING (NEARER TO OUR GATES), SO WE THEN BRIEFED RWY 5L. APCHING BASE LEG ON DOWNWIND, WE WERE ADVISED TO EXPECT ILS RWY 5R (FREQ 109.5). WE ACKNOWLEDGED AND REBRIEFED RWY 5R. WE WERE THEN VECTORED ONTO THE LOC AND TURNED OVER TO TWR, WHO ADVISED US WE WERE L OF COURSE. WE ACKNOWLEDGED THAT WE WERE SHOWING ON COURSE, TO WHICH TWR TOLD US TO TURN R AND CLB TO 3000 FT FOR MISSED APCH. WE COMPLIED, AND THEN REALIZED THAT WHEN GIVEN RWY 5R, WE HAD NOT CHANGED THE LOC FREQ FROM 109.1 TO 109.5. WE CONTACTED THE APCH CTLR, WHO GAVE US THE FREQ AT THAT POINT (109.5 FOR RWY 5R) AND WE PROCEEDED TO SHOOT RWY 5R ILS AND LAND WITH NO FURTHER INCIDENT. NO CONFLICT WITH ANY TFC OCCURRED AT ANY TIME. IN THE FUTURE, I WILL MAKE SURE TO SET NEW FREQ WITH NEW EXPECT CLRNC, IMMEDIATELY, OR IF I FEEL RUSHED TO MAKE THE CHANGE, INSIST THAT WE STAY WITH ORIGINAL RWY ASSIGNMENT.

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.

Flight crew of B737-200 has runway change when being vectored onto localizer. They input new information except for the new localizer frequency. Tower advises they are off course and give them a missed approach. Next approach is correct.