Atlanta ATC Cancels American Pilot’s Takeoff Clearance, Argument Follows

An American Airlines pilot and an air traffic controller at Hartsfield-Jackson Atlanta International Airport (ATL) got into an argument over separation between planes after takeoff clearance was issued. The American pilot wanted a little more separation due to wake turbulence concerns, but the air traffic controller didn’t like that, and it went downhill from there…

“I don’t need some pilot telling me how to do my job”

This incident happened this morning (Sunday, September 13, 2026), and involves American flight AA1428, operating from Atlanta to Philadelphia (PHL). The flight was operated by an Airbus A319 with the registration code N812AW.

So, what happened? Well, the American plane was cleared to line up and wait on runway 27R, shortly after the Delta Boeing 757 ahead of it was cleared for takeoff. Moments later, the tower controller cleared the American plane to take off. That’s when the issues started.

At that point, the American pilot requested a little more separation due to wake turbulence. So the tower controller told American to cancel their takeoff clearance and vacate the runway, and instead had a Frontier plane taxi onto the runway.

The controller then told the American pilot that “next time you need more than standard separation you need to notify us prior to taking the runway.” Initially the pilot just acknowledged that — I assume that was the first officer, because moments later, the other pilot (presumably the captain) chimed in.

He told the controller “yeah, just for your information, we do not carry your separation manuals in our flight deck, so you cleared us for takeoff behind a 757 with winds calm with 27 after his rotation, I don’t think that’s a proper separation for wake turbulence.” The controller responded “there is no wake turbulence separation, man.”

Then the American pilot said “let us fly the airplane, you guys can do your job,” and the controller gave the American pilot a phone number for a possible pilot deviation.

The Frontier plane that had been cleared for takeoff then started complimenting the air traffic controller on what a great job he was doing. The controller of course loved that, and said “I appreciate it, I’ve been doing it for 26 years, I don’t need some pilot telling me how to do my job.”

Neither side is fully right or wrong in this situation

I don’t know exactly what American’s pilot manual says about separation between an Airbus A319 and Boeing 757 when it comes to wake turbulence, though I tend to trust pilots to fly “their” plane, so if they say they need more separation, I think that’s fair. Admittedly pilots should also let air traffic controllers know in advance if there’s anything unusual they need, given the volume of traffic controllers deal with.

In other words, pilots are responsible for their planes, and air traffic controllers are responsible for the flow of traffic. Fair enough, right?

So where does that leave us with this situation? As I see it:

  • The American plane presumably needed another 20-30 seconds, so the controller was being petty and wanted to prove a point by canceling takeoff clearance, having them taxi off the runway, etc., since it didn’t save anyone time in the end
  • It’s one thing if the controller gave the pilot a number to call to discuss this further, but the controller claimed this was a possible pilot deviation, which is absurd
  • That Frontier pilot is such a brown-noser, talking about how much this controller “rocks”

This just seems like an unnecessary escalation. It’s hard to pick a side here in terms of manners — the air traffic controller was being pettier in terms of canceling takeoff clearance, while the pilot’s comment about how he should be allowed to fly the plane probably wasn’t the kindest, and rubbed the controller the wrong way.

Bottom line

An American Airlines pilot and an Atlanta air traffic controller had a disagreement over takeoff clearance. The American A319 was cleared for takeoff, but the pilot wanted a little more separation for wake turbulence. The controller claimed that wasn’t necessary, but the pilot said he was in charge of his plane. The controller didn’t like that, and it went downhill from there. But perhaps the oddest part in all of this is the Frontier pilot… oy.

What do you make of this Atlanta ATC interaction?

Conversations (65)
The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.
Comment as a member

Membership is free and takes no more information than commenting as a guest. Earn status points for good contributions, and see fewer ads as your status grows.

Type your response here.

If you'd like to participate in the discussion, please adhere to our commenting guidelines. Anyone can comment, and your email address will not be published. Register to save your unique username and earn special OMAAT reputation perks!

  1. Loading comments…
Recent Comments
The latest from the OMAAT community.

The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.

Ed Would Guest

There is no minimum time separation mandated because the A319 is Category F size and the B757 is Category E, a special category created after B757 vortices were cited in two business jet fatal crashes. If Atlanta was busy, it's possible the tower cleared the A319 before the B757 broke ground which was likely somewhere very roughly around 6,000 ft according to it's takeoff roll stats. The A319 has roughly the same takeoff roll stats. But the B757 climbs like a bat so if the A319 had a shorter takeoff roll, it's slower climb rate would likely leave it punching directly through B757 takeoff path at a very low altitude above the runway. I've been in a sudden CAT-induced 60 degree roll in a light airplane at 300 feet on final where I wasn't even sure I had the aileron to even stop the rotation so I certainly wouldn't want to meet B757 vortices 100 feet above the runway after takeoff, even if I was in a huge airplane. The rules say the pilot can refuse the tower if there's ANY question as to safety so the pilot was within his rights even if some don't think the pilot was justified because he's almost always held responsible when there's virtually any risk he might have been able to foresee. Maybe the co-pilot was new to that airport and not used to being crammed into the sequence that tightly or maybe the tower just got into the habit of prioritizing rapid departures over safety to reduce stress. They don't feel the wild wind in the tower that the pilot does when he runs into vortices turbulence and nobody should be subjected to that risk at half a wingspan above the ground.

0
‼ 0
Mike Guest

The pilot wasn't qualified to fly out of Atlanta. He needs to go back to crop dusting.

0
‼ 0
First Name Ron Guest

The PIC is the Pilot on Command of the Aircraft and is the “Final Authority” as to the operation of the aircraft.” That is the FAR - Federal Aviation Regulation. With that being said, both the Pilot and Controller over reacted. Safety must be the number one priority. It works better when all work together.

0
‼ 0
Kevin Reno Guest

It's simple, don't let ATC fly your aircraft. If in your opinion a clearance could put your aircraft in jeopardy you deny it. That's what the American pilot did. Perfectly in his rights to do that

0
‼ 0
FlyerDon Gold

The 757 generates unique wing tip vortices that are stronger and last longer than other narrow body aircraft. I don’t know if they still do, but at one time controllers were supposed to wait two minutes before clearing a smaller narrow body, like a 319, for takeoff if the previous departure was a 757. While lined up on the runway the AA pilots could see where the 757 rotated and they knew, with their early model 319, they weren’t going to out climb a 757. To me the AA captain made the right call.

1
‼ 0

Save posts to read later

Saving posts is a member feature. Become an OMAAT member to build a reading list you can come back to from any device.

Become a member
Meet Ben Schlappig, OMAAT Founder
5,883,136 Miles Traveled

43,914,800 Words Written

47,187 Posts Published