For obvious reasons, there has been a lot of talk lately about aviation safety. With the way that information is shared nowadays, there’s also a lot of misinformation, and perhaps alarm in areas where there shouldn’t be. Along those lines, a reader asked me a question that I figure might be worth addressing at large (to be clear, there’s no misinformation in his question, but it covers the same topic).
In this post:
What causes airplane go arounds?
Reader Will asked me the following question, regarding a go around (often referred to as an aborted landing, missed approach, or rejected landing) that he experienced on a flight today:
Today, I had an interesting experience on flight SK502 from London Heathrow (LHR) to Copenhagen (CPH), and I wanted to reach out with a question.
During our descent to CPH, there was a sudden and noticeable increase in altitude, and the cabin crew announced that our landing had been aborted. A few minutes later, the captain explained that the landing was aborted due to a slow-moving aircraft in front of us. We went around and landed without incident approximately 10 minutes later.
I’ve heard of aborted landings due to weather conditions, but this is the first time I have encountered an aborted landing due to another aircraft. Have you ever experienced anything similar on your travels? I’d love to hear your thoughts or any insights you might have on this situation.
Looking at Will’s specific flight, it appears that the aircraft descended down to just under 1,000 feet, and then terminated its approach, while still a few miles from the airport. As a matter of fact, the plane made its turn to resequence before even passing the airport.

