Narrative:

I was busy and working west radar. I gave a sequence to east radar on aircraft X to runway 4 at gsp. We were both busy and the east controller had been certified for 1 week. I did not notice a VFR on a 1200 code depart gmu to the southeast. The east controller was busy; but he noticed the gmu departure and issued vectors to aircraft X and held the plane at 3;000 MSL. From what I can tell he did a really great job.only about 20 minutes before this I had an aircraft on arrival to runway 4 at gsp. There was also a VFR that departed gmu. For whatever reason (the gmu controller or the pilot); it was the best deconfliction I have seen in this scenario from the VFR. The VFR crossed gsp runway 4 final 8 or 9 miles from the runway; which made it a non event for my traffic on the base.I was relieved shortly after the aircraft X event. I went to the tower before my break to suggest a runway change. I thought there would be a lot more gmu departures to the southeast because of a fly in at SC00. I had rather have the unidentified aircraft under a departure than an arrival. The tower initiated a runway change.recommendation: this is a terrible situation because it is not obvious that it is getting ready to happen. Once you realize it; your options are: an unstable approach; TCAS RA; or vectors around for a re-sequence. There are also wake turbulence issues. The gsp air traffic manager (atm) suggested a VFR fix on the gsp runway 4 final. The VFR's would be required to cross at or outside of it and at or below a certain altitude. We know this is a problem. We have the opportunity to fix it before the problem changes to disaster.

Google
 

Original NASA ASRS Text

Title: GSP TRACON Controller reported an occurrence which routinely happens of VFR aircraft not in communication with ATC departing one airport into the final approach course traffic of another airport.

Narrative: I was busy and working West radar. I gave a sequence to East radar on Aircraft X to Runway 4 at GSP. We were both busy and the East controller had been certified for 1 week. I did not notice a VFR on a 1200 code depart GMU to the southeast. The East controller was busy; but he noticed the GMU departure and issued vectors to Aircraft X and held the plane at 3;000 MSL. From what I can tell he did a really great job.Only about 20 minutes before this I had an aircraft on arrival to Runway 4 at GSP. There was also a VFR that departed GMU. For whatever reason (the GMU Controller or the pilot); it was the best deconfliction I have seen in this scenario from the VFR. The VFR crossed GSP Runway 4 final 8 or 9 miles from the runway; which made it a non event for my traffic on the base.I was relieved shortly after the Aircraft X event. I went to the Tower before my break to suggest a runway change. I thought there would be a lot more GMU departures to the southeast because of a fly in at SC00. I had rather have the unidentified aircraft under a departure than an arrival. The Tower initiated a runway change.Recommendation: This is a terrible situation because it is not obvious that it is getting ready to happen. Once you realize it; your options are: an unstable approach; TCAS RA; or vectors around for a re-sequence. There are also wake turbulence issues. The GSP Air Traffic Manager (ATM) suggested a VFR fix on the GSP Runway 4 final. The VFR's would be required to cross at or outside of it and at or below a certain altitude. We know this is a problem. We have the opportunity to fix it before the problem changes to disaster.

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.