Narrative:

While working combined sectors with moderate-heavy traffic, spc called for service. Because of the nature of his initial call-up, no visibility data displayed on radar and no flight progress strip indicating differently, I handled this aircraft as a VFR pop-up requesting arsa service. I advised the aircraft to remain outside the arsa and when workload permitted I returned to spc to provide arsa service. When spc's general position was determined to be within the san TRACON's airspace, a VFR handoff was coordinated with san TRACON, and the aircraft was changed to san TRACON's frequency. My supervisor was notified as soon as possible. Note: aircraft was actually on IFR flight plan from riv to nzy.

Google
 

Original NASA ASRS Text

Title: SPC ENTERED ADJACENT FAC'S AIRSPACE WITHOUT PROPER COORD.

Narrative: WHILE WORKING COMBINED SECTORS WITH MODERATE-HEAVY TFC, SPC CALLED FOR SVC. BECAUSE OF THE NATURE OF HIS INITIAL CALL-UP, NO VIS DATA DISPLAYED ON RADAR AND NO FLT PROGRESS STRIP INDICATING DIFFERENTLY, I HANDLED THIS ACFT AS A VFR POP-UP REQUESTING ARSA SVC. I ADVISED THE ACFT TO REMAIN OUTSIDE THE ARSA AND WHEN WORKLOAD PERMITTED I RETURNED TO SPC TO PROVIDE ARSA SVC. WHEN SPC'S GENERAL POS WAS DETERMINED TO BE WITHIN THE SAN TRACON'S AIRSPACE, A VFR HDOF WAS COORDINATED WITH SAN TRACON, AND THE ACFT WAS CHANGED TO SAN TRACON'S FREQ. MY SUPVR WAS NOTIFIED ASAP. NOTE: ACFT WAS ACTUALLY ON IFR FLT PLAN FROM RIV TO NZY.

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