Narrative:

We accepted a handoff on aircraft X believing he was climbing to FL340 with traffic above at FL350. At the time of aircraft X's check-on; I was figuring spacing that needed to be done; and became aware of a possible airspace violation involving ZID; the sector below; and aircraft X. Aircraft X had read back he was climbing to FL340 to ZID; then shortly after checked on with us climbing to FL350. We missed the readback because of the 2 distrs. I called traffic and used proper phraseology; stating that the traffic was '1000 ft above' his assigned altitude. The pilot never questioned his altitude assignment; stated that he had traffic in sight; and continued to climb to FL350. The conflict alert went off and my instructor issued evasive clrncs.

Google
 

Original NASA ASRS Text

Title: ZOB CTLR EXPERIENCED OPERROR AT APPROX FL340 WHEN FAILING TO HEAR WRONG ALT READBACK RESULTING IN TFC CLIMBING TO OCCUPIED ALT.

Narrative: WE ACCEPTED A HDOF ON ACFT X BELIEVING HE WAS CLBING TO FL340 WITH TFC ABOVE AT FL350. AT THE TIME OF ACFT X'S CHK-ON; I WAS FIGURING SPACING THAT NEEDED TO BE DONE; AND BECAME AWARE OF A POSSIBLE AIRSPACE VIOLATION INVOLVING ZID; THE SECTOR BELOW; AND ACFT X. ACFT X HAD READ BACK HE WAS CLBING TO FL340 TO ZID; THEN SHORTLY AFTER CHKED ON WITH US CLBING TO FL350. WE MISSED THE READBACK BECAUSE OF THE 2 DISTRS. I CALLED TFC AND USED PROPER PHRASEOLOGY; STATING THAT THE TFC WAS '1000 FT ABOVE' HIS ASSIGNED ALT. THE PLT NEVER QUESTIONED HIS ALT ASSIGNMENT; STATED THAT HE HAD TFC IN SIGHT; AND CONTINUED TO CLB TO FL350. THE CONFLICT ALERT WENT OFF AND MY INSTRUCTOR ISSUED EVASIVE CLRNCS.

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