Enroute controller described a loss of separation event noting some of the coordination relative to ...

Attributes
ACN	999663
Time
Date	201203
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.ARTCC
State Reference	US
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	MD-90 Series (DC-9-90) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Narrative:

A CRJ2; filed bae.EAU8.msp; climbing to FL330 (my top altitude); requesting FL340. Traffic was two overflight aircraft; both at FL310 and both direct grr; the second of which was the MD90. I gave the CRJ2 15 degrees left; entered it into the 4th line of the data block; and handed him off to hor (horicon super hi). I coordinated hor's control leaving FL320 (although not on a recorded line; the sectors are adjacent) and transferred communications. Apparently after checking on with hor the aircraft requested FL320 as I saw this altitude entered hard in the data block. The next time I looked the aircraft were coming together as the CRJ2 appeared to be back on course. I quickly advised the hor controller and very shortly thereafter the conflict alert went off. I turned the MD90 left to a 060 heading and it appeared that the hor controller also went left with the CRJ2; but I believe it was too late to avoid a loss of separation. My only recommendation would be to effect coordination on a recorded line; perhaps this might have helped in this event.

Original NASA ASRS Text

Title: Enroute Controller described a loss of separation event noting some of the coordination relative to this incident was made without utilizing a recorded land line.

Narrative: A CRJ2; filed BAE.EAU8.MSP; climbing to FL330 (my top altitude); requesting FL340. Traffic was two overflight aircraft; both at FL310 and both direct GRR; the second of which was the MD90. I gave the CRJ2 15 degrees left; entered it into the 4th line of the Data Block; and handed him off to HOR (Horicon Super Hi). I coordinated HOR's control leaving FL320 (although not on a recorded line; the sectors are adjacent) and transferred communications. Apparently after checking on with HOR the aircraft requested FL320 as I saw this altitude entered hard in the Data Block. The next time I looked the aircraft were coming together as the CRJ2 appeared to be back on course. I quickly advised the HOR Controller and very shortly thereafter the Conflict Alert went off. I turned the MD90 left to a 060 heading and it appeared that the HOR Controller also went left with the CRJ2; but I believe it was too late to avoid a loss of separation. My only recommendation would be to effect coordination on a recorded line; perhaps this might have helped in this event.

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

Enroute controller described a loss of separation event noting some of the coordination relative to this incident was made without utilizing a recorded land line.