Narrative:

At rdu, we have a jet departure (the packk 5) which joins a radial west of rdu to lib VORTAC and points west. We also have a turboprop departure (the blue devil 3) kewpi transition, which goes to a point west of rdu, then cuts southwest to lib VORTAC. This is a complicated scenario to describe. There are 2 tracons and 2 ctrs involved, but the end result is rdu sending aircraft to lib at 12000 ft and we are usually talking to neither -- ZDC gets the jet, gso gets the turbo and then hands him off to ZTL. We need some help from somebody to relieve this problem. Traffic has grown at rdu and this situation occurs either 'sort of' close, or very close 4, 5, or 6 times a day. Callback conversation with reporter revealed the following information: reporter states that rdu has met with ZDC, ZTL, gso and fay in the attempt to resolve a procedural situation for rdu traffic rted via the blue devil and pack sids without resolution. The controllers are concerned that aircraft propellers and jets are rted over lib VORTAC, xferred to either gso, ZTL or ZDC at the same altitude, expecting aircraft will remain clear of the other's airspace, meeting the appropriate altitude restrs. The reporter states that he frequently must back coordination with an adjoining facility when aircraft fail to meet SID restrs. Neither ZDC nor ZTL will amend their LOA's in order that traffic going into their delegated airspace will be allowed to climb above rdu TRACON delegated airspace, thus all high performance turboprops and jets climb to the same altitude toward the same fix, assigned differing airspace frequencys. Automation fixes have been discussed, but without concurrence or resolution. The reporter believes this is an unsafe condition, although no recent operrors have occurred.

Related reports:

Google
 

Original NASA ASRS Text

Title: RDU CTLR CONCERNED WITH PACKK AND BLUE DEVIL SIDS AND WITH FACILITY HDOF PROC TO GSO, ZDC AND ZTL.

Narrative: AT RDU, WE HAVE A JET DEP (THE PACKK 5) WHICH JOINS A RADIAL W OF RDU TO LIB VORTAC AND POINTS W. WE ALSO HAVE A TURBOPROP DEP (THE BLUE DEVIL 3) KEWPI TRANSITION, WHICH GOES TO A POINT W OF RDU, THEN CUTS SW TO LIB VORTAC. THIS IS A COMPLICATED SCENARIO TO DESCRIBE. THERE ARE 2 TRACONS AND 2 CTRS INVOLVED, BUT THE END RESULT IS RDU SENDING ACFT TO LIB AT 12000 FT AND WE ARE USUALLY TALKING TO NEITHER -- ZDC GETS THE JET, GSO GETS THE TURBO AND THEN HANDS HIM OFF TO ZTL. WE NEED SOME HELP FROM SOMEBODY TO RELIEVE THIS PROB. TFC HAS GROWN AT RDU AND THIS SIT OCCURS EITHER 'SORT OF' CLOSE, OR VERY CLOSE 4, 5, OR 6 TIMES A DAY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THAT RDU HAS MET WITH ZDC, ZTL, GSO AND FAY IN THE ATTEMPT TO RESOLVE A PROCEDURAL SIT FOR RDU TFC RTED VIA THE BLUE DEVIL AND PACK SIDS WITHOUT RESOLUTION. THE CTLRS ARE CONCERNED THAT ACFT PROPS AND JETS ARE RTED OVER LIB VORTAC, XFERRED TO EITHER GSO, ZTL OR ZDC AT THE SAME ALT, EXPECTING ACFT WILL REMAIN CLR OF THE OTHER'S AIRSPACE, MEETING THE APPROPRIATE ALT RESTRS. THE RPTR STATES THAT HE FREQUENTLY MUST BACK COORD WITH AN ADJOINING FACILITY WHEN ACFT FAIL TO MEET SID RESTRS. NEITHER ZDC NOR ZTL WILL AMEND THEIR LOA'S IN ORDER THAT TFC GOING INTO THEIR DELEGATED AIRSPACE WILL BE ALLOWED TO CLB ABOVE RDU TRACON DELEGATED AIRSPACE, THUS ALL HIGH PERFORMANCE TURBOPROPS AND JETS CLB TO THE SAME ALT TOWARD THE SAME FIX, ASSIGNED DIFFERING AIRSPACE FREQS. AUTOMATION FIXES HAVE BEEN DISCUSSED, BUT WITHOUT CONCURRENCE OR RESOLUTION. THE RPTR BELIEVES THIS IS AN UNSAFE CONDITION, ALTHOUGH NO RECENT OPERRORS HAVE OCCURRED.

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.