An air carrier crew reported Tower issued a go around on short final which caused them to fly too close to an aircraft departing an intersecting runway.
Synopsis
An air carrier crew reported Tower issued a go around on short final which caused them to fly too close to an aircraft departing an intersecting runway.
Narrative
Approach assigned us to RNAV RWY XX; vectoring us; and assigning speeds 210; then 190; then 170. ZZZ [airport] was landing intersecting runways XYR and XX. Knowing that spacing is critical and complicated; I was most diligent to achieve and precisely maintain speed assigned; immediately when assigned. Approach cleared us for the RNAV RWY XX. Tower cleared us to land RWY XX. Fully configured and stable by 1000' AFE (Above Field Elevation); remained stabled; flaps 22°; on speed; past minimums; auto-pilot off and hand-flying; about to land; when suddenly tower told us that spacing was not good; and called Go-around" at 150' AFE. I repeated "Go-around"; and continued with my SOP call outs and profile "Max thrust; Flaps 9"; while pressing the red GA buttons and pushing the thrust levers full forward.Tower was communicating a second call to us; to fly runway heading and climb to 3000'. Captain repeated the instructions and set the FGC (Flight Guidance Computer); the auto-pilot was OFF. As we were still flaps 22°; I repeated "Go-Around; Max thrust; Flaps 9°" at which point the Captain changed the flaps setting to 9°. I flew the Flight Director. Aircraft Y was taking off from intersecting RWY XYL; and crossed our flight path while already airborne just in front of us. The Captain reached for the controls without inputting any pressure and letting me continue to fly the plane. Both of us were shocked by how close we were to the conflicting traffic. We were vectored for the ILS RWY XYR; configured and performed the second approach to landing safely.Cause: There is a clear problem at ZZZ when landing intersecting runways as this is happening frequently with conflicting traffic. Approach regularly requires s-turns; and tower regularly calls for go-around; sometimes when uncomfortably low and already much much too close to traffic. This must be looked at closely before a catastrophe happens. Suggestion: More spacing between aircraft; less talking from tower when calling "go-around" and waiting a minute before assigning heading and target altitude. When a conflict is suspected; tower should initiate and call the go-around much sooner before it is so dangerously close."
Second reporter narrative
We were on the RNAV for [runway] XX into ZZZ [airport]. ZZZ was landing XYR/XX and departing XYL. We had a normal approach; we broke out at 1600 ft MLS and had the field in sight. Approaching minimums the FO disconnected the autopilot to continue to landing; while I went to set missed and Vac. Shortly after descending through minimums tower keyed up saying this is too close and told us to go around runway heading and maintain 3000. FO initiated the go around with call outs and max thrust. Tower calls the aircraft that is taking off XYL and tells them to level off while just beginning their takeoff climb. We see the aircraft close in front as we climb above and behind it. I guarded the controls in case of needing to make a left turn to clear traffic. We ended up climbing behind the aircraft but spacing was way closer than it should have been; especially when the converging aircraft is originating from the ground. We flew the go around; continued up to 4;000 and got vectored back around with no issues landing for ILS XYR. Cause: Poor spacing/ planning in ZZZ. The tower issued go around should have been issued earlier to avoid the close proximity. Suggestion. More attention has to be given to spacing in ZZZ when using RWY XX. Go arounds are frequent when using that runway. I do believe it is one thing to have difficulty with spacing when both aircraft are in the air landing converging runways. There are more variables in that; but when one is starting on the ground the spacing should in theory be easier to manage. I'm not sure if there was some mix up; if Aircraft Y took a long time to actually takeoff or what exactly.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.