View Full Version : 36 vs 39 banjo ???
wideglide74
09-27-2004, 08:53 PM
In trying to only do things once I have decided to replace the diff in my AV8 (drivline is to short) with a later banjo unit. I have both a clean 36 and 39 unit, I've also got a 34 torque tube/driveline and the appropriate weld on spring perch bracketry and I'm ready to make the swap as per the B/T book. My question is what are the relevant diffrences between the 36 and 39 diff's? I would prefer to use the 36 as it is a little less beefy looking in the axle housings and will lend itself better to the look of the car...
Bruce Lancaster
09-27-2004, 09:04 PM
they differ in tooth count on spiders, and I think different style driveshafts and splines on pinion. There is no real reason to prefer one over the other, IMHO, so look over gear ratio, mechanical condition, and, as you did, appearance.
Gears and bearings and such are expensive, so if one is correct ratio and is close to ready to use mechanically, go for it. You can interchange the axle housings and most other stuff.
visor
09-27-2004, 09:40 PM
I agree with you on the '36 rear.The axle bells are smaller in
diameter and
looks better under an A-v8.
The '36 axle tubes are smaller in diameter but are the same
length as the 39's, so you can use either set of axles.
If you use the '39 diff, you will need to use the '36
diff. carrior bearings and races with the '36 axle bells.
Another bonus is the nice spring hangers that are part of
the '36 bones.
You also will need to shortin them and bend them in a tad to
mount to the 34 torque tube.
--------------------------------------------------------
"OPOSSUM BENDERS"
Central Mo. chapter
Rand Man
09-28-2004, 03:21 PM
I have a complete banjo rear-end, torque-tube, assembly I would like to get rid of. How do I identify it? It doesn't have the "wide five" brakes. I would have to look for hydraulic brakes. How much should I ask for in the classifieds? I wanted to use it how much would it cost to convert it to an open system?
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.