Narrative:

Aircraft X was on left downwind for a visual approach to runway 16L at 030. An unknown VFR aircraft was approximately 5 miles north east of afw at 025 not talking to afw tower. Local issued traffic to aircraft X. Aircraft X climbed to 035 back into class B airspace. Aircraft X advised that they climbed for the VFR traffic. Aircraft X said they did respond to an RA and had the traffic in sight. D10 was notified that aircraft X responded to the RA; local asked aircraft X intentions and they said to continue to land. Local cleared aircraft X to land runway 16L. However aircraft X ended up going around on short final and was issued runway heading maintain 030. Aircraft X was re-sequenced by D10 and landed on runway 16L without further incident.this continues to happen in this area. The class bravo north of afw at 030 and our class delta airspace VFR traffic seems to be funneled to this area at 025. Aircraft X was on a visual; but many times aircraft on the ILS are in conflict with VFR aircraft at 025 as they cross wigzu. Afw airport continues to conduct pilot outreach to have these VFR pilots to contact us in this area so we could provide traffic advisories. Yet it still continues to happen. Since july 1st we have logged over 50 occasions where aircraft have been in close proximity in this area. Each occasion required traffic advisories or safety alerts. Several times these incidents have resulted in TCAS advisories or aircraft being forced to execute go-arounds like in the occurrence today. We need to be able to talk to these VFR aircraft. The delta airspace should be extended or the class bravo needs to be extended to include this dangerous area.

Related reports:

Google
 

Original NASA ASRS Text

Title: AFW Controller reported an airborne conflict and stated it is a common occurrence in the area. Controller would like the airspace changed to protect aircraft inbound to AFW.

Narrative: Aircraft X was on left downwind for a visual approach to Runway 16L at 030. An unknown VFR aircraft was approximately 5 miles north east of AFW at 025 not talking to AFW Tower. Local issued traffic to Aircraft X. Aircraft X climbed to 035 back into Class B airspace. Aircraft X advised that they climbed for the VFR traffic. Aircraft X said they did respond to an RA and had the traffic in sight. D10 was notified that Aircraft X responded to the RA; local asked Aircraft X intentions and they said to continue to land. Local cleared Aircraft X to land Runway 16L. However Aircraft X ended up going around on short final and was issued runway heading maintain 030. Aircraft X was re-sequenced by D10 and landed on Runway 16L without further incident.This continues to happen in this area. The Class Bravo north of AFW at 030 and our Class Delta airspace VFR traffic seems to be funneled to this area at 025. Aircraft X was on a visual; but many times aircraft on the ILS are in conflict with VFR aircraft at 025 as they cross WIGZU. AFW airport continues to conduct pilot outreach to have these VFR pilots to contact us in this area so we could provide traffic advisories. Yet it still continues to happen. Since July 1st we have logged over 50 occasions where aircraft have been in close proximity in this area. Each occasion required traffic advisories or safety alerts. Several times these incidents have resulted in TCAS advisories or aircraft being forced to execute go-arounds like in the occurrence today. We need to be able to talk to these VFR aircraft. The Delta airspace should be extended or the Class Bravo needs to be extended to include this dangerous area.

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.