Narrative:

Air carrier X departed bos runway 4L. First officer was the PF and I was the npf. We were successively given climbs of 4000 ft, 5000 ft on bos departure frequency 133.0. We then were switched to frequency 118.25 and were given climbs of 7000 ft and 14000 ft (our filed cruise altitude was 15000 ft). From about 5000 ft, we were in moderate turbulence, so we were climbing at 160 KIAS and getting about 2000+ FPM. Climbing through about 9500 ft, the following occurred: approach controller (normal voice): 'air carrier X, descend and maintain 8000 ft.' I thought I might have heard the controller incorrectly, since the call did not seem to make sense and it was said in a normal tone of voice. No mention of 'traffic' or 'traffic alert' on the controller's part. Captain said: 'was that for air carrier X?' approach controller (panicked urgent voice): 'air carrier X, descend to 8000 ft ! Descend now! Descend now!' I immediately grabbed the yoke, pitched down 20 degrees, pulled the power to idle and said 'my controls,' taking the aircraft from first officer (he had started the descent maneuver, but not as radically as I thought was appropriate). Though the controller had not once said the word 'traffic,' I glanced at the TCASII immediately after I had established the dive and there was a target overlapping with our aircraft at the same altitude (00 indicated as altitude difference). We were in a 4000+ FPM descent and I was praying we wouldn't collide with the other aircraft, who I determined about 10 seconds later (when the TCASII was showing about 1000 ft of vertical separation) was level at 10000 ft on an IFR flight plan. We were IMC in heavy rain and moderate turbulence, and we never saw the other aircraft. I would estimate there was no vertical separation and horizontal separation of less than 1/4 mi. Air carrier X does not have TCASII, and the tcasi never said 'traffic, traffic' or anything else. The unit tested ok during first flight checks and subsequent tests after the event. During the time that we initiated our descent until we were level at 8000 ft, the frequency was absolutely silent. The next radio call was from a different approach controller who had immediately stepped in to relieve the controller who had given us the climb to 7000 ft and 14000 ft and ordered us to descend. The new controller subsequently climbed us to 14000 ft and handed us off to ZBW on frequency 128.2. We were not with center for 5 mins when the following conversation occurred: boston center: 'air carrier Y, boston TRACON would like to talk to you when you get on the ground.' me: 'I would be interested in talking to them, too, do you have a phone number?' this near collision could have been avoided by requiring all part 121 carriers to have TCASII. In all likelihood, I would have gotten a 'monitor vertical speed' or a 'descend, descend' command shortly after passing 8000 ft. Because the aircraft only had tcasi, there was no command given. Additionally, the installed TCAS unit failed to even call 'traffic, 'traffic' even thought it passed the self-test before and after the incident. Precisely why it failed to issue an alert is not known.

Google
 

Original NASA ASRS Text

Title: B190 FLT CREW WITH A90 EXPERIENCED CONFLICT AT 10000 FT DUE TO OPERROR.

