Two reports of an aircraft that was doing what it was told to do. The error was the departing aircra...

Attributes
ACN	1177415
Time
Date	201406
Local Time Of Day	1201-1800
Place
Locale Reference	SCT.TRACON
State Reference	CA
Environment
Light	Daylight
Aircraft 1
Make Model Name	Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID CASTA3
Flight Plan	IFR
Aircraft 2
Make Model Name	Widebody Low Wing 4 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Flight Plan	IFR
Person 1
Function	Departure
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 15
Person 2
Function	Departure
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (mon) 6
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy

Narrative:

I had just relieved another controller and during the briefing I was told that aircraft X was issued 9;000 feet which is the standard altitude that casta departures climb to. I was also told that aircraft X was in a vector for spacing with the casta departure in front of him; due to insufficient spacing provided by lax tower. I was vectoring aircraft X back to join the SID at the ajaye intersection. Aircraft Y was inbound to lax at 10;000 feet. I saw that aircraft and was trying to get aircraft X in front of the aircraft Y so he wouldn't be what I thought would be 1;000 feet below the super aircraft. As I was vectoring the aircraft I observed a few hits at 9;000 feet which was the expected altitude for aircraft X to be at. As I cleared aircraft X direct ajaye I noticed his altitude was 10;000 feet; climbing. I questioned aircraft X and he told me that he was cleared to 13;000 feet. He told me that he had the aircraft in sight and was continuing his climb. I coordinated the altitude with the next sector since that was not the SOP altitude. I then switched aircraft X to the next controller.I don't know. It was just a mistake by the controller during the briefing.

Original NASA ASRS Text

Title: Two reports of an aircraft that was doing what it was told to do. The error was the departing aircraft was assigned the wrong altitude and came close to traffic that was level on an arrival.

Narrative: I had just relieved another controller and during the briefing I was told that Aircraft X was issued 9;000 feet which is the standard altitude that CASTA departures climb to. I was also told that Aircraft X was in a vector for spacing with the CASTA departure in front of him; due to insufficient spacing provided by LAX Tower. I was vectoring Aircraft X back to join the SID at the AJAYE intersection. Aircraft Y was inbound to LAX at 10;000 feet. I saw that aircraft and was trying to get Aircraft X in front of the Aircraft Y so he wouldn't be what I thought would be 1;000 feet below the super aircraft. As I was vectoring the aircraft I observed a few hits at 9;000 feet which was the expected altitude for Aircraft X to be at. As I cleared Aircraft X direct AJAYE I noticed his altitude was 10;000 feet; climbing. I questioned Aircraft X and he told me that he was cleared to 13;000 feet. He told me that he had the aircraft in sight and was continuing his climb. I coordinated the altitude with the next sector since that was not the SOP altitude. I then switched Aircraft X to the next controller.I don't know. It was just a mistake by the controller during the briefing.

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