JFK Emergency: An Airline Pilot’s Perspective

Gemini Sparkle

Key Takeaways:

  • An American Airlines 767 declared an emergency while approaching JFK on May 4, 2010, after being directed to land on Runway 22L with a strong, gusty crosswind, despite the crew requesting Runway 31R which was aligned with the wind.
  • The article suggests this emergency, driven by challenging wind conditions and pilot-controller interaction, may reflect a "normal" level of stress and operational issues at JFK.
  • To provide insight into JFK operations, the article features an interview with a veteran American Airlines pilot based at the airport, discussing stresses and potential improvements in pilot/controller interactions.
See a mistake? Contact us.

The emergency declared by an American Airlines 767 crew landing at JFK on May 4, 2010, may have been unusual, but it might also represent a situation that’s closer to “normal for JFK” than an emergency call might suggest. AVweb spoke this week to a JFK-based 13-year veteran American Airlines pilot and asked him to share his insights about operations, stresses, and pilot/controller interactions at JFK, and what — if anything — can be done to improve them.

Flight 2 was an American Airlines 767 out of Los Angeles for JFK on May 4, 2010. As the airliner approached, wind was 320 at 23 gusting to 35. Once in the queue, the flight was not directed to land on 31R into the wind. Controllers instead directed the jet to land on Runway 22L with a gusty direct crosswind. When the pilot responded that “if you don’t give us to Runway 31R, we’re going to declare an emergency,” the controller’s reaction to the “emergency” and the recorded interaction that followed quickly spread through the pilot community.

To hear the original radio transmissions, click here, then click here for our conversation with Goldberg.

Sign-up for newsletters & special offers!

Get the latest stories & special offers delivered directly to your inbox

SUBSCRIBE