ZID controller described a potential conflict when one aircraft experienced a 'stuck microphone ' an...

Narrative:

Aircraft X was an aircraft climbing on a vector. After acknowledging a clearance back to the fwa VORTAC; aircraft X unknowingly had their mic stick. At that same approximate time; a limited data block was identified approaching the boundary at nearly the same altitude that aircraft X was climbing through. I immediately called for the wolflake sector at chicago center. The controller there thought he had transferred radar control of aircraft Y but had not. I told him to turn aircraft Y; which was the limited data block; 25 degrees right because that aircraft was in conflict with aircraft X. The controller at chicago center said that he had given aircraft Y the frequency change to our sector. With the stuck mic; we were unable to talk to either aircraft. Fortunately aircraft Y out climbed aircraft X by a substantial margin and no separation was lost though the situation was uncontrolled. After a couple minutes; aircraft X checked back on the frequency and was notified of its stuck mic. Aircraft Y then was able to check on to the frequency as well. Aircraft Y was never issued the 25 degree right turn that I had requested to the chicago center controller. Recommendation; ensure that all aircraft are handed off and that separation is always controlled.

Original NASA ASRS Text

Title: ZID Controller described a potential conflict when one aircraft experienced a 'stuck microphone ' and was unable to communicate with conflicting traffic; which had entered the airspace without coordination and/or hand off.

Narrative: Aircraft X was an aircraft climbing on a vector. After acknowledging a clearance back to the FWA VORTAC; Aircraft X unknowingly had their mic stick. At that same approximate time; a limited data block was identified approaching the boundary at nearly the same altitude that Aircraft X was climbing through. I immediately called for the WolfLake Sector at Chicago Center. The controller there thought he had transferred RADAR control of Aircraft Y but had not. I told him to turn Aircraft Y; which was the limited data block; 25 degrees right because that aircraft was in conflict with Aircraft X. The controller at Chicago center said that he had given Aircraft Y the frequency change to our sector. With the stuck mic; we were unable to talk to either aircraft. Fortunately Aircraft Y out climbed Aircraft X by a substantial margin and no separation was lost though the situation was uncontrolled. After a couple minutes; Aircraft X checked back on the frequency and was notified of its stuck mic. Aircraft Y then was able to check on to the frequency as well. Aircraft Y was never issued the 25 degree right turn that I had requested to the Chicago Center controller. Recommendation; ensure that all aircraft are handed off and that separation is always controlled.

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

Attributes
ACN	941145
Time
Date	201104
Local Time Of Day	1201-1800
Place
Locale Reference	ZID.ARTCC
State Reference	IN
Aircraft 1
Make Model Name	EMB ERJ 145 ER&LR
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Component
Aircraft Component	Air/Ground Communication
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Critical Deviation - Procedural Published Material / Policy

ZID controller described a potential conflict when one aircraft experienced a 'stuck microphone ' and was unable to communicate with conflicting traffic; which had entered the airspace without coordination and/or hand off.