|
|
Engine Cranks, but won't start
|
|
|
| |
|
Deavin_b
New User
May 25, 2015, 10:19 PM
Post #1 of 4
(1529 views)
|
Engine Cranks, but won't start
|
Sign In
|
|
I have a 1995 Ford Ranger, with a 4.0L v6 engine. So basically what happened was earlier in the morning i started it just fine and drove it home. About 8 hours later when i went to start it, it barely started and then chugged a little bit and died. TheCheck engine light came on when this happened as well. Once it died, I tried starting it again but all it would do is crank and never start. I don't think its the starter because its cranking normally. One thing that could be causing it is that there is some radiator fluid that must have leaked, sitting in the cavities of the engine block on top. Is it possible it shorted a fuel sensor out? Thanks
|
|
| |
|
Tom Greenleaf
Ultimate Carjunky
/ Moderator
May 26, 2015, 2:00 AM
Post #2 of 4
(1515 views)
|
Re: Engine Cranks, but won't start
|
Sign In
|
|
It seem one issue caused the next but need to know right now why is doesn't run. Follow this for what's missing for an "All Crank, No Start" condition............ http://autoforums.carjunky.com/...LL_NOT_START_P75655/ This at least isolates what is missing - spark, fuel, compression in that. Then why the coolant is seen? Did it overheat right before this or do you know or perhaps didn't notice? I wouldn't run this engine for long if you find and can fix the current reason for a no start till why and where it leaked is also found, T
|
|
| |
|
Silas
New User
May 26, 2015, 12:09 PM
Post #3 of 4
(1501 views)
|
Re: Engine Cranks, but won't start
|
Sign In
|
|
hello in that case of ranking but not starting pls check the canshaft sensor first to no if is an open socket or close. Then after that put a diagnoseing machine to get your fault code
|
|
| |
|
Discretesignals
Ultimate Carjunky
/ Moderator
May 26, 2015, 3:47 PM
Post #4 of 4
(1494 views)
|
Re: Engine Cranks, but won't start
|
Sign In
|
|
Silas, you really should use spell checking if your going to provide advice. The reason for using that procedure that Tom pointed out is to help determine what is missing. It's fine to do a visual inspection and check for trouble codes, but you really don't want to disturb anything and create an intermittent no start/stall condition. Find out what is missing first then start making checks. Since we volunteer our time and knowledge, we ask for you to please follow up when a problem is resolved.
(This post was edited by Discretesignals on May 26, 2015, 3:48 PM)
|
|
| |
|