Narrative:

Aircraft Y departed orl runway 25 via a right-downwind departure and was then later instructed to turn right and fly a suggested heading of 090 and cross the runway 25 final approach course and proceed eastbound (aircraft Y's requested direction of flight). Aircraft Y was clear of all conflicting traffic and was issued instructions to remain outside of bravo airspace and was given a frequency change at the class delta boundary. Aircraft Y departed the class delta at 011 and maintained that altitude for a few miles after the frequency change.central florida TRACON (F11) vectored aircraft X; from the southeast and cleared the aircraft via a visual approach and frequency changed aircraft X before issuing traffic for merging targets (reference aircraft Y). Aircraft X was descending on the visual approach to join a five mile final when I; the local controller; told aircraft X to continue because I was sequencing other traffic and gathering pertinent flight data. I do not recall the altitude when aircraft X checked on frequency. At some point several miles east of the class delta airspace aircraft Y began a VFR climb as aircraft X descended toward the airport.the orl/F11 shout line was activated from F11 asking orl to issue traffic reference the two aircraft because F11 had not issued traffic before frequency changing aircraft X to orl tower frequency. I was unable to issue a timely traffic advisory to aircraft X before responding to a TCAS/RA (002 climb). Closure rate between the two aircraft was; I believe; near 300 knots. I asked aircraft X for intentions and allowed the aircraft [to] continue the approach per the pilot's request. Aircraft X landed without incident. Aircraft Y continued VFR eastbound without incident. Issue traffic between all known conflicts before frequency changing any aircraft.

Related reports:

Google
 

Original NASA ASRS Text

Title: ORL Tower Controllers report of a NMAC involving a VFR departure clear of the Class Delta but in the Class Bravo and an IFR arrival inbound. TRACON did not issue traffic to the arrival; and called to alert the Tower. Tower was unable to call traffic before the inbound aircraft responded to a RA.

Narrative: Aircraft Y departed ORL Runway 25 via a right-downwind departure and was then later instructed to turn right and fly a suggested heading of 090 and cross the runway 25 final approach course and proceed eastbound (Aircraft Y's requested direction of flight). Aircraft Y was clear of all conflicting traffic and was issued instructions to remain outside of Bravo airspace and was given a frequency change at the Class Delta boundary. Aircraft Y departed the Class Delta at 011 and maintained that altitude for a few miles after the frequency change.Central Florida TRACON (F11) vectored Aircraft X; from the Southeast and cleared the aircraft via a visual approach and frequency changed Aircraft X before issuing traffic for merging targets (reference Aircraft Y). Aircraft X was descending on the visual approach to join a five mile final when I; the local controller; told Aircraft X to continue because I was sequencing other traffic and gathering pertinent flight data. I do not recall the altitude when Aircraft X checked on frequency. At some point several miles east of the Class Delta Airspace Aircraft Y began a VFR climb as Aircraft X descended toward the airport.The ORL/F11 Shout line was activated from F11 asking ORL to issue traffic reference the two aircraft because F11 had not issued traffic before frequency changing Aircraft X to ORL Tower frequency. I was unable to issue a timely traffic advisory to Aircraft X before responding to a TCAS/RA (002 climb). Closure rate between the two aircraft was; I believe; near 300 knots. I asked Aircraft X for intentions and allowed the aircraft [to] continue the approach per the pilot's request. Aircraft X landed without incident. Aircraft Y continued VFR Eastbound without incident. Issue traffic between all known conflicts before frequency changing any aircraft.

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.