Narrative:

Deer valley requested release on IFR aircraft X off runway 25. I contacted luf north sector to request release as required by our LOA for dvt runway 25 IFR operations. During the coordination; I specified that aircraft X would be climbing to the flight levels towards bxk. Luf-north approved the release. I then released aircraft X with deer valley tower. When aircraft X became airborne and I radar identified them; I called luf-north for a point out to take aircraft X towards bxk climbing to FL210. Luf-north approved the point out. I coordinated a climb to 10;000 with the next departure sector and handed aircraft X off to navajo. A few moments later; luf-north called back with 'traffic'. The luf-north controller issued traffic 10 miles west of aircraft X indicating 2;400 MSL; a flight of 2 [military aircraft] climbing to conduct simulated flame-out operations over the luf TACAN. I responded with 'traffic observed' and; after quickly checking with the navajo controller; confirmed to the luf-north controller that aircraft X was climbing to FL210. Within seconds; the [military aircraft] climbed directly into the side of aircraft X at about the same indicated altitude. According to the navajo controller; aircraft X responded to an RA.recommend educating the luf RAPCON controllers about what taking a point out means and issuing restrictions if necessary. Also; the [military aircraft] operations could have taken place at a safer altitude; such as 9000 MSL; and not been in conflict with aircraft X. I informed luf of how we planned to work aircraft X at least twice and they did not communicate to me any concerns.

Related reports:

Google
 

Original NASA ASRS Text

Title: Phoenix TRACON Controller reported a departure that was coordinated; pointed out; and then had a conflict due to the other facility not knowing what to do.

Narrative: Deer Valley requested release on IFR Aircraft X off Runway 25. I contacted LUF North sector to request release as required by our LOA for DVT Runway 25 IFR operations. During the coordination; I specified that Aircraft X would be climbing to the flight levels towards BXK. LUF-N approved the release. I then released Aircraft X with Deer Valley Tower. When Aircraft X became airborne and I radar identified them; I called LUF-N for a point out to take Aircraft X towards BXK climbing to FL210. LUF-N approved the point out. I coordinated a climb to 10;000 with the next departure sector and handed Aircraft X off to Navajo. A few moments later; LUF-N called back with 'Traffic'. The LUF-N controller issued traffic 10 miles west of Aircraft X indicating 2;400 MSL; a flight of 2 [military aircraft] climbing to conduct simulated flame-out operations over the LUF TACAN. I responded with 'traffic observed' and; after quickly checking with the Navajo Controller; confirmed to the LUF-N controller that Aircraft X was climbing to FL210. Within seconds; the [Military aircraft] climbed directly into the side of Aircraft X at about the same indicated altitude. According to the Navajo controller; Aircraft X responded to an RA.Recommend educating the LUF RAPCON controllers about what taking a point out means and issuing restrictions if necessary. Also; the [military aircraft] operations could have taken place at a safer altitude; such as 9000 MSL; and not been in conflict with Aircraft X. I informed LUF of how we planned to work Aircraft X at least twice and they did not communicate to me any concerns.

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.