News:

It appears that the upgrade forces a login and many, many of you have forgotten your passwords and didn't set up any reminders. Contact me directly through helpmelogin@dodgecharger.com and I'll help sort it out.

Main Menu

Lakewood bellhousing on 383 problems fork ect..

Started by javakmcharger68, June 22, 2007, 10:27:59 AM

Previous topic - Next topic

javakmcharger68

I bought the lakewood bellhousing so I would not take a leg off if the original aluminum bellhousing decided to break apart while the clutch comes through my floor.(safe before sorry). I am using a 1971 4speed 18 spline out of a charger. I Used the original fork bracket out of the original aluminum 4speed bellhousing on the lakewood bellhousing. When I put the fork on the bracket where it feels like it wants to go, it hits the 4speed shaft bearing in the round area inside the fork between the two points that release the thwrowout bearing. It doesn't seem like it hits the throwout bearing right either. It seems like the fork wants to sit too far ahead, & just by a little bit. If I have to buy something, then I am fine with that, but I am 5000km away from the car. This bellhousing has been a pain in the ass from day one in my opinion. Need to here if anyone ran into this problem before & what I need to do to get myself out of this problem. I will be paying someone else to pull the engine out again, so I need to know what to do so I save labour cost. Anyone that has used this kind of bellhousing & had a problem, I would like to hear about it, because I know that the next step I have to figure out is the Z-bar setup or go with something else. Please save someone some time & give your  :Twocents: . Thanks again guys
What I have;
360250 pressure plate
260853 clutch disc
Throwout bearing for a 440 bought at CarQuest
143 tooth flywheel
BB fork off of ebay

I feel like this guy a lot of the time  :brickwall:  :brickwall:  :brickwall:  :brickwall:  :brickwall:  :eek2:

John_Kunkel


The "L" shaped pivot can be installed two ways, if installed backwards it will position the fork too close or too far from the TO bearing.
Pardon me but my karma just ran over your dogma.

tecmopar

As John said, make sure the bracket is installed correctly, also, the fork that you bought on Ebay, was it a NEW one, in the box because the BB and SB forks LOOK very similar, good luck.

javakmcharger68

The "L" shaped pivot can be installed two ways, if installed backwards it will position the fork too close or too far from the TO bearing.

If there are only two ways to install the bracket, then should it not place the fork in the right place in one of those positions? :icon_smile_question: . & the fork was bought used off of ebay, but if it was the fork, should it not be way off & not match up close at all? Thanks for the replys, but still confused.

John_Kunkel


It's been a few years since I messed with a 4-speed so I don't remember the correct orientation of the pivot. That's why I said "too far or too close" because I'm not sure of the correct position with any given fork; as mentioned, there are different forks.
Pardon me but my karma just ran over your dogma.

javakmcharger68

So are all the BB forks the same from say 68-72, or did the different body styles make a difference. I know that BB & SB are different but as I understood that was the only difference between the forks in those years. Keeping a car automatic is so much easier than dealing with the mess I am into. 4Speed fun in the end though! Thanks again for the reply John_Kunkel. Always a help.

John_Kunkel


Well, you sent me to the parts books.

The fork seems to be a year/body specific part while the pivot changes with the particular engine.

For example, all V8 B bodies in a certain year all use the same fork but the pivot is different with different motors. I could post exact part numbers for a particular year/engine but that wouldn't be of much use with used parts that have no numbers stamped.
Pardon me but my karma just ran over your dogma.

Chryco Psycho

Talk to Brewers , they have the pivots you need to correct the problem

javakmcharger68