ZID center controller reported they approved a point out for an aircraft deviating for weather then ...

Attributes
ACN	1683252
Time
Date	201909
Local Time Of Day	1801-2400
Place
Locale Reference	ZID.ARTCC
State Reference	IN
Aircraft 1
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	Direct
Flight Plan	IFR
Aircraft 2
Make Model Name	Medium Transport
Operating Under FAR Part	Part 91
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Component
Aircraft Component	Pressurization System
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 2.0
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Critical Conflict Airborne Conflict Deviation - Procedural Clearance Inflight Event / Encounter Weather / Turbulence

Narrative:

Aircraft X lost pressurization and diverted to ZZZ while the aircraft was northwest of the oom VOR. Approach contacted me and coordinated on a couple of occasions to arrange the aircrafts decent to ZZZ. Aircraft Y was pointed out to me by approach descending to 080 southwest bound and deviating around weather. The aircraft were on course to merge but were separated by 1000 feet. I called traffic to aircraft X for aircraft Y 1000 feet above. As I watched aircraft Y deviate further into my airspace I contacted approach and asked if they wanted to put the aircraft on my frequency; so I could descend and turn the aircraft for [their destination]. They told me the aircraft was already talking to [another] approach. After their courses were diverging aircraft Y began to deviate farther south. Then the aircraft began a descent. Shortly after this the controller at [the next approach facility] called and apologized saying he didn't realize the aircraft was going to deviate so far and told me aircraft Y was on a 220 heading. I then called the traffic again to aircraft X; however I failed to announce traffic alert. The aircraft came to within 4.45 mi of each other.I should have made my traffic call a traffic alert.

Original NASA ASRS Text

Title: ZID Center Controller reported they approved a point out for an aircraft deviating for weather then allowed another aircraft they were working to fly into confliction with the pointed out aircraft.

Narrative: Aircraft X lost pressurization and diverted to ZZZ while the aircraft was NW of the OOM VOR. Approach contacted me and coordinated on a couple of occasions to arrange the aircrafts decent to ZZZ. Aircraft Y was pointed out to me by Approach descending to 080 SW bound and deviating around weather. The aircraft were on course to merge but were separated by 1000 feet. I called traffic to Aircraft X for Aircraft Y 1000 feet above. As I watched Aircraft Y deviate further into my airspace I contacted Approach and asked if they wanted to put the aircraft on my frequency; so I could descend and turn the aircraft for [their destination]. They told me the aircraft was already talking to [another] Approach. After their courses were diverging Aircraft Y began to deviate farther south. Then the aircraft began a descent. Shortly after this the controller at [the next Approach facility] called and apologized saying he didn't realize the aircraft was going to deviate so far and told me Aircraft Y was on a 220 heading. I then called the traffic again to Aircraft X; however I failed to announce Traffic Alert. The aircraft came to within 4.45 mi of each other.I should have made my traffic call a Traffic Alert.

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

ZID center controller reported they approved a point out for an aircraft deviating for weather then allowed another aircraft they were working to fly into confliction with the pointed out aircraft.