ZBW controller described a conflict event between climbing and descending traffic when data block in...

Narrative:

Aircraft X climbing leveled at 10000 ft (normal ops) and was not on my frequency. I called bdl approach control asking them to 'switch aircraft X' and they said they already had. I had put interim of 17000 in the data block before talking to aircraft X and flashed the data block to sector 22 ZBW albany sector. Aircraft X was NORDO then appeared on sector 22's frequency (I don't know how) and sector 22 climbed aircraft X in the face of an air carrier I was vectoring behind aircraft X for his climb. Control was not given to sector 22 for a climb and when I asked sector 22 they said aircraft X reported climbing to 17000; I did not give him that clearance. I should have not used an interim of 17000 before flashing aircraft X. This caused confusion; but I did this because the subject traffic climb very well and I was trying to keep them from leveling off. Also; someone climbed aircraft X in my airspace; either pilot deviation or controller error. The interim of 17000 before the aircraft is on frequency should have never caused this kind of confusion because it is normal practice.

Original NASA ASRS Text

Title: ZBW Controller described a conflict event between climbing and descending traffic when data block information was confused and climb clearance misunderstood.

Narrative: Aircraft X climbing leveled at 10000 FT (normal ops) and was not on my frequency. I called BDL Approach control asking them to 'switch Aircraft X' and they said they already had. I had put interim of 17000 in the data block before talking to Aircraft X and flashed the data block to Sector 22 ZBW Albany Sector. Aircraft X was NORDO then appeared on Sector 22's frequency (I don't know how) and Sector 22 climbed Aircraft X in the face of an Air Carrier I was vectoring behind Aircraft X for his climb. Control was not given to Sector 22 for a climb and when I asked Sector 22 they said Aircraft X reported climbing to 17000; I did not give him that clearance. I should have not used an interim of 17000 before flashing Aircraft X. This caused confusion; but I did this because the subject traffic climb very well and I was trying to keep them from leveling off. Also; someone climbed Aircraft X in my airspace; either pilot deviation or controller error. The interim of 17000 before the aircraft is on frequency should have never caused this kind of confusion because it is normal practice.

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

Attributes
ACN	878527
Time
Date	201003
Local Time Of Day	1201-1800
Place
Locale Reference	ZBW.ARTCC
State Reference	NH
Aircraft 1
Make Model Name	Military Trainer
Flight Phase	Initial Climb
Flight Plan	IFR
Person 1
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy

ZBW controller described a conflict event between climbing and descending traffic when data block information was confused and climb clearance misunderstood.