Two Go-Arounds at MSP on 7/5 - DL 23

[ChadL]

I was on flight DL 23 yesterday (7/5) from DTW to MSP, where upon arriving at MSP, we had to go around twice.  The captain made it sound like each time was because of a runway incursion, but didn't give specifics.  I was looking for audio of it, but it looks like the KMSP tower feed has been down since 13:00 on 7/5.  Am I understanding that correctly?

Is there a different way to get the audio?  The first would have happened right around 21:27Z, and the second would have been around 21:39Z.

Thanks!

[dave]

Our feeds at MSP are down due to an equipment issue. If you want those recordings you can try a FoIA request with the FAA but act fast as the FAA expires them pretty quickly.

[ChadL]

Thanks, Dave.  Someone with knowledge of what exactly happened saw my post and sent me a message with the details.  Was more of a curiosity thing for me, which he was able to satisfy.  Never been on a double go-around before.

[GeoffSM1]

Thanks, Dave.  Someone with knowledge of what exactly happened saw my post and sent me a message with the details.  Was more of a curiosity thing for me, which he was able to satisfy.  Never been on a double go-around before.

I imagine that would be rather alarming if not explained at the time. What was the explanation please?

[tyketto]

I've been on one before. ROK316, KLAS-KLAX. We were on final for a visual approach to 25L, where we were asked to go around because the previous aircraft had missed the taxiway they were asked to exit on, while we were on short final. So down and up we went into the Pacific, left turn around the Palos Verdes Peninsula, back to SLI, and a 340 heading out of SLA for another visual approach.

We're on final again, and asked to go around, because an Air China Cargo B744 had been asked to hold short of 25L at T. At the time, there was no center taxiway between 25L and 25R. The B744 ended up crossing the hold bars, so around we went a second time. Back out to the ocean, left turn to 220, back to 080 around the PV, direct to SLI, then another 340 heading after SLI. At that time, the pilot indicated to ATC that we were approaching minimum fuel, so it had to be now or now.

Another visual approach, which this time we made it down.

BL.

[ChadL]

I imagine that would be rather alarming if not explained at the time. What was the explanation please?

There were tailwinds on final that day.  On the first go-around, the previous aircraft rolled long, and did not clear the runway in time.  It was still over a mile away, but still on the runway.  The second go-around was a spacing issue again from the previous arrival that did not clear in time.