Английская Википедия:Expeditionary Fighting Vehicle

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:Distinguish Шаблон:Redirect Шаблон:Use dmy dates Шаблон:Infobox weapon

The Expeditionary Fighting Vehicle (EFV) (formerly known as the Advanced Amphibious Assault Vehicle (AAAV)) was an amphibious assault vehicle developed by General Dynamics during the 1990s and 2000s for use by the U.S. Marine Corps. It would have been launched at sea, from an amphibious assault ship beyond the horizon, able to transport a full marine rifle squad to shore. It would maneuver cross country with an agility and mobility equal to or greater than the M1 Abrams.

The EFV was designed to replace the aging AAV-7A1 Assault Amphibious Vehicle (AAV),[1] which entered service in 1972,[2]Шаблон:Unreliable source? and was the Marine Corps' number one priority ground weapon system acquisition. It was to have had three times the speed in water and about twice the armor of the AAV, as well as superior firepower. The vehicle was to be deployed in 2015;[3] however, on 6 January 2011, Secretary of Defense Robert Gates recommended the EFV program be canceled.[4][5] The program, which was projected to cost $15 billion, had already cost $3 billion.[6][7]

The Marines asked for the EFV to be canceled in favor of the Assault Amphibian Vehicle Service Life Extension Program and the Marine Personnel Carrier, which itself became phase one of the Amphibious Combat Vehicle.[8]

History

In the 1980s, the US Marine Corps developed an "over the horizon" strategy for ocean-based assaults. The intention was to protect naval ships from enemy mines and shore defenses. It included the MV-22 Osprey, the Landing Craft Air Cushion (LCAC), and the EFV.

Development for the AAAV began in August 1974 with Landing Vehicle Assault (LVA) prototypes that continued in the early 1980s at the command at Marine Corps Base Camp Pendleton. The AAAV's predecessor, the LVTP-7, had its life expectancy extended in 1983–84 by use of a service life extension program, which modified and upgraded many of the key systems, creating the LVTP7A1 and re-designated it the AAVP7A1. At the time these vehicles were released, the USMC had anticipated and communicated delivery of the AAAV by 1993. As a result of delays, the AAVP7A1 received another service life extension-type upgrade in the mid 1990s while the USMC still awaited final development and delivery of the AAAV, 14 years behind original projected time frames.[9]

In 1988, defense officials authorized the concept exploration and definition phase. In 1995, the program entered into the definition and risk reduction phase, where it won two Department of Defense awards for successful cost and technology management.[9] In June 1996, a contract was awarded to General Dynamics Land Systems to begin full-scale engineering development of their design. Based on the early success of the program, the Marine Corps awarded a cost-plus contract to General Dynamics in July 2001 for the systems development and demonstration phase of the program, expected to be completed by October 2003. The AAAV was renamed "EFV" in September 2003. The Government Accountability Office later stated that the development phase of three years was insufficient, causing delays and prototype failures, particularly in reliability.[9] After the 2006 operational assessment was plagued by reliability issues and maintenance burdens, the Corps began a redesign of the EFV, requiring a new contract for an additional Шаблон:USD in February 2007.[9] That June, a reset of the development phase delayed completion by an additional four years.[9] Instead of initiating production as planned, the corps asked for seven new prototypes, to address the current deficiencies, which had caused an average of one failure for every four and a half hours of operation.[10]

On 7 April 2009, Defense Secretary Gates said that the EFV program would "continue as-is", pending an amphibious review in the 2010 Quadrennial Defense Review.[11] The vehicle was called "exquisite", which Gates usually reserved for programs he intended to cancel.[12] He later questioned the EFV as the proper ship-to-shore platform on 3 May 2010,[13] the day before the initial prototype was rolled out at a ceremony at Marine Corps Base Quantico.[14]

The USMC had reduced the number to be purchased from 1,013 to 573 AAAVs by 2015 due to escalation in unit cost estimated at $22.3 million in 2007.[9][14] The EFV might be a baseline vehicle for the US Army's BCT Ground Combat Vehicle Program, however it is more likely that the army will start a new program.[15]

Low rate initial production (LRIP) was projected to begin in January 2012.[16] Projected total program development cost of the type until first quarter of 2010 was estimated at 15.9 billion dollars.[17]

Controversy

Robert O. Work, while Undersecretary of the Navy sketched out a future for amphibious warfare in which either the Marines will land unopposed or it will take a major effort using all the long range weapons of the United States armed forces to clear out ship-killing missiles, so that amphibious ships can safely approach the hostile beach and neither scenario sees much use for the EFV.[18][19] New families of guided anti-ship weapons have extended target ranges of well past Шаблон:Convert making the EFV's capabilities less of a game-changer than originally hoped.[20]

