Sounds like UA had an issue that required getting off the runway after takeoff clearance, but the only available path to the next exit taxiway was across the intersecting runway, where Jetblue arrival was on short final. Tower may have gotten an alarm or not been absolutely sure UA was holding short of intersecting runway, so sent the Jetblue around. Go-around and incident lasts all of 10 seconds.
The fact that runway 33L offers no exit before the intersecting runway is not ideal. From the satellite photos it seems that 27 should have hold short lines and blinking lights at the intersection of 33L but who knows what the snow might have done...
The audio you can refer to:
http://archive-server.liveatc.net/kb...2018-2200Z.mp3
Also the airport diagram:
http://155.178.201.160/d-tpp/1801/00058AD.PDF
------------
My rough transcription:
11min5sec (11:05): Jetblue 1154 (the later go-around aircraft) ILS 27 cleared to land.
Jetblue is following a A319 on 6 mile final (so is perhaps about 10-12 mile final)
12:38: UA 1946 line up and wait 33L.
13:31: Jetblue is about 5 mile final (from Tower comms to next arrival)
14:44: UA 1946 cleared for takeoff. Jetblue ~3 mi final according to Tower comms to next departure to line up + wait.
15:12: UA has an issue after clearance and requests to get off the runway. This requires taxing on the runway to the next taxiway, but 33L intersects 27 before it reaches a next taxiway. Tower instructs UA to taxi on runway, hold short of 27.
15:53: Tower asks if UA needs assistance, needs to exit runway and return to gate, or return in line for takeoff. UA responds just needs to get off runway, not back to gate yet.
16:18: Tower instructs UA 1946 to hold short of 27.
16:22 (more urgently) "1946 hold short 27".
16:25: UA responds "we are short of 27".
16:27: "Jetblue 1154 go around"
16:49: "UA 1946, traffic 2 mile final, cross 27 no delay, left at Q" (4th exit way down the runway, the only available exit).
------
Next Jetblue arrival 27 cleared to land 30 sec later no issues.