Narrative: ACR X DEPARTED BOS RWY 4L. FO WAS THE PF AND I WAS THE NPF. WE WERE SUCCESSIVELY GIVEN CLBS OF 4000 FT, 5000 FT ON BOS DEP FREQ 133.0. WE THEN WERE SWITCHED TO FREQ 118.25 AND WERE GIVEN CLBS OF 7000 FT AND 14000 FT (OUR FILED CRUISE ALT WAS 15000 FT). FROM ABOUT 5000 FT, WE WERE IN MODERATE TURB, SO WE WERE CLBING AT 160 KIAS AND GETTING ABOUT 2000+ FPM. CLBING THROUGH ABOUT 9500 FT, THE FOLLOWING OCCURRED: APCH CTLR (NORMAL VOICE): 'ACR X, DSND AND MAINTAIN 8000 FT.' I THOUGHT I MIGHT HAVE HEARD THE CTLR INCORRECTLY, SINCE THE CALL DID NOT SEEM TO MAKE SENSE AND IT WAS SAID IN A NORMAL TONE OF VOICE. NO MENTION OF 'TFC' OR 'TFC ALERT' ON THE CTLR'S PART. CAPT SAID: 'WAS THAT FOR ACR X?' APCH CTLR (PANICKED URGENT VOICE): 'ACR X, DSND TO 8000 FT ! DSND NOW! DSND NOW!' I IMMEDIATELY GRABBED THE YOKE, PITCHED DOWN 20 DEGS, PULLED THE PWR TO IDLE AND SAID 'MY CTLS,' TAKING THE ACFT FROM FO (HE HAD STARTED THE DSCNT MANEUVER, BUT NOT AS RADICALLY AS I THOUGHT WAS APPROPRIATE). THOUGH THE CTLR HAD NOT ONCE SAID THE WORD 'TFC,' I GLANCED AT THE TCASII IMMEDIATELY AFTER I HAD ESTABLISHED THE DIVE AND THERE WAS A TARGET OVERLAPPING WITH OUR ACFT AT THE SAME ALT (00 INDICATED AS ALT DIFFERENCE). WE WERE IN A 4000+ FPM DSCNT AND I WAS PRAYING WE WOULDN'T COLLIDE WITH THE OTHER ACFT, WHO I DETERMINED ABOUT 10 SECONDS LATER (WHEN THE TCASII WAS SHOWING ABOUT 1000 FT OF VERT SEPARATION) WAS LEVEL AT 10000 FT ON AN IFR FLT PLAN. WE WERE IMC IN HVY RAIN AND MODERATE TURB, AND WE NEVER SAW THE OTHER ACFT. I WOULD ESTIMATE THERE WAS NO VERT SEPARATION AND HORIZ SEPARATION OF LESS THAN 1/4 MI. ACR X DOES NOT HAVE TCASII, AND THE TCASI NEVER SAID 'TFC, TFC' OR ANYTHING ELSE. THE UNIT TESTED OK DURING FIRST FLT CHKS AND SUBSEQUENT TESTS AFTER THE EVENT. DURING THE TIME THAT WE INITIATED OUR DSCNT UNTIL WE WERE LEVEL AT 8000 FT, THE FREQ WAS ABSOLUTELY SILENT. THE NEXT RADIO CALL WAS FROM A DIFFERENT APCH CTLR WHO HAD IMMEDIATELY STEPPED IN TO RELIEVE THE CTLR WHO HAD GIVEN US THE CLB TO 7000 FT AND 14000 FT AND ORDERED US TO DSND. THE NEW CTLR SUBSEQUENTLY CLBED US TO 14000 FT AND HANDED US OFF TO ZBW ON FREQ 128.2. WE WERE NOT WITH CTR FOR 5 MINS WHEN THE FOLLOWING CONVERSATION OCCURRED: BOSTON CTR: 'ACR Y, BOSTON TRACON WOULD LIKE TO TALK TO YOU WHEN YOU GET ON THE GND.' ME: 'I WOULD BE INTERESTED IN TALKING TO THEM, TOO, DO YOU HAVE A PHONE NUMBER?' THIS NEAR COLLISION COULD HAVE BEEN AVOIDED BY REQUIRING ALL PART 121 CARRIERS TO HAVE TCASII. IN ALL LIKELIHOOD, I WOULD HAVE GOTTEN A 'MONITOR VERT SPD' OR A 'DSND, DSND' COMMAND SHORTLY AFTER PASSING 8000 FT. BECAUSE THE ACFT ONLY HAD TCASI, THERE WAS NO COMMAND GIVEN. ADDITIONALLY, THE INSTALLED TCAS UNIT FAILED TO EVEN CALL 'TFC, 'TFC' EVEN THOUGHT IT PASSED THE SELF-TEST BEFORE AND AFTER THE INCIDENT. PRECISELY WHY IT FAILED TO ISSUE AN ALERT IS NOT KNOWN.

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.