What Will experienced here is extremely common. Generally speaking, go arounds happen for one of several reasons.
As Will mentions, sometimes go arounds happen due to weather or other flying conditions. It could be that there’s sudden wind shear on final approach, or that that visibility is below minimums, or that the aircraft is too high or too fast, etc. There’s a human element to aviation, and landing a plane is rather complex, so sometimes more than one try is needed.
But I’d guess that aircraft spacing and other traffic is at least as common of a reason for go arounds. Now, of course that sounds super scary, with recent incidents like what we saw with a Southwest 737 at Chicago Midway (MDW). Yes, that’s an extreme example, and that was a close call, and the Southwest pilots did a stellar job.
However, in a vast majority of situations, go arounds are totally routine and less dramatic. Why could traffic cause go arounds? Well, many airports are basically at capacity, and during peak periods, they have one plane landing after another. There’s often close to minimum spacing between aircraft, with little margin for things to not go exactly as planned.
So it could be that one plane is coming in a bit slow, while the plane behind it is coming in fast. Or it could be that a plane just takes several seconds too long to clear the runway, because it doesn’t exit at a certain taxiway. Or in some cases, runways are used for both takeoffs and landings, so it could be that a plane is a bit slot to start its takeoff roll.
While air traffic controllers do an incredible job giving pilots instructions that minimize disruptions, there’s still a human element to it. Pilots won’t always follow instructions the second that they’re given, and sometimes things get tricky, like when you have a turboprop in front of a heavy jet (with the aircraft having very different approach and landing speeds).
How common are airplane go arounds?
If you’ve ever wondered how common go arounds are, there’s some data on that. Now, I haven’t seen any reputable data about global go arounds, but the Federal Aviation Administration (FAA) has published data on go around numbers at 30 of the country’s busiest airports.
At those airports, 0.39% of flight arrivals experience go arounds, so that’s roughly one in every 250 flights. Even among those 30 airports, there’s quite a bit of variability — Washington (DCA) has a rate of over 0.8%, while Los Angeles (LAX) has a rate of just over 0.2%. I’d expect the global average to be a bit lower than 0.39%, since this rate is for the most congested airports in the country.
Since Will was asking about my travels, I’d say that as a passenger, I experience a go around an average of around once per year. Most commonly, they’re for the reason Will experienced (due to traffic), but I’ve also had some rough ones in bad weather.
Probably my favorite one goes back over a decade, where I was flying on a British Airways Boeing 747 on a windy day, seated in the nose. You really feel all movement in the nose of the 747, and there’s nothing quite like the (near) full power of the queen of the skies, especially when you aren’t expecting it.
My most recent go around was maybe six months ago, on an American flight from Tampa (TPA) to Miami (MIA). It was very similar to Will’s — we were at around 1,000 feet, and it was due to not enough spacing.
On social media, I’ve increasingly seen some people try to suggest that go arounds reflect a lack of safety culture. Quite to the contrary, go arounds are part of a healthy safety culture, and a go around represents pilots erring on the side of caution and following best practices, rather than just rushing to get on the ground.
Bottom line
Aircraft go arounds are a pretty common occurrence, even though I know that they can rattle some travelers. At the busiest airports in the country, they happen around 0.4% of the time, based on the latest data I’ve seen.
Go arounds typically happen either due to weather or landing conditions, or due to traffic or spacing. Go arounds are a standard procedure that pilots are trained for, so there’s nothing to be worried about. Of course in the Southwest situation above, that absolutely would’ve been something to be worried about, but that represents a tiny minority of go arounds.
If you’ve experienced a go around, what was your experience like?
It is about time to use AI in airport traffic control for landing, take off and on the ground aircraft movements .
The last thing anyone wants after a bumpy, skittish approach in dirty weather is to go around and live it all again, but better safe than sorry!
I’ve had two. First one in Johannesburg in a thunderstorm, the second in Cork where the wind was howling and we came in so sideways, I was looking directly down the runway from my window seat. Not fun.
Many moons ago at JFK. Just about to touch down like the Southwest flight and then we did a go around. Pilot stated there was a plane on the runway. Rather apologetic about the extra 20 minutes it would take just to be able to try to land again.
I guess I've been lucky, but only experienced 2 of them in all of my flying. One was due to horrible weather at JFK while coming in on Swiss. Worst turbulence I've ever experienced, and then we diverted to Montreal. The other was on VA into Melbourne - pilots never made an announcement as to why and the lady next to me joked that it must be a new pilot who was embarrassed with his initial performance.
There’s quite a lot happening up-front during a go-around in congested airspace, so I don’t expect an explanation. I can totally understand why some pax might find it alarming, though.
I was recently on an EK A380 into DXB that had to go around because the KLM that just landed didn’t clear out of the runway quickly enough. Such go arounds are pretty common.
They're particularly frustrating if you have airport pickups down to a science.
Landing at GVA on U2 a few years ago we went round from just above the runway, and the announcement a few minutes later from "This is Captain..." said "I thought we were too far down the runway for it to be safe to land".
I *think* that was a different voice from the earlier announcements (which would be from Pilot Flying?)
Would it be a reasonable deduction that the FO was flying and the Captain took control at the moment of Go Around?
It would typically be the Pilot Monitoring who makes announcements, while the Pilot Flying, well... flies. If the captain's voice was not the voice you heard through most of the flight, then it's most likely that the captain was Pilot Flying.
If someone does plane spotting, they will see hundreds of landings in a row without a go around.
I have not had a go around that I noticed for many years. I never or almost never sleep through a landing. The last I can remember was about 15 years ago when on a Delta flight at a hub.
I was aboard an earlier flight of the United 767 that rammed into the WTC on 9/11...
If someone does plane spotting, they will see hundreds of landings in a row without a go around.
I have not had a go around that I noticed for many years. I never or almost never sleep through a landing. The last I can remember was about 15 years ago when on a Delta flight at a hub.
I was aboard an earlier flight of the United 767 that rammed into the WTC on 9/11 except it was about a year before. I have also been on flights that had to land before the destination for refueling.
I don’t know how your comment about the United 767 has anything to do with the topic being discussed. I also think using the word “rammed” to describe what happened that day is callous and inappropriate.
An interesting one… a delta CRJ-900 from LGA to YUL on Feb 17th approx one hour prior to the same aircraft flipping upside down at YYZ.
Weather in YUL was abysmally snowy and gusty (like YYZ) but no explanation was given to us at all. Landed without incident but certainly not a smooth one. Found out what happened at YYZ while in the cab home.
They're not all that common but do happen. I fly 2-4 flights a week and maybe once a year on average experience a go around. Most of the time it's due to a/c spacing issues. Many years ago my plane had a good around because of a deer running on the runway at MCI.
So I guess my single go-around in over 400 flights is par for the course. That one was in a DC3 though, behind an apparently very slow Fokker 50. I didn't mind the extra 10 minutes of tooling around in the Dak!
Last was CR7 at PHX several months ago. We were wobbly and running out of runway, probably about 50ft up. A lot of the passengers were terrified, and while I knew what was going on, the captain didn’t make any sort of announcement, which I found to be very unprofessional.
Lots of missed connections with the extra 20 minutes to land and the 25 minute MCT at PHX.
Aviate, navigate THEN communicate, I understand it can be distressing as a passenger but the flight crew were doing the right thing.
Even after the intiial go-around manouver there can be a lot happening on the flight deck with 'cleaning up the aircraft' for PF and a fair bit of additional radio work for PM.
CB
The pilots' first priority is to fly the plane safely. Pilots learn to "aviate, navigate, communicate", in that order - and communicate means communicate with ground control. The very last priority is communicating with passengers.
My one go-round was in a small regional jet landing somewhere in Europe, probably Munich. The pilots didn't say anything until many minutes afterwards, presumably because they were busy with whatever they needed to do as a consequence of the...
The pilots' first priority is to fly the plane safely. Pilots learn to "aviate, navigate, communicate", in that order - and communicate means communicate with ground control. The very last priority is communicating with passengers.
My one go-round was in a small regional jet landing somewhere in Europe, probably Munich. The pilots didn't say anything until many minutes afterwards, presumably because they were busy with whatever they needed to do as a consequence of the change in course. Finally they explained that the plane in front of us was moving too slowly and therefore we were asked to go round.