Narrative:

While working ground control/controller in charge I noticed a VFR target on a 1200 code transitioning the corridor east of the class D airspace around 7000 feet MSL. By monitoring the operation; I ensured that the local controller saw the potential conflict this aircraft presented with another VFR inbound aircraft at 7000 feet flying a practice ILS approach. The conflict alert sounded as local control took action to issue traffic until the conflict passed.though workload permitted local control to handle this situation effectively; if there was greater traffic volume; higher priority duties; or the inbound aircraft had not yet switched to our frequency; there is the possibility that there may not be time to issue that traffic or take action to resolve that conflict. This event is very similar to other events reported in the past. I continue to believe that action needs to be taken to mitigate conflicts in this corridor that are created by transitioning aircraft that are not receiving air traffic service. Such aircraft can cause conflict alerts and add workload to both tower and radar controllers; when those controllers must guess at what a 1200 code is doing while operating in proximity to the other traffic that is utilizing the air traffic system. Simply receiving services from TRACON or contacting our tower to receive advisories or a class D transition should have made this conflict a non-issue.it's essential that pilots understand that working with ATC will enhance their safety in this busy terminal area; especially as close as they are operating to both class B and class D controlled airspace. Controllers will provide the appropriate instructions and clearances to not only help avoid possible airspace violations; but more importantly; avoid near midair events.

Google
 

Original NASA ASRS Text

Title: Tower Controllers are concerned that a published VFR flight corridor allows aircraft to fly too close to aircraft in their airspace.

Narrative: While working Ground Control/Controller in Charge I noticed a VFR target on a 1200 code transitioning the corridor east of the Class D airspace around 7000 feet MSL. By monitoring the operation; I ensured that the Local controller saw the potential conflict this aircraft presented with another VFR inbound aircraft at 7000 feet flying a practice ILS approach. The conflict alert sounded as Local Control took action to issue traffic until the conflict passed.Though workload permitted Local Control to handle this situation effectively; if there was greater traffic volume; higher priority duties; or the inbound aircraft had not yet switched to our frequency; there is the possibility that there may not be time to issue that traffic or take action to resolve that conflict. This event is very similar to other events reported in the past. I continue to believe that action needs to be taken to mitigate conflicts in this corridor that are created by transitioning aircraft that are not receiving air traffic service. Such aircraft can cause conflict alerts and add workload to both tower and radar controllers; when those controllers must guess at what a 1200 code is doing while operating in proximity to the other traffic that is utilizing the air traffic system. Simply receiving services from TRACON or contacting our Tower to receive advisories or a Class D transition should have made this conflict a non-issue.It's essential that pilots understand that working with ATC will enhance their safety in this busy terminal area; especially as close as they are operating to both Class B and Class D controlled airspace. Controllers will provide the appropriate instructions and clearances to not only help avoid possible airspace violations; but more importantly; avoid near midair events.

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.