Accidents and incidents involving the V-22 Osprey
| This article is an orphan, as few or no other articles link to it. Please introduce links to this page from related articles; suggestions may be available. (March 2010) |
The Bell-Boeing V-22 Osprey is an American military tiltrotor aircraft. The aircraft was developed by Bell Helicopter, which manufactures it in partnership with Boeing Helicopters.
There have been four significant failures during flight testing,[1] one combat-zone crash,[2] and a number of minor incidents.
Contents |
[edit] Crashes
The V-22 has had 5 crashes with a total of 34 fatalities.
[edit] 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]
[edit] July 1992
On 20 July 1992, a leaking gearbox led to a fire in the right nacelle, causing the aircraft to drop into the Potomac River in front of an audience of Congresspersons and other government officials at Quantico, killing all seven crewmen and grounding the aircraft for 11 months.[1]
[edit] 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.[3][4]
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.[5]
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]
[edit] December 2000
On 11 December, vibration-induced chafing from an adjacent wiring bundle caused a leak from the hydraulic line which fed the primary side of the swashplate actuators to the right side rotor blade controls. This 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) into a forest in Jacksonville, North Carolina, killing all four aboard. The wiring harnesses and hydraulic line routing in the nacelles were subsequently modified.[1]
[edit] 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.[6] It was unclear if the accident was the result of enemy fire. Taliban spokesmen have claimed responsibility, however previous claims for downing aircraft have often been false.[7][8] 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.[6][9] 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.[10]
Brig. Gen. Donald Harvel has fingered the "unidentified contrails" during the last 17 seconds of flight as indications of engine troubles.[11] The actual causes of the crash may never be known because US Military aircraft destroyed the wreckage and black box recorder.[12]
[edit] Other accidents and notable incidents
[edit] 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.[13]
[edit] 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 around US$ 7,068,028.[14] 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.[15]
[edit] 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.[16] 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.[17]
[edit] 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.[18]
[edit] March 2007
A V-22 experienced a hydraulic leak that led to an engine-compartment fire before takeoff on 29 March 2007.[19] 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.[19][20]
[edit] 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.[21]
[edit] 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 damage to the aircraft. However, no injuries resulted from the incident.[22]
After an investigation, it was determined that a design flaw with the EAPS (engine air particle separator) 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.[23]
[edit] FY 2009
An Air Force CV-22 suffered a Class A mishap causing more than a million dollars in damage sometime during FY 2009. No details were released.[24]
[edit] References
- ^ a b c d e f "Saving the Pentagon's Killer Chopper-Plane". Wired, July 2005. http://www.wired.com/wired/archive/13.07/osprey.html?pg=3&topic=osprey&topic_set=.
- ^ a b "CV-22 Osprey Crashes in Afghanistan". ISAF_NATO. 8 April 2010. http://www.isaf.nato.int/en/article/isaf-releases/cv-22-osprey-crashes-in-afghanistan.html.
- ^ Gross, Kevin, Lieutenant Colonel U.S. Marine Corps; Tom Macdonald, MV-22 test pilot and Ray Dagenhart, MV-22 lead government engineer (2004-09). "Dispelling the Myth of the MV-22". Proceedings (The Naval Institute) (September 2004). http://www.military.com/NewContent/0,13190,NI_Myth_0904,00.html. Retrieved 2009-04-09.
- ^ Cox, Bob, "V-22 Pilots Not To Blame For Crash, Widows Say", Fort Worth Star-Telegram, 4 June 2011.
- ^ Norton 2004, pp. 62–63.
- ^ a b "The high cost of building a new flying machine". Charlotte Observer. 2 May 2010. http://www.charlotteobserver.com/2010/05/02/1406049/the-high-cost-of-building-a-new.html.
- ^ "ISAF: 4 killed in U.S. aircraft crash in Afghanistan". CNN. 9 April 2010. http://edition.cnn.com/2010/WORLD/asiapcf/04/09/afghanistan.chopper.down/index.html?hpt=T2.
- ^ "Controversial Spec-Ops Tiltrotor Crashes in Afghanistan". Wired. 9 April 2010. http://www.wired.com/dangerroom/2010/04/controversial-spec-ops-tiltrotor-crashes-in-afghanistan/#more-23620.
- ^ McIntyre, Jamie. "CV-22 Lost Due to Pilot Error". dodbuzz.com, 18 May 2010.
- ^ "CV-22 Accident Investigation Board Results Released". U.S. Air Force, 16 December 2010.
- ^ Rolfsen, Bruce. "Generals clash on cause of April Osprey crash." Airforce Times, 22 January 2011.
- ^ Thompson, Mark. "So Why Did That V-22 Crash?" Time. 18 December 2010. Dead link
- ^ Stamford, Lincs., UK: Air Forces Monthly, compiled by Dave Allport, April 2005, Number 205, page 73.
- ^ "Osprey Down: Marines Shift Story on Controversial Warplane’s Safety Record". Condé Nast, October 13, 2011.
- ^ 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 2006-06-26. http://web.archive.org/web/20060626002833/http://www.usmc.mil/marinelink/mcn2000.nsf/main5/217128503734FF2B8525712A004D67BC?opendocument. Retrieved 2006-04-10.
- ^ "V-22 Osprey Makes Precautionary Landing En Route To UK". Air-Attack.com. http://www.air-attack.com/news/news_article/1864/V-22-Osprey-Makes-Precautionary-Landing-En-Route-To-UK.html. Retrieved 2007-08-06.
- ^ Castelli, Christopher J.. "Navy Probes Multiple V-22 Surges, Stalls". NewsStand. InsideDefense.com. http://www.military.com/features/0,15240,105828,00.html. Retrieved 2007-04-08.
- ^ Renae Merle (2007-02-10). "Marine Corps Grounds V-22 Osprey Aircraft". Washington Post. http://www.washingtonpost.com/wp-dyn/content/article/2007/02/09/AR2007020901860.html. Retrieved 2007-04-08.
- ^ a b Defensetalk.com (2007-04-05). "Hydraulic Problems Vex V-22". [1]. Archived from the original on 2007-09-27. http://web.archive.org/web/20070927185201/http://www.defencetalk.com/news/publish/airforce/Hydraulic_Problems_Vex_V-22100011256.php. Retrieved 2007-06-08.
- ^ Bob Cox (2007-03-31). "Fire reported after leak of hydraulic fluid". Star-Telegram.com. http://www.star-telegram.com/100/story/54055.html. Retrieved 2007-04-08.[dead link]
- ^ "Tilt-rotor aircraft deployed to Iraq". McClatchy Newspapers, October 8, 2007.
- ^ Osprey helicopter makes emergency landing. Havelock News, November 7, 2007.
- ^ V-22 mishap probe prompts US fleet restrictions. FlightGlobal, December 4, 2007.
- ^ http://www.afsc.af.mil/shared/media/document/AFD-080114-111.pdf
- Norton, Bill. Bell Boeing V-22 Osprey, Tiltrotor Tactical Transport. Midland Publishing, 2004. ISBN 1-85780-165-2.
[edit] External links
|
||||||||||||||