Welcome Visitor! Please take a few seconds and 
I just replaced the plastic thermostat housing on my 98 Mazda B4000, but it has a 4.0L 99 SOHC from an explorer. I bought the updated Motorcraft housing that takes clip in sensors instead of the original threaded type that is known to fail. Truck started up and ran ok until it reached operating temp and it stalled right at a major intersection. It wouldn't start and I had it towed back to my father in law's shop.
We got it running but it ran awful and continued to stall. After going through the basic diagnostic steps (fuel, spark, air) I suggested that we check the comp data values with his fancy scan tool. We discovered that the engine temp sensor was reading 460 degrees. We unplugged both sensors and it ran and started normally.
I bought aftermarket sensors (standard motor products) but have already ordered the motorcraft equivalents. Is it possible that the sensor was causing the motor to run/behave in this manner? It makes sense because it is the only thing they touched. I am not driving the truck until I get the OEM sensors tomorrow ( hopefully). Ironically the temp sending unit (for the dash gauge) was what prompted this swap and that one seems to be working/reading correctly now. Although I am swapping it too.
We got it running but it ran awful and continued to stall. After going through the basic diagnostic steps (fuel, spark, air) I suggested that we check the comp data values with his fancy scan tool. We discovered that the engine temp sensor was reading 460 degrees. We unplugged both sensors and it ran and started normally.
I bought aftermarket sensors (standard motor products) but have already ordered the motorcraft equivalents. Is it possible that the sensor was causing the motor to run/behave in this manner? It makes sense because it is the only thing they touched. I am not driving the truck until I get the OEM sensors tomorrow ( hopefully). Ironically the temp sending unit (for the dash gauge) was what prompted this swap and that one seems to be working/reading correctly now. Although I am swapping it too.
