faulty engine coolant temp sensor

2006 ford fusion 3.0 V6 engine customer complaint car stalled no crank no start, car sat cooled down restarted message center said charging problem . spoke with customer said last January here in Minneapolis hard start cold needed jump pack assist. was tuned up and new battery installed . customer said it took long crank time to start several times . hooked scantool found one code related to engine coolant sensor out of range . looked at live data notice temp was 130 at rest key on engine off car wasn't ran for 13 hrs outside temp was 72 , started car temp raised excess high showed 224 on scantool no over heat went 230 turned on ac temp dropped 225 engine fan running . replaced sensor temp dropped to 192 ? did pcm shut down car to protect from overheating damage ? what u guys think ? car hasn't stalled yet and temp in high 80s today was in low 90s when stalled.

What codes did you have, specifically? I'd expect to see some combination of P0217, P1299 and maybe P1289.

Typical Ford strategy is to shut off injectors, crank the fan(s) up and turn the A/C off. So, I could definitely see a stalling complaint, but not a no crank. Are you sure the customer was describing a no crank? Or a crank no start?

Does the cold soak CHT reading now match ambient temperature?

it didn't match act sensor it had one codes regarding ect sensor when I seen how high the sensor was and didn't match engine temp I knew sensor was bad I did unplug sensor tell check engine came on and coolant fan ran constant to check pcm limp in . funny it ddint store more then one code just out of range in pending no check engine light but it made sense to me to cause cold start promblems . its something to think about on intermitten high temp days or exstreme cold days