Air Force Osprey crashes at Florida base, injures five

The Ospreys were first deployed by the Marines in Iraq in 2007 after 18 years and $20 billion in development

Crashes The V-22 has had 6 crashes with a total of 36 fatalities. June 1991 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.[3] July 1992 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.[4][5][1] April 2000 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 610 m/min) from an unusually high altitude with a forward speed of under 45 miles per hour (72 km/h) when it suddenly stalled its right rotor at 245 feet (75 m), rolled over, crashed, and exploded, killing all nineteen on board.[6][7] 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.[8] 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/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 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] [9][10] 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.[11] It was initially unclear if the accident was the result of enemy fire.[12][13] 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.[11][14] 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.[15] Brig. Gen. Donald Harvel has fingered the "unidentified contrails" during the last 17 seconds of flight as indications of engine troubles.[16] The actual causes of the crash may never be known because US military aircraft destroyed the wreckage and black box recorder.[17] 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.[18][19][20] Other accidents and notable incidents November 2004 A USMC MV-22B, BuNo 165838, lost a substantial piece of a prop-rotor blade during test flight in Nova Scotia, Canada, on 26 November 2004, but was able to make safe precautionary landing at CFB Shearwater despite severe airframe vibration.[21] Early 2006 A V-22 experienced an uncommanded engine acceleration while ground turning at Marine Corps Air Station New River. 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 30 feet (9.1 m) into the air, and then fell to the ground with enough force to damage one of its wings; the total amount of damage was approximately US$7 million.[22] 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 amount of time needed for the switch between the redundant FADECs to eliminate the possibility of a similar mishap occurring in the future.[23] July 2006 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.[24] 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.[25] February 2007 The Air Force and Marine Corps commands temporarily grounded their entire fleet on 10 February 2007 after discovering a glitch in a computer chip that could cause the aircraft to lose control.[26] March 2007 A V-22 experienced a hydraulic leak that led to an engine-compartment fire before takeoff on 29 March 2007.[27] It was also reported at that time that a more serious nacelle fire occurred on a Marine MV-22 at New River in December 2006.[27][28] October 2007 Upon delivery of the Osprey to a combat zone for the first time, one of the ten aircraft experienced an unidentified malfunction which required it to land in Jordan on 4 October 2007. It was repaired and took off again for Iraq but the malfunction returned, forcing it to turn back and land in Jordan for new repairs.[29] November 2007 An MV-22 Osprey of VMMT-204 caught 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.[30] 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. This 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.[31] FY 2009 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.

How many billions wasted on this piece of shit?