Air carrier flight crew reported an airborne conflict with a UAS while on arrival. Flight crew reported they also had an airborne conflict with another aircraft and responded to a RA commanded climb.
Synopsis
Air carrier flight crew reported an airborne conflict with a UAS while on arrival. Flight crew reported they also had an airborne conflict with another aircraft and responded to a RA commanded climb.
Narrative
On the Ironman arrival into LAX; now at 5000' on downwind; PM noticed a drone in proximity to our aircraft. As we continued descent on approach; ATC continued to query us about drone with several separate transmissions. What was the type of drone; what direction was it heading; what was the proximity vertically/horizontally; what color was it;etc. It became very distracting. We are now on base turn; for 24R on north complex; descending to 2500 ft. ATC points out Aircraft Z landing on south complex. Traffic in sight. On final; cleared for the visual (but PF staying on LOC/GS); autopilot turned off; 1800'? ish; we get a 'traffic;traffic'. Traffic still in sight for south complex 25L. Then we get a 'Climb;Climb'. Autopilot already off; PF initiates response to RA; and immediately red bars go away; clear of conflict. Notify Tower about RA. Tower asks if we are going around or continuing. PF says we are good to continue approach; clear of conflict; and approach/landing is accomplished without incident.
Second reporter narrative
Established on visual to RWY 24R LAX; at approx 2200 feet MSL; received TCAS RA for traffic same altitude on approach to RWY 25L LAX. Captain; Pilot Flying; disconnected autopilot. Initial TCAS RA instructions were to not descend. Approximately 5 seconds later; the TCAS RA instructed a slight climb. The climb RA command only lasted about 1 second. Before the Captain was able to climb; RA was discontinued. Continued a stable visual approach without issue.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.