Accidents and incidents involving the V-22 Osprey

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
USAF CV-22 Osprey flies a test mission

The Bell Boeing V-22 Osprey is an American military tiltrotor aircraft with an accident history that has generated some controversy over its perceived safety. The aircraft was developed by Bell Helicopter and Boeing Helicopters; the companies partner in its manufacture and support.

The V-22 Osprey had 12 hull loss accidents that resulted in a total of 42 fatalities. During testing from 1991 to 2006 there were four crashes resulting in 30 fatalities.[1] Since becoming operational in 2007, the V-22 has had seven crashes including two combat-zone crashes,[2][3] and several other accidents and incidents that resulted in a total of 12 fatalities.[4]

Crashes and hull–loss accidents[edit]

June 1991[edit]

A miswired flight control system led to two minor injuries when the left nacelle struck the ground while the aircraft was hovering 15 feet (4.6 m) in the air, causing it to bounce and catch fire on 11 June 1991.[1] The pilot, Grady Wilson, suspected that he may have accidentally set the throttle lever the opposite direction to that intended, exacerbating the crash if not causing it.[5]

July 1992[edit]

On 20 July 1992, pre-production V-22 #4's right engine failed and caused the aircraft to drop into the Potomac River by Marine Corps Base Quantico with an audience of congressmen and other government officials. Flammable liquids collected in the right nacelle and led to an engine fire and subsequent failure. All seven on board were killed and the V-22 fleet was grounded for 11 months following the accident.[1][6][7] A titanium firewall now protects the composite propshaft.[8]

April 2000[edit]

A V-22 loaded with Marines, to simulate a rescue, attempted to land at Marana Northwest Regional Airport in Arizona on 8 April 2000. It descended faster than normal (over 2,000 ft/min or 10 m/s) from an unusually high altitude with a forward speed of under 45 miles per hour (39 kn; 72 km/h) when it suddenly stalled its right rotor at 245 feet (75 m), rolled over, crashed, and exploded, killing all 19 on board.[9][10]

The cause was determined to be vortex ring state (VRS), a fundamental limitation on vertical descent which is common to helicopters. At the time of the mishap, the V-22's flight operations rules restricted the Osprey to a descent rate of 800 feet per minute (4.1 m/s) at airspeeds below 40 knots (74 km/h) (restrictions typical of helicopters); the crew of the V-22 in question exceeded this operating restriction with a rate more than 100% greater.[11] Another factor that may have triggered VRS was their operating in close proximity, which is believed to be a risk factor for VRS in helicopters. Subsequent testing has shown that the V-22, and the tiltrotor in general, is less susceptible to VRS, the conditions are easily recognized by the pilots; recovery from VRS requires a more natural action by the pilot than recovery in helicopters, the altitude loss is significantly less than for helicopters, and, with sufficient altitude (2,000 ft or 610 m or more), VRS recovery is relatively easy.[1]

As a result of testing, the V-22 will have a descent envelope as large as or larger than most helicopters, further enhancing its ability to enter and depart hostile landing zones quickly and safely. The project team also dealt with the problem by adding a simultaneous warning light and voice that says "Sink Rate" when the V-22 approaches half of the VRS-vulnerable descent rate.[1]

December 2000[edit]

On 11 December 2000, a V-22 had a flight control error and crashed near Jacksonville, North Carolina, killing all four aboard. A vibration-induced chafing from an adjacent wiring bundle caused a leak in the hydraulic line which fed the primary side of the swashplate actuators to the right side rotor blade controls. The leak caused a Primary Flight Control System (PFCS) alert. A previously undiscovered error in the aircraft's control software caused it to decelerate in response to each of the pilot's eight attempts to reset the software as a result of the PFCS alert. The uncontrollable aircraft fell 1,600 feet (490 m) and crashed in a forest. The wiring harnesses and hydraulic line routing in the nacelles were subsequently modified. This caused the Marine Corps to ground its fleet of eight V-22s, the second grounding in 2000.[1][12][13]

March 2006[edit]

