We have the Taiwanese
CM-32 however it seems like we missed both the
CM-33 and
CM-34. along the way.
Not so much worried about the CM-33 but, the
CM-34 though sharing the
same chassis as its predecessors; comes in at
2 tons heavier part of that is due to the turret but the rest has to be I suspect due to some kind of applique armor upgrade as well.
They are in service as
APC/IFV and
120mm mortar carrier in regard to the
CM-34.
Track for
120mm/82mm mortar carrier for the
CM-32 and likewise in regard the
CM-34 also with the
81mm mortar carrier.
Starting with the
CM-32 tests and a PROTOTYPE(s) were built for a "
Fire Support" version with both a
105mm and
120mm.
This did not materialize for the
CM-32. For the
CM-34 PROTOTYPE testing should've been completed by the end of last year or
very early this year.
https://www.janes.com/osint-insights...v-for-delivery
"The vehicle is derived from the
common 6.35 m long, 2.7 m wide, and 2.2 m high welded steel hull
also used by the in-service CM-32 and
CM-33 Cloud Leopard armoured personnel carriers (APCs), although the
CM-34 has a combat weight of 24 tonnes as opposed to the
22 tonnes of the earlier variants."
What perplexes me is why there are no
AT versions.
They have the following
NOW for their helos they wouldn't to modify them much also they've been operating
TOW for decades.
TAIPERS as noted is in the field and placing
TOW in the process.
"Comprising four major sub-sections (seeker, propulsion, control mechanism, and battery) and the optical fibre cable at the rear, the missile has a
smokeless solid-propellant rocket motor, which gives it a
cruise speed of about 200 m/s and a maximum strike range of
8 km. Hanwha has said the missile
can penetrate up to 1,000 mm of rolled homogeneous armour (RHA).
The DAPA spokesperson said the missile will arm the Korea Aerospace Industries (KAI) Light Armed Helicopter (LAH) and MUH-1 Marineon helicopters of the Republic of Korea Marine Corps (RoKMC) from
2024."
https://www.janes.com/osint-insights...-tank-missiles
Yeah, just realized I got this in the wrong thread @^!-****!
Regards,
Pat
