{"id":108299,"date":"2025-08-16T21:09:00","date_gmt":"2025-08-16T15:39:00","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=108299"},"modified":"2025-08-16T16:35:17","modified_gmt":"2025-08-16T11:05:17","slug":"jetblue-pilots-aborts-landing-after-atc-distraction","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2025\/08\/16\/jetblue-pilots-aborts-landing-after-atc-distraction\/","title":{"rendered":"JetBlue Pilots Aborts Landing at New York JFK After ATC Distraction"},"content":{"rendered":"\n

NEW YORK\u2014<\/strong> JetBlue Airways (B6)<\/a> flight 1794, operated by an Airbus A320 (N760JB), from San Jose Juan Santamar\u00eda International Airport (SJO) to New York John F. Kennedy International Airport (JFK), was forced to go around on final approach due to repeated controller queries on August 9, 2025.<\/p>\n\n\n\n

The flight crew reported that constant questioning by air traffic control about visual separation from a preceding Airbus A330 distracted them and prevented timely aircraft configuration. The aircraft repositioned for another approach and landed safely.<\/p>\n\n\n\n

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

JetBlue Pilots Aborts Landing at JFK<\/h2>\n\n\n\n

On approach to runway 13L at JFK, JetBlue 1794 was following an Airbus A330-200<\/a>. The tower controller repeatedly asked if the A320 crew had the preceding aircraft in sight. Initially, the pilots confirmed they were searching but not yet visual, and later reported intermittent contact.<\/p>\n\n\n\n

As the questioning continued, the crew lost visual contact, reported distraction, and decided to execute a go-around at approximately 1,000 feet. They informed approach control that the repeated queries prevented them from properly configuring the aircraft for landing.<\/p>\n\n\n\n

ATC transmissions show the controller asking JetBlue 1794 multiple times for confirmation of visual separation. The pilots responded that they had the A330 on the transponder but not visually. Even after sighting the traffic, they reported losing visual contact again.<\/p>\n\n\n\n

When pressed for a definitive answer, the crew stated they preferred to remain under radar guidance rather than maintain visual separation. This led to a missed approach, with the crew later clarifying that the constant requests distracted them during a critical flight phase.<\/p>\n\n\n\n

After the go-around, JetBlue 1794 was vectored for an RNAV approach to runway 22L. The crew managed the descent and approach normally, and the aircraft landed without incident. Taxi instructions were issued, and the aircraft proceeded to its assigned gate.<\/p>\n\n\n\n

During post-landing communication, the pilots reiterated to ATC that the unstable approach was a result of distraction caused by repeated visual traffic queries. They emphasized that they could not complete configuration tasks by the required altitude due to the interruptions.<\/p>\n\n\n\n

\"JetBlue
Photo:N585JB JetBlue Airways 2004 Airbus A320-232 C\/N 2159 “I Go\u2026 | Flickr<\/figcaption><\/figure>\n\n\n\n

JetBlue Pilot and JFK ATC Comms<\/h2>\n\n\n\n

Here’s the detailed transcription between the JetBlue pilot and New York JFK ATC communication, as flagged by You can see ATC<\/a>:<\/p>\n\n\n\n

{ts:21}<\/strong>
Pilot (JetBlue 1794):<\/strong> Tower, 1794, ARNAV 13 left Zulu.
ATC:<\/strong> 1794, heavy A330 traffic in sight, 7 miles ahead at 2,900, runway 13 left, cleared to land.
Pilot:<\/strong> Cleared to land runway 13 left, and we’ll let you know if we see the heavy.<\/p>\n\n\n\n

{ts:38}<\/strong>
ATC:<\/strong> 1794, do you see that A330?
Pilot:<\/strong> Negative, we’re looking. We got him on the transponder, but no visual yet. 2,000 feet.<\/p>\n\n\n\n

{ts:57}<\/strong>
ATC:<\/strong>\u00a0Okay, yeah, we’re looking at JetBlue 1794, no problem.<\/p>\n\n\n\n

{ts:67}<\/strong>
ATC:<\/strong> 1794, do you see the traffic short final 13 left?
Pilot:<\/strong> Traffic now in sight.<\/p>\n\n\n\n

{ts:80}<\/strong>
ATC:<\/strong> 1794, maintain visual separation from that traffic.
Pilot:<\/strong> We’ll do our best.<\/p>\n\n\n\n

{ts:95}<\/strong>
ATC:<\/strong>\u00a0I need an answer affirmative or negative answer, JetBlue 1794, can you or not?
Pilot:<\/strong>\u00a0We’d like to stay under your radar surveillance, so negative, we’re on an approach.
ATC:<\/strong>\u00a0I don’t understand what you’re saying here.
Pilot:<\/strong>\u00a0We lost visuals. Are we clear to land on runway 13 left?<\/p>\n\n\n\n

{ts:122}<\/strong>
Pilot:<\/strong> JetBlue 1794, we’re going around.
ATC:<\/strong> JetBlue 1794, fly the public Smith at 3,200 or 4,000.<\/p>\n\n\n\n

{ts:140}<\/strong>
Pilot:<\/strong> Flying to Smith, right now going to 4,000.
ATC:<\/strong> Maintain 3,000, turn left heading 110.
Pilot:<\/strong> Going to 3,000, turning heading 110.<\/p>\n\n\n\n

{ts:162}<\/strong>
ATC:<\/strong> Contact your approach 135.9.
Pilot:<\/strong> 135.9.<\/p>\n\n\n\n

{ts:170}<\/strong>
Pilot:<\/strong> JetBlue 1794, out of 3,800 for 3,000, heading 110.
ATC (Approach):<\/strong> Expect vectors for the ARNAV X-ray to runway 22 left approach. Tango is current.<\/p>\n\n\n\n

{ts:207}<\/strong>
Pilot:<\/strong> ARNAV 22 left X-ray, picking up Tango, JetBlue 1794.
ATC:<\/strong> Turn left heading 040, contact approach on 125.7.
Pilot:<\/strong> Heading 040, switching to 125.7.<\/p>\n\n\n\n

{ts:230}<\/strong>
Pilot:<\/strong> JetBlue 1794, for 3,000 and heading 040.
ATC:<\/strong> Speed 210, expecting the X-ray 22 left.
Pilot:<\/strong> 210, will expect that.<\/p>\n\n\n\n

{ts:251}<\/strong>
ATC:<\/strong>\u00a0They need to know the reason for the go-around.
Pilot:<\/strong>\u00a0To be honest, the tower controller was very distracting. Kept asking if we had visual separation with the aircraft in front, which distracted us from flying the approach.<\/p>\n\n\n\n

{ts:261}<\/strong>
ATC:<\/strong>\u00a0Was that in the turn or mostly on the straight-in approach?
Pilot:<\/strong>\u00a0Basically, the whole profile, multiple times. Advised we were looking, got them in sight, lost them, distracted, and unable to be fully configured by 1,000 ft.<\/p>\n\n\n\n

{ts:285}<\/strong>
ATC:<\/strong> No problem, JetBlue 1794. Was it a heavy jet in front?
Pilot:<\/strong> Affirmative, A330.<\/p>\n\n\n\n

{ts:295}<\/strong>
ATC:<\/strong> Turn left 310.
Pilot:<\/strong> Left turn 310, JetBlue 1794.<\/p>\n\n\n\n

{ts:310}<\/strong>
ATC:<\/strong> Proceed direct CAPIT, cross above 2,900, cleared X-ray 22 left.
Pilot:<\/strong> Direct CAPIT, above 2,900, cleared for ARNAV 22 left.<\/p>\n\n\n\n

{ts:318}<\/strong>
ATC:<\/strong>\u00a0Speed 180 until 7-mile final.<\/p>\n\n\n\n

{ts:332}<\/strong>
ATC:<\/strong> Tower 119.1.
Pilot:<\/strong> Switching to tower.
ATC (Tower):<\/strong> JetBlue 1794 ARNAV X-ray 22 left. Runway 22 left cleared to land.
Pilot:<\/strong> Cleared to land 22 left.<\/p>\n\n\n\n

{ts:369}<\/strong>
ATC:<\/strong> Taxi Juliet, right on Zulu, hold short of taxiway Hotel.
Pilot:<\/strong> Juliet, Zulu, short Hotel 1794.<\/p>\n\n\n\n

{ts:380}<\/strong>
ATC:<\/strong>\u00a0What\u2019s your gate number?
Pilot:<\/strong>\u00a0524.
ATC:<\/strong>\u00a0Roger, when able, can you state the reason for the missed on 13 left earlier?
Pilot:<\/strong>\u00a0Told departure controller, tower controller was very distracting, contacted numerous times about traffic ahead, didn\u2019t have in sight, distracted trying to fly approach, not properly configured by the required thousand feet.<\/p>\n\n\n\n

{ts:422}<\/strong>
ATC:<\/strong> Okay, copy \u2014 unstable approach.<\/p>\n\n\n\n

\n