Originally Posted by
roknroll
The other thing that bothers me is how slow JetBlue is to update on the delays/diversions that it seems they fully know about. The past few days I've been watching the BOS-SJC flight and then the SJC-BOS redeye (BOS-SJC plane feeds the redeye). They'll update & delay the inbound, but not update the next flight. And when it does update, it's a completely unrealistic number. FlightAware will show the plane landing in SLC or DEN or somewhere to take on fuel, and also update the arrival time into SJC. The next SJC-BOS sometimes is updated to show it leaving exactly when the inbound plane is supposed to come in.
roknroll, I can assure you that bothers us on the operational side of the airline too! It's something we've been complaining about for years; I fully admit I don't understand all the specifics, but for a delay to be posted it starts as a multi-step process with rather archaic aircraft-routing software from our Sysops in Long Island City. For whatever reason all of our IT platforms (JetBlue.com, the JetBlue app, Flight Information Display Screens) are dependent on that output to show properly updated departure times, and we've been told it's very difficult to get the aircraft-tracking program to properly "flow" or cascade delays out from when they initially occur.
I hope all that sheds some light on the 'how' our delay notification process works; it's not an excuse for a poor process and is an issue I hope to see us resolve soon.