Originally Posted by
eng3
Well, if you know there will be a delay causing a misconnect, you can take action while still in the air. Ofcourse without knowing the length of the delay, it's tough. I guess it depends on the info.
For example, yesterday evening, we were waiting for crew. Every 30min, they'd delay the flight by 30min. A few I were talking to had not eaten anything all day. I told them, they were probably safe to goto a restaurant even if it took an hour but they didn't want to risk it. They ended up getting fast food crap and our flight was delayed another 3hrs after that. All this was with zero announcements, just refreshing the app. Screens were broken and the txt were coming through really late. I've had similar situations where the agent will admit that they have no idea on the time but it will be over an hour and encouraged people to go get something to eat.
For me, knowing is better than not knowing.
I agree knowing is better, but I revert back to my days working for a defense contractor - there is "nice to know" info and "need to know" info. Given the general immaturity of the flying public, I'm ok with keeping to the "need to know" being communicated.
As for 30 minute rolling delays, stuff happens, and I never, ever count on an airport/plane as a place for good nutritional choices.