Narrative:

Cga X was being worked by ZOB, heading 170 for spacing to washington nat'l, descending to FL310. No flight plan information was available on this aircraft, and it was a factor since the aircraft had to be sequenced. The controller working cga X was quite busy, with approximately 12 aircraft on frequency, 3 of which were unexpected. When cga X was 8 NM north of the cleveland/washington boundary, cleveland (note: all coordination was accomplished by the associate radar position, not the radar controller.) center initiated a 'pointout' to ZDC. Washington was unable to approve a pointout due to air carrier Y climbing nwbnd. Washington did not acknowledge the existence of cga X, cleveland did acknowledge air carrier Y and said 'we're turning left'. Washington took no action to turn air carrier Y, presumably because the aircraft was deviating for WX. Cleveland issued a turn to the left. The radar controller was confused as to what the air carrier Y was doing, since the associate controller at first said it was descending. Then the associate advised the air carrier Y was climbing. The radar controller then told the cga X to descend immediately to FL290. It seems there is a lot of controversy as to who is responsible. The radar controller at cleveland has been given full responsibility, even though the radar associate did all coordination. It appears that washington has been found completely free of any fault.

Google
 

Original NASA ASRS Text

Title: CGA CAME IN CLOSE PROX TO AN ACR BEING WORKED BY ADJACENT FAC. LESS THAN STANDARD SEPARATION RESULTED.

Narrative: CGA X WAS BEING WORKED BY ZOB, HDG 170 FOR SPACING TO WASHINGTON NAT'L, DESCENDING TO FL310. NO FLT PLAN INFO WAS AVAILABLE ON THIS ACFT, AND IT WAS A FACTOR SINCE THE ACFT HAD TO BE SEQUENCED. THE CTLR WORKING CGA X WAS QUITE BUSY, WITH APPROX 12 ACFT ON FREQ, 3 OF WHICH WERE UNEXPECTED. WHEN CGA X WAS 8 NM N OF THE CLEVELAND/WASHINGTON BOUNDARY, CLEVELAND (NOTE: ALL COORD WAS ACCOMPLISHED BY THE ASSOCIATE RADAR POSITION, NOT THE RADAR CTLR.) CENTER INITIATED A 'POINTOUT' TO ZDC. WASHINGTON WAS UNABLE TO APPROVE A POINTOUT DUE TO ACR Y CLIMBING NWBND. WASHINGTON DID NOT ACKNOWLEDGE THE EXISTENCE OF CGA X, CLEVELAND DID ACKNOWLEDGE ACR Y AND SAID 'WE'RE TURNING LEFT'. WASHINGTON TOOK NO ACTION TO TURN ACR Y, PRESUMABLY BECAUSE THE ACFT WAS DEVIATING FOR WX. CLEVELAND ISSUED A TURN TO THE LEFT. THE RADAR CTLR WAS CONFUSED AS TO WHAT THE ACR Y WAS DOING, SINCE THE ASSOCIATE CTLR AT FIRST SAID IT WAS DESCENDING. THEN THE ASSOCIATE ADVISED THE ACR Y WAS CLIMBING. THE RADAR CTLR THEN TOLD THE CGA X TO DSND IMMEDIATELY TO FL290. IT SEEMS THERE IS A LOT OF CONTROVERSY AS TO WHO IS RESPONSIBLE. THE RADAR CTLR AT CLEVELAND HAS BEEN GIVEN FULL RESPONSIBILITY, EVEN THOUGH THE RADAR ASSOCIATE DID ALL COORD. IT APPEARS THAT WASHINGTON HAS BEEN FOUND COMPLETELY FREE OF ANY FAULT.

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.