Narrative:

Radar controller at bsv sector received a point-out from adjacent hop sector on an aircraft level at 8000' requesting flight levels proceeding eastbound. The phraseology used by the hop associate radar controller was 'request control to climb eastbound with respect to all our traffic', which is the incorrect phraseology. The bsv radar controller approved the point-out. At the time, there was an aircraft over the bsv VOR level at 9000' proceeding nwbnd. The bsv controller thought the hop controller knew about the other traffic because he said 'with respect to all our traffic.' the bsv controller saw 9000' in the data block of the aircraft that was pointed out so the bsv controller, in less than a min from the time of the point out, called the hop controller to make sure he was watching 'all' the traffic, but he had already climbed the aircraft. The climbing aircraft was reclred to maintain 8000'. The resulting sep was 700' and 2 mi. To avoid any similar occurrence, use proper phraseology to convey one's intentions and to avoid confusion. Callback conversation with reporter revealed the following information. Reporter stated that he was charged with the system error for failing to issue traffic to the handoff controller. The 9000' traffic was on the handoff controller's scope but there was another data tog overlapping the target. He was not busy and he should have ensured that handoff controller displayed all of his active traffic. The automation equipment detected the error. The two aircraft were an small transport and an light transport.

Google
 

Original NASA ASRS Text

Title: INCOMPLETE COORD BETWEEN CTLRS RESULTED IN LESS THAN STANDARD SEPARATION BETWEEN TWO ACFT.

Narrative: RADAR CTLR AT BSV SECTOR RECEIVED A POINT-OUT FROM ADJACENT HOP SECTOR ON AN ACFT LEVEL AT 8000' REQUESTING FLT LEVELS PROCEEDING EBND. THE PHRASEOLOGY USED BY THE HOP ASSOCIATE RADAR CTLR WAS 'REQUEST CTL TO CLB EBND WITH RESPECT TO ALL OUR TFC', WHICH IS THE INCORRECT PHRASEOLOGY. THE BSV RADAR CTLR APPROVED THE POINT-OUT. AT THE TIME, THERE WAS AN ACFT OVER THE BSV VOR LEVEL AT 9000' PROCEEDING NWBND. THE BSV CTLR THOUGHT THE HOP CTLR KNEW ABOUT THE OTHER TFC BECAUSE HE SAID 'WITH RESPECT TO ALL OUR TFC.' THE BSV CTLR SAW 9000' IN THE DATA BLOCK OF THE ACFT THAT WAS POINTED OUT SO THE BSV CTLR, IN LESS THAN A MIN FROM THE TIME OF THE POINT OUT, CALLED THE HOP CTLR TO MAKE SURE HE WAS WATCHING 'ALL' THE TFC, BUT HE HAD ALREADY CLBED THE ACFT. THE CLBING ACFT WAS RECLRED TO MAINTAIN 8000'. THE RESULTING SEP WAS 700' AND 2 MI. TO AVOID ANY SIMILAR OCCURRENCE, USE PROPER PHRASEOLOGY TO CONVEY ONE'S INTENTIONS AND TO AVOID CONFUSION. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO. RPTR STATED THAT HE WAS CHARGED WITH THE SYS ERROR FOR FAILING TO ISSUE TFC TO THE HDOF CTLR. THE 9000' TFC WAS ON THE HDOF CTLR'S SCOPE BUT THERE WAS ANOTHER DATA TOG OVERLAPPING THE TARGET. HE WAS NOT BUSY AND HE SHOULD HAVE ENSURED THAT HDOF CTLR DISPLAYED ALL OF HIS ACTIVE TFC. THE AUTOMATION EQUIP DETECTED THE ERROR. THE TWO ACFT WERE AN SMT AND AN LTT.

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.