When (if ever) can ATC order an aircraft to go around?

Question

Can ATC order an aircraft to go around if there is a tailwind? Or should ATC give the pilots the current wind information and let them decide whether to go around or land?

Answer 1

In real world practice, ATC will have a specific direction for traffic to land and takeoff based on their specific criteria. Regardless of which direction ATC chooses to make the traffic flow, the PIC can choose any runway and/or direction he wishes to land. As long as both parties coordinate and agree, the aircraft can land based on the ATC’s chosen direction or the pilot’s chosen direction. ATC will usually make sure approaching aircraft are kept aware of the wind conditions so that agreement can be made. Either party can decline/deny the approach and/or landing.

An example of this is when aircraft approach our local Class D airfield VFR. They announce that they are inbound with the intention of landing. The PIC will typically then accept whichever runway ATC assigns. When an aircraft approaches IFR, they will typically know which approach and runway they wish to use. The PIC will typically have already negotiated/coordinated this with approach before being transferred to tower. If the aircraft is approaching the airport practicing IFR in VMC, they will negotiate/coordinate the approach and runway to use directly with the tower.

ATC is responsible for traffic separation in their area of jurisdiction. Although, the PIC has ultimate authority over the safety of flight of his/her aircraft, ATC has the authority on whether that flight can include ATC’s physical domain. That domain includes specifically the runway and taxiway surfaces. They can choose whether or not to give an aircraft clearance to use the runway. They can also revoke that clearance for the sake of safety. Some instances where ATC may revoke clearance and call for a go around include:

• Reversal of surface winds.
• Windshear.
• Runway incursion by another airplane.
• Runway incursion by a ground vehicle or personnel.
• Runway incursion by an animal.
• Ceilings or visibility going below acceptable runway visual range.
• Closing the airfield due to an accident or emergency.
• Inadequate spacing between aircraft.
• Landing gear issues unnoticed by the landing pilot.
• other safety issues specific to ground or airfield environment safety.

Even before an aircraft approaches the airport for landing, ATC can prohibit them from entering their airspace in its entirety. The aircraft will have to remain outside of the airspace until ATC gives them the clearance to enter.

All of this can be superseded by the PIC in the case of an actual emergency on the part of the aircraft.

Answer 2

Generally speaking, ATC must instruct an aircraft to go around whenever the controller has reason to believe the landing cannot be performed safely. In most cases, an ATC-initiated go around is caused by unexpected unavailability of the landing runway, for example if another aircraft, vehicle, person, wildlife (birds) or obstruction enters (or fails to leave in time) the runway.

The controller does not know the limitations of every specific aircraft type. Factors such as wind (crosswind, tailwind), braking action (snow/ice on runway) and ceiling/visibility is announced to the pilot, who is responsible for ensuring that the prevailing conditions are within aircraft and crew limitations. Crucially, different aircraft have vastly different limits, and they can even change from flight to flight (maybe one day the aircraft is heavily loaded and need a longer runway, for example.) The pilot knows the specific limitations, the controller does not. So a sudden change in wind should not cause the controller to instruct the aircraft to go around, rather, the controller will inform the pilot of the change, and it is up to them to determine whether or not to continue the approach.

Answer 3

Both answers are correct, just want to add my perspective here.

ATC can definitely tell an aircraft to go around. It happens all the time at busier airports. Almost 100% of the time it will be so that we as controllers maintain legal separation: the previous plane took too long on the runway, you're closing too fast on the plane ahead of you short final, there was a runway incursion, etc.

I can only think of a couple of instances where I would tell a pilot to go around for a non-traffic related reason: Landing gear appears up, aircraft appears lined up with a taxiway or incorrect runway, or aircraft is inside the final approach fix on an instrument approach and is obviously off centerline. That's about it.

All the rest of it—tailwind, wind shear, even low visibility or RVR—is not my area of expertise. You're the PIC. If you want to land with a 30-knot tailwind that's on you. If you want to land when the ceiling is showing VV001 that's on you. My job is to give you the information I have and let you decide if your skills, your aircraft's performance and configuration, and the FARs allow you to continue.