CRJ-900 flight crew took evasive action to avoid a VFR aircraft on a converging path.

Date: 2025-12 · Aircraft: Regional Jet 900 (CRJ900)

Anomalies: conflict-nmac

Synopsis

CRJ-900 flight crew took evasive action to avoid a VFR aircraft on a converging path.

Narrative

On Day 0 on Flight XXXX from ZZZ1-ZZZ we received a TA followed by a RA while on the arrival ZZZZZ. We were on frequency with ZZZ Approach. We were level at 8;000ft in between ZZZZZ1 and ZZZZZ2. On our MFD (Multi-function Flight Display); I noticed an aircraft at the same altitude on a converging path from our right at the same altitude. I asked the FO if she could see the aircraft visually and she said yes. A few seconds later we received a TA. ATC then tells an aircraft to immediately climb to 8;500ft due to traffic and make a left turn; I forgot what the heading was. However; the call sign was blocked so I did not know who the call was for. I did not want to assume it was for us so I asked the FO to ask ATC if that call was for us but at that time we received a RA to climb. I immediately disconnected autopilot and began my climb following the advisory to climb at 1;400 fpm. The advisory then told me to keep climbing at a rate of 2;500 fpm. As we were responding; the FO told ATC we were responding to an RA. ATC tells us ok and to fly heading 160 when able and to descend to 4;000 when able. We climbed from 8;000 to approximately 9;000ft before becoming clear of the conflict. ATC claimed that he was not talking to the other aircraft but that it was Aircraft Y out of ZZZ2. After leveling off and once clear of the conflict; I started my descent to 4;000ft and flew heading 160 to join the final. The flight continued without incident. Once we were at the gate; I asked the forward flight attendant if she felt anything to which she responded I had no clue we were climbing". Cause: There was either a misunderstanding from the other aircraft about which altitude to fly or another ATC controller gave the command to fly a wrong or incorrect altitude. I do believe this may be considered a near mid-air collision due to the fact that the aircraft who was on our converging path also climbed at the same time hence why our RA increased our climb rate by another 900fpm. The flight paths were extremely close when comparing flight radar. Suggestions: In these situations I do not believe there is any way to prevent it. Both me and the FO were situationally aware of the converging aircraft prior to any aircraft warning. I held course and altitude until it was no longer safe to do so and complied with the RA as procedures require."

Second reporter narrative

While on the ZZZZZ STAR into ZZZ; between ZZZZZ1 and ZZZZZ2 level at 8000ft we experienced a TCAS RA. Before the RA occurred; my CA and I noticed a target aircraft to the south west of us at the same altitude and heading towards us from the TCAS on our MFD (Multi-function Flight Display); I looked outside to my right and spotted the small aircraft. At this time we received no traffic alert or solution from atc. The CA prepared as the aircraft got closer in the next 10sec. Once we got the TRAFFIC" aural from the aircraft; ATC now then tried to issue us an altitude of 8500 and a heading to fly (as well as noting that the aircraft wasn't under his control) but halfway through his instructions to us we got a TCAS RA with the airplane saying "CLIMB". The CA executed the TCAS RA maneuver and I told ATC we were responding to a TCAS RA. ATC noted that during our RA the aircraft was "following us" as they also started to climb to try to avoid us. Initial VS I saw was 1.5fpm during the RA; but CA said she saw it go as high as requiring ~2.4fpm. Once we were clear of the conflict at 9000ft; ATC gave us a descent to 4000ft; a heading of 160 and the tailnumber of the target aircraft which is Aircraft Y. We landed in ZZZ after without any other event.Cause: Failure of other aircraft (Aircraft Y) to spot traffic (us). Possibly ATC awareness of both aircraft courses."

More incidents for this aircraft family →

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