Narrative:

We changed over to departure control soon after takeoff. We were cleared direct to ebber, climb to FL320 (cruise altitude I believe). We soon heard departure control talking to another aircraft that was inbound to ogg (at this point I do not believe we had changed over to center). My aircraft is equipped with TCASII, soon I saw a blip at 12 O'clock on my 10 mi radar scope, closing and descending. We were in the clouds. At about 7 mi, we were given a right 20 degree turn which we immediately took. Traffic was now displaced to 11 O'clock position; still closing and descending. Shortly thereafter, we were given a traffic alert, 'traffic, traffic.' we did not get a resolution advisory. Traffic passed us at 9 O'clock, 2 mi (my scope has a range ring at 2 mi on the 5 mi scope). At no time were we given any traffic information by the controller. This is just too close for 'two widebody aircraft' to get to each other on reciprocal headings; and under radar control and are being provided radar sep. The controller should have gotten a traffic conflict on his scope which he supposedly has to respond to in writing. We had an FAA controller on the jumpseat on this flight. He had wanted to see the TCASII system in operation, but he commented that he certainly did not want to see the system demonstrated in such a vivid and realist manner. This flight's conflict proved to me that the system and its controller do screw up. We can now watch them do it.

Google
 

Original NASA ASRS Text

Title: ACR CAPT SAYS HE HAD LESS THAN STANDARD SEPARATION WITH ANOTHER ACFT ACCORDING TO HIS TCASII EQUIPMENT.

Narrative: WE CHANGED OVER TO DEP CTL SOON AFTER TKOF. WE WERE CLRED DIRECT TO EBBER, CLB TO FL320 (CRUISE ALT I BELIEVE). WE SOON HEARD DEP CTL TALKING TO ANOTHER ACFT THAT WAS INBND TO OGG (AT THIS POINT I DO NOT BELIEVE WE HAD CHANGED OVER TO CTR). MY ACFT IS EQUIPPED WITH TCASII, SOON I SAW A BLIP AT 12 O'CLOCK ON MY 10 MI RADAR SCOPE, CLOSING AND DSNDING. WE WERE IN THE CLOUDS. AT ABOUT 7 MI, WE WERE GIVEN A R 20 DEG TURN WHICH WE IMMEDIATELY TOOK. TFC WAS NOW DISPLACED TO 11 O'CLOCK POS; STILL CLOSING AND DSNDING. SHORTLY THEREAFTER, WE WERE GIVEN A TFC ALERT, 'TFC, TFC.' WE DID NOT GET A RESOLUTION ADVISORY. TFC PASSED US AT 9 O'CLOCK, 2 MI (MY SCOPE HAS A RANGE RING AT 2 MI ON THE 5 MI SCOPE). AT NO TIME WERE WE GIVEN ANY TFC INFO BY THE CTLR. THIS IS JUST TOO CLOSE FOR 'TWO WIDEBODY ACFT' TO GET TO EACH OTHER ON RECIPROCAL HDGS; AND UNDER RADAR CTL AND ARE BEING PROVIDED RADAR SEP. THE CTLR SHOULD HAVE GOTTEN A TFC CONFLICT ON HIS SCOPE WHICH HE SUPPOSEDLY HAS TO RESPOND TO IN WRITING. WE HAD AN FAA CTLR ON THE JUMPSEAT ON THIS FLT. HE HAD WANTED TO SEE THE TCASII SYS IN OPERATION, BUT HE COMMENTED THAT HE CERTAINLY DID NOT WANT TO SEE THE SYS DEMONSTRATED IN SUCH A VIVID AND REALIST MANNER. THIS FLT'S CONFLICT PROVED TO ME THAT THE SYSTEM AND ITS CTLR DO SCREW UP. WE CAN NOW WATCH THEM DO IT.

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.