B737 flight crew reported parallel traffic overshot final resulting in a NMAC; unstable approach; and low altitude alert with a terrain advisory.
Synopsis
B737 flight crew reported parallel traffic overshot final resulting in a NMAC; unstable approach; and low altitude alert with a terrain advisory.
Narrative
On first contact with ZZZ Approach; we were assigned the Visual to runway XXL into ZZZ. This required an approach change in the FMC. As the approach is RNAV based; we loaded the approach; connecting to the ZZZZZ1 from ZZZZZ. Additionally we verified the correct RNP; 2 working GPS's; turned off VOR and DME updating; ensured the final approach courses were set to XXX; and the ILS/VOR Recievers were tuned to XXX.X. After verifying we had correctly set up for an RNAV approach; the Captain made the decision to keep the Autopilot connected in order to accurately make the turn from ZZZZZ and join the final approach course. In his judgement and mine; this was the safest course of action to avoid an overshoot on final. As is normal when flying FMC visual approaches into ZZZ; we were paired with parallel traffic; in this case Aircraft Y. We were able to clearly identify our traffic visually. As we begun our descent; on the lateral path inbound to runway XXL; TCAS gave us the aural alert; TRAFFIC; TRAFFIC." Both of us cross referenced the TCAS on the MFD (Multi-function Flight Display) to confirm Aircraft Y position in relation to us. Additionally; as the aircraft in question was off the right side of the aircraft; flying the approach to runway XXR; I once again visually confirmed the aircraft's position. At this moment; we received an RA requiring a descent to avoid conflict with the intruder aircraft. The Captain disconnected the automation and began following resolution guidance. Again I looked out to confirm the position of Aircraft Y however the aircraft had disappeared from view AND according to TCAS was within 300' of our altitude and appeared to be descending on top of us. We continued to follow RA guidance and began to discuss. Need to turn as altitude was running out. Just a few moments later we received the 'monitor vertical track' que from TCAS and the Captain arrested the descent rate. We also received a LOW ALTITUDE alert from ZZZ tower. We then coordinated a left hand turn from Tower; followed by a climb initially to 3100' and executed a go around. Following the go around; we set up for another approach into ZZZ and landed without further event. Upon listening to archived ATC recordings; Aircraft Y continued their approach and landed without incident and appeared unphased or unaware of what had occurred on final."
Second reporter narrative
On speed and path; AP on in LNAV/VNAV. ZZZZZ visual XXL. Aircraft Y cleared visual on XXR. FO initially had Aircraft Y in sight; but they overshot final and drifted behind us. Tcas showed them nearly on top of us using the lowest range of 2.5 miles. I understand the display limitations of tcas; but we had lost visual. As we queried tower; we received and followed a descending RA. We then asked for a breakout to the south and performed a go around. We shot another visual and landed w/o further incident.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.