2025-06 · NASA ASRS report 2250448
Air carrier flight crew reported a near miss with a helicopter on final approach. The air carrier flight received a TCAS RA and performed a go-around then returned for a landing.
I was the pilot monitoring (PM) and the Captain was the pilot flying (PF). We were on the ILS 17 inbound to PHL. Tower advised us that there was a helicopter that would stay either east or west of the approach course. We were told to keep visual separation. I than told ATC that we had negative contact on the helicopter. The helicopter responded with that he had us in sight. We were then cleared to land and fully configured. I had my TCAS up and was scanning for the traffic while we were approaching the runway at 800 feet. At this point the TA went off advising us to climb. I then spotted the traffic off or left a few hundred feet below us turning in our direction and into the approach course. We both stated to go-around and initiated the go-around procedure. After advising ATC of what happened they vectored us back around for 27R. We landed with no further issues.Cause: The helicopter pilot did not follow ATC instructions. Causing a go-around.Suggestion: Keep helicopters from circling around the approach end of runways during busy traffic hours at large airports. This seems to be an on going issue with airlines.
FLT ABCD ZZZ XA:53 PHL XC:06 Captain pilot flying (PF); First Officer (FO) pilot monitoring (PM)On the ILS 17 inbound ATC was advising helicopter traffic left and right of the approach course. Tower advised us of helicopter traffic at 400 ft that would remain left and right of the approach course and cleared us to land; however; subsequently stated 'maintain visual separation'. PM stated multiple times 'negative contact'. Tower then reiterated clearance to the helicopter left of our approach course to remain clear of approach course for landing traffic. Helicopter stated they had us 'in sight'. As we descended through 800 ft PM was looking for traffic as we received multiple TA Traffic Traffic TCAS advisories and I observed multiple targets left/right of approach course 400 below on TCAS. Subsequently PM observed traffic stating it was just below; directly ahead of us; turning towards us. I looked up from scanning and observed a helicopter 200-300 hundred feet below us that appeared to be making a sweeping right hand turn and entering our approach course.I initiated a go-around but immediately received a RA CLIMB which I executed.We were given vector back around and landed 27R without further incident.Cause: Helicopter not maintaining visual separation.Suggestion: Helicopter traffic allowed too close to approach course; visual separation not possible; practical; or safe on approach course below 1000 ft.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
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.
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.
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.
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.