Since becoming operational in 2007, the V-22 has had five crashes resulting in nine fatalities. None were due to technical problems with the aircraft.
April 2010
On 8 April 2010, a USAF CV-22 crashed in southern Afghanistan.[2] Three US service members and one civilian were killed and 16 injured in the crash.[13] Initially it was unclear if the accident was caused by enemy fire.[14][15] 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.[13][16] 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.[17]
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.[18] 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.[19] The actual causes of the crash may never be known because US military aircraft destroyed the wreckage and black box recorder.[20] 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.[21]
April 2012
On 11 April 2012, an MV-22 from the VMM-261 on USS Iwo Jima (LHD-7) 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.[22][23][24] U.S. investigators found no mechanical flaw with the aircraft,[25] and human error was determined to be the cause.[26]
June 2012
On 13 June 2012, a USAF CV-22 crashed at Eglin Air Force Base in Florida during training. All five aboard were injured;[27] two were released from the hospital shortly after.[28] The aircraft ended upside down and received major damage.[29] The cause of the crash was determined to be pilot error, with the CV-22 flying through the proprotor wash of another aircraft.[30] The USAF has restarted formation flight training in response.[31]
May 2015
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,[32] sustained a hard landing with fuselage damage[33] and caught fire. The accident lead to the death of two U.S. Marines, and injuries to 20 others.[34][35] The accident caused Marines to recommend improved air filters,[32] and require reduced hover time in dust from 60 to 30 seconds, although most pilots rarely spend more than 10 seconds in dusty conditions.[36]
December 2016
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.[37][38][39] An investigation into the mishap was launched.[40] Preliminary reports indicate that during in-flight refueling with a KC-130, the refueling hose was struck by the Osprey's rotor blades.[41] On 18 December, after a review of MV-22 safety procedures, the III Marine Expeditionary Force (IIIMEF) announced that it will resume flight operations concluding that they are confident that the mishap was due "solely to the aircraft's rotor blades coming into contact with the refueling line."[42]
