Narrative:

I was working the radar associate position at the athens sector (38) at ZBW. Air carrier X checked on frequency at FL370. Air carrier X was issued FL290, the pilot readback was correct. While performing other duties, posting flight progress strips, I did not have a chance to correlate the aircraft data block until later, at which time I noticed FL310 in the data block. I asked the radar controller to verify he issued FL310. He acknowledged yes. The radar controller issued traffic to air carrier X of crossing traffic, air carrier Y, level at FL290. Air carrier X simply acknowledged 'roger.' we observed air carrier X passing through FL309 and the radar controller started issuing corrective action. 3 clrncs issued to air carrier X were either not acknowledged or covered by other xmissions.

Google
 

Original NASA ASRS Text

Title: ZBW RADAR ASSOCIATE AND RADAR CTLR ARE UNABLE TO CORRECT A CONFLICT BTWN A DSNDING B737 AND AN ENRTE LEVEL B767 DUE TO FREQ BLOCKED XMISSIONS AND AN INCORRECT ALT DATA BLOCK ENTRY.

Narrative: I WAS WORKING THE RADAR ASSOCIATE POS AT THE ATHENS SECTOR (38) AT ZBW. ACR X CHKED ON FREQ AT FL370. ACR X WAS ISSUED FL290, THE PLT READBACK WAS CORRECT. WHILE PERFORMING OTHER DUTIES, POSTING FLT PROGRESS STRIPS, I DID NOT HAVE A CHANCE TO CORRELATE THE ACFT DATA BLOCK UNTIL LATER, AT WHICH TIME I NOTICED FL310 IN THE DATA BLOCK. I ASKED THE RADAR CTLR TO VERIFY HE ISSUED FL310. HE ACKNOWLEDGED YES. THE RADAR CTLR ISSUED TFC TO ACR X OF XING TFC, ACR Y, LEVEL AT FL290. ACR X SIMPLY ACKNOWLEDGED 'ROGER.' WE OBSERVED ACR X PASSING THROUGH FL309 AND THE RADAR CTLR STARTED ISSUING CORRECTIVE ACTION. 3 CLRNCS ISSUED TO ACR X WERE EITHER NOT ACKNOWLEDGED OR COVERED BY OTHER XMISSIONS.

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.