Narrative:

I was training a D side on 46. We were quite busy; with several conflicts that had either been rectified or were in the process. Aircraft Y was westbound on V94 at 120. V94 is the only airway we have going east and west that we can put IFR aircraft on due to high terrain northeast of tus. Aircraft X; was doing jump activities at E60. Military Y was westbound on V94 at 120. V94 is the only airway we have going east and west that we can put IFR aircraft on; due to high terrain northeast of tus. Aircraft X was doing jump activities at E60; which is about a half mile south of V94; close to totec intersection. We took a hand off on an air carrier climbing slowly out of 9;000 that we were worried about getting above military Y. The r-side told us to call and make sure we had positive separation; so I called the santan controller at phoenix to tell them to have the aircraft cross the boundary at or above 130. At the same time; a new r-side controller came in to get a relief briefing. I saw the aircraft X beacon code; no track started; about two miles away from military Y when the controller told one of the aircraft about the other; not sure which one. I believe the controller told them both about each other. We had a lot of data block clutter around the airport as well as several mode C intruder and VFR targets. Military Y advised that they were maneuvering to avoid the aircraft X; stating that they missed by 20 feet; had to use 90 degree bank to avoid; and descended out of 120 to 105. Aircraft X said a few minutes later that is was closer to 150 or 200 feet. At the time when the two aircraft got close; the code on aircraft X went from what appeared to be about 2 miles to merging with military Y.

Related reports:

Google
 

Original NASA ASRS Text

Title: Several ZAB controllers described a NMAC event when an IFR enroute aircraft was required to take evasive action to avoid a parachute jump aircraft; reporters indicating track starts on jump aircraft; drop zone relocation and VFR altitude restrictions could assist in preventing additional conflicts.

Narrative: I was training a D side on 46. We were quite busy; with several conflicts that had either been rectified or were in the process. Aircraft Y was westbound on V94 at 120. V94 is the only airway we have going East and West that we can put IFR aircraft on due to high terrain northeast of TUS. Aircraft X; was doing jump activities at E60. Military Y was westbound on V94 at 120. V94 is the only airway we have going East and West that we can put IFR aircraft on; due to high terrain northeast of TUS. Aircraft X was doing jump activities at E60; which is about a half mile south of V94; close to TOTEC intersection. We took a hand off on an Air Carrier climbing slowly out of 9;000 that we were worried about getting above Military Y. The R-side told us to call and make sure we had positive separation; so I called the Santan Controller at Phoenix to tell them to have the aircraft cross the boundary at or above 130. At the same time; a new R-side Controller came in to get a relief briefing. I saw the Aircraft X beacon code; no track started; about two miles away from Military Y when the Controller told one of the aircraft about the other; not sure which one. I believe the Controller told them both about each other. We had a lot of data block clutter around the airport as well as several Mode C intruder and VFR targets. Military Y advised that they were maneuvering to avoid the Aircraft X; stating that they missed by 20 feet; had to use 90 degree bank to avoid; and descended out of 120 to 105. Aircraft X said a few minutes later that is was closer to 150 or 200 feet. At the time when the two aircraft got close; the code on Aircraft X went from what appeared to be about 2 miles to merging with Military Y.

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.