Main IndexAuto Repair Home Search Posts SEARCH
POSTS
Who's Online WHO'S
ONLINE
Log in LOG
IN









Search Auto Parts

Ticking, then engine stoppped running


  Email This Post



MLauten1981
New User

Jan 30, 2011, 9:40 AM

Post #1 of 7 (1809 views)
Ticking, then engine stoppped running Sign In

2000 Dodge Intrepid
2.7 L / 125,000 miles

I was driving down the road, then heard a rapid ticking/clicking sound. I turned off my radio and noticed that it got louder as I stepped on the gas pedal. After that, the engine stopped working. Once I rolled off the road, I tried to restart it anagin and it tried to start, but would not turn over. I recently had to put radiator fluid in due to a small leak, so I checked that, and as I lifted the cap... a flaky, not wet residue was hanging from the cap. (have no idea what that is or if it has anything to due with the engine not starting.)

Just looking for any kind of help/ideas that I can get. Someone mentioned that it could be a timing belt issue.. is that true?
Thank You


Tom Greenleaf
Ultimate Carjunky / Moderator
Tom Greenleaf profile image

Jan 30, 2011, 11:49 AM

Post #2 of 7 (1801 views)
Re: Ticking, then engine stoppped running Sign In

If you've never done a timing belt it sure could be. Some are FATAL or very expensive as if an interference engine valves will strike pistons and it wouldn't run. Two things with those - they jump a couple teeth or break completely all at once - not good. Engines with rubber belts frequently will suggest as little as 60,000 miles for changing - some more.

You still need to tend to wherever it's leaking coolant and not sure that's totally related unless you overheated from low coolant level.

You could take a compression check and if VERY low or nothing you could guess timing by belt (if equipped) is the issue,

T



Hammer Time
Ultimate Carjunky / Moderator
Hammer Time profile image

Jan 30, 2011, 12:27 PM

Post #3 of 7 (1796 views)
Re: Ticking, then engine stoppped running Sign In

This engine doesn't have a belt.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

We offer help in answering questions, clarifying things or giving advice but we are not a substitute for an on-site inspection by a professional.



MLauten1981
New User

Jan 30, 2011, 12:30 PM

Post #4 of 7 (1792 views)
Re: Ticking, then engine stoppped running Sign In

would it be considered a timing chain then... not a belt???

And Thank You for your advice.


(This post was edited by MLauten1981 on Jan 30, 2011, 12:37 PM)


Tom Greenleaf
Ultimate Carjunky / Moderator
Tom Greenleaf profile image

Jan 30, 2011, 12:52 PM

Post #5 of 7 (1790 views)
Re: Ticking, then engine stoppped running Sign In

I was too lazy to look up what this engine used. Chains in cared for engines last lots longer but can still have issues. Find out if you can now what is/was ticking.

If too tricky now and not running find out if it lacks fuel or spark and can go from there,

T



Trevman243
Novice

Jan 31, 2011, 1:08 AM

Post #6 of 7 (1778 views)
Re: 00 Intrepid 2.7 125K Ticking, then engine stoppped running Sign In

The first thing that comes to mind for the ticking is the timing chain, especially if its never had one replaced before. I had a friend that had a similar problem and it was due for a timing chain, they kept cranking it and cranking it by the time i got to it they completely bent all the valves from the timing being off

(just changed subject line to include what car this is)


(This post was edited by Tom Greenleaf on Jan 31, 2011, 4:21 AM)


Tom Greenleaf
Ultimate Carjunky / Moderator
Tom Greenleaf profile image

Jan 31, 2011, 4:56 AM

Post #7 of 7 (1772 views)
Re: 00 Intrepid 2.7 125K Ticking, then engine stoppped running Sign In

Trevman - Are you the same person w same car as the top post in this thread? TMK if you change user name it will change them all or if you are using another's name please say so, so we know it's the same car or start a new thread for yours.
_______________________

Timing Chains: The idea is to turn cams at 1/2 the revolutions of the crankshaft via chain, belt or gear to gear. Some engine in fact many if cam(s) don't keep valves in place will allow a collision of valve to piston with likely damage up to total loss of that engine!

Some chains just sit there like a simple bicycle and some have tensioners. The tensioner could be faulty and too loose a chain can jump from that or wear. So far in a career I haven't seen the chains just break - ones I've dealt with wore out gears and chain wear were too loose. At RPM the centrifugal force is floating the chain high on gear teeth and can jump or completely go off.

If a noise like in this case - is it the chain itself or the valves beginning to whack the pistons? Dunno that yet. For that matter dunno if this is a timing chain issue at all yet.

When chain is off time for any reason the valve timing is off and compression low to none as mentioned. Since this engine has been cranked even if just by starter if that has collided in an interference engine the damage is done but might be less than if running but it happened while running.

If this engine was fine right till this, just take a quick cold compression test on even one cylinder would be telling and or take cover off to see if chain is very loose on some. Some it's quite a job to get to see the chain, some not so hard.

An engine that WAS running that has compression and now will only crank is lacking 1-2-3 either compression, spark or fuel/fuel delivery.

If this is really thought to be a chain issue and could be let's begin diagnosing that - in distributor-less engines I'd take a valve cover off and turn crank by bolt and see how far it turns back and forth before valves move among other possible tests.

The noise right before an engine that quits running does suggest a mechanical failure still to be determined on this vehicle.

Note: I am NOT strong in Mopar vehicles but the basics apply to how all four stroke engines run,

T







  Email This Post
 
 


Feed Button




Search for (options) Privacy Sitemap