Narrative:

Working bdl TRACON arrival position. Accepted handoff of air carrier X via dpk 1 arrival route at 110'. The aircraft had already crossed my lateral boundary and on initial contact advised he was deviating around WX. I did not observe any WX on my radar slope. He already was about to cross a boston center sector boundary so I initiated a descent to 100'. I attempted a pointout to the east departure controller, but as I leaned over to do so I heard him switch an air carrier Y to boston center climbing to 100'. I saw the air carrier X still level at 110' and noticed the mode C on the air carrier Y indicating 102' climbing to 103'. I advised the air carrier X to expedite descent to 90. An additional problem was east departure had traffic swbnd on V1 to mad slowly descending to 80'. Stopping the air carrier X at 90' was going to ensure separation with this traffic. I then advised boston center that the air carrier X was deviating around WX and I was expediting descent. The air carrier X had been advised of the converging air carrier and potential conflict, yet he still leveled at 100' to meet the far. I then advised the air carrier X to turn left 330 degree and descend immediately to 50'. I fully realized this was taking him toward the area he was attempting to go around, but figured this was preferable to possible midair. I still believe the pilot misunderstood the gravity of the situation. Either the pilot did not advise boston center he was deviating or the center did not advise me, but as soon as he flew through the mad 360 right on the arrival route, the potential for problems began. This was further compounded by the boston center not transferring communications in a timely manner. The close proximity of the dpk 1 arrival route to the boston center bosox/dxr boundary has been a problem before. There is no room for an aircraft to miss and go through the radial. Callback conversation with reporter revealed the following: the reporter stated there was no loss of separation between air carrier X and Y. He had forced air carrier X to leave 10,000' and descend to maintain separation from air carrier Y. Air carrier X had stopped descent at 10,000' to slow to 250 KTS. The reporter issued vector heading 330 to insure lateral separation from air carrier Y and keep air carrier X in the arrival position airspace. Air carrier X slopped into departure position airspace without coordination.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR X DELAYED TURN CAUSING ACFT TO ENTER AND EXIT DEP POSITION AIRSPACE WITHOUT COORD. PLT DEVIATION CAUSING OPERATIONAL ERROR.

Narrative: WORKING BDL TRACON ARR POSITION. ACCEPTED HANDOFF OF ACR X VIA DPK 1 ARR ROUTE AT 110'. THE ACFT HAD ALREADY CROSSED MY LATERAL BOUNDARY AND ON INITIAL CONTACT ADVISED HE WAS DEVIATING AROUND WX. I DID NOT OBSERVE ANY WX ON MY RADAR SLOPE. HE ALREADY WAS ABOUT TO CROSS A BOSTON CENTER SECTOR BOUNDARY SO I INITIATED A DSCNT TO 100'. I ATTEMPTED A POINTOUT TO THE EAST DEP CTLR, BUT AS I LEANED OVER TO DO SO I HEARD HIM SWITCH AN ACR Y TO BOSTON CENTER CLIMBING TO 100'. I SAW THE ACR X STILL LEVEL AT 110' AND NOTICED THE MODE C ON THE ACR Y INDICATING 102' CLIMBING TO 103'. I ADVISED THE ACR X TO EXPEDITE DSCNT TO 90. AN ADDITIONAL PROBLEM WAS EAST DEP HAD TFC SWBND ON V1 TO MAD SLOWLY DSNDING TO 80'. STOPPING THE ACR X AT 90' WAS GOING TO ENSURE SEPARATION WITH THIS TFC. I THEN ADVISED BOSTON CENTER THAT THE ACR X WAS DEVIATING AROUND WX AND I WAS EXPEDITING DSCNT. THE ACR X HAD BEEN ADVISED OF THE CONVERGING ACR AND POTENTIAL CONFLICT, YET HE STILL LEVELED AT 100' TO MEET THE FAR. I THEN ADVISED THE ACR X TO TURN LEFT 330 DEG AND DSND IMMEDIATELY TO 50'. I FULLY REALIZED THIS WAS TAKING HIM TOWARD THE AREA HE WAS ATTEMPTING TO GO AROUND, BUT FIGURED THIS WAS PREFERABLE TO POSSIBLE MIDAIR. I STILL BELIEVE THE PLT MISUNDERSTOOD THE GRAVITY OF THE SITUATION. EITHER THE PLT DID NOT ADVISE BOSTON CENTER HE WAS DEVIATING OR THE CENTER DID NOT ADVISE ME, BUT AS SOON AS HE FLEW THROUGH THE MAD 360 R ON THE ARR ROUTE, THE POTENTIAL FOR PROBLEMS BEGAN. THIS WAS FURTHER COMPOUNDED BY THE BOSTON CENTER NOT TRANSFERRING COMS IN A TIMELY MANNER. THE CLOSE PROX OF THE DPK 1 ARR ROUTE TO THE BOSTON CENTER BOSOX/DXR BOUNDARY HAS BEEN A PROBLEM BEFORE. THERE IS NO ROOM FOR AN ACFT TO MISS AND GO THROUGH THE RADIAL. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING: THE REPORTER STATED THERE WAS NO LOSS OF SEPARATION BETWEEN ACR X AND Y. HE HAD FORCED ACR X TO LEAVE 10,000' AND DSND TO MAINTAIN SEPARATION FROM ACR Y. ACR X HAD STOPPED DSCNT AT 10,000' TO SLOW TO 250 KTS. THE REPORTER ISSUED VECTOR HDG 330 TO INSURE LATERAL SEPARATION FROM ACR Y AND KEEP ACR X IN THE ARR POSITION AIRSPACE. ACR X SLOPPED INTO DEP POSITION AIRSPACE WITHOUT COORD.

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