A MV-22B experienced an uncommanded engine acceleration while ground turning at Marine Corps Air Station New River, NC. Since the aircraft regulates power turbine speed with blade pitch, the reaction caused the aircraft to go airborne with the Torque Control Lever (TCL, or throttle) at idle. The aircraft rose 6 to 7 feet (1.8 to 2.1 m) into the air (initial estimates suggested 20 to 30 feet) and then fell to the ground causing damage to its starboard wing; the damage was valued at approximately US$7 million.[14][15] It was later found that a miswired cannon plug to one of the engine's two Full Authority Digital Engine Controls (FADEC) was the cause. The FADEC software was also modified to decrease the time needed for switching between the redundant FADECs to eliminate the possibility of a similar mishap occurring in the future.[16] The aircraft was found to be damaged beyond repair and stricken from Navy's list in July 2009.[17][18]

April 2010[edit]

The 2010 Afghanistan CV-22 Crash occurred near the city of Qalat in Zabul Province, Afghanistan.[2] Three US service members and one civilian were killed and 16 injured in the crash.[19] Initially it was unclear if the accident was caused by enemy fire.[20][21] The loaded CV-22B was at its hovering capability limit, landing at night near Qalat (altitude approx. 5,000 feet) in brownout conditions, in turbulence due to the location in a gully.[19][22] The USAF investigation ruled out brownout conditions, enemy fire, and vortex ring state as causes. The investigation found several factors that significantly contributed to the crash; these include low visibility, a poorly executed approach, loss of situational awareness, and a high descent rate.[23]

Brig. Gen. Donald Harvel, board president of the first investigation into the crash, fingered the "unidentified contrails" during the last 17 seconds of flight as indications of engine troubles.[24] Harvel has become a critic of the aircraft since his retirement and states that his retirement was placed on hold for two years in order to silence him from speaking publicly about his concerns about the aircraft's safety.[25] The actual causes of the crash may never be known because US military aircraft destroyed the wreckage and black box recorder.[26] Former USAF chief V-22 systems engineer Eric Braganca stated that the V-22's engines normally emit puffs of smoke and the data recorders showed that the engines were operating normally at that time.[27]

April 2012[edit]

On 11 April 2012, an MV-22 from the VMM-261 on USS Iwo Jima crashed near Tan Tan and Agadir, Morocco, during a joint training exercise, named "African Lion". Two Marines were killed and two others were seriously injured, and the aircraft was lost.[28][29][30] U.S. investigators found no mechanical flaw with the aircraft,[31] and human error was determined to be the cause.[32]

June 2012[edit]

On 13 June 2012, a USAF CV-22 crashed at Eglin Air Force Base in Florida during training. All five aboard were injured;[33] two were released from the hospital shortly after.[34] The aircraft ended upside down and received major damage.[35] The cause of the crash was determined to be pilot error, with the CV-22 flying through the proprotor wash of another aircraft.[36] The USAF has restarted formation flight training in response.[37]

May 2015[edit]

One of three Osprey aircraft participating in a training exercise at Bellows Air Force Station (Waimanalo, Oahu, Hawaii) suffered from dust intake to the right engine,[38] sustained a hard landing with fuselage damage[39] and caught fire. The accident led to the deaths of two U.S. Marines, and injuries to 20 others.[40][41] The accident caused Marines to recommend improved air filters,[38] and require reduced hover time in dust from 60 to 30 seconds, although most pilots rarely spend more than 10 seconds in dusty conditions.[42]

December 2016[edit]

On 13 December 2016, at 10 pm, an MV-22 crashed while landing onto a reef in shallow water 0.6 miles (0.97 km) off the Okinawa coastline of Camp Schwab where the aircraft broke apart. All five crew members aboard with Marine Aircraft Group 36, 1st Marine Aircraft Wing were rescued. Two crew members were injured and all were transported for treatment. Ospreys in Japan were grounded the following day.[43][44][45] An investigation into the mishap was launched.[46] Preliminary reports indicate that during in-flight refueling with a HC-130, the refueling hose was struck by the Osprey's rotor blades.[47] On 18 December, after a review of MV-22 safety procedures, the III Marine Expeditionary Force (IIIMEF) announced that it would resume flight operations concluding that they were confident that the mishap was due "solely to the aircraft's rotor blades coming into contact with the refueling line."[48]

August 2017[edit]

On 5 August 2017, a U.S. Marine Corps MV-22 Osprey assigned to Marine Medium Tiltrotor Squadron 265 with the 31st Marine Expeditionary Unit after taking off from the amphibious assault ship USS Bonhomme Richard struck the USS Green Bay and then crashed in Shoalwater Bay on the east coast of Australia. 23 personnel were rescued, with three confirmed dead.[49][50][51][52][53]