In a joint report, the U.S. Public Interest Research Group and the National Taxpayers Union called the EFV program wasteful spending and asked for its cancellation along with the F-35 Joint Strike Fighter and the V-22 Osprey aircraft.[21] The co-chairs of the National Commission on Fiscal Responsibility and Reform have also supported the cancellation of the EFV.[22] During a Pentagon briefing, on 6 January 2011, revealing budget efficiencies and reinvestment possibilities, Secretary of Defense Gates announced his intention to cancel the EFV program.[5] In a statement released after Gates' press conference, Commandant of the Marine Corps General Amos said that he supported the cancellation of the EFV: Шаблон:Blockquote

Loren B. Thompson, of the Lexington Institute, said that Amos had been ordered to give this statement, which did not reflect his actual feelings on the issue.[23]

In an interview on 5 January 2011 with Bloomberg Businessweek, Duncan D. Hunter, a member of the House Armed Services Committee, anticipated the cancellation announcement by Gates. However, Hunter predicted that his committee would reject the cancellation.[24]

According to Lieutenant General George J. Flynn of the Marine Corps Combat Development Command, the USMC was to use funding from the cancelled EFV for other tactical ground vehicles over the next five years.[25] The EFV program was cut from a 2012 proposed budget by the White House.[26]

General Dynamics offered a cut down version of the EFV without the hydroplaning or weapons.[27] Ray Mabus has said that new defensive systems will allow navy ships to close to within Шаблон:Convert off hostile shores so a Шаблон:Convert amphibious tracked vehicle is no longer needed.[28]

Deputy Commandant George Flynn has said that the analysis of alternatives to replace the EFV will be accelerated to complete in six to nine months.[29] In the 2012 appropriations bill, Congress ordered that the EFV be one of the alternatives considered in the study.[30]

Design

Файл:EFVDesign.png
Diagram of EFVP1 variant

The EFV, designed by General Dynamics Land Systems, was an amphibious armored tracked vehicle with an aluminum hull. The engine is a custom MTU Friedrichshafen diesel (MT883) with two modes of operation; a high power mode for planing over the sea, and a low power mode for land travel. It has a crew of three and can transport 17 marines and their equipment. The EFV would have been the first heavy tactical vehicle with a space frame structure.[31]

The hull had a hydraulically actuated bow flap to aid planing with a maximum waterborne speed of Шаблон:Convert. Shrouded Honeywell waterjet propulsors are integrated into each side of the hull, which create over Шаблон:Convert of thrust. It was also outfitted with hydraulically actuated chines to cover the tracks while in seafaring mode.

The vehicle uses an Ethernet network connected by the Tactical Switch Router, based on the COTS DuraMAR Mobile IP router for its internal and external communications.[32]

Armament

The electrically powered two-man MK46 turret on the personnel variant accommodated the commander on the right and gunner on the left, a fire control system, and the main and coaxial weapons.

The standard version was to have had a Mk44 Bushmaster II 30 mm cannon, which fired up to 250 rounds per minute with single, burst, and fully automatic capabilities up to Шаблон:Convert in all weather conditions. A general purpose M240 7.62 mm machine gun with 600 rounds of ready-to-use ammunition was to be mounted coaxially with the main gun.

Countermeasures

Файл:EFVP1 Testing.png
EFVP1 engineering prototype undergoing shock testing

The EFV was fitted with composite armor, mine-blast protection, and a nuclear, biological and chemical defense system. Although aluminum hulls have been used for decades in military ground vehicles and watercraft, they have caused some concern due to protection issues.[33]

In June 2007 members of the House Armed Services Subcommittee on Seapower and Expeditionary Forces sent a letter to the Commandant of the Marine Corps urging that the EFV be redesigned to give troops better protection against roadside bombs.[34] The Marines suggested that underbelly armor appliqué could be applied after the EFVs come ashore and before they encounter IEDs.[9] The limited protection the EFV offers is an improvement on that offered by the AAV so the replacement is an advantage, given the current doctrine of using landing craft for land patrols.[35]

However, tests in January and February 2010 at Aberdeen Test Center demonstrated that the EFV offers blast protection equal to a category-2 Mine Resistant Ambush Protected vehicle, including two simulated improvised explosive devices under its belly and tracks.[36] Tests also show that it has superior protection from direct and indirect fire. The flat hull, which has endured persistent criticism for not being the more blast-resistant V-shape, was necessary for the EFV to plane across the surface of the water and reach its high speed, while dealing with sea states of Category 4.[36][37]

