{"id":155858,"date":"2026-08-27T20:14:56","date_gmt":"2026-08-27T14:44:56","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=155858"},"modified":"2026-08-27T20:27:19","modified_gmt":"2026-08-27T14:57:19","slug":"emirates-a380-pilots-gets-lesson-by-jfk-atc","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2026\/08\/27\/emirates-a380-pilots-gets-lesson-by-jfk-atc\/","title":{"rendered":"Emirates A380 Pilots Gets Lesson by New York JFK ATC During Landing"},"content":{"rendered":"\n

DUBAI-<\/strong> Emirates (EK)<\/a> Airbus A380 crew operating flight EK203 from Dubai International Airport (DXB) to John F. Kennedy International Airport (JFK) faced questions from New York Approach after changing frequency without confirming their assigned speed on August 23, 2026.<\/p>\n\n\n\n

The A380 crew initially declined a 180-knot instruction and switched to Kennedy Tower, prompting Approach to make repeated calls before directing the aircraft back to the previous frequency.<\/p>\n\n\n\n

\"Emirates
Photo: JFK Spotting<\/figcaption><\/figure>\n\n\n\n

Emirates A380 Crew Draws Attention From JFK Approach<\/h2>\n\n\n\n

The incident involved Emirates Airbus A380-800<\/a>, registration A6-EVF<\/strong>, operating flight UAE8ER \/ EK203 from Dubai to New York JFK.<\/p>\n\n\n\n

During the approach to JFK, the aircraft was established for the ILS approach to Runway 22L and was instructed by the Approach controller to maintain 180 knots and then contact Kennedy Tower on 119.1.<\/p>\n\n\n\n

The crew responded with Unable before changing to the Tower frequency. The controller then attempted several times to determine what speed the aircraft could maintain.<\/p>\n\n\n\n

The recorded communications show the controller asking the crew to state their achievable speed, followed by calls asking whether they were still listening. The crew did not respond before contacting Kennedy Tower.<\/p>\n\n\n\n

ALSO READ: All Nippon Airways Pilot And New York ATC Involved in Argument<\/a><\/strong><\/p>\n\n\n\n

\"Emirates
Photo: Cl\u00e9ment Alloing<\/figcaption><\/figure>\n\n\n\n

Crew Returns to Previous Frequency<\/h2>\n\n\n\n

After establishing contact with Kennedy Tower<\/a>, the Emirates crew reported that it was reducing speed to 150 knots while about eight miles from the airport.<\/p>\n\n\n\n

The Tower controller then instructed the crew to return to the previously assigned Approach frequency, 132.4. The crew acknowledged the instruction and returned to Approach.<\/p>\n\n\n\n

Once back on frequency, the Approach controller again asked what speed the A380 could maintain. The crew reported that it was reducing to 160 knots.<\/p>\n\n\n\n

The controller explained that the crew needed to communicate its intended speed rather than switching directly to Tower. The controller also noted that the information was important for managing traffic behind the A380, particularly aircraft that might need to slow because of the A380’s size and operating characteristics.<\/p>\n\n\n\n

The exchange ended with Approach authorizing the Emirates crew to contact Kennedy Tower again on 119.1.<\/p>\n\n\n\n

\"Emirates
Photo: Cl\u00e9ment Alloing<\/figcaption><\/figure>\n\n\n\n

Emirates A380 Cleared to Land on Runway 22L<\/h2>\n\n\n\n

After returning to Tower frequency, the Emirates A380 was cleared to land on Runway 22L. The controller reported winds from 250 degrees at 10 knots.<\/p>\n\n\n\n

Following landing, the aircraft was instructed to taxi via Zulu and hold short of Runway 31L. The crew acknowledged the instruction and subsequently received clearance to cross Runway 31L and continue on Zulu.<\/p>\n\n\n\n

The Tower controller also asked the Emirates crew to contact its ramp operation to confirm gate availability. The crew was advised that Alpha 7 was available, although other traffic was present.<\/p>\n\n\n\n

ALSO READ: Air France A350 Pilots Denied Clearance by Chicago O\u2019Hare, Flight Returns to Paris<\/a><\/strong><\/p>\n\n\n\n

\"Lufthansa
Photo: photo101 | Flickr<\/figcaption><\/figure>\n\n\n\n

New York Approach Requests Contact With Emirates<\/h2>\n\n\n\n

After the aircraft landed, Kennedy Tower told the Emirates crew that New York Approach wanted them to make a telephone call and provided a number for the crew to copy.<\/p>\n\n\n\n

The communication indicates that the request followed the earlier frequency change and the failure to establish the A380’s intended speed with Approach before transferring to Tower.<\/p>\n\n\n\n

The available exchange does not state that the aircraft encountered a safety-critical situation. Instead, the communications center on coordination between the flight crew and air traffic control during the arrival.<\/p>\n\n\n\n

\"\"
Photo: Emirates<\/figcaption><\/figure>\n\n\n\n

Why Speed Coordination Matters During A380 Arrivals<\/h2>\n\n\n\n

Speed control is an important tool for air traffic controllers<\/a> when sequencing aircraft on approach. Controllers can assign speeds to maintain spacing between arriving aircraft and accommodate different aircraft performance characteristics.<\/p>\n\n\n\n

An Airbus A380 requires particular consideration because of its size and wake turbulence category. Traffic following a large aircraft may require additional spacing or speed adjustments depending on the circumstances.<\/p>\n\n\n\n

In this case, the Approach controller specifically told the Emirates crew that knowing its intended speed would allow the controller to accommodate traffic behind the A380.<\/p>\n\n\n\n

The exchange highlights the importance of confirming speed restrictions and frequency changes during a busy arrival sequence. When a flight crew cannot comply with an assigned speed, communicating the speed it can maintain allows the controller to adjust the sequence accordingly.<\/p>\n\n\n\n

\n