EMB-175 flight crew reported wind shear encounter causing a GPWS alert resulted in a CFTT event and a go around with conflicting traffic.

Date: 2025-01 · Aircraft: EMB ERJ 170/175 ER/LR · Phase: approach

Anomalies: conflict-airborne-conflict|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-weather-turbulence|inflight-event-encounter-cftt-cfit

Synopsis

EMB-175 flight crew reported wind shear encounter causing a GPWS alert resulted in a CFTT event and a go around with conflicting traffic.

Narrative

During approach to XX in ZZZ during a strong wind event We were on the RNAV GPS XX approach. It was very windy and the current atis was 280@14Gust40. Not a typo...ZZZ landing and taking off XX only. Landing clearance was being received late by all aircraft. We had passed ZZZZZ FAF and FO had stated 1000 configured call as normal. Tower issue wind of approx 270@20GUST28. Much less and cleared to land. At about the time the FO switched the nose landing light switch to on for cleared to land we triggered a terrain proximity caution. I was flying and it was coupled on autopilot. Once conditions was encountered I went around. There was traffic passing overhead and traffic ahead that just departed. I elected to go to TOGA and not max because of close proximity to other aircraft. We missed the aircraft passing overhead by less than 1000 foot. The gear went up before flaps because between threading needle between aircraft and ATC issuing commands due to our close proximity things were moving very fast. I believe there may have been a communication and expectation difference between myself and FO. He was expecting the escape maneuver and it was a mixture so when I thought he had moved flaps I called for gear up. These events don't always happen so slowly as we practice in sim. We got vectored back for approach and landed uneventfully. I believe we encounter a performance decreasing windshear loss that caused our sink rate to trigger the ground proximity before the windshear. The buildings on east side of flushing are all roughly 300 feet. And we could not have gone below 700 feet from what I remember. We did not deviate from course and again was perfectly where we should have been on approach when it happened. The aircraft overhead did not allow for us to do a full escape maneuver. Aircraft should not have been over the course. It made the situation much harder.

Second reporter narrative

Around 900 feet directly over Flushing on final; we encountered 'obstacle' through the GPWS. CA was PF and initiated the go around. Current ATIS was reporting wind velocity of 14 knots gusting 40 and LLWS advisories were in effect. Tower gave us a current wind of ~20 kts gusting 28. We had a loss of ~14 kts on final around 1100 feet. CA elected for TOGA thrust due to traffic directly above our present position and didn't want to trigger an RA. During the go around; tower vectored us north about a mile before the runway and a level off at 2;000. Vectored around by approach and landed successfully the second attempt. We believe the vertical speed on final dropped to around -1;400 FPM triggering an obstacle warning due to the buildings in front of us. The wind gusts could have also yawed us in a direction of adjacent buildings triggering it as well.

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