A320 Captain reported a NMAC with a helicopter during approach resulting in a TCAS advisory. Flight responded to TCAS advisory to clear conflict and continue approach.

2024-05 · NASA ASRS report 2120752

Date: 2024-05 · Aircraft: A320 · Phase: approach

Anomalies: conflict-nmac

Synopsis

A320 Captain reported a NMAC with a helicopter during approach resulting in a TCAS advisory. Flight responded to TCAS advisory to clear conflict and continue approach.

Narrative

Aircraft Registration: Aircraft X (A230)Cleared by ZZZ Approach to the RNAV Z Runway XXL approach.Conflict registered descending from 3000ft to 2500ft from ZZZZZ to ZZZZZ1.PF: CaptainDuring the approach of Aircraft X from ZZZZ to ZZZ the pilots of Aircraft X were instructed to fly heading 360 and fly direct to ZZZZZ2. Just before reaching ZZZZZ2; ZZZ Approach instructed to maintain 3000ft until ZZZZZ2 and cleared us for the approach RNAV Z Runway XXL; speed at pilot discretion. After ZZZZZ2 and maintaining 3000ft as per the approach; the pilots began decelerating during the level segment from ZZZZZ2 to ZZZZZ. ZZZ Approach now instructed to change to ZZZ Tower over ZZZZZ1. Close to ZZZZZ we noticed a helicopter [Aircraft Y] northeast of ZZZZZ 400ft below as marked by TCAS. We immediately received a traffic advisory; however as soon as starting the descent as per the RNAV Z Runway XXL approach from ZZZZZ to ZZZZZ1 (descent from 3000ft to 2500 ft at ZZZZZ1); we soon realized the helicopter traffic was closely approaching our trajectory from of the RNAV Z XXL approach. Near to 2900 ft on the segment from ZZZZZ to ZZZZZ1; we received a TCAS resolution requesting an immediate level off. We responded to the TCAS resolution by leveling off; a second command again requested to continue level flight and a final and third instruction requested to initiate a climb. A couple of second later of responding to this final climb instruction and upon crossing 3100ft; the TCAS system called a 'Clear of Conflict'. Indeed the helicopter was now behind our trajectory and no further conflict was registered. We immediately notified ZZZ Approach of the TCAS resolution; at which they asked if we where still able to continue the approach. Not being too high of the recommended flight profile; we responded we where still able to continue the approach. ZZZ Approach again cleared us for the approach and instructed us to change to ZZZ Tower at XXX.X. The pilots where able to quickly configure the aircraft for landing and thus recovering the flight profile.ZZZ Tower cleared Aircraft X for landing at Runway XXL. Flying an stabilized approach at 1000ft; the pilots continued the final approach to Runway XXL and completed a successful landing with no further incidents.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.