On 13 October 2010 the navy awarded M Cubed Technologies a contract to develop new armor for the EFV to offer better protection and lighter weight.[38]

Mobility

Файл:Driving compartment of EFV prototype.jpg
EFVP1 driving compartment.

Given the increasing ranges of shore launched anti-ship missiles, the EFV's Шаблон:Convert range for amphibious landing may no longer provide the anticipated protection predicted for an over the horizon launch.[9] The U.S. Navy began reconsidering the over the horizon approach, and is considering Шаблон:Convert appropriate for amphibious launches. This shift in doctrine has made the EFV's high water speeds unnecessary.[6] The EFV's need for high water speed has resulted in an engine that is Шаблон:Convert more powerful than the M1 Abrams, even though the EFV weighs far less.[39]

Variants

Personnel variant

The EFVP1 with a three-man crew would have conducted the signature mission of the United States Marine Corps, expeditionary maneuver warfare from seabases by initiating amphibious operations from Шаблон:Convert over-the-horizon and transporting 17 combat-equipped Marines to inland objectives. The fully armored, tracked combat vehicle would have provided firepower to disembarked or mechanized infantry with its own fully stabilized MK46 weapon station with the 30 mm cannon and 7.62mm machine-gun.

Command variant

Файл:EFVC1 Expeditionary Fighting Vehicle.jpg
EFVC1

The EFVC1 was to have provided the same survival and mobility capabilities found in the EFVP1. The EFVC1 would have been employed as a tactical command post for maneuver unit commanders at the battalion and regimental level. The EFVC1 would have provided the supported commander and selected staff with the ability to communicate, via on-board communications, with senior, adjacent, and subordinate maneuver units. The EFVC1 was to be armed with only a 7.62mm machine gun.

See also

Related development
Comparable ground systems

References

Шаблон:Reflist

External links

Шаблон:Commons

Шаблон:General Dynamics

  1. Шаблон:Cite web
  2. Шаблон:Cite web
  3. Шаблон:Cite webШаблон:Dead linkШаблон:Cbignore
  4. Шаблон:Citation
  5. 5,0 5,1 Шаблон:Citation
  6. 6,0 6,1 Шаблон:Cite web
  7. Шаблон:Cite web
  8. Kuiper, Jahn R. "EFV ousted for less costly triumvirate." Шаблон:Webarchive USMC, 22 March 2011.
  9. 9,0 9,1 9,2 9,3 9,4 9,5 9,6 9,7 Шаблон:Cite web
  10. Шаблон:Cite news
  11. Шаблон:Cite web
  12. Шаблон:Cite webШаблон:Dead linkШаблон:Cbignore
  13. Шаблон:Cite web
  14. 14,0 14,1 Шаблон:Cite web
  15. Шаблон:Cite web
  16. Шаблон:Cite web
  17. Exhibit P-40, Budget Item Justification Sheet February 2007
  18. Шаблон:Citation
  19. Robert O. Work and F. G. Hoffman "Hitting the Beach in the 21st Century." Proceedings, November 2010.
  20. Шаблон:Cite web
  21. Шаблон:Citation
  22. Шаблон:Cite web
  23. Шаблон:Citation
  24. Шаблон:Citation
  25. Шаблон:Citation
  26. "The Budget for Fiscal Year 2012" "Office of Management and Budget", 14 February 2011.
  27. Beidel, Eric. "General Dynamics Makes Final Argument for Keeping EFV Alive." Шаблон:Webarchive National Defense Industrial Association, 25 January 2011.
  28. Steele, Jeanette. "Q & A with Navy Secretary Ray Mabus." The San Diego Union-Tribune, 24 February 2011.
  29. Fabey, Michael. "USMC Expedites EFV Analysis Of Alternatives." Aviation Week, 10 June 2011.
  30. Brannen, Kate. "Congress looks to wrap up budget bills." Federal Times, 16 December 2011.
  31. Шаблон:Cite web
  32. Шаблон:Cite web
  33. Шаблон:Cite web
  34. Шаблон:Cite web
  35. Шаблон:Cite web
  36. 36,0 36,1 Шаблон:Cite web
  37. Шаблон:Cite web
  38. M Cubed Technologies, Inc. Wins Contract To Develop Armor For U.S. Marine Corps Fighting Vehicles M Cubed Technologies, Inc. press release, 13 October 2010
  39. Шаблон:Cite web