Military Y after leaving R-5002 had near midair collision with atx X. See and avoid concept.

Attributes
ACN	219059
Time
Date	199208
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : acy
State Reference	NJ
Altitude	msl bound lower : 4000 msl bound upper : 4000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : lax
Operator	common carrier : air taxi
Make Model Name	Light Transport, High Wing, 2 Turboprop Eng
Flight Phase	cruise other
Route In Use	enroute : on vectors enroute airway : acy
Flight Plan	IFR
Aircraft 2
Operator	other
Make Model Name	Experimental
Flight Phase	cruise other
Route In Use	enroute : direct
Flight Plan	VFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller military : 5 controller radar : 1
ASRS Report	219059
Person 2
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : nmac non adherence : far
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Miss Distance	horizontal : 400 vertical : 0
Supplementary
Primary Problem	Flight Crew Human Performance

Narrative:

At the time of the conflict, atx X was inbound to acy from the northeast. Traffic was moderate with a few inbounds and a couple overflts. At the time, I was also briefing the relieving controller. I observed 2 targets entering R-5002 north of acy, so I kept atx X 7-8 mi south of R-5002 to avoid any spillage out of R-5002 and also for the sequence. The WX at the airport was IFR and I was about to turn my inbounds on to the ILS when atx X said he had a near midair collision with what he called a military X. When I looked at the target, I saw a transponder come on indicating 4000 ft 1 mi south of atx X who was also at 4000 ft. Upon further investigation, it was found that the military Y pilot lost his lead and proceeded sbound. Wri approach gave the lost military Y a squawk and when the controller I was briefing called wri, the incident occurred. That was when they informed us of the military Y. I suggest in the future if any aircraft become disoriented in R-5002 they be given direct cyn VOR at a low altitude that will not conflict with their traffic.

Original NASA ASRS Text

Title: MIL Y AFTER LEAVING R-5002 HAD NMAC WITH ATX X. SEE AND AVOID CONCEPT.

Narrative: AT THE TIME OF THE CONFLICT, ATX X WAS INBOUND TO ACY FROM THE NE. TFC WAS MODERATE WITH A FEW INBOUNDS AND A COUPLE OVERFLTS. AT THE TIME, I WAS ALSO BRIEFING THE RELIEVING CTLR. I OBSERVED 2 TARGETS ENTERING R-5002 N OF ACY, SO I KEPT ATX X 7-8 MI S OF R-5002 TO AVOID ANY SPILLAGE OUT OF R-5002 AND ALSO FOR THE SEQUENCE. THE WX AT THE ARPT WAS IFR AND I WAS ABOUT TO TURN MY INBOUNDS ON TO THE ILS WHEN ATX X SAID HE HAD A NMAC WITH WHAT HE CALLED A MIL X. WHEN I LOOKED AT THE TARGET, I SAW A TRANSPONDER COME ON INDICATING 4000 FT 1 MI S OF ATX X WHO WAS ALSO AT 4000 FT. UPON FURTHER INVESTIGATION, IT WAS FOUND THAT THE MIL Y PLT LOST HIS LEAD AND PROCEEDED SBOUND. WRI APCH GAVE THE LOST MIL Y A SQUAWK AND WHEN THE CTLR I WAS BRIEFING CALLED WRI, THE INCIDENT OCCURRED. THAT WAS WHEN THEY INFORMED US OF THE MIL Y. I SUGGEST IN THE FUTURE IF ANY ACFT BECOME DISORIENTED IN R-5002 THEY BE GIVEN DIRECT CYN VOR AT A LOW ALT THAT WILL NOT CONFLICT WITH THEIR TFC.

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