Narrative:

Socal TRACON (sct) called to apreq higher on aircraft Y 'reference all the departures' with my d-side. I heard the communication because I got on the line to listen to the coordination taking place. The d-side released the requested altitude of FL220 to sct in reference to aircraft Y and essentially placed the aircraft on a 265 heading to parallel the eastbound departures before vectoring the aircraft north/northeast towards sli. Sct shipped me aircraft X leaving 140 for 170 essentially. I climbed aircraft X to FL230; and called traffic on aircraft Y being 'worked by sct.' I did not receive communications on aircraft Y until enroute separation was obtained between the two aircraft. Additionally I apreq'd aircraft Y direct lhs to further separate the aircraft from jets proceeding sli..pom..dag.due to sct rules and procedures regarding separation and diverging courses; I did not believe an 'event' took place until after the supervisor brought this to my attention. As such; I have reviewed my own falcon and am honestly still not positive whether this constitutes a loss of separation based on the 7110 and the understanding the sct can hand off aircraft 3 NM and increasing with speeds. There are many instances where sct will transfer communications of an aircraft less than 5 NM above their stratum of 130 on either diverging courses or a faster aircraft in front.

Related reports:

Google
 

Original NASA ASRS Text

Title: An ARTCC Controller allowed a TRACON Controller to climb an aircraft into their airspace reference traffic the Center controller was working. The TRACON Controller transferred communications of their aircraft to the ARTCC Controller. The two aircraft were separated according to TRACON rules; but not Enroute (ARTCC) rules.

Narrative: SoCal TRACON (SCT) called to APREQ higher on Aircraft Y 'reference all the departures' with my D-Side. I heard the communication because I got on the line to listen to the coordination taking place. The D-side released the requested altitude of FL220 to SCT in reference to Aircraft Y and essentially placed the aircraft on a 265 heading to parallel the eastbound departures before vectoring the aircraft N/NE towards SLI. SCT shipped me Aircraft X leaving 140 for 170 essentially. I climbed Aircraft X to FL230; and called traffic on Aircraft Y being 'worked by SCT.' I did not receive communications on Aircraft Y until enroute separation was obtained between the two aircraft. Additionally I APREQ'D Aircraft Y direct LHS to further separate the aircraft from jets proceeding SLI..POM..DAG.Due to SCT rules and procedures regarding separation and diverging courses; I did not believe an 'event' took place until after the supervisor brought this to my attention. As such; I have reviewed my own Falcon and am honestly still not positive whether this constitutes a loss of separation based on the 7110 and the understanding the SCT can hand off aircraft 3 NM and increasing with speeds. There are many instances where SCT will transfer communications of an aircraft less than 5 NM above their stratum of 130 on either diverging courses or a faster aircraft in front.

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.