Narrative:

While working traffic; I noticed aircraft X turn northbound. As I did a route readout to see where aircraft was supposed to be going and realized where he was going; approach called asking where aircraft X was going. I said 'I don't know; I'll ask when he checks in'. As I was talking to approach aircraft X checks in; but I never heard what he said. I got off the line with approach and told aircraft X to amend altitude and maintain 10000 feet. He said he was already level at 10000 feet. I turned aircraft X to a 240 heading to get him out of approach's airspace. I asked aircraft X what his clearance and routing from tower was and he said he was issued the [SID] departure. We showed he was on a different SID which should have been a 250 heading into ZLA's airspace. I asked if he responded to an RA and aircraft X said affirmative; that's why he stopped at 10000 feet before I even told him to maintain 10000 feet. I called approach after and asked if they knew the call sign of their aircraft they were working but they weren't sure. A few minutes had passed since it happened. She said she thinks it was an air carrier and that their aircraft responded to an RA and descended. Aircraft X was on noise abatement procedures and not the normal SID. Noise abatement procedures start at xa:00 local and this even happened at roughly xa:45 local. He was issued the normal SID from the tower but with noise abatement procedures on; he was supposed to be on the noise abatement SID. Throughout this event; I don't recall conflict alert ever going off; even when I was talking to aircraft X and told him to maintain 10000 feet and saw a limited data block pass off his right side at 9800 feet. Approach and tower need to be more conscientious on noise abatement departing aircraft to verify their routes.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZLA Center controller reported they received an aircraft from Approach on the wrong SID which had just responded to an RA in Approach's airspace.

Narrative: While working traffic; I noticed Aircraft X turn northbound. As I did a route readout to see where aircraft was supposed to be going and realized where he was going; Approach called asking where Aircraft X was going. I said 'I don't know; I'll ask when he checks in'. As I was talking to Approach Aircraft X checks in; but I never heard what he said. I got off the line with Approach and told Aircraft X to amend altitude and maintain 10000 feet. He said he was already level at 10000 feet. I turned Aircraft X to a 240 heading to get him out of Approach's airspace. I asked Aircraft X what his clearance and routing from Tower was and he said he was issued the [SID] departure. We showed he was on a different SID which should have been a 250 heading into ZLA's airspace. I asked if he responded to an RA and Aircraft X said affirmative; that's why he stopped at 10000 feet before I even told him to maintain 10000 feet. I called Approach after and asked if they knew the call sign of their aircraft they were working but they weren't sure. A few minutes had passed since it happened. She said she thinks it was an air carrier and that their aircraft responded to an RA and descended. Aircraft X was on noise abatement procedures and not the normal SID. Noise abatement procedures start at XA:00 local and this even happened at roughly XA:45 local. He was issued the normal SID from the tower but with noise abatement procedures on; he was supposed to be on the noise abatement SID. Throughout this event; I don't recall conflict alert ever going off; even when I was talking to Aircraft X and told him to maintain 10000 feet and saw a limited data block pass off his right side at 9800 feet. Approach and Tower need to be more conscientious on noise abatement departing aircraft to verify their routes.

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.