FlyerTalk Forums - View Single Post - JFK Meltdown
Thread: JFK Meltdown
View Single Post
Old Jan 7, 2018, 10:28 am
  #4  
sbm12
A FlyerTalk Posting Legend
 
Join Date: Apr 2001
Location: PSM
Posts: 69,232
Originally Posted by coloneltigh
In all likelihood, OP's inbound was delayed from the ATC/Port limiting inbound traffic for a period to try to alleviate the JFK meltdown.
That NOTAM only applied to T1/T4/T7, not T5.

The trip was operated by N592JB. That aircraft flew JFK-SEA on Friday with the return cxld. The return was a ferry flight Saturday, arriving at JFK around 10:50p. https://www.flightradar24.com/data/aircraft/n592jb

The plane did not come in from JAX and the scheduled arrival time would likely be why the airport and res staff said the flight was on-time. Maybe that was a tail swap or something else but I see no record of another aircraft being assigned to the route. Also, BGI is a 321 route and JAX is a 320 route so not sure how that would work. FWIW, the late JAX-JFK (B6 478) did cancel on Saturday night after a few hours of rolling delay.

At 11:02p EST on Saturday night they knew it would be delayed until around 4:15am. That's when the OP got the email alert. Prior to that the company had nothing filed suggesting a delay. It was a crew issue and I don't know if this was a JFK-originating crew or supposed to connect in from elsewhere.

At 1a EST the 5:45a departure was known. I don't know if JetBlue's systems didn't propagate the alerts or what. But it was known.

https://www.flightstats.com/v2/fligh.../1/6/945491372

ETA: the data in those links will expire after a couple days but I promise that's what it said on Sunday afternoon when I looked.

Last edited by sbm12; Jan 7, 2018 at 10:45 am
sbm12 is offline