ZID controller becomes distraction and descends a B735 into conflict with an en route B727.

Attributes
ACN	522466
Time
Date	200108
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : dqn.vortac
State Reference	OH
Altitude	msl single value : 26000
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zid.artcc
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other vortac
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zid.artcc
Operator	common carrier : air carrier
Make Model Name	B737-500
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 2.5
ASRS Report	522466
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation non adherence : published procedure
Independent Detector	atc equipment : conflict alert other controllera
Resolutory Action	none taken : insufficient time
Consequence	faa : investigated
Miss Distance	horizontal : 15000 vertical : 700
Supplementary
Problem Areas	Environmental Factor ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

Air carrier Y was level at FL260 from yyz via rod J29 pxv to mem. Air carrier X came to me at FL330 off of mem to dtw via dqn mizar 3 dtw. I initially descended air carrier X to FL290. Approximately 2 mins later, I descended air carrier X to FL240 to comply with LOA with ZOB. I initially missed the air carrier Y as traffic. 10 seconds later, I had an aircraft put on my frequency incorrectly. I spent 10-15 seconds to find the aircraft and the correct frequency. As I was issuing the correct frequency, I began my scan again. Right away I noticed the air carrier X was about to descend through FL270, which would cause a loss of separation with air carrier Y. A split second later, conflict alert and adep went off at the same time. I did not ask for evasive actions, because air carrier X was at least 2.5 mi past air carrier Y. I do feel if the aircraft was not placed on my frequency incorrectly, I would have scanned sooner, and caught the situation before it occurred.

Original NASA ASRS Text

Title: ZID CTLR BECOMES DISTR AND DSNDS A B735 INTO CONFLICT WITH AN ENRTE B727.

Narrative: ACR Y WAS LEVEL AT FL260 FROM YYZ VIA ROD J29 PXV TO MEM. ACR X CAME TO ME AT FL330 OFF OF MEM TO DTW VIA DQN MIZAR 3 DTW. I INITIALLY DSNDED ACR X TO FL290. APPROX 2 MINS LATER, I DSNDED ACR X TO FL240 TO COMPLY WITH LOA WITH ZOB. I INITIALLY MISSED THE ACR Y AS TFC. 10 SECONDS LATER, I HAD AN ACFT PUT ON MY FREQ INCORRECTLY. I SPENT 10-15 SECONDS TO FIND THE ACFT AND THE CORRECT FREQ. AS I WAS ISSUING THE CORRECT FREQ, I BEGAN MY SCAN AGAIN. RIGHT AWAY I NOTICED THE ACR X WAS ABOUT TO DSND THROUGH FL270, WHICH WOULD CAUSE A LOSS OF SEPARATION WITH ACR Y. A SPLIT SECOND LATER, CONFLICT ALERT AND ADEP WENT OFF AT THE SAME TIME. I DID NOT ASK FOR EVASIVE ACTIONS, BECAUSE ACR X WAS AT LEAST 2.5 MI PAST ACR Y. I DO FEEL IF THE ACFT WAS NOT PLACED ON MY FREQ INCORRECTLY, I WOULD HAVE SCANNED SOONER, AND CAUGHT THE SIT BEFORE IT OCCURRED.

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.