Narrative:

I just split the miramar sector off from north. There were 4 controllers coordinating with me during the split and for the first 5 mins thereafter. During this time, I released the C130 from nkx. When the C130 reported airborne, he was acknowledged, but not idented. At this time, flight data coordinated with me for special operations into nkx, (flight data controller is not checked out on the miramar sector). When I finished explaining to flight data controller what is required, the supervisor brought me a piece of paper and explained that special coordination would be needed. At this point, an aircraft called requesting clearance to nkx. (The aircraft was already in class B airspace without a clearance.) I turned to request arrival information to nkx from my supervisor who said he'd have to go get it. I coordinated with nkx ATCT at length just as ont area (hemet) was requesting special services on a C141 handoff from the north. While trying to ascertain from the pilot of the C141 what exactly he wanted to do, the C130 tagged up 29 mi north of nkx. This was adjacent airspace. This was a very typical chain of events leading to an operational error. There was no primary or secondary associated with the C130 when he departed. (There was training going on at the sector the C130 entered and flew through.) both controllers stated they saw nothing fly through -- primary or secondary. Not one operation at the sector was normal. There was far too much coordination required at the sector. There needed to be a handoff controller. Information pertaining to air show activities was not available at the sector. When it did arrive, the information was set in front of me on top of the departure strip. In short, when this aircraft departed, there were too many distrs, there was no target to identify for 29 mi. The refresher training I received had no bearing on what occurred at the sector!

Related reports:

Google
 

Original NASA ASRS Text

Title: TRACON CTLR DESCRIBES MULTIPLE DISTR EVENTS THAT TAKE HIS ATTN AWAY FROM RADAR IDENTING A RELEASED IFR DEP.

Narrative: I JUST SPLIT THE MIRAMAR SECTOR OFF FROM N. THERE WERE 4 CTLRS COORDINATING WITH ME DURING THE SPLIT AND FOR THE FIRST 5 MINS THEREAFTER. DURING THIS TIME, I RELEASED THE C130 FROM NKX. WHEN THE C130 RPTED AIRBORNE, HE WAS ACKNOWLEDGED, BUT NOT IDENTED. AT THIS TIME, FLT DATA COORDINATED WITH ME FOR SPECIAL OPS INTO NKX, (FLT DATA CTLR IS NOT CHKED OUT ON THE MIRAMAR SECTOR). WHEN I FINISHED EXPLAINING TO FLT DATA CTLR WHAT IS REQUIRED, THE SUPVR BROUGHT ME A PIECE OF PAPER AND EXPLAINED THAT SPECIAL COORD WOULD BE NEEDED. AT THIS POINT, AN ACFT CALLED REQUESTING CLRNC TO NKX. (THE ACFT WAS ALREADY IN CLASS B AIRSPACE WITHOUT A CLRNC.) I TURNED TO REQUEST ARR INFO TO NKX FROM MY SUPVR WHO SAID HE'D HAVE TO GO GET IT. I COORDINATED WITH NKX ATCT AT LENGTH JUST AS ONT AREA (HEMET) WAS REQUESTING SPECIAL SVCS ON A C141 HDOF FROM THE N. WHILE TRYING TO ASCERTAIN FROM THE PLT OF THE C141 WHAT EXACTLY HE WANTED TO DO, THE C130 TAGGED UP 29 MI N OF NKX. THIS WAS ADJACENT AIRSPACE. THIS WAS A VERY TYPICAL CHAIN OF EVENTS LEADING TO AN OPERROR. THERE WAS NO PRIMARY OR SECONDARY ASSOCIATED WITH THE C130 WHEN HE DEPARTED. (THERE WAS TRAINING GOING ON AT THE SECTOR THE C130 ENTERED AND FLEW THROUGH.) BOTH CTLRS STATED THEY SAW NOTHING FLY THROUGH -- PRIMARY OR SECONDARY. NOT ONE OP AT THE SECTOR WAS NORMAL. THERE WAS FAR TOO MUCH COORD REQUIRED AT THE SECTOR. THERE NEEDED TO BE A HDOF CTLR. INFO PERTAINING TO AIR SHOW ACTIVITIES WAS NOT AVAILABLE AT THE SECTOR. WHEN IT DID ARRIVE, THE INFO WAS SET IN FRONT OF ME ON TOP OF THE DEP STRIP. IN SHORT, WHEN THIS ACFT DEPARTED, THERE WERE TOO MANY DISTRS, THERE WAS NO TARGET TO IDENT FOR 29 MI. THE REFRESHER TRAINING I RECEIVED HAD NO BEARING ON WHAT OCCURRED AT THE SECTOR!

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.