ZJX CTLR DESCRIBED BUSY TFC PERIOD WHEN TMU RELEASED TFC WITHOUT SECTOR COORD RESULTING IN IFR ACFT ENTERING RESTRICTED AREA.

Date: 2008-03 · Aircraft: Any Unknown or Unlisted Aircraft Manufacturer · Phase: initial_climb

Anomalies: airspace-violation-all-types

Synopsis

ZJX CTLR DESCRIBED BUSY TFC PERIOD WHEN TMU RELEASED TFC WITHOUT SECTOR COORD RESULTING IN IFR ACFT ENTERING RESTRICTED AREA.

Narrative

WHILE WORKING R58 TODAY; I WITNESSED THE DEVELOPMENT OF A VERY UNSAFE SITUATION; WHICH CULMINATED IN A GA ACFT ENTERING ACTIVE NASA AIRSPACE. THIS SITUATION WAS CAUSED BY A COMBINATION OF SEVERAL CONTRIBUTING FACTORS. DURING THE ENTIRE SESSION; THE NASA AIRSPACE SE OF OMN WAS ACTIVE FROM SURFACE TO UNLIMITED. W158A AND W158C WERE ACTIVE TO FL450. A PIECE OF AIRSPACE KNOWN AS THE PINE LOW ALTRV WAS ACTIVE BLOCK ALT FL190-FL210 UNUSABLE IN A LARGE PORTION OF MY SECTOR. DUE TO THE COMPLEX NATURE OF THE SUA ACTIVE THAT DAY; JAX APCH WAS SUPPOSED TO CALL R58 FOR IFR RELEASE ON ALL ACFT THAT WOULD ENTER R58 AIRSPACE. NOT LONG AFTER ARRIVING AT R58; WHILE WORKING MODERATE TO HVY TFC WITH EXTREME COMPLEXITY; JAX APCH ATTEMPTED TO HAND OFF A JAX DEP TO ME FOR WHICH THEY HAD NOT CALLED FOR RELEASE. I ASKED MY SUPVR TO VERIFY THAT JAX APCH WAS AWARE OF THE RESTR; TO WHICH HE REPLIED 'THEY CALLED YOU AND YOU DID NOT ANSWER THE PHONE; SO THEY CALLED TMU WHO RELEASED THE ACFT.' THIS IS A VERY BAD DECISION. I DIDN'T ANSWER THE PHONE CALL BECAUSE I WAS TOO BUSY; THEN TMU MAKES A DECISION TO LAUNCH ANOTHER ACFT INTO MY SECTOR; GREATLY INCREASING MY WORKLOAD. IF I HAD TIME FOR ANOTHER ACFT; I WOULD HAVE ANSWERED THE LINE AND RELEASED THE DEP. IT IS A DECISION THAT SHOULD ONLY BE MADE BY R58. A FEW MOMENTS LATER; WHILE VECTORING AN MCO ARR TO ACHIEVE SPACING THAT WAS NOT PROVIDED TO MY SECTOR AS WAS REQUIRED; MY WORKLOAD INCREASED YET AGAIN. SIMULTANEOUSLY; JAX APCH FLASHED ME THE HDOF ON A JET DEP OFF OF JAX AND A PROP DEP OFF OF SGJ. AGAIN; I HAD NOT RELEASED THESE ACFT INTO MY SECTOR. MY D-SIDE SPOKE WITH JAX APCH WHO CLAIMED TO KNOW NOTHING ABOUT A 'CALL FOR RELEASE.' I WAS NOW EXTREMELY BUSY WITH AN EXTREMELY COMPLEX SITUATION DEVELOPING. I WAS STRUGGLING TO GET MY MCO ARRS; THAT CAME TO ME STACKED AND HIGH; SPACED AND UNDERNEATH THE ACTIVE ALTRV. I WAS FORCED TO PUT SEVERAL FL220 OVERFLTS ALONG MY WESTERN BOUNDARY TO ENABLE THE MCO ARRS TO DSND. AS SUCH; I HAD NO PLACE TO PUT THE DEPS THAT JAX HAD RELEASED WITHOUT MY APPROVAL. I CLBED THE JAX DEP TO 16000 FT; WHICH WAS MY ONLY REMAINING ALT; AS I HAD MCO ARRS DSNDING TO FL180 AND CONVERGING. I COULDN'T GET THE JAX DEP ABOVE THE ALTRV DUE TO THE OVERFLT TFC AT FL220 OVERHEAD. I WAS FORCED TO USE VISUAL SEPARATION OVER OMN TO ALLOW THE JAX DEP AT 16000 FT AND AN MCO ARR AT FL180 SWAP OUT. THIS IS TIME CONSUMING; COMPLEX; AND USING A LOT OF RADIO TFC. THE PROP DEP FROM SGJ I WAS FORCED TO STOP AT 14000 FT AND RTE ON A 270 DEG HDG OUT OF MY SECTOR; I HAD NO ROOM FOR HIM. JUST WHEN I THOUGHT THE SECTOR HAD CALMED DOWN; I REALIZED I HAD THE BIGGEST PROB YET. THE JAX JET DEP HAD FINALLY CLRED TFC AND THE ALTRV AND WAS ABLE TO CLB. I ISSUED FL340. I THEN ISSUED A REROUTE TO A BE20; THAT SHOULD HAVE BEEN ISSUED BY PREVIOUS SECTOR. AS THAT PLT WAS READING BACK THE CLRNC; I NOTICED THE GA JAX JET DEP HEADING DIRECTLY TOWARD ACTIVE NASA AREA. I COULDN'T TURN HIM; AS THE BE20 WAS READING BACK CLRNC. AS SOON AS I COULD I TURNED THE JET AWAY FROM THE NASA BUT IT WAS TOO LATE; HE ENTERED ITS NW CORNER. THE FLT PLAN SHOWED THE ACFT ROUTED OMN.J45.VRB..MYNN; WHICH IS CLR OF NASA. THE PLT STATED JAX APCH CLRED HIM OMN..MYNN. THAT AMENDMENT WAS NEVER ENTERED INTO THE COMPUTER BY JAX. THIS WHOLE SESSION WAS A DISASTER. LUCKILY NO ONE GOT HURT.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.