• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

What the Hell happened here?

Sounds like it could have been an honest mistake on the part of the pilot. The AF handles the landings, why didn't they warn them off?
 
Meh, so what? A small mistake. I don't know how it is to be a pilot, but he misjudged by a couple miles or whatever. Why the big fuss?

I've had to wait 8 hours in an airport because a flight out of San Jose was delayed by two hours because of the "nose cone," and when we arrived in Chicago, our flight had already left and Continental refused to reschedule our tickets saying it wasn't their fault.

So, 8 hours of arguing, they finally give us an option of either taking GreyHound to Ohio and arriving at some insane time like 3AM in the morning or staying overnight at some run-down motel (Cross-Country Inn, what a POS place). We chose the motel route and then hopped on a 1 hour flight the next day to Dayton.

Worst flying experience ever.
 
Originally posted by: HappyPuppy
Sounds like it could have been an honest mistake on the part of the pilot. The AF handles the landings, why didn't they warn them off?
Click to expand...

As ex-Air Force I have seen it happen a few times before.
 
my guess is that they mis-tuned the nav radio to the AF base's localizer 110.3. the one they wanted was 109.3 for Rapid City so it could have been a simple mistake. the airports are only a few miles apart, with similar runways in the same direction. still the pilots should have identified that they were tracking the correct nav aid.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top