September 2017[edit]

On 28 September 2017, a V-22 Osprey operating in Syria as part of Operation Inherent Resolve was damaged beyond repair in a hard landing. Two people on board the aircraft were injured.[54][55][56] The non–salvageable Osprey was later destroyed by troops.[57]

Other accidents and notable incidents[edit]

July 2006[edit]

A V-22 experienced compressor stalls in its right engine in the middle of its first transatlantic flight to the United Kingdom for the Royal International Air Tattoo and Farnborough Airshow on 11 July 2006.[58] It had to be diverted to Iceland for maintenance. A week later it was announced that other V-22s had been having compressor surges and stalls, and the Navy launched an investigation into it.[59]

December 2006[edit]

It was reported that a serious nacelle fire occurred on a Marine MV-22 at New River in December 2006.[60][61]

March 2007[edit]

A V-22 experienced a hydraulic leak that led to an engine-compartment fire before takeoff on 29 March 2007.[60]

November 2007[edit]

An MV-22 Osprey of VMMT-204 caught on fire during a training mission and was forced to make an emergency landing at Camp Lejeune on 6 November 2007. The fire, which started in one of the engine nacelles, caused significant aircraft damage, but no injuries.[62]

After an investigation, it was determined that a design flaw with the engine air particle separator (EAPS) caused it to jam in flight, causing a shock wave in the hydraulics system and subsequent leaks. Hydraulic fluid leaked into the IR suppressors and was the cause of the nacelle fires. As a result, all Block A V-22 aircraft were placed under flight restrictions until modification kits could be installed. No fielded Marine MV-22s were affected, as those Block B aircraft already incorporated the modification.[63]


An Air Force CV-22 suffered a Class A mishap with more than a $1 million in damage during FY 2009. No details were released.[64]

October 2014[edit]

In early October 2014, an MV-22 Osprey lost power shortly after takeoff from the USS Makin Island in the Middle East. The pilots regained control and landed safely, but one U.S. Marine drowned because of life preserver dysfunction when bailing out of the aircraft.[65]

December 2016[edit]

On 13 December 2016 when a MV-22 crash-landed, a second MV-22 reportedly did a belly landing at MCAS Futenma.[44]

January 2017[edit]

