The Chevy Silverado MD line covers conventional medium-duty trucks in the Class 4 and Class 5 segments. Now, Chevy Silverado MD customers running their medium-duty truck in colder climates will be happy to learn that 2023 Chevy Silverado MD models are once again available to order with heated front seats. That includes 2023 Chevy Silverado 4500 HD, 5500 HD, and 6500 HD models.
The heated front seats feature for the 2023 Chevy Silverado MD is tagged with RPO code KA1, and was previously available up until the end of the 2021 model year. However, the feature was not offered for the 2022 model year due to supplier issues. Now, however, the heated front seats feature is once again available for the 2023 Chevy Silverado MD.
Heated front seats are optional for 2023 Chevy Silverado MD Crew Cab 1LT variants in conjunction with the standard 40/20/40 front split bench seat (driver and front outboard passenger, not in the middle), tagged with RPO code A52. Heated front seats are also equipped as standard when selecting the optional bucket seats (RPO code A95) for the 2023 Chevy Silverado MD Crew Cab 1LT configurations. Heated front seats are not offered at all for 2023 Chevy Silverado MD Regular Cab 1WT and 1LT models, nor are they available for the Crew Cab 1WT trim level.
The Chevy Silverado MD is equipped as standard with the 6.6L V8 L5D turbodiesel Duramax engine, which is rated at a maximum of 350 horsepower at 2,700 rpm and 700 pound-feet of torque at 1,600 rpm. Output is routed through an Allison-branded transmission. Both 2WD and 4WD configurations are offered.
Under the skin, the Chevy Silverado MD rides on a platform jointly developed by Navistar and GM. Vehicle assembly takes place at the Navistar plant located in Springfield, Ohio.
Subscribe to GM Authority for more Chevy Silverado news, Chevy news, GM production news, GM business news, and around-the-clock GM news coverage.
Comments
The Silverado MD is equipped with a L5D Duramax not the higher output L5P. The L5D is rated at 350 HP and 700 lbs.ft of torque.
Thanks for calling out that error, Bill. The post has been updated.