OEProofOE-verified aftermarket transmission & engine seals

2017 Chevrolet Cobalt 6T30 Gen3 axle seal part numbers: RH 24273970, LH 24273971

In the bounded 2017 Chevrolet Cobalt JX69/L2C/MNJ/FV1 EPC context, 24273970 is the right axle seal and 24273971 is the left axle seal. Scope is 2017–2018 only.

For the 2017 Chevrolet Cobalt JX69 / L2C / MNJ / FV1 EPC context, the two axle-seal rows are unusually clear: 24273970 is printed with the right-axle token, and 24273971 is printed with the left-axle token. The captured application range is 2017–2018.

Right side: 24273970

E644 is the exact primary row for 24273970. The row binds the number to JX69, L2C, MNJ and FV1 and prints both к корпусу (“to case”) and правый мост (“right axle”). This is strong enough to publish the side assignment for this exact Cobalt application.

Left side: 24273971

E645 is the exact primary row for 24273971 on the same Cobalt 2017 page. It prints левый мост (“left axle”) with the same JX69 / L2C / MNJ / FV1 application context and the same 2017–2018 range.

What this does not prove

These two rows do not authorize a universal rule for every Cobalt, every market or every 6T30. They must not be projected backward to the 2013 Cobalt MH9 application. They also do not prove a global supersession chain from older seal numbers to 24273970/24273971, and they do not establish these as current ordering numbers.

The same audit also produced an important method rule in E646: position text such as TO CASE or TO HSG cannot be converted into LH/RH by a fixed rule. Here the side is publishable because the same row prints the side token directly, not because “to case” was interpreted as one side.

Ordering boundary

If the vehicle is a different Cobalt year or uses a different transmission RPO, do not reuse this pair from the model name alone. Verify VIN / RPO first. For a bounded quote, send the VIN, market and any known OE number through the RFQ.

Evidence boundary

This page is drafted from the current B3/fitment evidence and does not widen those source boundaries. Demand Intelligence was used only to choose the topic, not as technical evidence.