On 29 January 2017, an MV-22 experienced a hard landing during the Yakla raid in Al Bayda, Yemen against Al-Qaeda in the Arabian Peninsula militants, causing two injuries to U.S. troops. The aircraft could not fly afterward and was destroyed by U.S. airstrikes.[66][67][3]


  1. ^ a b c d e f "Saving the Pentagon's Killer Chopper-Plane". Wired. July 2005.
  2. ^ a b "CV-22 Osprey Crashes in Afghanistan". ISAF_NATO. 9 April 2010. Archived from the original on 19 April 2013.
  3. ^ a b Raid in Yemen: Risky From the Start and Costly in the End, The New York Times, Eric Schmitt & David Sanger, February 1, 2017. Retrieved 10 February 2017.
  4. ^ "Bell Boeing MV-22 Osprey accidents and incidents" Aviation Safety Network Database
  5. ^ Whittle 2010, pp. 200–202.
  6. ^ "V-22 Osprey crash kills 7 Aircraft second of 5 prototypes to go down." Fort Worth Star-Telegram, 21 July 1992.
  7. ^ Norton 2004, pp. 46–47.
  8. ^ Whittle 2010, p. 246.
  9. ^ Gross, Kevin, Lieutenant Colonel U.S. Marine Corps; Tom Macdonald, MV-22 test pilot; Ray Dagenhart, MV-22 lead government engineer (September 2004). "Dispelling the Myth of the MV-22". Proceedings. The Naval Institute (September 2004). Retrieved 2009-04-09.
  10. ^ Cox, Bob. "V-22 Pilots Not To Blame For Crash, Widows Say", Fort Worth Star-Telegram, 4 June 2011.
  11. ^ Norton 2004, pp. 62–63.
  12. ^ Dao, James. "After North Carolina Crash, Marines Ground Osprey Program." New York Times, 13 December 2000.
  13. ^ "Marine V-22 Ospreys cleared to soar again." Spokesman-Review, 6 September 2000.
  14. ^ "V22 Osprey's 3.2 second accident Flight"., accessed 14 October 2013.
  15. ^ "Osprey Down: Marines Shift Story on Controversial Warplane’s Safety Record". Condé Nast, 13 October 2011.
  16. ^ White, Lance Cpl. Samuel D. (2006). "VMM-263 ready to write next chapter in Osprey program". Marine Corps News. United States Marine Corps. Archived from the original on 26 June 2006. Retrieved 10 April 2006.
  17. ^ Bell-Boeing MV-22B Osprey 27-MAR-2006. Aviation Safety Network
  18. ^ Bell MV-22B Osprey c/n D0056.
  19. ^ a b "The high cost of building a new flying machine". Charlotte Observer. 2 May 2010.[permanent dead link]
  20. ^ "ISAF: 4 killed in U.S. aircraft crash in Afghanistan". CNN. 9 April 2010.
  21. ^ Hodge, Nathan (9 April 2010). "Controversial Spec-Ops Tiltrotor Crashes in Afghanistan". Wired.
  22. ^ McIntyre, Jamie. "CV-22 Lost Due to Pilot Error"., 18 May 2010.
  23. ^ "CV-22B Accident Investigation Board" Archived 2011-11-06 at the Wayback Machine, "CV-22 Accident Investigation Board Results Released" Archived 2012-01-25 at the Wayback Machine. U.S. Air Force, 16 December 2010.
  24. ^ Rolfsen, Bruce. "Generals clash on cause of April Osprey crash." Airforce Times, 22 January 2011.
  25. ^ Axe, David. "General: ‘My Career Was Done’ When I Criticized Flawed Warplane" Archived 2013-07-26 at the Wayback Machine. Wired, 4 October 2012
  26. ^ Thompson, Mark. "So Why Did That V-22 Crash?" Archived December 20, 2010, at the Wayback Machine. Time. 18 December 2010.
  27. ^ Axe, David. "Air Force Engineer Takes on General Over Controversial Warplane Crash." Wired Magazine, 15 October 2012.
  28. ^ Majumdar, Dave. "Two killed in USMC MV-22 accident in Morocco." Flight International, 11 April 2012. Retrieved: 13 April 2012.
  29. ^ "Two U.S. Marines killed in Morocco helicopter crash" Archived 2012-04-15 at the Wayback Machine. BNO News, 12 April 2012. Retrieved: 16 April 2012.
  30. ^ "ASN Wikibase Occurrence # 144945" Aviation Safety Network, 15 April 2012. Retrieved: 16 April 2012.
  31. ^ "MV-22 Osprey that crashed in Morocco was mechanically perfect" Yomiuri Shimbun, 9 June 2012. Retrieved: 15 June 2012.
  32. ^ Whittle, Richard. "Marines Peg 'Bad Flying' As Cause of April V-22 Crash in Morocco" Archived 2012-07-13 at the Wayback Machine. AOL Defense, 9 July 2012. Retrieved: 10 July 2012.
  33. ^ "5 airmen injured when Air Force Osprey crashes during training mission in Florida Panhandle". Washington Post. Associated Press. 14 June 2012. Retrieved 16 June 2012.
  34. ^ "Two airmen injured in Osprey crash released from hospital". Northwest Florida Daily News, 15 June 2012. Retrieved: 16 June 2012.
  35. ^ "5 airmen hurt in Osprey crash near Navarre". Pensacola News Journal, 14 June 2012. Retrieved: 16 June 2012.
  36. ^ "AFSOC Crash Report Faults Understanding Of Osprey Rotor Wake". Breaking Defense.
  37. ^ "Crash Drives Air Force to Restart CV-22 Pilot Formation Training: EXCLUSIVE". Breaking Defense. Archived from the original on 2012-10-22.
  38. ^ a b Fatal MV-22 crash in Hawaii linked to excessive debris ingestion 25 November 2015
  39. ^ McGarry, Brendan. "Billows of Dust, a Sudden 'Pop' and an Osprey Falls from the Sky". Retrieved 7 August 2017.
  40. ^ "1 killed, several injured in Osprey crash at Bellows Air Force Station". HawaiiNewsNow. 17 May 2015. Retrieved 17 May 2015.
  41. ^ "2nd Marine dies of injuries suffered in military plane crash". Associated Press. 20 May 2015. Archived from the original on 24 July 2015. Retrieved 20 May 2015.
  42. ^ Whittle, Richard. "Fatal Crash Prompts Marines To Change Osprey Flight Rules" Breaking Defense, 16 July 2015.
  43. ^ Butterfield, Joseph, 1st Lt. "Okinawa Area Coordinator addresses the media about MV-22 incident". III Marine Expeditionary Force, United States Marine Corps, 14 December 2016. Retrieved 20 December 2016.
  44. ^ a b McCurry, Justin. "US grounds Osprey fleet in Japan after aircraft crashes off Okinawa". the Guardian, 14 December 2016. Retrieved: 15 December 2016.
  45. ^ オスプレイ墜落:機体折れ、無残 衝撃の大きさ物語る【写真特集】, Okinawa Times, December 14, 2016. Retrieved 10 February 2017.
  46. ^ Butterfield, Joseph, 1st Lt. "Crew Rescued after MV-22 Mishap off Coast of Okinawa". III Marine Expeditionary Force, United States Marine Corps, 13 December 2016. Retrieved 13 December 2016.
  47. ^ MATTHEW M. BURKE AND CHIYOMI SUMIDA, "Marines ground Ospreys on Okinawa, blame crash on severed hose" STARS AND STRIPES, 13 December 2016. Retrieved 14 December 2016.
  48. ^ Butterfield, Joseph, 1st Lt. "MV-22 Ospreys in Japan continue flight operations". III Marine Expeditionary Force, United States Marine Corps, 18 December 2016. Retrieved 20 December 2016.
  49. ^ Ironside, Robyn; Gordon, Krystal; Vujkovic, Melanie (7 August 2017). "Osprey mishap: Second marine identified after US military aircraft crash". ABC News. Australia. Retrieved 7 August 2017.
  50. ^ Schogol, Jeff. "Three Marines missing after Osprey crashes off Australia". Marine Corps Times. Retrieved 7 August 2017.
  51. ^ "3 U.S. Marines missing after heli-plane crashes off Australian coast". NBC News. Retrieved 7 August 2017.
  52. ^ "MV-22 struck flight deck before fatal crash". Flight Global. 10 August 2017. Retrieved 13 August 2017.
  53. ^ "Osprey involved in fatal crash off Australia has been recovered". Stars and Stripes. 6 September 2017.
  54. ^ "Two Service Members Injured after V-22 Osprey Suffers 'Hard Landing' in Syria". World Maritime News. 2 October 2017. Retrieved 3 October 2017.
  55. ^ 2 Troops Injured in Non-Combat V-22 Crash in Syria
  56. ^ Bell/Boeing MV22B Osprey 29-SEP-2017. Aviation Safety Network
  57. ^ us-marine-corps-v-22-osprey-crash-syria Aviationanalysis
  58. ^ "V-22 Osprey Makes Precautionary Landing En Route To UK". Archived from the original on 28 September 2007. Retrieved 6 August 2007.
  59. ^ Castelli, Christopher J. (n.d.). "Navy Probes Multiple V-22 Surges, Stalls". NewsStand. Retrieved 2007-04-08.
  60. ^ a b "Hydraulic Problems Vex V-22". 5 April 2007. Archived from the original on 27 September 2007. Retrieved 8 June 2007.
  61. ^ Bob Cox (31 March 2007). "Fire reported after leak of hydraulic fluid". Retrieved 2007-04-08.[dead link]
  62. ^ Trimble, Stephen. "V-22 Osprey severely damaged after engine fire". Flight Global, 8 November 2007.
  63. ^ "V-22 mishap probe prompts US fleet restrictions". FlightGlobal, 4 December 2007.
  64. ^ "Archived copy" (PDF). Archived from the original (PDF) on 2011-07-22. Retrieved 2010-03-14.CS1 maint: archived copy as title (link)
  65. ^ "Deadly Osprey crash spurred safety changes". The San Diego Union-Tribune. 30 June 2015.
  66. ^ "U.S. Commando Killed in Yemen in Trump's First Counterterrorism Operation". The New York Times. 29 January 2017.
  67. ^ "US raid on al-Qaeda in Yemen: What we know so far". BBC News. 1 February 2017. Retrieved 1 February 2017.

External links[edit]