Narrative:

Aircraft X was on a VFR practice approach to runway 1 at gmu. An unidentified aircraft departed runway 5 at gyh and turned southbound. Because I have seen a lot of close calls and I wasn't busy; I noticed the aircraft squawking 1200. Since the aircraft were converging; I called gyh tower to find out the aircraft's intentions. I then instructed gyh tower to turn the aircraft to a 090 degree heading. This took care of the issue.because this situation happens quickly; without warning; and with multiple frequencies involved; we can't ensure that this won't lead to a midair collision. I am told the FAA is about to get a second briefing for a proposed dbrite (tower radar display) for gyh. Hopefully [they] will approve it; but I doubt [they] know about the last two incidents.the dbrite is very important; but must be paired with VFR departure procedures for gyh. My supervisor suggested that all VFR departures off gyh should exit the class D laterally. This would keep the aircraft from climbing above 1800 feet before getting 5 miles from gyh. This would substantially reduce the risk to the system. It would require more phraseology from gyh tower. Something like remain at or below 1800 feet until 5 miles from gyh and outside of gmu class D and gsp class C. If unable; advise. Last year gyh tower; gmu tower; and gsp tower tried to reach an agreement about VFR departures; but failed. If IFR/VFR traffic is a top 5 issue and the FAA has the capacity to manage the system; this can be fixed easily and quickly. It needs to be fixed immediately because sooner or later; our luck will run out.

Google
 

Original NASA ASRS Text

Title: A Controller reported a VFR aircraft depart an airport that was going to be in confliction with their aircraft on approach so they issued a vector away to the the VFR aircraft.

Narrative: Aircraft X was on a VFR practice approach to runway 1 at GMU. An unidentified aircraft departed runway 5 at GYH and turned southbound. Because I have seen a lot of close calls and I wasn't busy; I noticed the aircraft squawking 1200. Since the aircraft were converging; I called GYH tower to find out the aircraft's intentions. I then instructed GYH tower to turn the aircraft to a 090 degree heading. This took care of the issue.Because this situation happens quickly; without warning; and with multiple frequencies involved; we can't ensure that this won't lead to a midair collision. I am told the FAA is about to get a second briefing for a proposed DBRITE (Tower Radar Display) for GYH. Hopefully [they] will approve it; but I doubt [they] know about the last two incidents.The DBRITE is very important; but must be paired with VFR departure procedures for GYH. My supervisor suggested that ALL VFR departures off GYH should exit the Class D laterally. This would keep the aircraft from climbing above 1800 feet before getting 5 miles from GYH. This would substantially reduce the risk to the system. It would require more phraseology from GYH tower. Something like remain at or below 1800 feet until 5 miles from GYH and outside of GMU Class D and GSP class C. If unable; advise. Last year GYH tower; GMU tower; and GSP tower tried to reach an agreement about VFR departures; but failed. If IFR/VFR traffic is a top 5 issue and the FAA has the capacity to manage the system; this can be fixed easily and quickly. It needs to be fixed immediately because sooner or later; our luck will run out.

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.