Citation 560XL flight crew has a track/heading deviation during seavu one arrival to lax.

Attributes
ACN	730388
Time
Date	200703
Local Time Of Day	0601 To 1200
Place
Locale Reference	intersection : krain
State Reference	CA
Altitude	msl single value : 10000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : sct.tracon
Operator	general aviation : corporate
Make Model Name	Citation Excel
Operating Under FAR Part	Part 91
Navigation In Use	ils localizer & glide slope : 24r other
Flight Phase	descent : approach
Route In Use	approach : instrument precision arrival star : seavu 1
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : cfi
Experience	flight time last 90 days : 150 flight time total : 7000 flight time type : 2500
ASRS Report	730388
Person 2
Affiliation	company : corporate
Function	flight crew : first officer
Events
Anomaly	non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

During approach to lax outside of tnp we were assigned the seavu one arrival. We were originally given the PDZ4. At that time we had to pick a runway in order to load the approach into the FMS. We chose runway 25R since it was closest to our parking location. After konzl we were cleared to descend via the seavu one arrival. I do not recall receiving a runway assignment at that time. The arrival is the same for all runways until the fix luvyn; then it breaks off each of the 4 runways. At krain we were told to intercept the localizer at palac. We noticed palac was a fix for runway 24R. We then asked for a vector and to clarify runway. We were told to turn right 10 degrees and intercept runway 24R localizer. At no time did ATC query us regarding course. Nor did they say anything after we asked for the vector. At the point we caught the error we had deviated less than 2 miles; 30 degrees off course; for 4 miles. We were following the arrival for runway 25R. There was no altitude deviation. There was no traffic conflict.

Original NASA ASRS Text

Title: CITATION 560XL FLT CREW HAS A TRACK/HEADING DEVIATION DURING SEAVU ONE ARR TO LAX.

Narrative: DURING APCH TO LAX OUTSIDE OF TNP WE WERE ASSIGNED THE SEAVU ONE ARR. WE WERE ORIGINALLY GIVEN THE PDZ4. AT THAT TIME WE HAD TO PICK A RWY IN ORDER TO LOAD THE APCH INTO THE FMS. WE CHOSE RWY 25R SINCE IT WAS CLOSEST TO OUR PARKING LOCATION. AFTER KONZL WE WERE CLRED TO DSND VIA THE SEAVU ONE ARR. I DO NOT RECALL RECEIVING A RWY ASSIGNMENT AT THAT TIME. THE ARR IS THE SAME FOR ALL RWYS UNTIL THE FIX LUVYN; THEN IT BREAKS OFF EACH OF THE 4 RWYS. AT KRAIN WE WERE TOLD TO INTERCEPT THE LOCALIZER AT PALAC. WE NOTICED PALAC WAS A FIX FOR RWY 24R. WE THEN ASKED FOR A VECTOR AND TO CLARIFY RWY. WE WERE TOLD TO TURN R 10 DEGS AND INTERCEPT RWY 24R LOCALIZER. AT NO TIME DID ATC QUERY US REGARDING COURSE. NOR DID THEY SAY ANYTHING AFTER WE ASKED FOR THE VECTOR. AT THE POINT WE CAUGHT THE ERROR WE HAD DEVIATED LESS THAN 2 MILES; 30 DEGS OFF COURSE; FOR 4 MILES. WE WERE FOLLOWING THE ARRIVAL FOR RWY 25R. THERE WAS NO ALT DEV. THERE WAS NO TFC CONFLICT.

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.