Editing Lockheed Martin F-22 Raptor (section)

==Accidents==
{{for|accidents relating to the F-22's technology demonstrator|Lockheed YF-22#Accidents}}

The first F-22 crash occurred during [[takeoff]] at Nellis AFB on 20 December 2004, in which the pilot ejected safely before impact.<ref>Mount, Mike. [http://edition.cnn.com/2004/US/12/22/fighter.crash/index.html "Nevada crash grounds F-22 fighters."] {{Webarchive|url=https://web.archive.org/web/20120124221647/http://edition.cnn.com/2004/US/12/22/fighter.crash/index.html |date=24 January 2012}} CNN, 22 December 2004. Retrieved 28 August 2011.</ref> The investigation revealed that a brief interruption in power during an engine shutdown prior to flight caused a flight-control system malfunction;<ref>{{cite report |url=http://usaf.aib.law.af.mil/ExecSum2005/F-22A_20Dec04.pdf |title=USAF AIB Report Executive Summary on 20 December 2004 F-22A mishap |archive-url=https://web.archive.org/web/20130216174551/http://usaf.aib.law.af.mil/ExecSum2005/F-22A_20Dec04.pdf |archive-date=16 February 2013}}</ref> consequently the aircraft design was corrected to avoid the problem. Following a brief grounding, F-22 operations resumed after a review.<ref>{{cite press release |url=https://www.af.mil/News/Article-Display/Article/135290/raptors-cleared-to-fly-again/ |title=Raptors cleared to fly again |publisher=U.S. Air Force |date=6 January 2005 |url-status=live |archive-url=https://web.archive.org/web/20150518103749/http://www.af.mil/News/ArticleDisplay/tabid/223/Article/135290/raptors-cleared-to-fly-again.aspx |archive-date=18 May 2015}}</ref>

On 25 March 2009, an EMD F-22 crashed {{convert|35|mi|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, or [[g-LOC]], then ejected when he found himself too low to recover. Cooley was killed during ejection by blunt-force [[Blunt trauma|trauma]] from windblast due to the aircraft's speed. The investigation found no design issues.<ref>{{cite news |title=F-22 Crash Linked To G-Forces |newspaper=The Washington Post |date=5 August 2009 |page=2}}</ref><ref>{{cite report |url=http://www.airforcemag.com/SiteCollectionDocuments/Reports/2009/July%202009/Day31/F-22_AIB_073109.pdf |title=USAF AIB Report on 25 March 2009 F-22A mishap |archive-url=https://web.archive.org/web/20190331150934/http://www.airforcemag.com/SiteCollectionDocuments/Reports/2009/July%25202009/Day31/F-22_AIB_073109.pdf |archive-date=31 March 2019 |access-date=31 May 2014}}</ref>

On 16 November 2010, an F-22 from Elmendorf AFB crashed, killing the pilot, Captain Jeffrey Haney. F-22s were restricted to flying below 25,000 feet, then grounded during the investigation.<ref>Fontaine, Scott and Dave Majumdar. [https://archive.today/20120730001228/http://www.airforcetimes.com/news/2011/05/airforce-grounds-entire-f22-fleet-050511w/ "Air Force grounds entire F-22 fleet."] ''[[Military Times]]'', 5 May 2011.</ref> The crash was attributed to a bleed air system malfunction after an engine overheat condition was detected, shutting down the [[Environmental control system (aircraft)|Environmental Control System]] (ECS) and OBOGS. The accident review board ruled Haney was to blame, as he did not react properly to engage the [[emergency oxygen system]].<ref>{{cite report |url=http://www.pacaf.af.mil/shared/media/document/AFD-131024-066.pdf |title=USAF AIB Report on 16 November 2010 F-22A mishap |archive-url=https://web.archive.org/web/20140714225512/http://www.pacaf.af.mil/shared/media/document/AFD-131024-066.pdf |archive-date=14 July 2014 |access-date=1 July 2014}}</ref> Haney's widow sued Lockheed Martin, claiming equipment defects, and later reached a settlement.<ref>{{cite web |author=Majumdar, Dave |url=http://www.flightglobal.com/news/articles/settlement-reached-in-haney-f-22-crash-lawsuit-375445/ |title=Settlement reached in Haney F-22 crash lawsuit |work=FlightGlobal |date=13 August 2012 |access-date=30 October 2013 |archive-url=https://web.archive.org/web/20131024033808/http://www.flightglobal.com/news/articles/settlement-reached-in-haney-f-22-crash-lawsuit-375445/ |archive-date=24 October 2013 |url-status=live}}</ref><ref name=physio/> After the ruling, the emergency oxygen system engagement handle was redesigned and the entire system was eventually replaced by an automatic backup.<ref>{{cite news|title=Fatal crash leads to change in F-22's backup oxygen system|work=Los Angeles Times|page=B1|date=20 March 2012|access-date=13 November 2020|url=https://newspapers.com/clip/63154626/|via=[[Newspapers.com]]|archive-date=13 March 2023|archive-url=https://web.archive.org/web/20230313155359/https://www.newspapers.com/clip/63154626/f-22-crash/|url-status=live}}</ref><ref>{{cite web|title=Installation of backup oxygen system in F-22 combat fleet continues|url=https://www.af.mil/News/Article-Display/Article/478362/installation-of-backup-oxygen-system-in-f-22-combat-fleet-continues/|date=10 April 2014|work=U.S. Air Force|access-date=13 March 2023|archive-date=8 August 2022|archive-url=https://web.archive.org/web/20220808203116/https://www.af.mil/News/Article-Display/Article/478362/installation-of-backup-oxygen-system-in-f-22-combat-fleet-continues/|url-status=live}}</ref> On 11 February 2013, the DoD's [[Office of the Inspector General|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.<ref>{{cite report |url=http://www.dodig.mil/pubs/report_summary.cfm?id=5025 |title=DoD IG report on 16 November 2010 F-22A mishap AIB report |archive-url=https://web.archive.org/web/20130215181008/http://www.dodig.mil/pubs/report_summary.cfm?id=5025 |archive-date=15 February 2013 |access-date=11 February 2013}}</ref>

On 15 November 2012, an F-22 crashed to the east of [[Tyndall AFB]] during a training mission. The pilot ejected safely and no injuries were reported on the ground.<ref>{{Cite news|url=https://www.tyndall.af.mil/News/story/id/123326594/ |title=Safety paramount as F-22 investigation continues (press release) |work=U.S. Air Force |date=16 November 2012 |access-date=16 November 2013 |url-status=live |archive-url=https://web.archive.org/web/20131215042225/http://www.tyndall.af.mil/news/story.asp?id=123326594 |archive-date=15 December 2013}}</ref> The investigation determined that a "chafed" electrical wire ignited the fluid in a hydraulic line, causing a fire that damaged the flight controls.<ref>{{cite web |author=Everstine, Brian |url=http://www.airforcetimes.com/article/20130809/NEWS04/308090025/Air-Force-Faulty-wire-brought-down-F-22 |archive-url=https://archive.today/20130810073211/http://www.airforcetimes.com/article/20130809/NEWS04/308090025/Air-Force-Faulty-wire-brought-down-F-22 |archive-date=10 August 2013 |title=Air Force: Faulty wire brought down F-22 |work=Air Force Times |date=9 August 2013 |access-date=16 August 2013}}</ref>

On 15 May 2020, an F-22 from [[Eglin Air Force Base]] crashed during a routine training mission shortly after takeoff; the pilot ejected safely. The cause of the crash was attributed to a maintenance error after an aircraft wash resulting in faulty air data sensor readings.<ref>{{cite web|title=A $201M maintenance error: Air Force releases cause of F-22 crash at Eglin AFB in 2020|url=https://www.nwfdailynews.com/story/news/local/2021/07/28/air-force-maintenance-error-caused-2020-f-22-crash-at-eglin-afb/5399988001/|last=Thompson|first=Jim|website=Northwest Florida Daily News Herald|date=28 July 2021|access-date=31 July 2021|archive-date=31 July 2021|archive-url=https://web.archive.org/web/20210731143616/https://www.nwfdailynews.com/story/news/local/2021/07/28/air-force-maintenance-error-caused-2020-f-22-crash-at-eglin-afb/5399988001/|url-status=live}}</ref>