Originally Posted by
Orion316
Let's get the facts sraight. Just because it was on the ground for 45 min, doesn't mean the delay was 45 min. And even yesterday it was not.
No, but if we're talking about just how much of a delay the tech stop itself adds, we can probably come up with a rough 45 minute average. This itself is pretty high, given only a need to refuel on the ground. You can account for delays as far as climb and descent, as well, but they are overall negligible when you also factor in that the flight could be subjected to holding, ATC redirection, any number of otherwise uncontrollable factors.
As someone else mentioned, it's all about managing expectations. But if it's more or less common knowledge that a stop will be required whether due to short runways & the heat in the summer or strong headwinds in the winter, this should be noted. Also, you can look at the data starting at september and get a 6% rate, or look at it in december and get a 20% rate. Maybe the winter schedule should include a tech stop.
At 20%? This becomes a matter of subjectivity. I don't think even a percentage as high as 20 is "frequent." Your mileage may vary, as the case may be.
When my flight is BUR-JFK and it came in from JFK, I can see why weather at JFK should be an issue, but weather at SLC is irrelevant as far as I'm concerned. Otherwise, it's like saying just because it's snowing heavily somewhere in the US, I can delay your flight & blame it on the weather.
Then I'm not sure you understand the concept of air traffic. Weather at SLC may be irrelevant to you right now, but when you're the one in the air going through it, opinions change. If it's snowing heavily in your flight path, you'd care.