Radio communications on airliners are typically the ultimate in cool, calm and collected. Transitions between flight phases, the intricacies of the operation, and the pressure to do it all right, are just a few of the factors that add up to high-stress environments for pilots and air traffic controllers. Which makes the events captured in the audio of the Newark approach frequency from April 22, 2026, so extraordinary, and in the end, so ironic.

A United Boeing 787-10, en route from Brussels to Newark Liberty International Airport after a transatlantic flight, was on final approach to Newark approach frequency when the pilot thought the approach controller was taking too long. The ensuing exchange was a lesson in how not to work on a shared frequency of the aviation world, and was immediately followed by a twist in that story that was both ironic and unexpected by those listening in.

A 787 on Final: A Controller with a Lot to Do and a Captain with a Short Fuse

United 787-10 was approaching Newark, and was being vectored for an ILS approach to runway 22L. As the flight passed over Teterboro Airport and was about to turn towards Newark, the captain became impatient for the approach controller to give the intercept heading.

Instead of waiting the several seconds it would take, the captain called out:

"United 995."

The controller immediately replied, "Go ahead". The captain's reply:

"Do you wanna give me that intercept?"

The busy controller maintained his cool and replied that he was doing his job and he just needed another five seconds. A reasonable enough answer. Any pilot would have accepted this and waited.
Instead, the captain immediately ratcheted things up:

"All right, I could have a phone number as well if possible."

Translation: I want to contact your boss and make a complaint. On the same frequency. On a shared frequency, so that all the other planes can hear.

The controller then promptly cleared the ILS approach, as agreed. As the captain repeated it back, he couldn't resist saying: "I thought you know what you are doing?"

The final dig, with an added splash of contempt, was the captain's parting shot, delivered over a shared air radio channel. It didn't land the way he intended.

What the Controller Was (Almost Certainly) Doing

Here's what makes the captain's frustration even more unwarranted now. At the time the captain complained about the five-second delay, the approach controller was also handling a Teterboro departure that was underneath the United 787's approach.

Teterboro is a general aviation airport almost directly beneath the Newark approach. A departure from Teterboro and a heavy Boeing 787 sequencing for final approach requires a high degree of coordination. The five-second delay that annoyed the captain wasn't due to lack of attention, it was due to the controller having to manage multiple aircraft in close proximity and having to do both safely.

The captain didn't know what the controller was doing at that time. And that's why the correct response to a minor delay is patience, not irony.

The Paradox: First Officer's Radio Work

Now, the twists and turns begin. Once the United 787 landed and switched to the tower frequency to receive taxi instructions, the radio voice changed and the first officer, who is in charge of radio communications during the taxi stage while the captain was on the ground with the aircraft.

The tower controller issued a simple taxi direction: to taxi southbound on taxiways P and AA, and then hold short of runway 22R while they waited for the gate to clear. Basic stuff. The sort of thing that you read back hundreds of times a shift at any large airport.

What ensued was one of the more cringe-worthy radio exchanges you'll hear at a major U.S. airport:

The first officer didn't include all the information in his first read-back. The controller asked for confirmation, and asked for the hold-short point. The first officer replied "affirmative" which is not a read-back. The controller, now specifically asking for the read-back, attempted again. Another incomplete response. Again the controller patiently corrected the read-back. Another incomplete attempt. This went on for nine transmissions before a successful, full read-back was finally achieved.

It's worth noting the calm of the tower controller in this communication. His voice didn't rise, nor did his patience, as he step-by-step dealt with each transmission until the instruction was acknowledged as correct. He did what was expected - and it is a good thing.

The read-back isn't a rule. It's there because there are dire consequences to misinterpreted taxi instructions on or near active runways. Controllers require full and accurate read-backs precisely to avoid the sort of communication breakdown that has resulted in runway incursions and more.

The Behaviors that Made this So Difficult to Listen To

I'd like to name a couple of issues with how this crew handled the initial and final phases of the arrival:

• Pressuring for an intercept heading before the requested five second delay a minor delay with a legitimate reason that did not need to be resolved
• Going straight to asking for the supervisor's phone number for a minor interaction on the same frequency in front of other aircraft
• Teasing the controller following the clearance an unnecessary (and unprofessional) parting shot
• Not providing a correct read-back after repeated requests by the tower controller a fundamental skill that should be straightforward for pilots

The captain then, it is claimed, continued to request a supervisor's phone number from the tower controller after landing presumably to follow up on his complaint about the approach controller. In light of the events on the tower frequency, it's self-evident what irony that request contains.

What This Exchange Says

Radio incidents in aviation are interesting for more than their entertainment value and yes, this one is entertaining (and cringe-worthy). The airspace around a large airport such as Newark is a public good in which brevity, clarity and professionalism impact safety.

This trouble with a captain who antagonises the controllers and a first officer who has difficulty stringing together a good read-back are two different issues. The captain's behaviour suggests an attitude that probably developed over time. The first officer's radio communications would indicate either a lack of training or a degree of fatigue or distraction which led to poor communications under little stress.

The approach controller who responded with calm "I know what I'm doing, just give me about five more seconds" and the tower controller who handled a total of nine transmissions without losing his cool both must be commended for their professionalism in dealing with an unnecessarily difficult pilot crew.

The Bottom Line

On April 22 United Airlines 787 captain was over-the-top with the approach controller for a short, completely justified delay, asking sarcastically for a supervisor's phone number and mockingly questioning the controller's ability to do his job. A few minutes after this encounter with the approach controller, his first officer required nine radio calls to correctly read back a simple taxi sequence. The tower controller who handled that crew through the taxi instructions with patience and efficiency epitomised the professionalism that the captain had just denied was present in the approach controller. Sometimes the universe has a sense of timing.