It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
Originally posted by billy565
9/11.
Traffic is stopped for his motorcade so of course they won't allow commercial aircraft to fly near his plane. I understand your frustration and you should be compensated for your time and expense but I'll bet that won't happen.
Originally posted by Chett
As much as this guy travels this must have become almost routine. It really is sad that he doesn't really care how much impact his fun and games have on the life of everyone else.
Originally posted by ownbestenemy
Having intimate knowledge on this, I can tell you it is a pain. First, when Air Force One is on final (meaning they are ready to land), all airspace is cleared at a determined distance. On top of that, all ground traffic (baggage handlers, fuel trucks, airliners, etc) are halted. All runways are cleared and checked for FOD (foreign object debris) when AF1 is on its 5mi final.
It causes about 15 minutes of delay, but in the aviation world, 15 minutes is a lifetime and a ton of money. This isn't to even get into the nitty gritty; all maintenance is stopped (airliners, FAA, etc), ATC is stagnant, automobile travel around the airport is disrupted, resources are diverted to one man.....
Originally posted by ownbestenemy
reply to post by LadyGreenEyes
Well the "hours" claim can't be corroborated honestly. Such delays do have a cascade effect eventually in the day, but "hours" seems a stretch to me given each and every time AF1 landed in Vegas, it was a 15-20 minute delay with an "all-ground stop" issued.
For instance, at SFO, weather was reported as gust of 20mph (can cause delays if they are causing cross-winds, forcing a runway configuration change), steady rain (not too much a factor). Clouds and mist can slow departure rates and couple that with flight restrictions due to AF1 coming in, it snowballs. I am not condoning it or apologizing for it; just pointing out there are many factors involved here.
Originally posted by LadyGreenEyes
Originally posted by ownbestenemy
reply to post by LadyGreenEyes
Well the "hours" claim can't be corroborated honestly. Such delays do have a cascade effect eventually in the day, but "hours" seems a stretch to me given each and every time AF1 landed in Vegas, it was a 15-20 minute delay with an "all-ground stop" issued.
For instance, at SFO, weather was reported as gust of 20mph (can cause delays if they are causing cross-winds, forcing a runway configuration change), steady rain (not too much a factor). Clouds and mist can slow departure rates and couple that with flight restrictions due to AF1 coming in, it snowballs. I am not condoning it or apologizing for it; just pointing out there are many factors involved here.
Thought this thread got lost. I was there. It was about 3 hours. The airline (United) announced every once and awhile, Air Force one is in the area....still in the area..air traffic controllers still have not released any flights...and at 3 hours...air force 1 has cleared the area (or something to that effect), and we are going to begin boarding.... They were 3 or 4 flights behind schedule. There were a lot of upset people. Didn't know it was common. Not a bother to me since wasn't in a hurry but was astounded at the wait and inconvenience to others who did have firm schedules. Arrived at my destination 3 hours and 20 minutes later than was scheduled so a little over 3 hours but only about 3 could be blamed on Air Force 1.
Yes, there are, indeed, and it's possible this was exaggerated, but if it was that long, that would be a bit much. Wish there was some way to confirm or deny that timeline.
Originally posted by Dianec
Thought this thread got lost. I was there. It was about 3 hours. The airline (United) announced every once and awhile, Air Force one is in the area....still in the area..air traffic controllers still have not released any flights...and at 3 hours...air force 1 has cleared the area (or something to that effect), and we are going to begin boarding.... They were 3 or 4 flights behind schedule. There were a lot of upset people. Didn't know it was common. Not a bother to me since wasn't in a hurry but was astounded at the wait and inconvenience to others who did have firm schedules. Arrived at my destination 3 hours and 20 minutes later than was scheduled so a little over 3 hours but only about 3 could be blamed on Air Force 1.
Yes, there are, indeed, and it's possible this was exaggerated, but if it was that long, that would be a bit much. Wish there was some way to confirm or deny that timeline.