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

Date: 2010-03 · Aircraft: Military Trainer · Phase: initial_climb

Anomalies: conflict-airborne-conflict|deviation-altitude-excursion-from-assigned-altitude|deviation-discrepancy-procedural-published-material-policy

Synopsis

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.

Second reporter narrative

Aircraft X called on 'leveling at 100'; datablock showed climbing to 170 out of sector 21/7. I stated 'verify climbing to 170' Aircraft X replied; 'Roger; leaving 100 for 170'. I climbed him to 230. Sector 21 called and asked if I climbed Aircraft X; I said affirmative. An Air Carrier was direct ACOVE descending to 160; 21 had the Air Carrier on frequency and control. Sector 21 called back and said they never spoke to Aircraft X and did not climb him to 170. I then expedited the climb thru 160; Aircraft X replied leaving 160. Recommendation; Sector 21 should not put 170 in the data block and flash him to me without even talking to the aircraft.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.