Narrative:

While working sector R43 on this date, I noticed bmb X limited data block exiting IR320 northbound. Also, I noticed a VFR/code 1200/target on a converging course of approximately 250 degree, at an unverified altitude of 8800. I attempted to contact bmb X on my primary UHF 298.9 located at winslow to issue traffic advisories/alert with no reply or observed evasive action. (Bmb X is not required to monitor 298.9). I then attempted several times to issue traffic on my 243.0 located at prescott with no reply or observed action. As the targets merged at 9000 and 8800 my next radar update indicated bmb X had climbed to 9800. Contributing factors are failure of the VFR aircraft to contact FSS for information on ir route activities/and see and avoid. Equipment (243.0) removed or not available to controllers. Suggestions would be to install UHF 243.0 at sites within a usable range of military training routes and airspace to be available to controllers. On this IR320/276 route, have aircraft exiting the route contact albuquerque ARTCC on 298.9 for exit clearance and traffic advisories, prior to point. Present procedures have the aircraft contact ZDV for exit clearance. Comment: aircraft in this route have had and filed numerous hatr's and near midair collision reports in the past few yrs. It's obvious we, as controllers, are willing to go to the limit to prevent these situations from occurring, but we cannot do it without the equipment. Hopefully it won't take a bmb collision with a light aircraft to help correct this situation.

Related reports:

Google
 

Original NASA ASRS Text

Title: BMB CAME IN CLOSE PROX TO AN UNIDENTIFIED ACFT WHILE EXITING AN IR ROUTE.

Narrative: WHILE WORKING SECTOR R43 ON THIS DATE, I NOTICED BMB X LIMITED DATA BLOCK EXITING IR320 NBND. ALSO, I NOTICED A VFR/CODE 1200/TARGET ON A CONVERGING COURSE OF APPROX 250 DEG, AT AN UNVERIFIED ALT OF 8800. I ATTEMPTED TO CONTACT BMB X ON MY PRIMARY UHF 298.9 LOCATED AT WINSLOW TO ISSUE TFC ADVISORIES/ALERT WITH NO REPLY OR OBSERVED EVASIVE ACTION. (BMB X IS NOT REQUIRED TO MONITOR 298.9). I THEN ATTEMPTED SEVERAL TIMES TO ISSUE TFC ON MY 243.0 LOCATED AT PRESCOTT WITH NO REPLY OR OBSERVED ACTION. AS THE TARGETS MERGED AT 9000 AND 8800 MY NEXT RADAR UPDATE INDICATED BMB X HAD CLIMBED TO 9800. CONTRIBUTING FACTORS ARE FAILURE OF THE VFR ACFT TO CONTACT FSS FOR INFO ON IR ROUTE ACTIVITIES/AND SEE AND AVOID. EQUIPMENT (243.0) REMOVED OR NOT AVAILABLE TO CTLRS. SUGGESTIONS WOULD BE TO INSTALL UHF 243.0 AT SITES WITHIN A USABLE RANGE OF MIL TRAINING ROUTES AND AIRSPACE TO BE AVAILABLE TO CTLRS. ON THIS IR320/276 ROUTE, HAVE ACFT EXITING THE ROUTE CONTACT ALBUQUERQUE ARTCC ON 298.9 FOR EXIT CLRNC AND TFC ADVISORIES, PRIOR TO POINT. PRESENT PROCS HAVE THE ACFT CONTACT ZDV FOR EXIT CLRNC. COMMENT: ACFT IN THIS ROUTE HAVE HAD AND FILED NUMEROUS HATR'S AND NMAC REPORTS IN THE PAST FEW YRS. IT'S OBVIOUS WE, AS CTLRS, ARE WILLING TO GO TO THE LIMIT TO PREVENT THESE SITUATIONS FROM OCCURRING, BUT WE CANNOT DO IT WITHOUT THE EQUIPMENT. HOPEFULLY IT WON'T TAKE A BMB COLLISION WITH A LIGHT ACFT TO HELP CORRECT THIS SITUATION.

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