He sounds so bored. Even when he said he'd have to punch out, he said it with mild annoyance more than anything. Kudos to that computer though, just crashed and it was more concerned about the lack of fuel than anything.
@@microdesigns2000 until I tell it that I'm still the captain now! Then it chills out, and then SEALS show up and I haven't been able to get past that part.
RU-vid always recommends to me videos I just watched a hour earlier. One time every video in my recommendations had the red line across the bottom indication i had watched them all, all the way through. I have to click "not interested" and then "Tell Us Why" and then "I've already watched the video", dozens of times everyday. I guarantee after watching this all the way through, when I go back to recommendations, it will have this video listed. They really need to fix this.
What I love about this one is the ability to identify a professional, well trained and focused pilot by physiological cues that are involuntary and give a true representation of the pilots control of the situation, his respiratory rate and depth. It never changes from happy sunny day to time of ejection. Many emergency situations HUD videos of this era will show an immediate and pronounced onset of near hyperventilation from those, along with nearly every human alive, who are controlled by their fight or flight rather than in control of it.
@Todd Sin Ehhhh, can't agree with you there. It may be true that he does a good job of controlling his respirations, but it didn't do anything for his situational awareness or "control of the situation." He makes a left turn onto short final at over 350 knots!!!! And touches down at something like 260 knots. Both with an engine fire. Had he been capable of making a sober assessment during the first five minutes of the incident, he had ample time to realize that his approach was completely busted. I'm not claiming I would've done better, I'm just claiming that you're mistaken to say he correctly evaluated his situation. He could've and should've gotten out shortly after realizing that he had a persistent fire.
@@deltamike2154 With an engine out, he’d wouldn’t of been able to make a turn to go around at low-altitude, safely anyway. Besides that, at the end of the HUD tape the bingo fuel warning plays. Even without the fire, he wouldn’t of had much fuel to spare to go around and redo the approach. I think he was in control of the situation and he made the best choice. Sorry for the late reply, lol.
@@alisardar9149 The engine fire probably caused a loss of almost all thrust. He’d want as much speed as possible to avoid stalling before he gets to the runway. With a potentially catastrophic fire, he wouldn’t have time to turn to bleed speed or go around. More of a ‘get this down as fast as possible’ kind of thing.
@@moistman6930 all around pretty bad situation. The pilot also ignored the checklist for this situation. The checklist for a F15A shows if engine fire persists after attempting to extinguish eject. The co pilot was kind of hinting around about this but the pilot ignored. CW Lemoine did a really good break down of this video. The pilot should have pointed the jet in a safe direction and ejected once they realized the engine was still on fire.
Worked the crash recovery of this jet. I remember the local farmer was all too happy to let us in his field with our equipment. JP8 made a muddy mess around the jet. Wreckage was in the hanger on our flatbed trailer for months, waiting to get picked up.
It's actually just all the different renderings and compressions it's been through before finally being messed with on youtube. I promise you. When they extract the video from the aircrafts systems...it's perfectly clear on their screens.
Perfect training kicked in. Pilot had balls and nerves of steel! He did everything right. No way to save the F-15. I was a goner from the start. He was lucky to survive. The price of a pilots life over the cost of the jet is a no brainer. He's a trained fighter pilot. Invaluable! A single life saved, is invaluable, no matter who and/or what they are. The aircraft can be replaced. A life can not.
@@jefffreeman8905 Yep. What's really bad is that his plane crashed and smashed across the runway's perimeter road and a major state highway, thank god that crashing plane didn't kill any motorists. The decision-making here was very poor. I'll concede that he had a poor team behind him that was telling him to do stupid things, but he should've intervened. He's the Aircraft Commander, the course of action is ultimately up to him. It should've occurred to him that his brake energies would be off the charts high and he'd never get the jet stopped.
This Eagle Driver had one great wingman; I mean the point he made about the fire stagnating once he hit the runway was prescient. I didn't even think of that and I'm in my "GD" easy chair!
I was on Interstate 95 one night, and I came up on a Semi pulling a Reefer(No, not that kind of "Reefer." Lol..... A Refrigerated Trailer, is called a Reefer.) trailer. Unfortunately for him, the curbside rear hub on his trailer was glowing red hot and caught fire. The only thing keeping the fire at bay, was the airflow from traveling at 65 mph. No sooner than he would have stopped, that trailer would have gone up in flames...!!!! He had to coordinate with DOT and the upcoming county's Fire Dept., to keep that from happening. Stakes were a tad bit higher with the F-15 though, I'd say...lol.
The landing gear tire rubber problem is way more severe. When you try to brake at _that_ speed it will just overheat and you'll slide across the runway with little friction on a liquid rubber pad (as long as you have some rubber to hold the pressure inside). I understand his desire to touch down AFAP but I honestly don't know of how he envisioned stopping his fighter.
At that speed, his brakes would immediately disintegrate. Also, his tires are not rated for anything close to 260 knots, they immediately shredded upon contact with the runway. Even attempting this was the height of stupidity.
As a pilot, his checklist said to eject as he should have done according to SOP. In the F-15, right in front of you, is the checklist for engine fires and the procedure that is to be followed. The procedure lists one word for this situation and that word was EJECT! Landing at 275 kts is nuts.The stars were aligned for this very foolish but very lucky pilot. There are old pilots and bold pilots, but no old, bold pilots. I still commend and honor him for his service to our country and am very happy he is OK.
Nah his checklist told him to eject right away and he ignored it which is very dangerous because if the fire burns through he could lose control of the aircraft. And he tried to land at 300 knots lmao
@@billjamison2877 I've heard he got dismissed for improper Crew Resource Management and later on got dismissed from a commercial airline..then he passed away in a traffic accident a year or two ago.
thanks to the USAFs training he was in good shape. I would've aimed for the very end of the runway and when the plane slowed down enough id open the canopy and jump away from the burning plane before the fire gets any worse
Touched down at 260-270KTS. Of course he ran off the runway. Whiteman has a long runway (12400') but not enough for that. Maybe Edwards with 15K + the lakebed.
@@gonun69 That's nothing to do with it, never is, and never has been. Pilot has one concern at this point, saving HIS life. Ejections are risky and only a very last resort. Better to try a landing if you can.
@@gonun69 Lots of empty field = low risk. This guy disregarded boldface emergency procedure and it cost him his career. Thank god he didn't kill anybody when his plane smashed across the runway's perimeter road and a major state highway at over 200 knots. What was that about high-risk again?
i was always under the impression that you cannot eject from an aircraft at ground height, the ejection seat cannot get you from ground level to a height were parachutes can fully unfurl, so you would basically smash into the ground while attached to a heavy ejection seat... is that not true? also, i know the aircraft was on fire AND at the end of the runway but wouldnt it have been safer to ride out the crash into the dirt and then get out? or would the plane disintegrate?
I know early ejector seats were like that, however the newer ones are classified as something like "zero/zero" (i dont know what's it's actually called) but it means you can eject from zero altitude and zero speed.
His ejection decision was sound, it's a zero/zero seat. When he actuated in-frame fire extinguishers and his tail-end kept burning, he should've followed the checklist, pointed the jet toward an empty field, and ejected. Coming in at 260 knots is the height of stupidity. This video is used as an example of what not do. This guy and his team showed a lot of balls but their IQs took a vacation.
There must be a reason he came in that fast, right? He sounded as though he had pretty good situational awareness. His wingman did suggest side slipping with no reply.
I wondered that myself not sure possibly damage to the Hydraulics maybe he couldn't get the flaps to work possibly he was coming in with no power maybe thought if you shut down them both the engine fire would go out I'm not sure
Coming in that fast was incredibly stupid. This ended his career. If his team kept their careers (which is anything but certain), they're now subject-matter experts on checklist-discipline after training half the Air Force on it. Now we know why the -1 pilot manual says that if you actuate in-frame fire extinguishers and the tail-end keeps burning, you point the jet somewhere safe and eject. I'm just glad that his crashing jet didn't kill anybody after crashing across the runway's perimeter road and a state highway at over 200 MPH. This video is used in training as a prime example of what not to do.
@Marius Cramer shut up with toyr technical bullshit, the f-15 lands at 130-150 knots witch is at least 240km/h, witch is FAST ASF, so I'm 100% right,you land fast or you fall
@@treelonmusk8324 youre not 100% right, the others are talking about speeds relative to the landing speeds, which the pilot exceeded by 100 knots, which is why he couldnt stop. Perhaps he was heavy because he still had too much fuel, perhaps he was in a rush to get on the ground, either way landing 'fast' doesnt often end well.
@@slickstrings your so stupid tho😂 no matter what a jet is landing fast and theres nothing you can say thays differnt, lowest landing speed for a jet is 130 knots, thays fast as fuck it's like 240km/h, not my fault all u muscle boud military guys cant read😂💕
Overtemp is a different circuit. Likely when slowing down the fire stagnated and the left engine bay began to sense the temperature rising that while in the air, the airflow was flushing out . . .
The left engine was damaged when the jet went of the end of the runway at over 150 knots. That caused the gear to collapse and damage the left engine. Notice that you do not hear the over temp message till after he goes off the end of the runway and you see that the camera was then at ground level.
@@mikeyo4406 - I remember we would worry most when the fire light went out. Did it mean the fire was out? More often than not, it meant the fire had burned through the sensor or wiring, thus the sitution was getting worse.
There went 100 million dollars. I don't blame him for ejecting. Nothing else he could do at that point. If I owned a 100 million dollar jet, I'd die trying to land and save it. Even if logically I knew it was going to crash with or without me in it, I'd find it difficult to give up on a 100 million dollar jet and eject.
People are asking why the pilot came in hot for his landing. Remember, he has an engine fire that won’t go out. His wingman asked him to confirm that his afterburner was not lit. So, it’s fair to assume that the fire was causing some degree of unwanted thrust and may have also caused damage to other systems precluding a normal landing.
-1 says shut down affect engine in question, if fire does not stop, EJECT. We use this video for what NOT to do. Should have found nearest body of water and preformed a mode 2 ejection.
Antares Yes, the air Force now uses this video in their training as everything that you should not do. fly the plane first, communicate later, he came in at over a hundred knots too fast because his wingman put him in a panic with all that talk about stagnating flame the brakes faded and were not going to stop that jet at 275 knots he could have slowed to approach speed or even slower and stayed on the runway without overshooting it, and his wingman should have shut his mouth and let him fly the plane with minimal amount of traffic needed on the radio but it was jabber jabber jabber the all the time, I live 26 miles south of white men directly in the flight path of their aircraft and I see the f-15s and BTS come in and out all the time but never seen one in distress
Mike o Actually I read the Air Force Accident Review Board report and those were the final conclusions that were made by the board. I'm addition the pilot suffered some Spinal Compression injuries but that happens in 1 out of 3 ejects so that's not surprising
Does the F-15 not have fire suppression system? I worked on 130's we have them. After pulling emergency shut down handle if fire still burned, you popped suppression bottle to smother fire with foam. Any crew chiefs with an answer?
No, most fighters don't. You just shutdown the engine for a confirmed fire and hope it stops it. The A-10 is one of the few fighters with an actual fire suppression system.
Any reason he touched down so fast? I understand he was on fire, but if he made it that far, he probably could have lasted a little longer and slowed below 250, or am I missing something?
@Rata 4U you can't know what's going throgth the man's mind but I think this type of thinking is wrong. Most military clothing has some level of fire resistance, and he has oxygen supply and is fully covered including gloves, helmet and breathing mask and boots, he should have enougth time to see that the fire is increasing rapidly and eject even from a standstill. So the only fear is an explosion, which would be more likely to happen on touchdown or earlier or in the first brake action. Also I'd like to point out he didn't do any sort of aerobrakeing which likely decresed his chances of stopping
I don’t know exactly how an F-15 works but shutting down an engine may mean he lost hydraulic pressure to the brakes. Depends how the hydraulic systems are driven.
@@nitaihat12 looked weird, when he landed, he just seemed to coast at around 200knts for a very long time after touching down, maybe burned threw hydraulics to his brakes
That would require an arrestor cable those are generally only on aircraft carriers. Not to say that there is nowhere on the ground I'm sure there's some place. But I haven't heard of any
Mike o f-15s have hooks and most AF bases have arrest or cables for damaged aircraft. Where he landed in particular, did not have a hook apparently. He requested a hook in the video tho.
You still absolutely have to coordinate with air traffic so they know you're coming and to have crash fire & rescue ready. My best guess, it sounded like a flight of 2 F15s, and when the guy declared an emergency, the pilot we watched only focused on his own plane and comms with his wingman, while the wingman (possibly flight lead) coordinated with atc as well as helped the pilot though his emergency procedures
No. Communication in an emergency situation is vital and these guys did a very good job in my opinion. The bleeder is the leader. The pilot without problems assists as necessary and will usually follow in a trail position. That’s exactly how this flight handled this particular emergency.
Aviate, navigate, communicate. Always in that order. No matter what. BUT, when nothing absolutely important is happening, especially with fighters, wingmen help troubleshoot because the pilot almost certainly can't start going through the manuals for checklists and procedures.
I have zero piloting experience but I'd guess that they wanted the plane on the ground ASAP in case the other engine dies (IIRC the F15 is more a rocket with wings than a plane). Protocol is probably such that losing control of the aircraft on the runway is better than losing it while taking more time to drop speed because it may endanger the public.
probably because having 1 engine out, if he came in on normal Vref speed, the plane would have been a bit out of control very close to the ground, so keeping his speed up on final ensured him more control of the aircraft but a longer landing roll.
He landed over speed on purpose. Normally you can put a fire out by increasing thrust through the shut down engine. You basically blast it out. When the jet stayed actively on fire he kept the speed up and landed as fast as possible so he could get out, rather than risk blowing up or having to eject over populated area and dropping the jet on homes/people. Dude made about 1000 decisions in the span of about four minutes and saved himself, anyone below him, and, surprisingly, the airplane. Major props.
Interesting how many comments here are saying "perfect training", "such a professional pilot" when the pilot actually broke protocol and tried to be a hero, and failed ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-sGwPObO0x9Q.html. Maybe this just wasn't this pilot's day.
Dude was shooting for a Distinguished Flying Cross for gallantly saving equipment, when all he accomplished was losing his wings and retiring under a cloud. Pretty lousy end to a nice career, I heard that he had several thousand hours in the jet, was very senior, and was a well-known and liked leader. Boy did he blow it that day.
Shit, I started sweating.. But, I like Viper IP, I have flown with Luke Skywalker and flew the X-Wing along with the Naboo N-1 starfighter, either one of them had no ejection seat, in space it would not do any good.. But like Viper IP, I could have landed them with no problem, because I used to pilot for Howard Hughes! Oh, by the way, damn good job of not dropping it on someone's head!
I blame the idiot that made him think of coming as as fast as possible. You have to stop sometime. I met a lot of meathead AF pilots and this squadon makes it an art form. Any student that did that would be washed out right away - even in an actual emergency.
Millions and the stupid thing can only tell you there's a problem AFTER it's happened! He even had to confirm with someone God knows how many miles away. You people depend on tech too much. But if would help if you found yourselves a good tech in the first place! Lol
Learn something from the Pakistan Airforce Pilot who landed his F-16 after fuel line exploded and took out half the engine. He managed to glide for a long time at night and managed to land safely without ejecting. US pilots do not care about the taxpayers money...Fuck it...just eject..we will get another aircraft.
His EPU would've only lasted a few minutes and the F-16 glides like a brick, your story sounds like bullshit to be honest. Also, nearly killing yourself in an attempt to save equipment on a stateside peacetime mission = STUPID.
Looks to me like a bit of a 'Fail'!! Incorrect Drills, Wingman distracting at critical moment, Not Sorting his speed out (Should be about 160 Kts NOT 260!!). Could have successfully landed, just by slowing down sooner (or at all). Wingman should have prompted him about his excessive speed. I bet they both got fried in the inquiry. But Hey, what do I know?, I only flew Vipers! (F16s)
Alternative to not flying home fast was to lose controls, and definitely lose the aircraft. His only chance at saving the aircraft is getting it down fast. He was abit too fast to stop of course, but at least the aircraft was wrecked safely, and not dropped on somebodies head as could easily have happened if he'd taken his time about things.
You heard the wingman say he feared the fire spreading rapidly as the plane slowed down on landing as the airflow through the engine decreased. Perhaps the excess landing speed was him trying to avoid that.
Sorry for all of you guys that think this pilot did good but Viper IP is spot on. The HUD indication on the left hand side is his airspeed and he touched down at roughly 260-275 knots. WAAAY too fast. I don't know the specs on the F-15 landing gear but anything beyond 300 knots is an overspeed of the F-16 landing gear. Meaning that you are not even supposed to have the landing gear extended at that high of a speed. Let alone trying to land an aircraft. Him not setting up the aircraft for a proper landing is why it was crashed not the engine fire. If you pork up an approach that badly you go around. Regardless of the IFE that was not a landing that could ever be successfully made by ANY pilot.
Cian Broderick LOL do you even know what bingo fuel is for? Trust me if he gets his bingo warning and he is AT the airbase he wants to land at with good weather (looked good on the tape) then yes you can go around. Fuel quantity wasn't his concern it was the engine on fire. Regardless of any of those side points it still is a text book example of a porked approach to an airbase.
he was worried that if he slowed down the fire would spread if he slowed down as there would be no more wind blowing on the fire and fighting it, i think he had the right idea comeing in for the landing above the speed he normally would, but he should have slowed down more at the last moment and delay the gear extention as much as possibole. baseically come in as fast as safe and slow down to the limits at the last chance
Stubbies2003 first i like thank all of these men and woman for there Service. 2nd all of you fuckers saying he should have done this or that fuck you . i love to see you ass hats in this guys situation making split decisions well trying not to die .
He took a huge risk not punching as soon as fire was confirmed. Obviously he made it back to the ground safely, but hind sight is 20/20. He's super lucky to be alive. He should have pointed the jet to some farm land and punched, he took a huge risk here. I'm just glad that he made it home safe.
Of course it isn't risk free. Neither is your jet being on fire!!!! There's a reason the checklist says if there's a fire to eject immediately!! You're saying he made the right call cause he made it back but theres no guarantee he would. He literally violated safety protocols and orders by doing what he did. I'm glad he lived and made it back. But you are 100% wrong!!! Ask any Air Force or Navy pilot!!
@@thelmaviaduct on RU-vid look up C.W. Lemoine F-15A Hud video breakdown. He was an Airforce F-16 pilot and a Navy pilot as well and he breaks down this exact video. Watch that and tell me he still made the right call. You have no clue what you're talking about
Scot Rule - F-15A, 76-0061, 110th FS out of Whiteman AFB. Crashed 9 November, 1995, pilot ejected with _minor_ injuries. Dunno where you get your info from, but you might want to find another source.
Being a Monday morning quarterback...he DID NOT NEED TO PUNCH OUT !! ! !! He clearly could have rode out the overshoot and brought the aircraft to rest. He must have been going what,
The hud is clearly showing he's 200kts when touching down, so the only "rest" he could've brought to the aircraft, and himself, would've been eternal. This is a very used accident case for formation purposes "F-15A, 76-0061, 110th FS out of Whiteman AFB. Crashed 9 November, 1995" The punchout at the end was pretty much the only optimal thing he did, while the rest of the procedure was globally bad decision making, wrong advice from airborne entourage and a limited ability do to things correctly, with a single engine, and an active fire (+reduced brake hydraulics due to the engine cutoff, and probably fire damage). Please refrain from interpreting things you don't understand, or just check some info on what you dont understand to be able to grasp what really happens. If you really thing he ejected at 50mph, you are blind as well as misinformed.
