A B757 lands on runway 26R after being vectored for a landing on runway 26L at phx, az.

Attributes
ACN	448059
Time
Date	199909
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : phx.airport
State Reference	AZ
Altitude	agl bound lower : 0 agl bound upper : 1500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : phx.tower
Operator	common carrier : air carrier
Make Model Name	B757 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	approach : visual arrival : 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 : 200 flight time total : 18000 flight time type : 200
ASRS Report	448059
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : clearance
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Being vectored for a landing on runway 26L, the controller instructed us to tune in and contact tower. I mistakenly looked at the tower frequency for runway 26R. When we contacted tower the controller cleared us to land on runway 26R. We questioned the clearance since we were being vectored and expected clearance for runway 26L at phx. We were again cleared to land on runway 26R. We sidestepped to the right and landed without incident. Upon taxiing to our gate, the ground controller asked us who cleared us to land. We responded, the tower. The captain was then requested to contact the tower chief by phone. He had a conversation with the tower chief. We surprised the approach controller by landing on a different runway than he had vectored us to. The tower controller did not question us and just cleared us to land on his runway when we contacted him. There was no traffic conflict fortunately.

Original NASA ASRS Text

Title: A B757 LANDS ON RWY 26R AFTER BEING VECTORED FOR A LNDG ON RWY 26L AT PHX, AZ.

Narrative: BEING VECTORED FOR A LNDG ON RWY 26L, THE CTLR INSTRUCTED US TO TUNE IN AND CONTACT TWR. I MISTAKENLY LOOKED AT THE TWR FREQ FOR RWY 26R. WHEN WE CONTACTED TWR THE CTLR CLRED US TO LAND ON RWY 26R. WE QUESTIONED THE CLRNC SINCE WE WERE BEING VECTORED AND EXPECTED CLRNC FOR RWY 26L AT PHX. WE WERE AGAIN CLRED TO LAND ON RWY 26R. WE SIDESTEPPED TO THE R AND LANDED WITHOUT INCIDENT. UPON TAXIING TO OUR GATE, THE GND CTLR ASKED US WHO CLRED US TO LAND. WE RESPONDED, THE TWR. THE CAPT WAS THEN REQUESTED TO CONTACT THE TWR CHIEF BY PHONE. HE HAD A CONVERSATION WITH THE TWR CHIEF. WE SURPRISED THE APCH CTLR BY LNDG ON A DIFFERENT RWY THAN HE HAD VECTORED US TO. THE TWR CTLR DID NOT QUESTION US AND JUST CLRED US TO LAND ON HIS RWY WHEN WE CONTACTED HIM. THERE WAS NO TFC CONFLICT FORTUNATELY.

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.