Oshkosh Awarded $1 Billion Order for 1,700 Additional M-ATVs
Aug 4, 2009 4:15 PM
Oshkosh Corporation (NYSE:OSK) announced that it has received an additional $1.06 billion delivery order from the U.S. Army Tank-automotive and Armaments Command Life Cycle Management Command (TACOM LCMC).
Oshkosh Defense will deliver 1,700 additional MRAP All Terrain Vehicles (M-ATV) to the U.S. Armed Forces by February 2010. The contract also includes aftermarket parts packages to be supplied by April 2010, along with field service support. The delivery order follows an initial $1.05 billion delivery order Oshkosh Defense received for 2,244 M-ATVs on June 30.
“At Oshkosh, our main focus is to ensure that M-ATVs are waiting in theater for the Warfighters when they arrive, rather than having the Warfighter wait for the vehicle,” said Robert G. Bohn, Oshkosh Corporation chairman and chief executive officer. “We are confident in our ability to ramp up production to 1,000 per month in December and this additional order will allow us to sustain that rate of production through February 2010.”
Oshkosh also announced it surpassed its first delivery requirements for 45 vehicles in July, by providing 46 units. Advance production of the M-ATV began weeks before the first delivery order was awarded.
The Oshkosh M-ATV’s mobility, which includes a 70 percent off-road profile capability, is achieved through the incorporation of the Oshkosh TAK-4 independent suspension system. The system has undergone more than 400,000 miles of government testing and is standard equipment on the more than 10,000 Medium Tactical Vehicle Replacements (MTVR) used by the Marines and Navy Seabees, and also on the Army’s next-generation Palletized Load System (PLS) and the Marine Corps’ Logistics Vehicle System Replacement (LVSR).
Oshkosh Defense teamed with Plasan North America to provide an advanced armor solution for the M-ATV. Plasan also developed the armor system used on more than 5,000 legacy MRAPs and thousands of Oshkosh Armored Cab MTVRs already in theater.
Acceptable Use Policy blog comments powered by Disqus
