Reporter states an air carrier on a visual approach responded to an RA due to a small aircraft in cl...

Narrative:

I cleared aircraft X for a visual approach to the left runway at ZZZ. I thought I had transferred communications to ZZZ tower; but had not. Aircraft X advised they were responding to an RA as they turned final. I observed a partial data block approximately 1 mile west of aircraft X. I selected the target and discovered it was a 'traffic watch' aircraft under control of ZZZ local north. The altitude indicated 200 ft below aircraft X. I acknowledged aircraft X and transferred communications to ZZZ tower. The targets did not merge and qc data later reported closest (distance) as .86 NM.this type of situation was a frequent recurring problem for ZZZ arrivals 2.5 to 3 years ago. At that time; TRACON natca requested a work group to meet with ZZZ to discuss this issue and other letter of agreement changes. We held multiple meetings in 2012 and had a finalized LOA ready to sign. This issue however; was not one that we felt was resolved. At the time; TRACON natca did not believe it was a good idea for another facility to own airspace underneath a final that TRACON controlled. ZZZ did not want to relinquish the airspace and a compromise resolution was pursued. ZZZ agreed to meet with the 'traffic watch' operator and believed they would be willing to move their route further west so that ZZZ arrivals would pass safely above them at all times. TRACON agreed to meet with ZZZ1 tower who owned the airspace that would be required to move the 'traffic watch' route. ZZZ1 acknowledged that they did not need or use the airspace; but did not want to give it up because they felt it would place traffic watch aircraft close to the third busiest airport in the world. With ZZZ1's unwillingness to assist; ZZZ advised that they would just hold the traffic watch aircraft west of the final until it was clear. This was not confirmed in the LOA; and I don't believe ZZZ briefed their personnel of this agreement. The LOA that contained many other safety fixes still has still not been signed. It sits in the TRACON procedures office and on the desk of a staff specialist at ZZZ. I believe the best resolution to this would be for TRACON to acquire the airspace currently being worked by ZZZ tracab and some of the airspace currently owned by ZZZ1 tower.

Original NASA ASRS Text

Title: Reporter states an Air Carrier on a visual approach responded to an RA due to a small aircraft in close proximity. Reporter also states LOA needs to be changed to encompass who owns what airspace in close proximity of airport and final approach course.

Narrative: I cleared Aircraft X for a visual approach to the left runway at ZZZ. I thought I had transferred communications to ZZZ Tower; but had not. Aircraft X advised they were responding to an RA as they turned final. I observed a partial data block approximately 1 mile west of Aircraft X. I selected the target and discovered it was a 'traffic watch' aircraft under control of ZZZ Local North. The altitude indicated 200 FT below aircraft X. I acknowledged Aircraft X and transferred communications to ZZZ Tower. The targets did NOT merge and QC data later reported closest (distance) as .86 NM.This type of situation was a frequent recurring problem for ZZZ arrivals 2.5 to 3 years ago. At that time; TRACON NATCA requested a work group to meet with ZZZ to discuss this issue and other Letter of Agreement changes. We held multiple meetings in 2012 and had a finalized LOA ready to sign. This issue however; was not one that we felt was resolved. At the time; TRACON NATCA did not believe it was a good idea for another facility to own airspace underneath a final that TRACON controlled. ZZZ did not want to relinquish the airspace and a compromise resolution was pursued. ZZZ agreed to meet with the 'traffic watch' operator and believed they would be willing to move their route further west so that ZZZ arrivals would pass safely above them at all times. TRACON agreed to meet with ZZZ1 Tower who owned the airspace that would be required to move the 'traffic watch' route. ZZZ1 acknowledged that they did not need or use the airspace; but did not want to give it up because they felt it would place traffic watch aircraft close to the third busiest airport in the world. With ZZZ1's unwillingness to assist; ZZZ advised that they would just hold the traffic watch aircraft west of the final until it was clear. This was not confirmed in the LOA; and I don't believe ZZZ briefed their personnel of this agreement. The LOA that contained many other safety fixes still has still not been signed. It sits in the TRACON Procedures Office and on the desk of a Staff Specialist at ZZZ. I believe the best resolution to this would be for TRACON to acquire the airspace currently being worked by ZZZ TRACAB and some of the airspace currently owned by ZZZ1 Tower.

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.

Attributes
ACN	1158799
Time
Date	201402
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Light	Daylight
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft Low Wing 1 Eng Fixed Gear
Flight Phase	Cruise
Flight Plan	VFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 18
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Reporter states an air carrier on a visual approach responded to an RA due to a small aircraft in close proximity. Reporter also states LOA needs to be changed to encompass who owns what airspace in close proximity of airport and final approach course.