Here’s List of All F-22 Raptor Crash So far

Here's List of All F-22 Raptor Crash So far

The Lockheed Martin F-22 Raptor is a fifth-generation, single-seat, twin-engine, all-weather stealth tactical fighter aircraft.So far Thirteen F-22 Raptor are involved in crash, belly landing, engine and other issue Incident

Here is a list of All F-22 Crash So far

1) April 1992 YF-22 crash at Edwards AFB

In April 1992, the second YF-22 crashed while landing at Edwards AFB. The test pilot, Tom Morgenfeld, escaped without injury. The cause of the crash was found to be a flight control software error that failed to prevent a pilot-induced oscillation.

During a touch-and-go began to oscillate violently for eight seconds before slamming back down onto the runway and slid several thousand feet trailing a shower of sparks. A resulting fire was quickly extinguished. The pilot was fine and never had to eject, but the aircraft was never to fly again and thus ended any test flights with any YF-22.

2) April 2002 F-22 Raptor Engine issue

On 22 April  2002 an F-22A Block 10 Took-off from Dobbins AFB, Georgia on a planned cross-country ferry flight to Edwards AFB, California. Shortly after take-off and during rendezvous with two chase F-15s at 1335 hours the F-22 ingested an 8.5-pound Loon in its right engine. Surprisingly even though a lot of damage to the engine, the engine continued to operate normally. Damage to the aircraft was to the intake and the engine itself. The engine could not be repaired.

3) September 2004 raptor Airframe overstressed

28 Sep 2004 USAF F-22A Block 2 Airframe was overstressed during tests with two external tanks. G-load limiter was exceeded when control was lost after the aircraft passed through the wake of an F-16. Maximum was to be 7.3 Gs but actually climbed to 11.7 Gs. Flight control software was found to be the problem. The aircraft landed safely but never flew again.

This video of F-22 Shot Down is circulated on you tube. Video Seemed to be Fake
Video caption claims:  The Russian Ministry of Defense has reported that an S-400 battery stationed in Syria has brought down an F-22 Stealth Fighter. The Russian MOD claims that the F-22 was shot down after it was spotted on radar. The US state department denies that any US aircraft were in the area. But new video footage shows that an F-22 stealth fighter was, indeed, shot down, despite denials by the US government.

4) December 2004 F-22 crash at Nellis AFB

The first F-22 crash occurred during takeoff at Nellis AFB on 20 December 2004, in which the pilot ejected safely before impact.The investigation revealed that a brief interruption in power during an engine shutdown prior to flight caused a flight-control system malfunction; consequently, the aircraft design was corrected to avoid the problem. Following a brief grounding, F-22 operations resumed after a review

Details: Crashed on take-off from Nellis AFB, Nevada at 15.40 hours. At the moment the wheels left the ground the aircraft began a series of un-commanded roll and pitch maneuvers that quickly became more violent. The pilot ejected moments before impact and the aircraft wreckage remained within Nellis AFB grounds.

Cause of the loss came about through a unique set of circumstances. The Flight Control System was inoperative at the time of the crash. A pilot must run the Initiate Built-in Test (IBIT) on engine start in order to ensure a fully functioning Flight Control System. The pilot shut down the engine for quick maintenance work and thought Auxiliary Power Unit (APU), which was running, would provide power for the Flight Control System. Believing the APU provided power to the Flight Control System, the pilot thought another IBIT after engine restart was unnecessary and taxied for his sortie. However, the APU didn’t provide continuous power and another IBIT should have been performed. Running the IBIT would not have corrected the issue but would have warned that the Flight Control System had a serious failure. As the engine shut down there was a power interruption that caused a catastrophic failure of the Flight Control System.

5) October 2005 F22 Raptor Engine Damage

On October 20, 2005, at around 20.30 hours the aircraft was starting its engines for a night training mission. The right engine ingested a nose landing gear “remove before flight” safety pin/flag. Damage to the engine was $6.7 million but there was no damage to the rest of the aircraft. The pin was pulled out by the ground crew during engine run which is not proper procedure as it should be pulled prior to engine start. Suction pulled it out of his hand.

6) April 2006 F-22 Raptor Canopy stuck issue 

On 10 Apr 2006 F-22  Canopy stuck in the closed position trapping a pilot after a flight for several hours. Eventually, the canopy had to be cut to rescue the pilot after all other options where exhausted. The aircraft was easily repaired. In the photo, you can see Rescue team extracting the pilot of F-22A Raptor 03-4041 after cutting the canopy. The canopy was only cut as a last resort after all other options were exhausted.

