Sorry,
craz, but as noted in all of my posts, I am talking about
last night's CO 36, which didn't leave until
this morning.
That's the 2008-08-11 iteration of the flight,
not the 2008-08-12 one you keep talking about. And both FlyteComm and Continental.com say it didn't leave 'til this morning (and didn't arrive 'til this evening, when it should have arrived this morning).
Yes, today's is relatively on-time. And most times I've taken it, it's been relatively on-time. But if you're going to make dismissive remarks about other users here, the data they present, or the sources of that data, please read for comprehension first.
I'd still be interested in any more in-depth information on what happened the night of the 11th in Newark that resulted in CO 36 not leaving until the morning of the 12th. My wild guess is bad weather leading to ground stop, leading to crew timeouts, or something like that.