ZOA controller described loss of separation event listing the probable cause as the failure of a nct...

Narrative:

While working right/D sector 44 received hand off from nct on aircraft X. Aircraft data block indicated VFR/065 climbing; heading eastbound. Nct called to advise aircraft was preceding direct truck intersection. Issued departure clearance to aircraft Y from trk via Truck3 departure truck intersection and hold; climb to 120. When aircraft X was about 15 miles west of truck intersection; I advised him that an IFR departure would be leaving trk climbing to 120. He advised he would be looking for him. Shortly after I advised aircraft Y that a VFR aircraft would be transiting the area and aircraft Y said he would look for him. After the transmission to aircraft Y; aircraft X advised that he was on an IFR flight plan. Considering the probable proximity of the two aircraft; one of which was non-radar; I took the aircraft X at his word and issued expedited climb to 130. I tried to get a hold of aircraft Y to cancel his departure clearance but did not receive a response. Aircraft X accepted climb clearance and verified he could maintain his own terrain clearance. Since I could not get in touch with aircraft Y; I issued 40 degree left turn to aircraft X to drive him away from truck intersection. Then aircraft Y checked on; having departed and climbing out of 085 to 120 heading to truck. I asked if he could maintain terrain clearance at 105 and he said he could but made it through 110 before heading back down. The aircraft X had difficulty climbing and stopped at 112 for some time; creating the loss of separation. Through the initial investigation I found that the aircraft X had in fact been given an IFR clearance from nct but the information on the data block indicated VFR. Also; listening to the aircraft X's initial check in he states that he is climbing to 'climbing to one zero thousand IFR' but due to significant static on the frequency and I believe I heard him say climbing to 'one zero thousand five'. Why the data block indicated VFR when the aircraft was IFR; I do not know. I have been advised that nct followed proper procedure regarding the starting and hand off of the aircraft data block.

Original NASA ASRS Text

Title: ZOA controller described loss of separation event listing the probable cause as the failure of a NCT controller to properly code the Data Block as IFR; resulting in a conflict with an IFR departure from TRK.

Narrative: While working R/D Sector 44 received hand off from NCT on Aircraft X. Aircraft data block indicated VFR/065 climbing; heading eastbound. NCT called to advise aircraft was preceding direct Truck intersection. Issued departure clearance to Aircraft Y from TRK via Truck3 departure TRUCK intersection and hold; climb to 120. When Aircraft X was about 15 miles west of TRUCK intersection; I advised him that an IFR departure would be leaving TRK climbing to 120. He advised he would be looking for him. Shortly after I advised Aircraft Y that a VFR aircraft would be transiting the area and Aircraft Y said he would look for him. After the transmission to Aircraft Y; Aircraft X advised that he was on an IFR flight plan. Considering the probable proximity of the two aircraft; one of which was non-RADAR; I took the Aircraft X at his word and issued expedited climb to 130. I tried to get a hold of Aircraft Y to cancel his departure clearance but did not receive a response. Aircraft X accepted climb clearance and verified he could maintain his own terrain clearance. Since I could not get in touch with Aircraft Y; I issued 40 degree left turn to Aircraft X to drive him away from TRUCK intersection. Then Aircraft Y checked on; having departed and climbing out of 085 to 120 heading to TRUCK. I asked if he could maintain terrain clearance at 105 and he said he could but made it through 110 before heading back down. The Aircraft X had difficulty climbing and stopped at 112 for some time; creating the loss of separation. Through the initial investigation I found that the Aircraft X had in fact been given an IFR clearance from NCT but the information on the data block indicated VFR. Also; listening to the Aircraft X's initial check in he states that he is climbing to 'climbing to one zero thousand IFR' but due to significant static on the frequency and I believe I heard him say climbing to 'one zero thousand five'. Why the data block indicated VFR when the aircraft was IFR; I do not know. I have been advised that NCT followed proper procedure regarding the starting and hand off of the aircraft data block.

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	882538
Time
Date	201004
Local Time Of Day	1801-2400
Place
Locale Reference	ZOA.ARTCC
State Reference	CA
Aircraft 1
Make Model Name	Skylane 182/RG Turbo Skylane/RG
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Light Transport Low Wing 2 Turbojet Eng
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

ZOA controller described loss of separation event listing the probable cause as the failure of a nct controller to properly code the data block as IFR; resulting in a conflict with an IFR departure from trk.