Here is the official Air Force explanation:

Air Force: Fogging Caused F-16 OSH Overrun

The F-16 that ran off the end of Runway 36 at Wittman Regional Airport after landing during the 2011 EAA Oshkosh AirVenture gathering did so because the cockpit got foggy, according to the Air Force. The Air Force accident investigation board report says that the jet's environmental control system caused extreme fogging that completely obscured the pilot's vision. Contributing factors were a fast touchdown speed and inadequate aerobraking by the pilot, which increased the landing distance.

The jet and pilot were assigned to the 100th Fighter Squadron, 187th Fighter Wing at Dannelly Field, Ala. The pilot landed in the number-two position of a two-ship formation at midday as part of a training flight. According to Air Combat Command, the pilot "applied the defog procedure" without success during landing and was therefore deprived of "necessary visual clues." The F-16 departed the paved surface of the runway and came to rest roughly 300 feet beyond the runway's end. The pilot was not injured in the incident. Damage to the aircraft has been estimated at $5.4 million.

IMO
Applied the defog, didn't work. OK, lets just land blind at the busiest fricking airport in the country. No need to declare an emergency or tell the tower your landing blind and maybe you should move people out of harms way. He is so darn lucky he didn't hit anyone because he didn't have visual clues.

Good day

OregonMaule wrote:
IMO
Applied the defog, didn't work. OK, lets just land blind at the busiest fricking airport in the country. No need to declare an emergency or tell the tower your landing blind and maybe you should move people out of harms way. He is so darn lucky he didn't hit anyone because he didn't have visual clues.

Good day

So the plane is on the ground, or nearly so, he can't see, there's another F16 in front of him on the runway and lots of planes nearby and you want him to just hammer it and attempt a takeoff? That would have been a dumbass move.

Surely there is a go-around procedure while in formation and he had radios to talk to the pilot at his 12.

'Greg

Remember guys, what gets released to the public from the "Legal" Accident Investigation Board (AIB) is not the whole story. The complete story is the Safety Investigation Board (SIB)results. The SIB results are not releasable to the public. I have read both reports and the AIB is going down the right path, but doesn't tell the whole story. Yes, mistakes were made. If you have never made a mistake or screwed up in your aviation career, then fell free to throw stones. If not, then lets be thankful no one was hurt and know that others have learned from this incident.

Jon "Jughead" Counsell
USAF, F-15C, T-38C, Global Express,T-6II, T-34C, C-170B

Southern Boy wrote:O-2, I agree. He may well have had a lapse in judgement. I just don't know.


I completely agree that skills in the F16 don't necessarily translate to other planes. I've done enough T 6 transition training to know that...but, OTOH, this pilot was a full time F16 guy. He had demonstrated good skill and judgement, in that plane many times before. Some of our group at OSH had talked with him the day after the accident, and he reported a massive internal systems failure. So, I'm willing to let the facts come out. If that makes me a "nut job wacko" here, then I perhaps misjudged the general attitude and demeanor here. He may have indeed simply screwed up. I don't know. However, neither do some of the people who are quick to vilify him.

So the plot thickens. I went back to the beginning and read this. We are always bitching how the media gets the facts wrong. So here we have 1st hand account of "massive internal system failure" OK, stupid me. That must be fighter jock talk for window fog.
Forgive me for having fun at his expense. I'm an asshole.

I am jealous I was never good enough to wipe the fog off the canopy for guys like him.

When my day comes and I bend my plane, I will stand straight up look you in the eye and say "I screwed the pooch" Now wheres my phone, I got to call the insurance company to fix my screw up.

I'm just pissy because my plane is down and I missed a great fly day. And I have to fork out $3000.00 for a new exhaust and Uncle Sam won't help. I need a chill pill. I shouldn't drink so much coffee.

Good day

I still like ya Rob! I used to have to wipe the fog from Jughead's canopy ...though a pilot can reach it better in the Eagle than the Viper, so I think he was just lazy or something!

I know it's 4 AM but I just checked my insurance policy and I'm covered for that.

Tadpole

If you had sat in my seat, to keep it from getting rained on, you could have more easily reached my windscreen to wipe it off. Besides, you know I don't need a clean window. I do some of my best flying asleep!

jugheadF15 wrote:I do some of my best flying asleep!

Proven fact!

No body got hurt and that's the import thing.

In the fire dept and my group of friends, when you screw up if your still alive we all mess with each other. You did what you dumb shit, stuff like that.

I was wondering, is it like that in the military? Are his buddies messing with him? I would guess yes. If it's anything like the fire dept he will probably get another nickname, like, ohhhh lets see. Mr Magoo. You old guys remember him.

OM
A new Warrant, in a company with a bunch of RLOs in SE Asia would probably stay away from the O Club for awhile, while if it was the CO - getting ready to DEROs, wouldn't probably change his schedule. Kinda like some websites.....

jugheadF15 wrote:mistakes were made.

That's a bit of an understatement. I wonder if it was the fog in the cockpit that caused the multiple burner closed patterns under the low overcast prior to the mishap landing?

Things must be different in the guard, really different. That guy should be thanking his lucky stars nobody got hurt.

Vick

You are getting warmer. The lesson that every pilot can learn from this accident is 1. Land On Speed, as early on the runway as safe to do so, especially when it is wet. 2. Aviate, Navigate, Communicate, Checklist --- In that order. Don't worry about the little things. I define little things as anything that doesn't affect the lift equation or thrust/power production. 3. Any delay in getting on the brakes, only puts more worthless runway behind you quicker.

Tadpole, This summer I will plan to stop in CO and let you clean my windshield on my -170 after we go flying.

Jughead

jugheadF15 wrote:Tadpole, This summer I will plan to stop in CO and let you clean my windshield on my -170 after we go flying.

Only if you squawk Code 3 and let me get your tapes and if you have a redball when you go to leave

Tadpole wrote:

jugheadF15 wrote:Tadpole, This summer I will plan to stop in CO and let you clean my windshield on my -170 after we go flying.

Only if you squawk Code 3 and let me get your tapes and if you have a redball when you go to leave

I'm not wild about the Code 3 part, but the Go-Pro will be mounted for you to get and the Redball may involve filling my coffee thermos and bringing me a few piddle packs.

jugheadF15 wrote:the Redball may involve filling my coffee thermos and bringing me a few piddle packs.

I don't know how to fix your coffee redball with a chalk and safety wire

jugheadF15 wrote:You are getting warmer. The lesson that every pilot can learn from this accident is 1. Land On Speed, as early on the runway as safe to do so, especially when it is wet. 2. Aviate, Navigate, Communicate, Checklist --- In that order. Don't worry about the little things. I define little things as anything that doesn't affect the lift equation or thrust/power production. 3. Any delay in getting on the brakes, only puts more worthless runway behind you quicker.

Oh I was there for the whole thing and I've read the SIB too. Without getting into privileged, sadly I don't think there are any lessons to learn from the incident - only re-learn. Episodes like this are exactly why senior leadership gets anxious these days when you talk about aerial event attendance, all it takes is one guy to hang his ass out and you've got bent metal and a PR nightmare. Hero to zero in 8000'.

Tadpole wrote:

jugheadF15 wrote:the Redball may involve filling my coffee thermos and bringing me a few piddle packs.

I don't know how to fix your coffee redball with a chalk and safety wire

Oh you guys need to quit talking dirty like that. Burson's getting all excited.

Gump