Narrative:

During radar vectors from bwi approach at 4000 ft to the airport, we were given a heading of 240 degrees. Approximately 2 mins after flying this heading we saw lights from another aircraft. During the time we were discussing the aircraft and its relative position and movement to our aircraft, the TCASII issued a TA. The TCASII indicated the aircraft was 200 ft below our current altitude of 4000 ft as the TCASII was issuing this advisory. Bwi approach control began to issue a traffic call. This caused a bit of confusion between us (the crew members) because of our own discussion, the TCASII and ATC. At this time, bwi issued an advisory to turn right to avoid the traffic at nearly the same time TCASII issued a RA to descend. This advisory caused even more confusion because we could see the aircraft altitude indicated 200 ft below our own altitude. Almost instantly the TCASII then issued a climbing RA. We started a climb and reached an altitude of 4250 ft as the traffic passed slightly left and below our aircraft. Overall, the TCASII did an excellent job of raising awareness of the traffic and suggesting the best evasive action. My biggest concern is the tremendous amount of information that occurred in the less than 1 min the sequence took place. Between our own discussion, ATC issuing TA's and the TCASII, it could easily have caused a delay in reaction time. This being because of the time necessary to process all of the incoming information. This delay could have been critical if the closure rates would have been higher.

Google
 

Original NASA ASRS Text

Title: THE RPTR EXPERIENCED VISUALLY SEEING THE LIGHTS OF AN ACFT, THEN RECEIVED A TCASII TA, THEN A CTLR INSTRUCTION TO TURN, AND THEN A TCASII RA TO FIRST DSND AND WHILE THE RPTR WAS PONDERING THE TCASII RA COMMANDED A CLB FROM 4000 FT TO 4250 FT AS THE TFC PASSED UNDERNEATH.

Narrative: DURING RADAR VECTORS FROM BWI APCH AT 4000 FT TO THE ARPT, WE WERE GIVEN A HEADING OF 240 DEGS. APPROX 2 MINS AFTER FLYING THIS HEADING WE SAW LIGHTS FROM ANOTHER ACFT. DURING THE TIME WE WERE DISCUSSING THE ACFT AND ITS RELATIVE POS AND MOVEMENT TO OUR ACFT, THE TCASII ISSUED A TA. THE TCASII INDICATED THE ACFT WAS 200 FT BELOW OUR CURRENT ALT OF 4000 FT AS THE TCASII WAS ISSUING THIS ADVISORY. BWI APCH CTL BEGAN TO ISSUE A TFC CALL. THIS CAUSED A BIT OF CONFUSION BTWN US (THE CREW MEMBERS) BECAUSE OF OUR OWN DISCUSSION, THE TCASII AND ATC. AT THIS TIME, BWI ISSUED AN ADVISORY TO TURN R TO AVOID THE TFC AT NEARLY THE SAME TIME TCASII ISSUED A RA TO DSND. THIS ADVISORY CAUSED EVEN MORE CONFUSION BECAUSE WE COULD SEE THE ACFT ALT INDICATED 200 FT BELOW OUR OWN ALT. ALMOST INSTANTLY THE TCASII THEN ISSUED A CLBING RA. WE STARTED A CLB AND REACHED AN ALT OF 4250 FT AS THE TFC PASSED SLIGHTLY L AND BELOW OUR ACFT. OVERALL, THE TCASII DID AN EXCELLENT JOB OF RAISING AWARENESS OF THE TFC AND SUGGESTING THE BEST EVASIVE ACTION. MY BIGGEST CONCERN IS THE TREMENDOUS AMOUNT OF INFO THAT OCCURRED IN THE LESS THAN 1 MIN THE SEQUENCE TOOK PLACE. BTWN OUR OWN DISCUSSION, ATC ISSUING TA'S AND THE TCASII, IT COULD EASILY HAVE CAUSED A DELAY IN REACTION TIME. THIS BEING BECAUSE OF THE TIME NECESSARY TO PROCESS ALL OF THE INCOMING INFO. THIS DELAY COULD HAVE BEEN CRITICAL IF THE CLOSURE RATES WOULD HAVE BEEN HIGHER.

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.