April 2006 F-22 Raptor Canopy stuck issue 

7) March 2009 F-22 crashed northeast of Edwards AFB

On 25 March 2009, an EMD (Engineering, Manufacturing, and Development) F-22 crashed 35 miles (56 km) northeast of Edwards AFB during a test flight, resulting in the death of Lockheed Martin test pilot David P. Cooley. An Air Force Materiel Command investigation found that Cooley momentarily lost consciousness during a high-G maneuver, then ejected when he found himself too low to recover. Cooley was killed during ejection by blunt-force trauma from windblast due to the aircraft’s speed. The investigation found no design issues.

8) November 2010 F-22 from Elmendorf Air Force Base crashed

On 16 November 2010, an F-22 from Elmendorf Air Force Base crashed, killing the pilot, Captain Jeffrey Haney. F22s were restricted to flying below 25,000 feet, then grounded during the investigation. The crash was attributed to a bleed air system malfunction after an engine overheat condition was detected, shutting down the Environmental Control System (ECS) and OBOGS. The accident review board ruled Haney was to blame, as he did not react properly and did not engage the emergency oxygen system. Haney’s widow sued Lockheed Martin, claiming equipment defects. She later reached a settlement A design flaw with the oxygen system was described in a 2000 document. After the ruling, the engagement handle of the emergency oxygen system was redesigned; the system should engage automatically if OBOGS shuts down due to engine failure. On 11 February 2013, the DoD’s Inspector General released a report stating that the USAF had erred in blaming Haney, and that facts did not sufficiently support conclusions; the USAF stated that it stood by the ruling.

9) May 2012 F-22A Block 10 takeoff issue 

A trainee pilot failed to advance to military power during take-off and prematurely retracted the undercarriage resulting in the jet skidding along the runway causing $35 Million damage

10) November 2012 F-22 crashed to the east of Tyndall AFB

During a training mission, an F-22 crashed to the east of Tyndall AFB, on 15 November 2012. The pilot ejected safely and no injuries were reported on the ground. The investigation determined that a “chafed” electrical wire ignited the fluid in a hydraulic line, causing a fire that damaged the flight controls

November 2012 F-22 crashed to the east of Tyndall AFB

11) Jan 2015 F-22A  Break fire and gear collapse Incident

On 4 Jan 2015 USAF F-22A Block 30 Break fire and gear collapse on the starboard side while landing at Hickham AFB, Hawaii. Aircraft was eventually repaired at Honolulu.

12) April 2018,F-22 Raptor engine failure

On April 6th 2018, a F-22 Raptor of the Alaska-based 3rd Wing, flying out of Tyndall Air Force Base, experienced an engine failure but the fighter landed safely.

13) April 2018 Engine Power Loss on takeoff

On 13 April, 2018, an F-22 from the 90th Fighter Squadron in the 3rd Wing at Joint Base Elmendorf-Richardson (JBER) skidded to a stop on the runway of Fallon in Nevada, shortly after takeoff. The pilot egressed the aircraft safely. The aircraft was at NAS Fallon to participate in a training exercise with the U.S. Navy.”

Unofficial sources at the scene of the incident said that, “The slide happened on takeoff. It appears to have been a left engine flameout when the pilot throttled up to take off. By the time he realized the engine was dead, he had already been airborne for a few seconds and raised the gear. The jet bounced for around 1500 feet, and then slid for about 5000 feet. They got it off the ground and on its landing gear last night, so the runway is clear.”

April 2018 Engine Power Loss on takeoff


Check Also

Ukrainian Entrepreneur Turns Russian Su-30 Wreckage into Souvenir Keychains

Ukrainian Entrepreneur Turns Russian Su-30 Wreckage into Souvenir Keychains

Credits: Fuselage Creations / Instagram Amidst the turmoil of conflict between Ukraine and Russia, a …


  1. Manual override on all control surfaces might be a consideration. Fly-by-wire’s great, until your bird gets hacked and jacked by E.T. .

  2. David “Cools” Cooley did not die at the time of the ejection. He was still alive when he landed and crawled nearly a mile with most of his bones broken. He did not pass until the next day in the hospital. He was a truly gifted test pilot that went above and beyond what was necessary to accomplish the test mission. His loss was greatly felt by the Edwards Raptor community.

Leave a Reply

Your email address will not be published. Required fields are marked *