Narrative:

South of choppy intersection; flying direct to lfv; climbing in IMC to 11000 ft; at approximately 9700 ft; we received a TCAS TA. I switched the TCAS display to 2 NM and located the traffic at 1-2 O'clock position; descending; less than 1 mi; with 700 ft separation. The PF disconnected the autoplt and initiated a turn to the left as the traffic passed aft of the right wing with 300 ft separation and less than 1/2 mi. We were climbing to 10000 ft with cape approach; and then handed off to ZBW (128.75) and instructed to climb to 11000 ft. I asked bos if he was working the traffic that just passed off our right wing and the controller said the aircraft was working cape approach. I told him of the loss of separation and that I would be filing a 'near miss' report. 10-15 mins later just prior to handoff; the same controller advised that they were looking into the situation and that I could call for information in about an hour. After returning to btv I contacted ZBW and was advised that the loss of separation was the fault of the cape approach/departure controller who 'lost track' of the situation. He was controling aircraft Y overflt from ack to lga. He prematurely climbed us to 10000 ft and made the handoff to bos without properly assessing the conflict possibility. He stated that the separation was reduced to 3/10 mi lateral and 500 ft vertical. I inquired as to why the bos controller didn't pick up on the situation; and why didn't the conflict alert system work. He explained that the radar return from the cape controled aircraft would not have had a 'data block' but only a primary target. Also there was a very heavy traffic situation in progress and the primary target may have been combined with other traffic above or below. As for the conflict alert system he said it is often unreliable for many reasons; one of which is missed mode-C (skipped) data.

Google
 

Original NASA ASRS Text

Title: BE9L HAS LOSS OF SEPARATION WITH SAAB 340 10000 FT OVER CHOPPY DUE TO CTLR ERROR.

Narrative: S OF CHOPPY INTXN; FLYING DIRECT TO LFV; CLBING IN IMC TO 11000 FT; AT APPROX 9700 FT; WE RECEIVED A TCAS TA. I SWITCHED THE TCAS DISPLAY TO 2 NM AND LOCATED THE TFC AT 1-2 O'CLOCK POS; DSNDING; LESS THAN 1 MI; WITH 700 FT SEPARATION. THE PF DISCONNECTED THE AUTOPLT AND INITIATED A TURN TO THE L AS THE TFC PASSED AFT OF THE R WING WITH 300 FT SEPARATION AND LESS THAN 1/2 MI. WE WERE CLBING TO 10000 FT WITH CAPE APCH; AND THEN HANDED OFF TO ZBW (128.75) AND INSTRUCTED TO CLB TO 11000 FT. I ASKED BOS IF HE WAS WORKING THE TFC THAT JUST PASSED OFF OUR R WING AND THE CTLR SAID THE ACFT WAS WORKING CAPE APCH. I TOLD HIM OF THE LOSS OF SEPARATION AND THAT I WOULD BE FILING A 'NEAR MISS' RPT. 10-15 MINS LATER JUST PRIOR TO HDOF; THE SAME CTLR ADVISED THAT THEY WERE LOOKING INTO THE SITUATION AND THAT I COULD CALL FOR INFO IN ABOUT AN HR. AFTER RETURNING TO BTV I CONTACTED ZBW AND WAS ADVISED THAT THE LOSS OF SEPARATION WAS THE FAULT OF THE CAPE APCH/DEP CTLR WHO 'LOST TRACK' OF THE SITUATION. HE WAS CTLING ACFT Y OVERFLT FROM ACK TO LGA. HE PREMATURELY CLBED US TO 10000 FT AND MADE THE HDOF TO BOS WITHOUT PROPERLY ASSESSING THE CONFLICT POSSIBILITY. HE STATED THAT THE SEPARATION WAS REDUCED TO 3/10 MI LATERAL AND 500 FT VERT. I INQUIRED AS TO WHY THE BOS CTLR DIDN'T PICK UP ON THE SITUATION; AND WHY DIDN'T THE CONFLICT ALERT SYS WORK. HE EXPLAINED THAT THE RADAR RETURN FROM THE CAPE CTLED ACFT WOULD NOT HAVE HAD A 'DATA BLOCK' BUT ONLY A PRIMARY TARGET. ALSO THERE WAS A VERY HVY TFC SITUATION IN PROGRESS AND THE PRIMARY TARGET MAY HAVE BEEN COMBINED WITH OTHER TFC ABOVE OR BELOW. AS FOR THE CONFLICT ALERT SYS HE SAID IT IS OFTEN UNRELIABLE FOR MANY REASONS; ONE OF WHICH IS MISSED MODE-C (SKIPPED) DATA.

Data retrieved from NASA's ASRS site as of January 2009 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.