ZOB controller experienced operational error at FL180 when coordination with adjacent controller was...

Attributes
ACN	671439
Time
Date	200509
Place
Locale Reference	navaid : vwv.vor
State Reference	OH
Altitude	msl single value : 18000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zob.artcc
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : initial
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zob.artcc
Operator	common carrier : air carrier
Make Model Name	Regional Jet CL65 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller time certified in position1 : 1 controller time certified in position2 : 6 flight time total : 10
ASRS Report	671439
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 18 flight time total : 50
ASRS Report	670951
Events
Anomaly	conflict : airborne critical non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	flight crew : took evasive action
Consequence	faa : investigated
Miss Distance	horizontal : 3000 vertical : 500
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Had an aircraft heading sbound on the boundary between myself and another controller at FL190. I was handed off a second aircraft heading west at 17000 ft. The coordination between myself and the other controller I believed was 'I stopped this aircraft 17000 ft so you can climb the other aircraft at FL190.' I thought for whatever reason I had control to climb the aircraft at 17000 ft. I then climbed the aircraft at FL190 to FL230. The second aircraft checked on at 17000 ft and I climbed him to FL190; not seeing the limited data block at FL180 in his face at 1 mi. Separation was lost; .3 mi; 400 ft. Supplemental information from acn 670951: air carrier X was stopped at 17000 ft. Air carrier Y was at FL180. Air carrier X was switched to next controller. That controller thought he had control to climb him; but I had not given him control. Air carrier X was issued FL190 and got together with air carrier Y. Both pilots took action to miss. Both controllers tried to issue climbs and dscnts to fix the problem.

Original NASA ASRS Text

Title: ZOB CTLR EXPERIENCED OPERROR AT FL180 WHEN COORD WITH ADJACENT CTLR WAS MISUNDERSTOOD.

Narrative: HAD AN ACFT HEADING SBOUND ON THE BOUNDARY BTWN MYSELF AND ANOTHER CTLR AT FL190. I WAS HANDED OFF A SECOND ACFT HEADING W AT 17000 FT. THE COORD BTWN MYSELF AND THE OTHER CTLR I BELIEVED WAS 'I STOPPED THIS ACFT 17000 FT SO YOU CAN CLB THE OTHER ACFT AT FL190.' I THOUGHT FOR WHATEVER REASON I HAD CTL TO CLB THE ACFT AT 17000 FT. I THEN CLBED THE ACFT AT FL190 TO FL230. THE SECOND ACFT CHKED ON AT 17000 FT AND I CLBED HIM TO FL190; NOT SEEING THE LIMITED DATA BLOCK AT FL180 IN HIS FACE AT 1 MI. SEPARATION WAS LOST; .3 MI; 400 FT. SUPPLEMENTAL INFO FROM ACN 670951: ACR X WAS STOPPED AT 17000 FT. ACR Y WAS AT FL180. ACR X WAS SWITCHED TO NEXT CTLR. THAT CTLR THOUGHT HE HAD CTL TO CLB HIM; BUT I HAD NOT GIVEN HIM CTL. ACR X WAS ISSUED FL190 AND GOT TOGETHER WITH ACR Y. BOTH PLTS TOOK ACTION TO MISS. BOTH CTLRS TRIED TO ISSUE CLBS AND DSCNTS TO FIX THE PROB.

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.

ZOB controller experienced operational error at FL180 when coordination with adjacent controller was misunderstood.