2024-04 · NASA ASRS report 2104963
Air carrier flight crew reported receiving a TCAS RA that was determined to have been a phantom RA. While responding to the phantom RA; the flight crew descended toward an aircraft resulting in an airborne conflict requiring ATC to deconflict the aircraft.
We were level at FL360 in cruise; heading southbound. I was the PF and the Captain was the PM. We got a TCAS TA and shortly thereafter; a descend TCAS RA. I immediately complied with the RA. While in the descent; the RA changed to 'increase descent'; and I complied with that as well; increasing the rate of descent. When the Captain made his radio transmission to ZZZ Center saying we were complying with a TCAS RA; the controller said there was no traffic at FL360; but that we were actually descending right into traffic at FL350. She immediately gave us a left turn to a heading I don't specifically recall; and then a further left turn to get us away from traffic. After we were clear of conflict; we were cleared back on our route and climbed back up to FL360. The airplane's logbook had two recent write-ups for the same exact issue- 'phantom targets'. After that transpired we left the TCAS in TA only as not to have another false RA fly us right into traffic again. A while later we got yet another phantom target at out 12 o'clock and same altitude. We verified with ATC and they confirmed it was a phantom traffic. We then decided that the best course of action was to turn the TCAS off altogether for the remainder of the flight. We were informed by Center of a possible pilot deviation; since we left our altitude without a clearance. Of course we did that in compliance with the RA; but from ATC's standpoint there was no reason for us to leave FL360. The flight continued without any further issues. After we wrote the item up for the third time upon arriving in ZZZ1; Maintenance said they would defer the TCAS for our flight back to ZZZ. We then refused the aircraft.
Level at FL 360 southbound cruise Autopilot on TCAS RA descend now and increasing. Responded which descended us into northbound traffic at FL 350. ATC turned us away from traffic. Apparent phantom traffic previously written up twice. Climbed back to FL 360 on course selected ta only 3 minutes later received a traffic TA selected TCAS off. Put everyone on 2 aircraft in a dangerous situation. Seatbelt sign was off and fortunately no one was injured in the back. MEL says we don't need TCAS. This phantom RA put us in a very dangerous situation. Thank goodness the controller was sharp and paying attention; she prevented what could have been a terrible accident.
More incidents for this aircraft family
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.