Narrative:

I was working as an atcs at jax TRACON, assigned to jax arrival radar north, departure radar north, and final radar combined on departure radar north. Traffic was moderate. I was working a spc X in the practice IFR pattern, being vectored to a localizer-back course runway 31 approach. As the spc X neared the position for a vector to base leg, I was distraction by several aircraft checking onto frequency. When I returned my attention to the spc X he was entering coast satellite radar airspace. I immediately issued a heading to return the aircraft to my sector, and immediately reached for the coordination line to alert the adjacent controller of my encroachment. Simultaneously, the 'satellite' controller alerted me verbally (not on recorded line) that he had IFR departure traffic airborne off crg airport. His traffic was not yet radar idented or tagged by ARTS. As the spc X was already wnwbound, and the traffic would at that time have already been east of the spc X, no traffic alert was issued to the spc X. The major cause of the error was my failure to give the top priority in very restrictive airspace. Contributing to the error were the combined sectors, requiring monitoring of quite a large area. Also, the close proximity of the 2 airports and current procedures not only allow but require a base leg turn to the localizer-back course runway 31 approach at jax to be made within 4 mi of adjacent airspace, and allows departures to be released, heading 010 off crg municipal airport without coordination between sectors. This procedure allows for almost zero errors in the vector pattern and absolutely no 'outs' should the turn not be issued, received and executed within a 15-20 second time frame.

Related reports:

Google
 

Original NASA ASRS Text

Title: APCH CTLR WORKING COMBINED POS ALLOWED SPC TO PENETRATE ADJACENT SECTOR AIRSPACE AND CAUSED A LTSS INCIDENT WITH AN SMT.

Narrative: I WAS WORKING AS AN ATCS AT JAX TRACON, ASSIGNED TO JAX ARR RADAR N, DEP RADAR N, AND FINAL RADAR COMBINED ON DEP RADAR N. TFC WAS MODERATE. I WAS WORKING A SPC X IN THE PRACTICE IFR PATTERN, BEING VECTORED TO A LOC-BC RWY 31 APCH. AS THE SPC X NEARED THE POS FOR A VECTOR TO BASE LEG, I WAS DISTR BY SEVERAL ACFT CHKING ONTO FREQ. WHEN I RETURNED MY ATTN TO THE SPC X HE WAS ENTERING COAST SATELLITE RADAR AIRSPACE. I IMMEDIATELY ISSUED A HDG TO RETURN THE ACFT TO MY SECTOR, AND IMMEDIATELY REACHED FOR THE COORD LINE TO ALERT THE ADJACENT CTLR OF MY ENCROACHMENT. SIMULTANEOUSLY, THE 'SATELLITE' CTLR ALERTED ME VERBALLY (NOT ON RECORDED LINE) THAT HE HAD IFR DEP TFC AIRBORNE OFF CRG ARPT. HIS TFC WAS NOT YET RADAR IDENTED OR TAGGED BY ARTS. AS THE SPC X WAS ALREADY WNWBOUND, AND THE TFC WOULD AT THAT TIME HAVE ALREADY BEEN E OF THE SPC X, NO TFC ALERT WAS ISSUED TO THE SPC X. THE MAJOR CAUSE OF THE ERROR WAS MY FAILURE TO GIVE THE TOP PRIORITY IN VERY RESTRICTIVE AIRSPACE. CONTRIBUTING TO THE ERROR WERE THE COMBINED SECTORS, REQUIRING MONITORING OF QUITE A LARGE AREA. ALSO, THE CLOSE PROX OF THE 2 ARPTS AND CURRENT PROCS NOT ONLY ALLOW BUT REQUIRE A BASE LEG TURN TO THE LOC-BC RWY 31 APCH AT JAX TO BE MADE WITHIN 4 MI OF ADJACENT AIRSPACE, AND ALLOWS DEPS TO BE RELEASED, HDG 010 OFF CRG MUNICIPAL ARPT WITHOUT COORD BTWN SECTORS. THIS PROC ALLOWS FOR ALMOST ZERO ERRORS IN THE VECTOR PATTERN AND ABSOLUTELY NO 'OUTS' SHOULD THE TURN NOT BE ISSUED, RECEIVED AND EXECUTED WITHIN A 15-20 SECOND TIME FRAME.

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.