B737-700 flight crew has a close-in runway change issued on the seavu one arrival to lax.

Attributes
ACN	722932
Time
Date	200701
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : lax.airport
State Reference	CA
Altitude	msl single value : 11000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : sct.artcc
Operator	common carrier : air carrier
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	arrival star : seavu
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 211 flight time type : 5500
ASRS Report	722932
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 192 flight time type : 500
ASRS Report	722927
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Ambiguous

Narrative:

First officer was flying the SEAVU1 RNAV arrival to lax. Approach (socal) cleared us to descend via the SEAVU1 to runway 24R. I read back that clearance. First officer heard the radio communication. When we switched to the next approach controller; he cleared us the ILS runway 25R after musik. When he said that; I queried him on the runway we were cleared to and he responded it was runway 25R. We were past luvyn on the arrival so he gave us a vector back to the course for runway 25R. The rest of the approach and landing were normal. Neither of us thought we were cleared to runway 25R from the previous controller and we both thought I had read back cleared for runway 24R. Traffic was light and it was VFR. The first officer had briefed a planned visual approach to runway 24R. We may have both simply heard what we wanted to hear from the first approach. We debriefed the event between each other after landing at lax. I will check in with the new approach control from now on with the intended runway to verify in the future instead of just stating company number at 12000 feet descending via the SEAVU1 (add 'for runway 24R').

Original NASA ASRS Text

Title: B737-700 FLT CREW HAS A CLOSE-IN RWY CHANGE ISSUED ON THE SEAVU ONE ARR TO LAX.

Narrative: FO WAS FLYING THE SEAVU1 RNAV ARRIVAL TO LAX. APPROACH (SOCAL) CLEARED US TO DESCEND VIA THE SEAVU1 TO RWY 24R. I READ BACK THAT CLEARANCE. FO HEARD THE RADIO COMMUNICATION. WHEN WE SWITCHED TO THE NEXT APPROACH CONTROLLER; HE CLEARED US THE ILS RWY 25R AFTER MUSIK. WHEN HE SAID THAT; I QUERIED HIM ON THE RUNWAY WE WERE CLEARED TO AND HE RESPONDED IT WAS RWY 25R. WE WERE PAST LUVYN ON THE ARRIVAL SO HE GAVE US A VECTOR BACK TO THE COURSE FOR RWY 25R. THE REST OF THE APPROACH AND LANDING WERE NORMAL. NEITHER OF US THOUGHT WE WERE CLEARED TO RWY 25R FROM THE PREVIOUS CONTROLLER AND WE BOTH THOUGHT I HAD READ BACK CLEARED FOR RWY 24R. TRAFFIC WAS LIGHT AND IT WAS VFR. THE FO HAD BRIEFED A PLANNED VISUAL APPROACH TO RWY 24R. WE MAY HAVE BOTH SIMPLY HEARD WHAT WE WANTED TO HEAR FROM THE FIRST APPROACH. WE DEBRIEFED THE EVENT BETWEEN EACH OTHER AFTER LANDING AT LAX. I WILL CHECK IN WITH THE NEW APPROACH CONTROL FROM NOW ON WITH THE INTENDED RUNWAY TO VERIFY IN THE FUTURE INSTEAD OF JUST STATING COMPANY NUMBER AT 12000 FEET DESCENDING VIA THE SEAVU1 (ADD 'FOR RWY 24R').

Data retrieved from NASA's ASRS site as of January 2009 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.