ZID radar controller experienced a loss of separation.

Attributes
ACN	580306
Time
Date	200304
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : vhp.vortac
State Reference	IN
Altitude	msl bound lower : 31000 msl bound upper : 33000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zid.artcc
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise : enroute altitude change
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zid.artcc
Operator	general aviation : corporate
Make Model Name	Citationjet, C525/C526
Operating Under FAR Part	Part 91
Flight Phase	cruise : enroute altitude change
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 13 controller time certified in position1 : 4
ASRS Report	580306
Person 2
Affiliation	government : faa
Function	controller : radar
Experience	controller military : 7.50 controller non radar : 0.25 controller supervisory : 3 controller time certified in position1 : 2 controller time certified in position2 : 1
ASRS Report	580307
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation
Independent Detector	atc equipment : conflict alert other controllera other controllerb other other : ctlr 3
Resolutory Action	controller : issued new clearance
Consequence	faa : investigated
Miss Distance	horizontal : 27000 vertical : 800
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Intra Facility Coordination Failure

Narrative:

Aircraft X was at FL330 landing 27 KTS, FL270 (georgetown, ky). Aircraft Y was swbound at FL310. My super high sector called and told me aircraft X was my control for lower with sector my d-side took a pointout on aircraft Y, then mistakenly dropped the data block a few mins later. When aircraft X called on frequency, I descended the aircraft to FL260. Conflict alert activated with aircraft Y. At first, I assumed the alert was erroneous, caused by a departing aircraft. When I realized this to be untrue, I turned aircraft X to a 270 degree heading, told him to expedite turn and descent. I called the traffic, then cleared aircraft X to proceed direct georgetown leaving FL290.

Original NASA ASRS Text

Title: ZID RADAR CTLR EXPERIENCED A LOSS OF SEPARATION.

Narrative: ACFT X WAS AT FL330 LNDG 27 KTS, FL270 (GEORGETOWN, KY). ACFT Y WAS SWBOUND AT FL310. MY SUPER HIGH SECTOR CALLED AND TOLD ME ACFT X WAS MY CTL FOR LOWER WITH SECTOR MY D-SIDE TOOK A POINTOUT ON ACFT Y, THEN MISTAKENLY DROPPED THE DATA BLOCK A FEW MINS LATER. WHEN ACFT X CALLED ON FREQ, I DSNDED THE ACFT TO FL260. CONFLICT ALERT ACTIVATED WITH ACFT Y. AT FIRST, I ASSUMED THE ALERT WAS ERRONEOUS, CAUSED BY A DEPARTING ACFT. WHEN I REALIZED THIS TO BE UNTRUE, I TURNED ACFT X TO A 270 DEG HDG, TOLD HIM TO EXPEDITE TURN AND DSCNT. I CALLED THE TFC, THEN CLRED ACFT X TO PROCEED DIRECT GEORGETOWN LEAVING FL290.

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