E10 controller described a loss of separation event when ZLA amended the route of a previous point o...

Narrative:

I was working the antelope; isabella and owens radar combined positions. I received a manual hand off from nellis approach from the northeast causing me to range out even further. Sct valley sector called me with an IFR point out (a hs-125) climbing to ZLA sector 17's airspace on the NUAL6 departure out of vny; I tagged up the point out; and continued working other traffic in other areas. ZLA made an amendment in fdio with the point out while the aircraft was still in my airspace; causing my data block to drop off the scope. I continued working my traffic and the 'event' occurred when a B737 was given a crossing restriction to cross janny at and maintain 8;000. Shortly after I observed the limited data block from the point out I had earlier received from sct valley sector within an unsafe proximity of the B737 and gave the B737 a sharp turn to the right.I believe that our equipment needs to be corrected so that when ZLA makes an amendment on an aircraft in our sky; it does not drop our data block; or there needs to be an LOA requiring coordination before any route amendments are made.

Original NASA ASRS Text

Title: E10 Controller described a loss of separation event when ZLA amended the route of a previous point out that resulted in the Data Block being dropped at the E10 display causing the conflict.

Narrative: I was working the Antelope; Isabella and Owens RADAR combined positions. I received a manual hand off from Nellis Approach from the northeast causing me to range out even further. SCT Valley Sector called me with an IFR point out (a HS-125) climbing to ZLA Sector 17's airspace on the NUAL6 departure out of VNY; I tagged up the point out; and continued working other traffic in other areas. ZLA made an amendment in FDIO with the point out while the aircraft was still in my airspace; causing my Data Block to drop off the scope. I continued working my traffic and the 'event' occurred when a B737 was given a crossing restriction to cross JANNY at and maintain 8;000. Shortly after I observed the limited Data Block from the point out I had earlier received from SCT Valley Sector within an unsafe proximity of the B737 and gave the B737 a sharp turn to the right.I believe that our equipment needs to be corrected so that when ZLA makes an amendment on an aircraft in our sky; it does not drop our Data Block; or there needs to be an LOA requiring coordination before any route amendments are made.

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

Attributes
ACN	963546
Time
Date	201108
Local Time Of Day	0001-0600
Place
Locale Reference	E10.TRACON
State Reference	CA
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Descent
Flight Plan	IFR
Aircraft 2
Make Model Name	HS 125 Series
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	SID NUAL6
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types

E10 controller described a loss of separation event when ZLA amended the route of a previous point out that resulted in the data block being dropped at the E10 display causing the conflict.