Flyboy7974 From United States of America, joined Jan 2003, 1540 posts, RR: 2 Posted (8 years 8 months 1 week 6 days 7 hours ago) and read 3222 times:
I think it's CALMSP that might be able to help with this one, but I have been watching CO 287 today and waiting for it, and then all of a sudden, it drops into Phoenix out of nowhere. Medical or maintenance because it was only on ground for 11 minutes? Interesting
Ikramerica From United States of America, joined May 2005, 21583 posts, RR: 59
Reply 5, posted (8 years 8 months 1 week 6 days ago) and read 2965 times:
Quoting Artsyman (Reply 4): Where it had problems was sitting on the ground at EWR. It sat "waiting" for takeoff for a few hours. Was originally scheduled to leave EWR at 8.40am, but did not get wheels up until 11.08am
aha. so it left the gate at 8:41, then taxied for 2:27, using too much fuel to make it against the storm winds over SoCal so they had to just land and top off.
Why so late out of EWR? Was there weather there, or some other issue?
What's funny is that if you look at the CO website, it says there was a scheduled time to arrive in PHX and it "Arrived Gate Late." That must have been news to the pax.
Of all the things to worry about... the Wookie has no pants.
Dutchjet From Netherlands, joined Oct 2000, 7864 posts, RR: 56
Reply 7, posted (8 years 8 months 1 week 5 days 14 hours ago) and read 2827 times:
Just one of those flights where everything seems to go wrong.......left the gate at the wrong moment, the weather was terrible at that time, got stuck in the ground hold, lost its slot and sequence, finally took off hours late and then, likely because of the extended time sitting on the ground at EWR, ran a bit short of fuel and as a precaution did a quick stop at PHX.....in summary, a lousy day for the pax on that particular flight. This is nothing particular to CO, sometimes one issue builds on another, and the result is a very, very late arrival.
Quoting Ikramerica (Reply 3): which I doubt is a fuel stop. Maybe a mechanical problem or medical emergency?
Quoting IAHcsr (Reply 2): Why it needed a fuel stop is unknown.... But it was Ship 720 ... And that 11 min stop cost a 3:41 hour delay into SNA ....
Quoting Dutchjet (Reply 7): left the gate at the wrong moment, the weather was terrible at that time, got stuck in the ground hold, lost its slot and sequence, finally took off hours late and then, likely because of the extended time sitting on the ground at EWR, ran a bit short of fuel and as a precaution did a quick stop at PHX.....in summary, a lousy day for the pax on that particular flight
From a friend at CO, the flight pushed on time for a normal flight but got caught up in departure delays out the New York area due to heavy restrictions on the west gate departures. Since there were no weather/restrictions on the north gate departures the plan was made to have the crew request a northbound routing but this would have mitigated a gate return for more fuel. That was not an option since the flight had pushed and the flight would have lost its taxi status time on the return. A fuel stop was planned to avoid both the gate return and another long taxi delay allowing to flight to depart.
There is a lot more behind the scenes coordination than most people realize and to think this flight was considered any less important than another is a misconception. Every flight gets the same amount of attention, if not more for SNA due to curfew and noise abatement restrictions. Regardless it is impossible to know all the details from watching flight tracking software and as you can see form the above example there were lots of people working on the fly to get this flight out of the NY area.
It's politically sensitive, but it's going to happen.