Future Combat Systems Manned Ground Vehicles: Difference between revisions
Rescuing orphaned refs ("Pernin197" from rev 1073134991) |
Six Oh Five (talk | contribs) →Vehicles: typos, consistency |
||
(38 intermediate revisions by 20 users not shown) | |||
Line 43: | Line 43: | ||
}} |
}} |
||
The '''Manned Ground Vehicles''' ('''MGV''') was a family of lighter and more transportable ground vehicles developed by [[BAE Systems]] and [[General Dynamics]] as part of the [[U.S. Army]]'s [[Future Combat Systems]] (FCS) program. The MGV program was intended as a successor to the [[Stryker]] of the [[Interim Armored Vehicle]] program. |
The '''Manned Ground Vehicles''' ('''MGV''') was a family of lighter and more transportable ground vehicles developed by [[Boeing]] and subcontractors [[BAE Systems]] and [[General Dynamics]] as part of the [[U.S. Army]]'s [[Future Combat Systems]] (FCS) program. The MGV program was intended as a successor to the [[Stryker]] of the [[Interim Armored Vehicle]] program. |
||
The MGV program was set in motion in 1999 by Army Chief of Staff [[Eric Shinseki]]. |
The MGV program was set in motion in 1999 by Army Chief of Staff [[Eric Shinseki]]. |
||
The MGVs were based on a common [[tracked vehicle]] chassis.<ref>[http://www.boeing.com/defense-space/ic/fcs/bia/080828_manned_ground_veh_ovrvw.pdf Manned Ground Vehicle overview] {{Webarchive|url=https://web.archive.org/web/20081230122301/http://www.boeing.com/defense-space/ic/fcs/bia/080828_manned_ground_veh_ovrvw.pdf |date=2008-12-30 }}. Boeing, 7 August 2008.</ref> The lead vehicle, and the only to be produced as a prototype, was the [[XM1203 Non-Line-of-Sight Cannon|Non-Line-of-Sight Cannon]]. Seven other vehicle variants were to follow. |
The MGVs were based on a common [[tracked vehicle]] chassis.<ref>[http://www.boeing.com/defense-space/ic/fcs/bia/080828_manned_ground_veh_ovrvw.pdf Manned Ground Vehicle overview] {{Webarchive|url=https://web.archive.org/web/20081230122301/http://www.boeing.com/defense-space/ic/fcs/bia/080828_manned_ground_veh_ovrvw.pdf |date=2008-12-30 }}. Boeing, 7 August 2008.</ref> The lead vehicle, and the only one to be produced as a prototype, was the [[XM1203 Non-Line-of-Sight Cannon|Non-Line-of-Sight Cannon]]. Seven other vehicle variants were to follow. |
||
The MGV vehicles were conceived to be exceptionally lightweight (initially capped at 18 tons base weight) |
The MGV vehicles were conceived to be exceptionally lightweight (initially capped at 18 tons base weight) to meet the Army's intra-theatre air mobility requirements. The vehicles that the Army sought to replace with the MGVs ranged from 30 to 70 tons. In order to reduce weight, the Army substituted armor with passive and [[active protection system]]s. |
||
The FCS program was terminated in 2009 due to concerns about the program's affordability and technology readiness. The MGV program was succeeded by the [[Ground Combat Vehicle]] program, which was |
The FCS program was terminated in 2009 due to concerns about the program's affordability and technology readiness. The MGV program was succeeded by the [[Ground Combat Vehicle]] program, which was canceled in 2014. |
||
==History== |
==History== |
||
{{Expand section|date=September 2010}} |
|||
Initial Technology Demonstrator Vehicle by United Defense yielded both tracked and wheeled prototypes.<ref name="Wheeled">{{cite web|url=http://www.globalsecurity.org/military/systems/ground/fcs-mgv-p.htm|title=Future Combat System Prototype Vehicles|date=30 September 2006|publisher=GlobalSecurity.org|access-date=6 May 2010|archive-url=https://web.archive.org/web/20090902093910/http://www.globalsecurity.org/military/systems/ground/fcs-mgv-p.htm|archive-date=2 September 2009|url-status=live|df=dmy-all}}</ref> Only the tracked variant was pursued further. |
Initial Technology Demonstrator Vehicle by United Defense yielded both tracked and wheeled prototypes.<ref name="Wheeled">{{cite web|url=http://www.globalsecurity.org/military/systems/ground/fcs-mgv-p.htm|title=Future Combat System Prototype Vehicles|date=30 September 2006|publisher=GlobalSecurity.org|access-date=6 May 2010|archive-url=https://web.archive.org/web/20090902093910/http://www.globalsecurity.org/military/systems/ground/fcs-mgv-p.htm|archive-date=2 September 2009|url-status=live|df=dmy-all}}</ref> Only the tracked variant was pursued further. |
||
FCS-Wheeled (FCS-W) was an early concept designed to demonstrate hybrid-electric drive system and two-man cockpit |
FCS-Wheeled (FCS-W) was an early concept designed to demonstrate a hybrid-electric drive system and two-man cockpit workstations. A Technology Demonstrator Vehicle was built by [[United Defense]] and was unveiled in 2002. |
||
FCS-W was designed to deliver a top road speed of 75 mph and a top cross-country speed of 40 mph. The vehicle's armor utilized armor similar to the tracked variant but was lighter. The vehicle would have also had some type of [[active protection system]]. The arrangement of the turbine and drive motor provided for a two-man, side-by-side cockpit and a sizable payload compartment. |
FCS-W was designed to deliver a top road speed of 75 mph and a top cross-country speed of 40 mph. The vehicle's armor utilized armor similar to the tracked variant but was lighter. The vehicle would have also had some type of [[active protection system]]. The arrangement of the turbine and drive motor provided for a two-man, side-by-side cockpit and a sizable payload compartment. |
||
In May 2000 [[DARPA]] awarded four contracts to four industry teams to develop Future Combat Systems designs and in March 2002, the Army chose [[Boeing]] and [[Science Applications International Corporation]] (SAIC) to serve as the "lead systems integrators" to oversee the development and eventual production of the FCS’ 18 systems.<ref name="2006 CRS"/> In October 2002 United Defense (UD) and Boeing/SAIC signed a memorandum of understanding to bring the Objective Force Non-Line-of-Sight Cannon under the FCS umbrella.<ref name="NLOS-C merger">{{cite news|title=Army Working To Bring FCS, NLOS Cannon Efforts Together|url=https://www.highbeam.com/doc/1G1-93168097.html|archive-url=https://web.archive.org/web/20181121012533/https://www.highbeam.com/doc/1G1-93168097.html|url-status=dead|archive-date=21 November 2018|access-date=14 May 2017|work=Defense Daily|date=22 October 2002}}</ref> |
In May 2000, [[DARPA]] awarded four contracts to four industry teams to develop Future Combat Systems designs and in March 2002, the Army chose [[Boeing]] and [[Science Applications International Corporation]] (SAIC) to serve as the "lead systems integrators" to oversee the development and eventual production of the FCS’ 18 systems.<ref name="2006 CRS"/> In October 2002 United Defense (UD) and Boeing/SAIC signed a memorandum of understanding to bring the Objective Force Non-Line-of-Sight Cannon under the FCS umbrella.<ref name="NLOS-C merger">{{cite news|title=Army Working To Bring FCS, NLOS Cannon Efforts Together|url=https://www.highbeam.com/doc/1G1-93168097.html|archive-url=https://web.archive.org/web/20181121012533/https://www.highbeam.com/doc/1G1-93168097.html|url-status=dead|archive-date=21 November 2018|access-date=14 May 2017|work=Defense Daily|date=22 October 2002}}</ref> |
||
In January 2003, Boeing and SAIC reached an agreement with [[General Dynamics Land Systems]] (GDLS) and |
In January 2003, Boeing and SAIC reached an agreement with [[General Dynamics Land Systems]] (GDLS) and United Defense LP (UDLP) to develop the MGVs. UDLP was responsible for leading development of five of the vehicles (including the NLOS-C) while GDLS took responsibility for leading development of the other three.<ref name="UDLP GD">{{cite news |last1=Hsu |first1=Emily |title=Team Will Design Eight Manned Ground Vehicles for FCS: GD, United Defense Team Up for Army's Future Combat Systems |url=https://www.jstor.org/stable/24819825 |access-date=17 February 2022 |work=Inside the Army |issue=4 |publisher=Inside Washington Publishers |date=27 January 2003 |volume=15 |pages=2–3 |jstor=24819825 |archive-date=17 February 2022 |archive-url=https://web.archive.org/web/20220217093840/https://www.jstor.org/stable/24819825 |url-status=live }}</ref> |
||
In May 2003 the Defense Acquisition Board (DAB) approved the FCS’ next acquisition phase, and in August 2004 Boeing and SAIC awarded contracts to 21 companies to design and build its various platforms and hardware and software.<ref name="2006 CRS">{{cite web|last1=Feickert|first1=Andrew|title=The |
In May 2003 the Defense Acquisition Board (DAB) approved the FCS’ next acquisition phase, and in August 2004 Boeing and SAIC awarded contracts to 21 companies to design and build its various platforms and hardware and software.<ref name="2006 CRS">{{cite web|last1=Feickert|first1=Andrew|title=The Army's Future Combat System (FCS): Background and Issues for Congress|url=http://apps.dtic.mil/dtic/tr/fulltext/u2/a472541.pdf|archive-url=https://web.archive.org/web/20210312052533/http://www.dtic.mil/dtic/tr/fulltext/u2/a472541.pdf|url-status=live|archive-date=March 12, 2021|access-date=12 May 2017|date=5 May 2006}} {{PD-notice}}</ref> |
||
In December 2003, GDLS received a $2 billion MGV design contract from Boeing. Per the contract, GDLS would produce 8 Mounted Combat Systems, 6 command and control vehicles, and 4 reconnaissance and surveillance vehicle prototypes.<ref>{{cite news |last1=Hamilton |first1=Robert A. |title=GD wins $2B design contract for Army 'tanks' |url=https://www.newspapers.com/image/972548970/?terms=%22Mounted%20Combat%20System%22 |access-date=10 February 2024 |work=The Day |date=16 December 2003}}</ref> |
|||
⚫ | In March 2005, the Army's acquisition chief [[Claude Bolton]] told the House Armed Services subcommittee that getting the MGV's weight to under 19-tons was proving difficult.<ref name="Bolton">{{cite news |last1=Jen DiMascio |first1=Jen |title=Both Face Technical Hurdles: JTRS and Manned Ground Vehicles Critical to Success of Fcs, GAO Says |url=https://www.jstor.org/stable/24823654 |access-date=21 February 2022 |work=Inside the Army |issue= |
||
⚫ | In March 2005, the Army's acquisition chief [[Claude Bolton]] told the House Armed Services subcommittee that getting the MGV's weight to under 19-tons was proving difficult.<ref name="Bolton">{{cite news |last1=Jen DiMascio |first1=Jen |title=Both Face Technical Hurdles: JTRS and Manned Ground Vehicles Critical to Success of Fcs, GAO Says |url=https://www.jstor.org/stable/24823654 |access-date=21 February 2022 |work=Inside the Army |issue=11 |publisher=Inside Washington Publishers |date=21 March 2005 |volume=17 |pages=12–13 |jstor=24823654 |archive-date=21 February 2022 |archive-url=https://web.archive.org/web/20220221012102/https://www.jstor.org/stable/24823654 |url-status=live }}</ref> In 2005 the Army relented on the vehicle's requirement for roll-off [[C-130]] transportability. Relaxing the C-130 requirement to allow vehicles to be transported in a stripped-down configuration allowed the weight cap to be increased from 18 tons per vehicle to 24 tons.<ref>{{cite news|last1=Erwin|first1=Sandra|title=For Army's Future Combat Vehicles, Flying by C-130 No Longer Required|url=https://www.highbeam.com/doc/1G1-138538205.html|access-date=14 May 2017|work=National Defense|date=1 November 2005}}{{dead link|date=February 2019|bot=medic}}{{cbignore|bot=medic}}</ref> |
||
⚫ | In August 2005, GDLS selected [[Detroit Diesel]]'s 5L890 to power the eight variants.<ref name="Engine selected">{{cite news |last1=Roque |first1=Ashley |title=$47 Million Contract Awarded: Army Selects Diesel Engine to Power FCS Manned Ground Vehicles |url=https://www.jstor.org/stable/24824724 |access-date=17 February 2022 |work=Inside the Army |issue= |
||
⚫ | In August 2005, GDLS selected [[Detroit Diesel]]'s 5L890 to power the eight variants.<ref name="Engine selected">{{cite news |last1=Roque |first1=Ashley |title=$47 Million Contract Awarded: Army Selects Diesel Engine to Power FCS Manned Ground Vehicles |url=https://www.jstor.org/stable/24824724 |access-date=17 February 2022 |work=Inside the Army |issue=34 |publisher=Inside Washington Publishers |date=29 August 2005 |volume=17 |pages=1, 9–10 |jstor=24824724 |archive-date=17 February 2022 |archive-url=https://web.archive.org/web/20220217095235/https://www.jstor.org/stable/24824724 |url-status=live }}</ref> |
||
The Department of Defense announced budget cuts in April 2009,<ref>[https://www.nytimes.com/2009/04/07/us/politics/07defense.html?_r=1&hp "Military Budget Reflects a Shift in U.S. Strategy"] {{Webarchive|url=https://web.archive.org/web/20170628001941/http://www.nytimes.com/2009/04/07/us/politics/07defense.html?_r=1&hp |date=2017-06-28 }}. ''New York Times'', April 7, 2009. Retrieved in April 2009.</ref> which resulted in the cancellation of the FCS Manned Ground Vehicles family.<ref>{{Cite news|first=Gina |last=Cavallaro |title=Panel to discuss new ground combat vehicle |url=http://www.armytimes.com/news/2009/06/army_ground_combat_vehicle_061109w/ |work=Army Times |date=June 11, 2009 |access-date=June 14, 2009}}</ref><ref>McLeary, Paul. [http://www.aviationweek.com/aw/generic/story.jsp?id=news/GROUND050809.xml&headline=U.S.%20Army%20Ground%20Vehicles%20Up%20and%20Down&channel=defense "U.S. Army Ground Vehicles Up and Down"]{{Dead link|date=May 2019 |bot=InternetArchiveBot |fix-attempted=yes }}. ''Aviation Week'', 8 May 2009.</ref> The Army issued a stop-work order for MGV and NLOS-C efforts in June. In July the army terminated the MGV, but not the NLOS-C. In the news release the Army said cancelation would "negatively impact" NLOS-C development but said it was seeking a "viable path forward" for the NLOS-C.<ref>{{cite news|last1=Jagirdar|first1=Sarabjit|title=ARMY PARTIALLY TERMINATES FUTURE COMBAT SYSTEMS MANNED GROUND VEHICLE|url=https://www.highbeam.com/doc/1P3-1798992061.html|archive-url=https://web.archive.org/web/20181116000954/https://www.highbeam.com/doc/1P3-1798992061.html|url-status=dead|archive-date=16 November 2018|access-date=12 May 2017|work=US Fed News Service|date=20 July 2009}}</ref> |
The Department of Defense announced budget cuts in April 2009,<ref>[https://www.nytimes.com/2009/04/07/us/politics/07defense.html?_r=1&hp "Military Budget Reflects a Shift in U.S. Strategy"] {{Webarchive|url=https://web.archive.org/web/20170628001941/http://www.nytimes.com/2009/04/07/us/politics/07defense.html?_r=1&hp |date=2017-06-28 }}. ''New York Times'', April 7, 2009. Retrieved in April 2009.</ref> which resulted in the cancellation of the FCS Manned Ground Vehicles family.<ref>{{Cite news|first=Gina |last=Cavallaro |title=Panel to discuss new ground combat vehicle |url=http://www.armytimes.com/news/2009/06/army_ground_combat_vehicle_061109w/ |work=Army Times |date=June 11, 2009 |access-date=June 14, 2009}}</ref><ref>McLeary, Paul. [http://www.aviationweek.com/aw/generic/story.jsp?id=news/GROUND050809.xml&headline=U.S.%20Army%20Ground%20Vehicles%20Up%20and%20Down&channel=defense "U.S. Army Ground Vehicles Up and Down"]{{Dead link|date=May 2019 |bot=InternetArchiveBot |fix-attempted=yes }}. ''Aviation Week'', 8 May 2009.</ref> The Army issued a stop-work order for MGV and NLOS-C efforts in June. In July the army terminated the MGV, but not the NLOS-C. In the news release the Army said cancelation would "negatively impact" NLOS-C development but said it was seeking a "viable path forward" for the NLOS-C.<ref>{{cite news|last1=Jagirdar|first1=Sarabjit|title=ARMY PARTIALLY TERMINATES FUTURE COMBAT SYSTEMS MANNED GROUND VEHICLE|url=https://www.highbeam.com/doc/1P3-1798992061.html|archive-url=https://web.archive.org/web/20181116000954/https://www.highbeam.com/doc/1P3-1798992061.html|url-status=dead|archive-date=16 November 2018|access-date=12 May 2017|work=US Fed News Service|date=20 July 2009}}</ref> |
||
The DoD determined that the proposed FCS vehicle designs would not provide sufficient protection against [[improvised explosive device|IEDs]].<ref>[ |
The DoD determined that the proposed FCS vehicle designs would not provide sufficient protection against [[improvised explosive device|IEDs]].<ref>[https://thehill.com/business-a-lobbying/168352-contractors-vie-for-lucrative-vehicle-work/ "Contractors vie for lucrative vehicle work"] . ''The Hill'', August 5, 2010. Retrieved on August 21, 2010.</ref> |
||
The Army planned to restart from the beginning on manned ground vehicles.<ref>Military Deputy for Budget Office of the Assistant Secretary of the Army (Financial Mgt and Comptroller) Lt. Gen. Edgar Stanton and Acting Director, Army Budget Office William Campbell May 07, 2009, [http://www.defenselink.mil/transcripts/transcript.aspx?transcriptid=4419 News Transcript] {{Webarchive|url=https://web.archive.org/web/20090530054902/http://www.defenselink.mil//transcripts/transcript.aspx?transcriptid=4419 |date=2009-05-30 }}, U.S. Department of Defense, Office of the Assistant Secretary of Defense (Public Affairs).</ref> The program's heavier successor, the [[Ground Combat Vehicle]], was cancelled in 2014. |
The Army planned to restart from the beginning on manned ground vehicles.<ref>Military Deputy for Budget Office of the Assistant Secretary of the Army (Financial Mgt and Comptroller) Lt. Gen. Edgar Stanton and Acting Director, Army Budget Office William Campbell May 07, 2009, [http://www.defenselink.mil/transcripts/transcript.aspx?transcriptid=4419 News Transcript] {{Webarchive|url=https://web.archive.org/web/20090530054902/http://www.defenselink.mil//transcripts/transcript.aspx?transcriptid=4419 |date=2009-05-30 }}, U.S. Department of Defense, Office of the Assistant Secretary of Defense (Public Affairs).</ref> The program's heavier successor, the [[Ground Combat Vehicle]], was cancelled in 2014. |
||
Line 83: | Line 84: | ||
In order to reduce weight, the Army substituted armor with passive and [[active protection system]]s. This was hoped to provide a level of protection similar to the legacy armored vehicles being replaced.<ref name="Andrew Feickert" /> |
In order to reduce weight, the Army substituted armor with passive and [[active protection system]]s. This was hoped to provide a level of protection similar to the legacy armored vehicles being replaced.<ref name="Andrew Feickert" /> |
||
[[File:FCS Quick Kill.webm|thumb|right|[[Quick Kill]] [[active protection system]] takes out an RPG in a test in October 2007]] |
|||
Most vehicles were protected with hard-kill [[active protection system]]s capable of defeating most threats.<ref>{{cite web |url=http://contracting.tacom.army.mil/majorsys/gcv/ID_1_Master_19Oct091.pptx |title=GCV, Industry Day #1 |publisher=Contracting.tacom.army.mil |access-date=2011-03-31 |archive-url=https://web.archive.org/web/20110722183427/http://contracting.tacom.army.mil/majorsys/gcv/ID_1_Master_19Oct091.pptx |archive-date=2011-07-22 |url-status=dead }}</ref> The armor was a unique secret matrix that may be utilized by industry in the [[Ground Combat Vehicle]] program. |
Most vehicles were protected with hard-kill [[active protection system]]s capable of defeating most threats.<ref>{{cite web |url=http://contracting.tacom.army.mil/majorsys/gcv/ID_1_Master_19Oct091.pptx |title=GCV, Industry Day #1 |publisher=Contracting.tacom.army.mil |access-date=2011-03-31 |archive-url=https://web.archive.org/web/20110722183427/http://contracting.tacom.army.mil/majorsys/gcv/ID_1_Master_19Oct091.pptx |archive-date=2011-07-22 |url-status=dead }}</ref> The armor was a unique secret matrix that may be utilized by industry in the [[Ground Combat Vehicle]] program. |
||
The common MGV chassis was required to provide full protection from 30 mm and 45 mm cannon fire in a 60 |
The common MGV chassis was required to provide full protection from 30 mm and 45 mm cannon fire in a 60-degree arc opening towards the front of the vehicle. 360-degree protection from small arms fire up to 14.5 mm heavy machine gun and 155 mm artillery shell air-bursts was planned. Protection from higher caliber rounds as well as anti-tank guided missiles would be provided by an active protection system manufactured by Raytheon known as "[[Quick Kill active protection system|Quick Kill]]". |
||
Use of a common chassis was to reduce the need for specialized training of personnel and allow for faster fielding of repairs. The MGV platform utilized a hybrid diesel-electric propulsion system. The MGV also employed numerous weight-saving features, including composite armor, composite and titanium structural elements, and continuous band tracks. |
Use of a common chassis was to reduce the need for specialized training of personnel and allow for faster fielding of repairs. The MGV platform utilized a hybrid diesel-electric propulsion system. The MGV also employed numerous weight-saving features, including composite armor, composite and titanium structural elements, and continuous band tracks. |
||
The 30 |
The 30 mm [[Mk44 Bushmaster II]] chain gun on the reconnaissance and surveillance vehicle and infantry carrier vehicle provided greater firepower, yet weighed 25% less than the [[M242 Bushmaster]] it would replace.<ref name="Andrew Feickert">{{cite web |author=Andrew Feickert |url=http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA501559&Location=U2&doc=GetTRDoc.pdf |title=The Army's Future Combat Systems Program |date=May 29, 2009 |access-date=March 7, 2011 |archive-url=https://web.archive.org/web/20110629002237/http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA501559&Location=U2&doc=GetTRDoc.pdf |archive-date=June 29, 2011 |url-status=dead |df=mdy-all }}</ref> |
||
===Weight growth=== |
===Weight growth=== |
||
Weight at full combat capability (FCC) was raised to 24 tons in June 2006, then to 27.4 tons in January. According to a former program official, MGV chassis weights entered a "death spiral," as any weight growth to the subsystems cascaded to the whole system (e.g. heavier armor required a stronger suspension to carry it). FCC weight was eventually raised to 30 tons.<ref name="Pernin95">Pernin et al, Ch. 5, p. 95-118.</ref> |
Weight at full combat capability (FCC) was raised to 24 tons in June 2006, then to 27.4 tons in January. According to a former program official, MGV chassis weights entered a "death spiral," as any weight growth to the subsystems cascaded to the whole system (e.g. heavier armor required a stronger suspension to carry it). FCC weight was eventually raised to 30 tons.<ref name="Pernin95">Pernin et al, Ch. 5, p. 95-118.</ref> |
||
[[United States Army Training and Doctrine Command|TRADOC]] was slow to update its expectations for the MGV. TRADOC recommended removing C-130 transportability requirements in 2007 and raising the weight limit to 27.4 tons in requirements drafted in 2007. However, TRADOC's essential combat configuration MGV weight remained capped at 38,000 pounds (19 tons) until the program's cancelation.<ref name="Pernin95" |
[[United States Army Training and Doctrine Command|TRADOC]] was slow to update its expectations for the MGV. TRADOC recommended removing C-130 transportability requirements in 2007 and raising the weight limit to 27.4 tons in requirements drafted in 2007. However, TRADOC's essential combat configuration MGV weight remained capped at 38,000 pounds (19 tons) until the program's cancelation.<ref name="Pernin95"/> |
||
==Armor and countermeasures== |
==Armor and countermeasures== |
||
MGVs in essential combat configuration were required to have all-around protection from 14.5 |
MGVs in essential combat configuration were required to have all-around protection from 14.5 mm caliber ammunition, and [[30 mm caliber|30 mm]] from the front. This requirement was changed later that year to 14.5 mm protection with [[Appliqué armour|add-on armor]].<ref name="Pernin95"/> |
||
In 2008, the Army added a requirement for an add-on [[V-hull]] kit.<ref name="Pernin95" |
In 2008, the Army added a requirement for an add-on [[V-hull]] kit.<ref name="Pernin95"/> |
||
==Vehicles== |
==Vehicles== |
||
Line 126: | Line 128: | ||
===Reconnaissance and Surveillance Vehicle=== |
===Reconnaissance and Surveillance Vehicle=== |
||
[[File:XM1201 RSV.jpg|thumb|right|XM1201 Reconnaissance and Surveillance Vehicle (RSV)]] |
[[File:XM1201 RSV.jpg|thumb|right|XM1201 Reconnaissance and Surveillance Vehicle (RSV)]] |
||
The |
The XM1201 Reconnaissance and Surveillance Vehicle (RSV) featured a suite of advanced [[sensor]]s to detect, locate, track, classify and automatically identify targets under all [[weather|climatic conditions]], day or night. |
||
The suite included a mast-mounted, long-range [[optoelectronic]] [[infrared]] sensor, an emitter mapping sensor for [[radio frequency]] interception and [[direction finding]], [[chemical weapons|chemical]] sensor and a multifunction radio frequency sensor. |
The suite included a mast-mounted, long-range [[optoelectronic]] [[infrared]] sensor, an emitter mapping sensor for [[radio frequency]] interception and [[direction finding]], [[chemical weapons|chemical]] sensor and a multifunction radio frequency sensor. |
||
Line 136: | Line 138: | ||
The XM1202 Mounted Combat System (MCS) was planned as a successor to the [[M1 Abrams]] [[main battle tank]].<ref name="Andrew Feickert" /> |
The XM1202 Mounted Combat System (MCS) was planned as a successor to the [[M1 Abrams]] [[main battle tank]].<ref name="Andrew Feickert" /> |
||
The MCS was to provide both direct and beyond-line-of-sight ('indirect') firepower capability |
The MCS was to provide both direct and beyond-line-of-sight ('indirect') firepower capability and allowed for in-depth destruction of point targets up to {{convert|8|km|abbr=on}} away.<ref name="Andrew Feickert" /> |
||
[[File:Fcs-mcs c. 2004 b&w.png|thumb|right|MCS computer drawing {{circa|2004}}]] |
|||
As of 2009 the MCS was to have had a crew of two and to be armed with an |
As of 2009 the MCS was to have had a crew of two and to be armed with an [[autoloader|autoloaded]] 120 mm main gun, a [[.50 BMG|12.7 mm (.50) caliber]] machine gun, and a 40 mm [[automatic grenade launcher]].<ref>{{cite web |url=http://www.dtic.mil/cgi-bin/GetTRDoc?Location=U2&doc=GetTRDoc.pdf&AD=ADA501037 |title=The Army's Future Combat System (FCS): Background and Issues for Congress |publisher=DTIC.mil |date=28 May 2009 |access-date=2011-03-31 |archive-url=https://web.archive.org/web/20110604232356/http://www.dtic.mil/cgi-bin/GetTRDoc?Location=U2&doc=GetTRDoc.pdf&AD=ADA501037 |archive-date=4 June 2011 |url-status=dead |df=dmy-all }}</ref> |
||
The MCS was intended to deliver precision fire at a rapid rate, in order to destroy multiple targets at standoff ranges quickly, and would complement the other systems in the unit of action. It would be capable of providing direct support to the dismounted [[infantry]] in an assault, defeating [[bunker]]s, and breaching walls during tactical assaults. It was also intended to be highly mobile, in order to maneuver out of contact and into positions of advantage; given the vehicle's light weight, this was especially important. |
The MCS was intended to deliver precision fire at a rapid rate, in order to destroy multiple targets at standoff ranges quickly, and would complement the other systems in the unit of action. It would be capable of providing direct support to the dismounted [[infantry]] in an assault, defeating [[bunker]]s, and breaching walls during tactical assaults. It was also intended to be highly mobile, in order to maneuver out of contact and into positions of advantage; given the vehicle's light weight, this was especially important. |
||
In May 2003 Army officials revealed a computer model of the MCS, allowing reporters to view the inside of the vehicle through a [[Cave automatic virtual environment]]. This concept used a crew of three.<ref>{{cite news |last1=Hsu |first1=Emily |title=Virtual tool to aid in FCS vehicle designs: ARMY REVEALS PRELIMINARY DESIGN FOR FCS MOUNTED COMBAT SYSTEM |url=https://www.jstor.org/stable/24821903 |access-date=10 February 2024 |work=Inside the Army |volume=15|issue=21 |date=26 May 2003}}</ref> |
|||
The XM360 tank gun underwent test firing at [[Aberdeen Proving Ground]] beginning in March 2008.<ref>{{cite news|last1=Roosevelt|first1=Ann|title=Advanced 120mm Gun For FCS Mounted Combat System In Safety Testing|url=https://www.highbeam.com/doc/1G1-178098609.html|archive-url=https://web.archive.org/web/20181115222413/https://www.highbeam.com/doc/1G1-178098609.html|url-status=dead|archive-date=15 November 2018|access-date=12 May 2017|work=Defense Daily|date=26 March 2008}}</ref> |
|||
The [[Picatinny Arsenal]] [[XM360]] tank gun had been selected by September 2006.<ref>{{cite news |title=Fifteen Picatinny employees receive Army's top research award |url=https://www.newspapers.com/image/494119618/?terms=%22Mounted%20Combat%20System%22&match=1 |access-date=10 February 2024 |work=AIM Jefferson |date=1 September 2006 |page=A8}}</ref> tank gun underwent test firing at [[Aberdeen Proving Ground]] beginning in March 2008.<ref>{{cite news|last1=Roosevelt|first1=Ann|title=Advanced 120mm Gun For FCS Mounted Combat System In Safety Testing|url=https://www.highbeam.com/doc/1G1-178098609.html|archive-url=https://web.archive.org/web/20181115222413/https://www.highbeam.com/doc/1G1-178098609.html|url-status=dead|archive-date=15 November 2018|access-date=12 May 2017|work=Defense Daily|date=26 March 2008}}</ref> General Dynamics Armament and Technical Products was awarded a $14 million contract in 2007 to develop the ammunition handling system.<ref>{{cite news |title=General Dynamics in Lincoln developing tank ammo magazines |url=https://journalstar.com/business/general-dynamics-in-lincoln-developing-tank-ammo-magazines/article_27701f07-8629-5528-b1c4-ac95ded1af4e.html |access-date=10 February 2024 |work=The Lincoln Journal Star |date=22 April 2007 |language=en}}</ref> In January 2008, [[Raytheon]] was awarded a $232 million contract to develop the [[XM1111 Mid-Range Munition]]. The munition had been test fired from an M1 Abrams as early as March 2007.<ref name="MRM">{{cite news |title=Raytheon wins $232.2 million contract |url=https://www.newspapers.com/image/213648807/?terms=%22Mounted%20Combat%20System%22&match=1 |access-date=10 February 2024 |work=Arizona Daily Star |date=3 January 2008}}</ref> The Army tested a 27-round magazine ammunition handling system at [[Aberdeen Proving Ground]] by July 2008.<ref name="turret component">{{cite news |last1=Wasserby |first1=Daniel |title=Live-fire evaluation slated for February: ARMY BEGINS TESTING FCS MOUNTED COMBAT SYSTEMS' TURRET COMPONENT |url=https://www.jstor.org/stable/24826646 |access-date=10 February 2024 |work=Inside the Army |volume=20|issue=30 |date=28 July 2008}}</ref> |
|||
This was considered the most complex of the three vehicles GDLS was contracted to build.<ref>{{cite news |last1=Bennett |first1=Jeff |title=General Dynamics gets Army Contract |url=https://www.newspapers.com/image/362493716/?terms=%22Mounted%20Combat%20System%22 |access-date=10 February 2024 |work=Detroit Free Press |date=16 December 2003}}</ref> |
|||
===Non-Line-of-Sight Cannon=== |
===Non-Line-of-Sight Cannon=== |
||
{{main|XM1203 Non-Line-of-Sight Cannon}} |
{{main|XM1203 Non-Line-of-Sight Cannon}} |
||
[[File:XM1203 Non Line of Sight-Cannon (NLOS-C).jpg|thumb|right |
[[File:XM1203 Non Line of Sight-Cannon (NLOS-C).jpg|thumb|right|Non-Line-of-Sight Cannon at Yuma Proving Ground ''c.'' 2009]] |
||
The |
The [[XM1203 Non-Line-of-Sight Cannon]] (NLOS-C) was a [[155 mm]] [[self-propelled howitzer]] to succeed the [[M109 howitzer]]. This was the lead vehicle effort, and most far along when the program was terminated in 2009. The NLOS-C used technology from the canceled [[XM2001 Crusader]] project. |
||
The NLOS-C incorporated the autoloader from the Crusader project.<ref>{{cite web |url=http://www.strategypage.com/htmw/htart/articles/20070724.aspx |title=M-109 Replacement Enters Production |publisher=Strategypage.com |date=2007-07-24 |access-date=2011-03-31 |archive-url=https://web.archive.org/web/20120118213251/http://www.strategypage.com/htmw/htart/articles/20070724.aspx |archive-date=2012-01-18 |url-status=live }}</ref> The NLOS-C featured an improved fire rate over the M109. It was capable of [[multiple rounds simultaneous impact]] (MRSI), where the cannon fires a sequence of several rounds at different trajectories such that the rounds all hit the same target at the same time. The system had the ability to switch shell types quickly on a one-by-one basis. |
The NLOS-C incorporated the autoloader from the Crusader project.<ref>{{cite web |url=http://www.strategypage.com/htmw/htart/articles/20070724.aspx |title=M-109 Replacement Enters Production |publisher=Strategypage.com |date=2007-07-24 |access-date=2011-03-31 |archive-url=https://web.archive.org/web/20120118213251/http://www.strategypage.com/htmw/htart/articles/20070724.aspx |archive-date=2012-01-18 |url-status=live }}</ref> The NLOS-C featured an improved fire rate over the M109. It was capable of [[multiple rounds simultaneous impact]] (MRSI), where the cannon fires a sequence of several rounds at different trajectories such that the rounds all hit the same target at the same time. The system had the ability to switch shell types quickly on a one-by-one basis. |
||
Line 154: | Line 161: | ||
Improvements in the refueling arrangements and automation of ammunition reloading reduced the amount of time spent on resupply and during which the gun would be unavailable for combat support. This also allowed the system to use a crew of two instead of five. |
Improvements in the refueling arrangements and automation of ammunition reloading reduced the amount of time spent on resupply and during which the gun would be unavailable for combat support. This also allowed the system to use a crew of two instead of five. |
||
The NLOS-C had high commonality with the NLOS-Mortar vehicle.<ref name="Mortar commonality"/> |
The NLOS-C had a high commonality with the NLOS-Mortar vehicle.<ref name="Mortar commonality"/> |
||
The first NLOS-C prototype was rolled out in May 2008. Eight prototypes were delivered to the U.S. Army's [[Yuma Proving Ground]] in Arizona by 2009.<ref name=autogenerated1>{{cite web |author=C. Todd Lopez |url=http://www.army.mil/-news/2008/05/30/9539-first-fcs-manned-vehicle-to-make-public-debut/ |title=First FCS Manned Vehicle to Make Public Debut |publisher=Army.mil |date=2008-05-30 |access-date=2011-03-31 |archive-url=https://web.archive.org/web/20100412072353/http://www.army.mil/-news/2008/05/30/9539-first-fcs-manned-vehicle-to-make-public-debut/ |archive-date=2010-04-12 |url-status=live }}</ref> |
The first NLOS-C prototype was rolled out in May 2008. Eight prototypes were delivered to the U.S. Army's [[Yuma Proving Ground]] in Arizona by 2009.<ref name=autogenerated1>{{cite web |author=C. Todd Lopez |url=http://www.army.mil/-news/2008/05/30/9539-first-fcs-manned-vehicle-to-make-public-debut/ |title=First FCS Manned Vehicle to Make Public Debut |publisher=Army.mil |date=2008-05-30 |access-date=2011-03-31 |archive-url=https://web.archive.org/web/20100412072353/http://www.army.mil/-news/2008/05/30/9539-first-fcs-manned-vehicle-to-make-public-debut/ |archive-date=2010-04-12 |url-status=live }}</ref> |
||
Although Defense Secretary [[Robert Gates]] ended the MGV program in April 2009, Congress had directed that the Army continue working on the NLOS-C as a separate initiative. The Pentagon directed the Army to cancel the NLOS-C in December.<ref name="terminated">{{cite news |last1=Censer |first1=Marjorie |title=Promising thorough vehicle review ...: DOD Acquisition Chief Formally Terminates Army's NLOS Cannon |url=https://www.jstor.org/stable/24831487 |access-date=18 February 2022 |work=Inside the Army |issue= |
Although Defense Secretary [[Robert Gates]] ended the MGV program in April 2009, Congress had directed that the Army continue working on the NLOS-C as a separate initiative. The Pentagon directed the Army to cancel the NLOS-C in December.<ref name="terminated">{{cite news |last1=Censer |first1=Marjorie |title=Promising thorough vehicle review ...: DOD Acquisition Chief Formally Terminates Army's NLOS Cannon |url=https://www.jstor.org/stable/24831487 |access-date=18 February 2022 |work=Inside the Army |issue=49 |publisher=Inside Washington Publishers |date=14 December 2009 |volume=21 |jstor=24831487 |archive-date=18 February 2022 |archive-url=https://web.archive.org/web/20220218001422/https://www.jstor.org/stable/24831487 |url-status=live }}</ref> |
||
===Non-Line-of-Sight Mortar=== |
===Non-Line-of-Sight Mortar=== |
||
{{for|the 50 |
{{for|the 50 mm air burst munition|XM1204 High Explosive Air Burst}} |
||
[[File:XM1204 NLOS-M.jpg|thumb|right|XM1204 Non-Line-of-Sight Mortar (NLOS-M)]] |
[[File:XM1204 NLOS-M.jpg|thumb|right|XM1204 Non-Line-of-Sight Mortar (NLOS-M)]] |
||
The |
The XM1204 Non-Line-of-Sight Mortar (NLOS-M) was a turreted [[mortar carrier]] with a crew of four.<ref name="Andrew Feickert" /> |
||
The NLOS-M had a breech-loading, gun-mortar that fired 120 mm munitions including the [[Precision Guided Mortar Munition]] (PGMM). It had a fully automated firing control system and a manually assisted, semi-automated ammunition loading system. |
The NLOS-M had a breech-loading, gun-mortar that fired 120 mm munitions including the [[Precision Guided Mortar Munition]] (PGMM). It had a fully automated firing control system and a manually assisted, semi-automated ammunition loading system. |
||
The NLOS-M would carry an 81 |
The NLOS-M would carry an 81 mm mortar for dismounted operations away from the carrier.<ref name="Andrew Feickert" /> |
||
The NLOS-M provides fires on-demand to engage complex and simultaneous target sets. As part of an NLOS-M battery, individual NLOS-M vehicles |
The NLOS-M provides fires on-demand to engage complex and simultaneous target sets. As part of an NLOS-M battery, individual NLOS-M vehicles would have provided precision-guided rounds to destroy high-value targets, protective fires to suppress and obscure the enemy, and illumination fires. |
||
The FCS command, control, communications, computers, intelligence, surveillance and reconnaissance ([[C4ISTAR|C4ISR]]) network |
The FCS command, control, communications, computers, intelligence, surveillance and reconnaissance ([[C4ISTAR|C4ISR]]) network would have enabled the NLOS-M fire control system to conduct semi- to autonomous computation of technical fire direction, automatic gun lay, preparation of the ammunition for firing, and mortar round firing. |
||
In January 2003 |
In January 2003 United Defense, now part of [[BAE Systems]], was selected by the Army and the FCS lead systems integrators ([[Boeing]] and [[Science Applications International Corporation|SAIC]]) to develop and build the NLOS-M. |
||
The NLOS-M had high commonality with the [[XM1203 Non-Line-of-Sight Cannon|NLOS-Cannon]].<ref name="Mortar commonality">{{cite news |last1=Wasserbly |first1=Daniel |title=FCS Mortar System Moving Ahead in Wake of Its 'Big Brother' Cannon |url=https://www.jstor.org/stable/24826636 |access-date=18 February 2022 |work=Inside the Army |issue= |
The NLOS-M had high commonality with the [[XM1203 Non-Line-of-Sight Cannon|NLOS-Cannon]].<ref name="Mortar commonality">{{cite news |last1=Wasserbly |first1=Daniel |title=FCS Mortar System Moving Ahead in Wake of Its 'Big Brother' Cannon |url=https://www.jstor.org/stable/24826636 |access-date=18 February 2022 |work=Inside the Army |issue=16 |publisher=Inside Washington Publishers |date=21 April 2008 |volume=20 |page=FCS Mortar System Moving Ahead in Wake of Its 'big Brother' Cannon |jstor=24826636 |archive-date=18 February 2022 |archive-url=https://web.archive.org/web/20220218072624/https://www.jstor.org/stable/24826636 |url-status=live }}</ref> |
||
===Recovery and Maintenance Vehicle=== |
===Recovery and Maintenance Vehicle=== |
||
[[File:XM1205 FRMV.jpg|thumb|right|XM1205 Field Recovery and Maintenance Vehicle (FRMV)]] |
[[File:XM1205 FRMV.jpg|thumb|right|XM1205 Field Recovery and Maintenance Vehicle (FRMV)]] |
||
The |
The XM1205 Field Recovery and Maintenance Vehicle (FRMV) was the [[armoured recovery vehicle]] and maintenance system for employment within both the unit of action (UA) and unit of employment (UE). |
||
The recovery vehicle was designed to hold a crew of three with additional space for three additional recovered crew.<ref name="Andrew Feickert" /> |
The recovery vehicle was designed to hold a crew of three with additional space for three additional recovered crew.<ref name="Andrew Feickert" /> |
||
Each UA would have a small number of 2–3 |
Each UA would have a small number of 2–3 soldier combat repair teams within the organic [[Forward Support Battalion]] to perform field maintenance requirements beyond the capabilities of the crew chief/crew, more in-depth battle damage assessment repair, and limited recovery operations. |
||
The FRMV was armed with a [[close combat]] support weapon (CCSW) and a 40 mm [[Mk 19 grenade launcher]]. |
The FRMV was armed with a [[close combat]] support weapon (CCSW) and a 40 mm [[Mk 19 grenade launcher]]. |
||
Line 194: | Line 201: | ||
[[File:XM1206 Infantry Carrier Vehicle.png|thumb|right|Artist's impression of the XM1206 Infantry Carrier Vehicle]] |
[[File:XM1206 Infantry Carrier Vehicle.png|thumb|right|Artist's impression of the XM1206 Infantry Carrier Vehicle]] |
||
The |
The XM1206 Infantry Carrier Vehicle (ICV) was a set of similar [[infantry fighting vehicle]]s for transporting and supporting ground troops. The ICV featured a crew of 2 and space for 9 passengers. |
||
It was armed with a 30 mm or |
It was armed with a 30 mm or 40 mm cannon<ref name="Andrew Feickert"/> and a 7.62 mm machine gun. |
||
The ICV family consists of four versions fitted for the specific roles of: a [[Company (military unit)|company]] commander; a [[platoon]] leader; rifle squad; and a weapons squad. All were visually similar to prevent targeting of a specific ICV versions.<ref name="Andrew Feickert"/> |
The ICV family consists of four versions fitted for the specific roles of: a [[Company (military unit)|company]] commander; a [[platoon]] leader; rifle squad; and a weapons squad. All were visually similar to prevent targeting of a specific ICV versions.<ref name="Andrew Feickert"/> |
||
Line 202: | Line 209: | ||
A platoon would consist of a platoon leader vehicle, three rifle squad vehicles and a weapon squad vehicle.<ref>[https://web.archive.org/web/20080204164318/http://www.army.mil/fcs/icv.html Infantry Carrier Vehicle (ICV)] army.mil</ref> |
A platoon would consist of a platoon leader vehicle, three rifle squad vehicles and a weapon squad vehicle.<ref>[https://web.archive.org/web/20080204164318/http://www.army.mil/fcs/icv.html Infantry Carrier Vehicle (ICV)] army.mil</ref> |
||
The Rifle Squad ICV<ref name="Andrew Feickert"/> and Weapons Squad ICV each carry a 9-person infantry |
The Rifle Squad ICV<ref name="Andrew Feickert"/> and Weapons Squad ICV each carry a 9-person infantry squad into close battle and support the squad by providing offensive and defensive fire, while carrying the majority of the soldiers' equipment. The ICV can move, shoot, communicate, detect threats, and protect crew and critical components under all weather conditions, day or night. |
||
The squad would have access to Army and joint fire delivery systems from external sources (e.g. the NLOS-Cannon) to enhance the squad's range, precision, or quantity of fire. [[FCS Network |
The squad would have access to Army and joint fire delivery systems from external sources (e.g. the NLOS-Cannon) to enhance the squad's range, precision, or quantity of fire. [[FCS Network]]ing with other components of the unit of action permits rapid identification of targets and improves [[situational awareness]]. |
||
===Medical Vehicle=== |
===Medical Vehicle=== |
||
[[File:XM1207 MV-E and XM1208 MV-T.jpg|thumb|right|XM1207 Medical Vehicle-Evacuation (MV-E)/XM1208 Medical Vehicle-Treatment (MV-T)]] |
[[File:XM1207 MV-E and XM1208 MV-T.jpg|thumb|right|XM1207 Medical Vehicle-Evacuation (MV-E)/XM1208 Medical Vehicle-Treatment (MV-T)]] |
||
The |
The XM1207 and XM1208 Medical Vehicle was an [[Ambulance#Military use|armoured ambulance]] designed to provide advanced [[Physical trauma|trauma]] [[life support]] within one hour to critically injured [[soldier]]s. The Medical Vehicle serves as the primary medical system within the unit of action (UA) with two mission modules: "Evacuation" and "Treatment".<ref name="Andrew Feickert"/> |
||
The XM1207 Medical Vehicle–Evacuation ( |
The XM1207 Medical Vehicle–Evacuation (MV—E) vehicle allows trauma specialists, maneuvering with combat forces, to be closer to the casualty's point-of-injury and was to be used for casualty evacuation.<ref name="Andrew Feickert"/> |
||
The XM1208 Medical Vehicle–Treatment (MV–T) vehicle enhances the ability to provide Advanced Trauma Management (ATM)/Advanced Trauma Life Support (ATLS) treatments and procedures forward for more rapid casualty interventions and clearance of the battlespace.<ref name="Andrew Feickert"/> |
The XM1208 Medical Vehicle–Treatment (MV–T) vehicle enhances the ability to provide Advanced Trauma Management (ATM)/Advanced Trauma Life Support (ATLS) treatments and procedures forward for more rapid casualty interventions and clearance of the battlespace.<ref name="Andrew Feickert"/> |
||
⚫ | Both would have crews of four and the capability to carry four patients. Both Medical Vehicle mission modules were intended to be capable of conducting medical procedures and treatments using installed networked [[telemedicine]] interfaces:<ref name="Andrew Feickert"/> Medical Communications for Combat Casualty Care, and the Theater Medical Information Program (TMIP). |
||
Both would have four-man crews and the capability to |
|||
⚫ | carry four patients. Both Medical Vehicle mission modules |
||
===Command and Control Vehicle=== |
===Command and Control Vehicle=== |
||
[[File:XM1209 C2V.png|thumb|right|XM1209 Command and Control Vehicle (C2V)]] |
[[File:XM1209 C2V.png|thumb|right|XM1209 Command and Control Vehicle (C2V)]] |
||
⚫ | |||
{{buzzword|section|date=September 2021}} |
|||
⚫ | |||
The C2V was to have had a crew of two and carry four staff officers.<ref name="Andrew Feickert"/> |
The C2V was to have had a crew of two and carry four staff officers.<ref name="Andrew Feickert"/> |
||
Line 227: | Line 232: | ||
It was to be located within the headquarters sections at each echelon of the unit of action down to the company level, and with its integrated command, control, and communications equipment suite, was to make command and control on the move possible. |
It was to be located within the headquarters sections at each echelon of the unit of action down to the company level, and with its integrated command, control, and communications equipment suite, was to make command and control on the move possible. |
||
The C2Vs were to contain all the interfaces required to enable the commander to |
The C2Vs were to contain all the interfaces required to enable the commander to use the [[Department of Defense Architecture Framework|C4ISR]] network. In addition, the C2Vs were meant to make possible the establishment, maintenance and distribution of a [[common operating picture]] fused from the friendly, enemy, civilian, [[weather]] and terrain situations, while on the move. The crew was to use its integrated C4ISR suite (communication, [[computer]]s and sensor systems) to receive, analyze and transmit [[military tactics|tactical]] information via voice, video and data inside and outside the unit of action. |
||
The C2V was also planned to employ unmanned systems, such as [[unmanned aerial vehicle]]s (UAVs).<ref name="Andrew Feickert"/> |
The C2V was also planned to employ unmanned systems, such as [[unmanned aerial vehicle]]s (UAVs).<ref name="Andrew Feickert"/> |
||
Line 235: | Line 240: | ||
* [[Armored Systems Modernization]], a wide-ranging U.S. Army combat vehicle acquisition program cancelled after the end of the Cold War |
* [[Armored Systems Modernization]], a wide-ranging U.S. Army combat vehicle acquisition program cancelled after the end of the Cold War |
||
* [[XM2001 Crusader]], a canceled U.S. Army self-propelled howitzer |
* [[XM2001 Crusader]], a canceled U.S. Army self-propelled howitzer |
||
* [[Combat Vehicle Reconnaissance (Tracked)]], similar British equivalent |
|||
* [[Armata Universal Combat Platform]] Similar Russian program |
|||
==References== |
==References== |
||
Line 240: | Line 247: | ||
== Sources == |
== Sources == |
||
*{{cite report|url=https://apps.dtic.mil/dtic/tr/fulltext/u2/a582405.pdf|title=Lessons from the Army's Future Combat Systems Program|last1=Pernin|first1=Christopher|last2=Axelband|first2=Elliot|date=2012|publisher=RAND Corporation|last3=Drezner|first3=Jeffrey|last4=Dille|first4=Brian|last5=Gordon IV|first5=John|last6=Held|first6=Bruce|last7=McMahon|first7=Scott|last8=Perry|first8=Walter|last9=Rizzi|first9=Christopher|last11=Wilson|first10=Akhil|first11=Peter|last12=Sollinger|last10=Shah|via=Defense Technical Information Center|first12=Sollinger}} |
*{{cite report|url=https://www.rand.org/content/dam/rand/pubs/monographs/2012/RAND_MG1206.pdf|archive-url=https://web.archive.org/web/20200325115822/https://apps.dtic.mil/dtic/tr/fulltext/u2/a582405.pdf|url-status=live|archive-date=March 25, 2020|title=Lessons from the Army's Future Combat Systems Program|last1=Pernin|first1=Christopher|last2=Axelband|first2=Elliot|date=2012|publisher=RAND Corporation|last3=Drezner|first3=Jeffrey|last4=Dille|first4=Brian|last5=Gordon IV|first5=John|last6=Held|first6=Bruce|last7=McMahon|first7=Scott|last8=Perry|first8=Walter|last9=Rizzi|first9=Christopher|last11=Wilson|first10=Akhil|first11=Peter|last12=Sollinger|last10=Shah|via=Defense Technical Information Center|first12=Sollinger}} |
||
*{{cite report |title=The |
*{{cite report |title=The Army's Future Combat Systems Program and Alternatives |date=August 2006 |url=https://www.cbo.gov/sites/default/files/109th-congress-2005-2006/reports/08-02-army.pdf |access-date=21 February 2022 |publisher=Congressional Budget Office}} |
||
* [http://www.army.mil/fcs/whitepaper/FCSWhitepaper(11_Apr_06).pdf "FCS Whitepaper"]. U.S. Army, 11 April 2006. |
* [http://www.army.mil/fcs/whitepaper/FCSWhitepaper(11_Apr_06).pdf "FCS Whitepaper"] {{Webarchive|url=https://web.archive.org/web/20070314012829/http://www.army.mil/fcs/whitepaper/FCSWhitepaper(11_Apr_06).pdf |date=2007-03-14 }}. U.S. Army, 11 April 2006. |
||
* [http://www.globalsecurity.org/military/systems/ground/fcs-mortar.htm Non-Line-Of-Sight Mortar (NLOS-M)]. Globalsecurity.org |
* [http://www.globalsecurity.org/military/systems/ground/fcs-mortar.htm Non-Line-Of-Sight Mortar (NLOS-M)]. Globalsecurity.org |
||
{{US Army}} |
{{US Army}} |
||
Line 248: | Line 255: | ||
==External links== |
==External links== |
||
{{External links|date=February 2016}} |
{{External links|date=February 2016}} |
||
{{Commons category|Future Combat Systems |
{{Commons category|Future Combat Systems Manned Ground Vehicles}} |
||
* [http://opencrs.com/document/RL32888 RL32888 "The Army's Future Combat System (FCS): Background and Issues for Congress"]. Congressional Research Service, May 29, 2009. |
* [http://opencrs.com/document/RL32888 RL32888 "The Army's Future Combat System (FCS): Background and Issues for Congress"]. Congressional Research Service, May 29, 2009. |
||
* [http://www.globalsecurity.org/military/systems/ground/fcs-mgv.htm Manned Ground Vehicles page on GlobalSecurity.org] |
* [http://www.globalsecurity.org/military/systems/ground/fcs-mgv.htm Manned Ground Vehicles page on GlobalSecurity.org] |
||
Line 262: | Line 269: | ||
* [https://web.archive.org/web/20080204015746/http://www.army.mil/fcs/nlosm.html US Army NLOS-M page (archived version)] |
* [https://web.archive.org/web/20080204015746/http://www.army.mil/fcs/nlosm.html US Army NLOS-M page (archived version)] |
||
* [https://web.archive.org/web/20080204015751/http://www.army.mil/fcs/rsv.html US Army RSV page (archived version)] |
* [https://web.archive.org/web/20080204015751/http://www.army.mil/fcs/rsv.html US Army RSV page (archived version)] |
||
* [https://web.archive.org/web/20050307131206/http://www.uniteddefense.com/prod/fcs_w.htm United Defense FCS Wheeled (archived version)] |
|||
* [https://web.archive.org/web/20050307125828/http://www.uniteddefense.com/prod/fcs_t.htm United Defense FCS Tracked (archived version)] |
|||
{{FCS Subsystems}} |
{{FCS Subsystems}} |
||
Line 271: | Line 280: | ||
[[Category:DARPA projects]] |
[[Category:DARPA projects]] |
||
[[Category:DARPA vehicles]] |
[[Category:DARPA vehicles]] |
||
[[Category:BAE Systems land vehicles]] |
|||
[[Category:General Dynamics land vehicles]] |
|||
[[Category:United Defense]] |
Latest revision as of 05:07, 25 August 2024
FCS Manned Ground Vehicles | |
---|---|
Type | Tracked armored fighting vehicles |
Place of origin | United States of America |
Production history | |
Designer | BAE Systems and General Dynamics |
Designed | 2002–2009 |
Variants | Reconnaissance and Surveillance Vehicle, Mounted Combat System, Non-Line-of-Sight Cannon, Non-Line-of-Sight Mortar, Field Recovery and Maintenance Vehicle, Infantry Carrier Vehicle, Medical Vehicle, Command and Control Vehicle |
Specifications | |
Crew | Varies from 2–4 depending on vehicle |
Secondary armament | Most vehicles armed with a machine gun |
Engine | Detroit Diesel 5L890 |
The Manned Ground Vehicles (MGV) was a family of lighter and more transportable ground vehicles developed by Boeing and subcontractors BAE Systems and General Dynamics as part of the U.S. Army's Future Combat Systems (FCS) program. The MGV program was intended as a successor to the Stryker of the Interim Armored Vehicle program.
The MGV program was set in motion in 1999 by Army Chief of Staff Eric Shinseki.
The MGVs were based on a common tracked vehicle chassis.[1] The lead vehicle, and the only one to be produced as a prototype, was the Non-Line-of-Sight Cannon. Seven other vehicle variants were to follow.
The MGV vehicles were conceived to be exceptionally lightweight (initially capped at 18 tons base weight) to meet the Army's intra-theatre air mobility requirements. The vehicles that the Army sought to replace with the MGVs ranged from 30 to 70 tons. In order to reduce weight, the Army substituted armor with passive and active protection systems.
The FCS program was terminated in 2009 due to concerns about the program's affordability and technology readiness. The MGV program was succeeded by the Ground Combat Vehicle program, which was canceled in 2014.
History
[edit]Initial Technology Demonstrator Vehicle by United Defense yielded both tracked and wheeled prototypes.[2] Only the tracked variant was pursued further.
FCS-Wheeled (FCS-W) was an early concept designed to demonstrate a hybrid-electric drive system and two-man cockpit workstations. A Technology Demonstrator Vehicle was built by United Defense and was unveiled in 2002.
FCS-W was designed to deliver a top road speed of 75 mph and a top cross-country speed of 40 mph. The vehicle's armor utilized armor similar to the tracked variant but was lighter. The vehicle would have also had some type of active protection system. The arrangement of the turbine and drive motor provided for a two-man, side-by-side cockpit and a sizable payload compartment.
In May 2000, DARPA awarded four contracts to four industry teams to develop Future Combat Systems designs and in March 2002, the Army chose Boeing and Science Applications International Corporation (SAIC) to serve as the "lead systems integrators" to oversee the development and eventual production of the FCS’ 18 systems.[3] In October 2002 United Defense (UD) and Boeing/SAIC signed a memorandum of understanding to bring the Objective Force Non-Line-of-Sight Cannon under the FCS umbrella.[4]
In January 2003, Boeing and SAIC reached an agreement with General Dynamics Land Systems (GDLS) and United Defense LP (UDLP) to develop the MGVs. UDLP was responsible for leading development of five of the vehicles (including the NLOS-C) while GDLS took responsibility for leading development of the other three.[5]
In May 2003 the Defense Acquisition Board (DAB) approved the FCS’ next acquisition phase, and in August 2004 Boeing and SAIC awarded contracts to 21 companies to design and build its various platforms and hardware and software.[3]
In December 2003, GDLS received a $2 billion MGV design contract from Boeing. Per the contract, GDLS would produce 8 Mounted Combat Systems, 6 command and control vehicles, and 4 reconnaissance and surveillance vehicle prototypes.[6]
In March 2005, the Army's acquisition chief Claude Bolton told the House Armed Services subcommittee that getting the MGV's weight to under 19-tons was proving difficult.[7] In 2005 the Army relented on the vehicle's requirement for roll-off C-130 transportability. Relaxing the C-130 requirement to allow vehicles to be transported in a stripped-down configuration allowed the weight cap to be increased from 18 tons per vehicle to 24 tons.[8]
In August 2005, GDLS selected Detroit Diesel's 5L890 to power the eight variants.[9]
The Department of Defense announced budget cuts in April 2009,[10] which resulted in the cancellation of the FCS Manned Ground Vehicles family.[11][12] The Army issued a stop-work order for MGV and NLOS-C efforts in June. In July the army terminated the MGV, but not the NLOS-C. In the news release the Army said cancelation would "negatively impact" NLOS-C development but said it was seeking a "viable path forward" for the NLOS-C.[13]
The DoD determined that the proposed FCS vehicle designs would not provide sufficient protection against IEDs.[14]
The Army planned to restart from the beginning on manned ground vehicles.[15] The program's heavier successor, the Ground Combat Vehicle, was cancelled in 2014.
Design
[edit]In order to reduce weight, the Army substituted armor with passive and active protection systems. This was hoped to provide a level of protection similar to the legacy armored vehicles being replaced.[16]
Most vehicles were protected with hard-kill active protection systems capable of defeating most threats.[17] The armor was a unique secret matrix that may be utilized by industry in the Ground Combat Vehicle program.
The common MGV chassis was required to provide full protection from 30 mm and 45 mm cannon fire in a 60-degree arc opening towards the front of the vehicle. 360-degree protection from small arms fire up to 14.5 mm heavy machine gun and 155 mm artillery shell air-bursts was planned. Protection from higher caliber rounds as well as anti-tank guided missiles would be provided by an active protection system manufactured by Raytheon known as "Quick Kill".
Use of a common chassis was to reduce the need for specialized training of personnel and allow for faster fielding of repairs. The MGV platform utilized a hybrid diesel-electric propulsion system. The MGV also employed numerous weight-saving features, including composite armor, composite and titanium structural elements, and continuous band tracks.
The 30 mm Mk44 Bushmaster II chain gun on the reconnaissance and surveillance vehicle and infantry carrier vehicle provided greater firepower, yet weighed 25% less than the M242 Bushmaster it would replace.[16]
Weight growth
[edit]Weight at full combat capability (FCC) was raised to 24 tons in June 2006, then to 27.4 tons in January. According to a former program official, MGV chassis weights entered a "death spiral," as any weight growth to the subsystems cascaded to the whole system (e.g. heavier armor required a stronger suspension to carry it). FCC weight was eventually raised to 30 tons.[18]
TRADOC was slow to update its expectations for the MGV. TRADOC recommended removing C-130 transportability requirements in 2007 and raising the weight limit to 27.4 tons in requirements drafted in 2007. However, TRADOC's essential combat configuration MGV weight remained capped at 38,000 pounds (19 tons) until the program's cancelation.[18]
Armor and countermeasures
[edit]MGVs in essential combat configuration were required to have all-around protection from 14.5 mm caliber ammunition, and 30 mm from the front. This requirement was changed later that year to 14.5 mm protection with add-on armor.[18]
In 2008, the Army added a requirement for an add-on V-hull kit.[18]
Vehicles
[edit]Name | Developer[19] | Vehicle replaced[20] | Number per brigade[20] |
---|---|---|---|
XM1201 Reconnaissance and Surveillance Vehicle (RSV) | General Dynamics (GD) | M3 Bradley | 30 |
XM1202 Mounted Combat System (MCS) | GD | M1 Abrams | 60 |
XM1203 Non-Line-of-Sight Cannon (NLOS-C) | BAE Systems (BAE) | M109 howitzer | 18 |
XM1204 Non-Line-of-Sight Mortar (NLOS-M) | BAE | M1064 mortar carrier | 24 |
XM1205 Field Recovery and Maintenance Vehicle (FRMV) | BAE | M88 Recovery Vehicle | 10 |
XM1206 Infantry Carrier Vehicle (ICV) | BAE | M2 Bradley and M113 | 102 |
XM1207 and XM1208 Medical Vehicle (MV) | BAE | N/A | 29 |
XM1209 Command and Control Vehicle (C2V) | GD | M113 command variant | 49 |
Reconnaissance and Surveillance Vehicle
[edit]The XM1201 Reconnaissance and Surveillance Vehicle (RSV) featured a suite of advanced sensors to detect, locate, track, classify and automatically identify targets under all climatic conditions, day or night.
The suite included a mast-mounted, long-range optoelectronic infrared sensor, an emitter mapping sensor for radio frequency interception and direction finding, chemical sensor and a multifunction radio frequency sensor.
The RSV also features the onboard capability to conduct automatic target detection, aided target recognition and level-one sensor fusion. To further enhance the scout capabilities, the RSV was also to be equipped with Unattended Ground Sensors, a Small Unmanned Ground Vehicle with various payloads and two unmanned aerial vehicles. It was to be armed with a 30 mm MK44 autocannon and a coaxial 7.62 mm M240 machine gun.
Mounted Combat System
[edit]The XM1202 Mounted Combat System (MCS) was planned as a successor to the M1 Abrams main battle tank.[16]
The MCS was to provide both direct and beyond-line-of-sight ('indirect') firepower capability and allowed for in-depth destruction of point targets up to 8 km (5.0 mi) away.[16]
As of 2009 the MCS was to have had a crew of two and to be armed with an autoloaded 120 mm main gun, a 12.7 mm (.50) caliber machine gun, and a 40 mm automatic grenade launcher.[21]
The MCS was intended to deliver precision fire at a rapid rate, in order to destroy multiple targets at standoff ranges quickly, and would complement the other systems in the unit of action. It would be capable of providing direct support to the dismounted infantry in an assault, defeating bunkers, and breaching walls during tactical assaults. It was also intended to be highly mobile, in order to maneuver out of contact and into positions of advantage; given the vehicle's light weight, this was especially important.
In May 2003 Army officials revealed a computer model of the MCS, allowing reporters to view the inside of the vehicle through a Cave automatic virtual environment. This concept used a crew of three.[22]
The Picatinny Arsenal XM360 tank gun had been selected by September 2006.[23] tank gun underwent test firing at Aberdeen Proving Ground beginning in March 2008.[24] General Dynamics Armament and Technical Products was awarded a $14 million contract in 2007 to develop the ammunition handling system.[25] In January 2008, Raytheon was awarded a $232 million contract to develop the XM1111 Mid-Range Munition. The munition had been test fired from an M1 Abrams as early as March 2007.[26] The Army tested a 27-round magazine ammunition handling system at Aberdeen Proving Ground by July 2008.[27]
This was considered the most complex of the three vehicles GDLS was contracted to build.[28]
Non-Line-of-Sight Cannon
[edit]The XM1203 Non-Line-of-Sight Cannon (NLOS-C) was a 155 mm self-propelled howitzer to succeed the M109 howitzer. This was the lead vehicle effort, and most far along when the program was terminated in 2009. The NLOS-C used technology from the canceled XM2001 Crusader project.
The NLOS-C incorporated the autoloader from the Crusader project.[29] The NLOS-C featured an improved fire rate over the M109. It was capable of multiple rounds simultaneous impact (MRSI), where the cannon fires a sequence of several rounds at different trajectories such that the rounds all hit the same target at the same time. The system had the ability to switch shell types quickly on a one-by-one basis.
Improvements in the refueling arrangements and automation of ammunition reloading reduced the amount of time spent on resupply and during which the gun would be unavailable for combat support. This also allowed the system to use a crew of two instead of five.
The NLOS-C had a high commonality with the NLOS-Mortar vehicle.[30]
The first NLOS-C prototype was rolled out in May 2008. Eight prototypes were delivered to the U.S. Army's Yuma Proving Ground in Arizona by 2009.[31]
Although Defense Secretary Robert Gates ended the MGV program in April 2009, Congress had directed that the Army continue working on the NLOS-C as a separate initiative. The Pentagon directed the Army to cancel the NLOS-C in December.[32]
Non-Line-of-Sight Mortar
[edit]The XM1204 Non-Line-of-Sight Mortar (NLOS-M) was a turreted mortar carrier with a crew of four.[16]
The NLOS-M had a breech-loading, gun-mortar that fired 120 mm munitions including the Precision Guided Mortar Munition (PGMM). It had a fully automated firing control system and a manually assisted, semi-automated ammunition loading system.
The NLOS-M would carry an 81 mm mortar for dismounted operations away from the carrier.[16]
The NLOS-M provides fires on-demand to engage complex and simultaneous target sets. As part of an NLOS-M battery, individual NLOS-M vehicles would have provided precision-guided rounds to destroy high-value targets, protective fires to suppress and obscure the enemy, and illumination fires.
The FCS command, control, communications, computers, intelligence, surveillance and reconnaissance (C4ISR) network would have enabled the NLOS-M fire control system to conduct semi- to autonomous computation of technical fire direction, automatic gun lay, preparation of the ammunition for firing, and mortar round firing.
In January 2003 United Defense, now part of BAE Systems, was selected by the Army and the FCS lead systems integrators (Boeing and SAIC) to develop and build the NLOS-M.
The NLOS-M had high commonality with the NLOS-Cannon.[30]
Recovery and Maintenance Vehicle
[edit]The XM1205 Field Recovery and Maintenance Vehicle (FRMV) was the armoured recovery vehicle and maintenance system for employment within both the unit of action (UA) and unit of employment (UE).
The recovery vehicle was designed to hold a crew of three with additional space for three additional recovered crew.[16]
Each UA would have a small number of 2–3 soldier combat repair teams within the organic Forward Support Battalion to perform field maintenance requirements beyond the capabilities of the crew chief/crew, more in-depth battle damage assessment repair, and limited recovery operations.
The FRMV was armed with a close combat support weapon (CCSW) and a 40 mm Mk 19 grenade launcher.
The FMRV was deferred in 2003, then restored in July 2004.[33]
Infantry Carrier Vehicle
[edit]The XM1206 Infantry Carrier Vehicle (ICV) was a set of similar infantry fighting vehicles for transporting and supporting ground troops. The ICV featured a crew of 2 and space for 9 passengers.
It was armed with a 30 mm or 40 mm cannon[16] and a 7.62 mm machine gun.
The ICV family consists of four versions fitted for the specific roles of: a company commander; a platoon leader; rifle squad; and a weapons squad. All were visually similar to prevent targeting of a specific ICV versions.[16]
A platoon would consist of a platoon leader vehicle, three rifle squad vehicles and a weapon squad vehicle.[34]
The Rifle Squad ICV[16] and Weapons Squad ICV each carry a 9-person infantry squad into close battle and support the squad by providing offensive and defensive fire, while carrying the majority of the soldiers' equipment. The ICV can move, shoot, communicate, detect threats, and protect crew and critical components under all weather conditions, day or night.
The squad would have access to Army and joint fire delivery systems from external sources (e.g. the NLOS-Cannon) to enhance the squad's range, precision, or quantity of fire. FCS Networking with other components of the unit of action permits rapid identification of targets and improves situational awareness.
Medical Vehicle
[edit]The XM1207 and XM1208 Medical Vehicle was an armoured ambulance designed to provide advanced trauma life support within one hour to critically injured soldiers. The Medical Vehicle serves as the primary medical system within the unit of action (UA) with two mission modules: "Evacuation" and "Treatment".[16]
The XM1207 Medical Vehicle–Evacuation (MV—E) vehicle allows trauma specialists, maneuvering with combat forces, to be closer to the casualty's point-of-injury and was to be used for casualty evacuation.[16]
The XM1208 Medical Vehicle–Treatment (MV–T) vehicle enhances the ability to provide Advanced Trauma Management (ATM)/Advanced Trauma Life Support (ATLS) treatments and procedures forward for more rapid casualty interventions and clearance of the battlespace.[16]
Both would have crews of four and the capability to carry four patients. Both Medical Vehicle mission modules were intended to be capable of conducting medical procedures and treatments using installed networked telemedicine interfaces:[16] Medical Communications for Combat Casualty Care, and the Theater Medical Information Program (TMIP).
Command and Control Vehicle
[edit]The XM1209 Command and Control Vehicle (C2V) was to provide for information management of the integrated network of communications and sensor capability within the unit of action and provide the tools for commanders to synchronize their knowledge with leadership.
The C2V was to have had a crew of two and carry four staff officers.[16]
It was to be located within the headquarters sections at each echelon of the unit of action down to the company level, and with its integrated command, control, and communications equipment suite, was to make command and control on the move possible.
The C2Vs were to contain all the interfaces required to enable the commander to use the C4ISR network. In addition, the C2Vs were meant to make possible the establishment, maintenance and distribution of a common operating picture fused from the friendly, enemy, civilian, weather and terrain situations, while on the move. The crew was to use its integrated C4ISR suite (communication, computers and sensor systems) to receive, analyze and transmit tactical information via voice, video and data inside and outside the unit of action.
The C2V was also planned to employ unmanned systems, such as unmanned aerial vehicles (UAVs).[16]
See also
[edit]- Interim Armored Vehicle, a U.S. Army program that resulted in the acquisition of the Stryker
- Armored Systems Modernization, a wide-ranging U.S. Army combat vehicle acquisition program cancelled after the end of the Cold War
- XM2001 Crusader, a canceled U.S. Army self-propelled howitzer
- Combat Vehicle Reconnaissance (Tracked), similar British equivalent
- Armata Universal Combat Platform Similar Russian program
References
[edit]- ^ Manned Ground Vehicle overview Archived 2008-12-30 at the Wayback Machine. Boeing, 7 August 2008.
- ^ "Future Combat System Prototype Vehicles". GlobalSecurity.org. 30 September 2006. Archived from the original on 2 September 2009. Retrieved 6 May 2010.
- ^ a b Feickert, Andrew (5 May 2006). "The Army's Future Combat System (FCS): Background and Issues for Congress" (PDF). Archived (PDF) from the original on March 12, 2021. Retrieved 12 May 2017. This article incorporates text from this source, which is in the public domain.
- ^ "Army Working To Bring FCS, NLOS Cannon Efforts Together". Defense Daily. 22 October 2002. Archived from the original on 21 November 2018. Retrieved 14 May 2017.
- ^ Hsu, Emily (27 January 2003). "Team Will Design Eight Manned Ground Vehicles for FCS: GD, United Defense Team Up for Army's Future Combat Systems". Inside the Army. Vol. 15, no. 4. Inside Washington Publishers. pp. 2–3. JSTOR 24819825. Archived from the original on 17 February 2022. Retrieved 17 February 2022.
- ^ Hamilton, Robert A. (16 December 2003). "GD wins $2B design contract for Army 'tanks'". The Day. Retrieved 10 February 2024.
- ^ Jen DiMascio, Jen (21 March 2005). "Both Face Technical Hurdles: JTRS and Manned Ground Vehicles Critical to Success of Fcs, GAO Says". Inside the Army. Vol. 17, no. 11. Inside Washington Publishers. pp. 12–13. JSTOR 24823654. Archived from the original on 21 February 2022. Retrieved 21 February 2022.
- ^ Erwin, Sandra (1 November 2005). "For Army's Future Combat Vehicles, Flying by C-130 No Longer Required". National Defense. Retrieved 14 May 2017.[dead link ]
- ^ Roque, Ashley (29 August 2005). "$47 Million Contract Awarded: Army Selects Diesel Engine to Power FCS Manned Ground Vehicles". Inside the Army. Vol. 17, no. 34. Inside Washington Publishers. pp. 1, 9–10. JSTOR 24824724. Archived from the original on 17 February 2022. Retrieved 17 February 2022.
- ^ "Military Budget Reflects a Shift in U.S. Strategy" Archived 2017-06-28 at the Wayback Machine. New York Times, April 7, 2009. Retrieved in April 2009.
- ^ Cavallaro, Gina (June 11, 2009). "Panel to discuss new ground combat vehicle". Army Times. Retrieved June 14, 2009.
- ^ McLeary, Paul. "U.S. Army Ground Vehicles Up and Down"[permanent dead link ]. Aviation Week, 8 May 2009.
- ^ Jagirdar, Sarabjit (20 July 2009). "ARMY PARTIALLY TERMINATES FUTURE COMBAT SYSTEMS MANNED GROUND VEHICLE". US Fed News Service. Archived from the original on 16 November 2018. Retrieved 12 May 2017.
- ^ "Contractors vie for lucrative vehicle work" . The Hill, August 5, 2010. Retrieved on August 21, 2010.
- ^ Military Deputy for Budget Office of the Assistant Secretary of the Army (Financial Mgt and Comptroller) Lt. Gen. Edgar Stanton and Acting Director, Army Budget Office William Campbell May 07, 2009, News Transcript Archived 2009-05-30 at the Wayback Machine, U.S. Department of Defense, Office of the Assistant Secretary of Defense (Public Affairs).
- ^ a b c d e f g h i j k l m n o p Andrew Feickert (May 29, 2009). "The Army's Future Combat Systems Program" (PDF). Archived from the original (PDF) on June 29, 2011. Retrieved March 7, 2011.
- ^ "GCV, Industry Day #1". Contracting.tacom.army.mil. Archived from the original on 2011-07-22. Retrieved 2011-03-31.
- ^ a b c d Pernin et al, Ch. 5, p. 95-118.
- ^ Pernin et al, p. 197.
- ^ a b CBO, Ch. 2, p. 17-27.
- ^ "The Army's Future Combat System (FCS): Background and Issues for Congress". DTIC.mil. 28 May 2009. Archived from the original on 4 June 2011. Retrieved 31 March 2011.
- ^ Hsu, Emily (26 May 2003). "Virtual tool to aid in FCS vehicle designs: ARMY REVEALS PRELIMINARY DESIGN FOR FCS MOUNTED COMBAT SYSTEM". Inside the Army. Vol. 15, no. 21. Retrieved 10 February 2024.
- ^ "Fifteen Picatinny employees receive Army's top research award". AIM Jefferson. 1 September 2006. p. A8. Retrieved 10 February 2024.
- ^ Roosevelt, Ann (26 March 2008). "Advanced 120mm Gun For FCS Mounted Combat System In Safety Testing". Defense Daily. Archived from the original on 15 November 2018. Retrieved 12 May 2017.
- ^ "General Dynamics in Lincoln developing tank ammo magazines". The Lincoln Journal Star. 22 April 2007. Retrieved 10 February 2024.
- ^ "Raytheon wins $232.2 million contract". Arizona Daily Star. 3 January 2008. Retrieved 10 February 2024.
- ^ Wasserby, Daniel (28 July 2008). "Live-fire evaluation slated for February: ARMY BEGINS TESTING FCS MOUNTED COMBAT SYSTEMS' TURRET COMPONENT". Inside the Army. Vol. 20, no. 30. Retrieved 10 February 2024.
- ^ Bennett, Jeff (16 December 2003). "General Dynamics gets Army Contract". Detroit Free Press. Retrieved 10 February 2024.
- ^ "M-109 Replacement Enters Production". Strategypage.com. 2007-07-24. Archived from the original on 2012-01-18. Retrieved 2011-03-31.
- ^ a b Wasserbly, Daniel (21 April 2008). "FCS Mortar System Moving Ahead in Wake of Its 'Big Brother' Cannon". Inside the Army. Vol. 20, no. 16. Inside Washington Publishers. p. FCS Mortar System Moving Ahead in Wake of Its 'big Brother' Cannon. JSTOR 24826636. Archived from the original on 18 February 2022. Retrieved 18 February 2022.
- ^ C. Todd Lopez (2008-05-30). "First FCS Manned Vehicle to Make Public Debut". Army.mil. Archived from the original on 2010-04-12. Retrieved 2011-03-31.
- ^ Censer, Marjorie (14 December 2009). "Promising thorough vehicle review ...: DOD Acquisition Chief Formally Terminates Army's NLOS Cannon". Inside the Army. Vol. 21, no. 49. Inside Washington Publishers. JSTOR 24831487. Archived from the original on 18 February 2022. Retrieved 18 February 2022.
- ^ Pernin et al, Ch. 8, p. 191-246.
- ^ Infantry Carrier Vehicle (ICV) army.mil
Sources
[edit]- Pernin, Christopher; Axelband, Elliot; Drezner, Jeffrey; Dille, Brian; Gordon IV, John; Held, Bruce; McMahon, Scott; Perry, Walter; Rizzi, Christopher; Shah, Akhil; Wilson, Peter; Sollinger, Sollinger (2012). Lessons from the Army's Future Combat Systems Program (PDF) (Report). RAND Corporation. Archived (PDF) from the original on March 25, 2020 – via Defense Technical Information Center.
- The Army's Future Combat Systems Program and Alternatives (PDF) (Report). Congressional Budget Office. August 2006. Retrieved 21 February 2022.
- "FCS Whitepaper" Archived 2007-03-14 at the Wayback Machine. U.S. Army, 11 April 2006.
- Non-Line-Of-Sight Mortar (NLOS-M). Globalsecurity.org
This article incorporates public domain material from websites or documents of the United States Army.
External links
[edit]This article's use of external links may not follow Wikipedia's policies or guidelines. (February 2016) |
- RL32888 "The Army's Future Combat System (FCS): Background and Issues for Congress". Congressional Research Service, May 29, 2009.
- Manned Ground Vehicles page on GlobalSecurity.org
- StrategyPage.com article
- First Round fired from 38-Calibre NLOS Cannon
- US Army FCS page with MGVs listed (archived version)
- US Army MCS page (archived version)
- US Army NLOS-C page (archived version)
- US Army C2V page (archived version)
- US Army ICV page (archived version)
- US Army FRMV page (archived version)
- US Army MV-T/MV-E page (archived version)
- US Army NLOS-M page (archived version)
- US Army RSV page (archived version)
- United Defense FCS Wheeled (archived version)
- United Defense FCS Tracked (archived version)