The Data Doesn’t Lie. People Do. [Part 3]

Part 3: The “Key Cycle Confusion” Isn’t Confusion at All

You’ve probably heard some version of this by now from #FKR: “The key cycles don’t line up, so the vehicle data can’t be trusted.” I’ve been seeing #KarenRead sycophants pushing this hard again lately, which is perfect, because it gives us another opportunity to mythbust. My favorite.

It sounds compelling… until you actually walk through the timeline. As usual, let’s break it down. Starting with what doesn’t lie: the odometer:

* Start: The beginning of key cycle 1162 at 12,629 miles.

* End: The vehicle is in police custody at the Sallyport, and the ODO is reading 12,665 miles.

That’s a 36-mile difference.

So the question isn’t complicated. Did Karen drive about 36 miles after leaving Fairview? The answer is clearly, yes. And it lines up almost perfectly with her route that night. Now lets layer in the key cycles.

Key Cycle 1162
This is the drive from the Waterfall (12:12 a.m.) to 34 Fairview (12:32 a.m.) to 1 Meadows. At 12:32 a.m., the Lexus records the high-speed reverse event at 12,629 miles. That’s your collision event.

Key Cycle 1163
This is the short drive from 1 Meadows to Jen McCabe’s house and back. Nothing complicated here, this is Karen “searching ”the 2-square miles” from the previous night.

Key Cycle 1164
This is the Reads getting the SUV back to Dighton before anyone notices the damaged right-rear taillight. This is the long drive from 1 Meadows to Dighton, to her parents’ house. By the end of this drive, the vehicle's odometer reads 12,665 miles.

That’s your ~36 miles right there. Fairview to Meadows, to Jen’s, back to Meadows, then down to Dighton.

Key Cycle 1165
The vehicle is loaded onto a tow truck at Karen’s parents’ home in Dighton. You see handling-type events like traction control (TRC), but no meaningful change in mileage.

Key Cycle 1166
The vehicle is unloaded at the sallyport at Canton PD, and the odometer still reads 12,665 miles.

Key Cycle 1167
This is where Trooper Paul conducts his testing, and this is the part that got people spun up because at trial, he said his testing started on 1164. But when you actually look at the data, that doesn’t hold. Key Cycle 1164 shows the same odometer reading repeated at 12,665. No real movement and no meaningful driving behavior. Paul mistook the odometer reading as key cycle 1164, but it’s 1167.

We know this because, at Key Cycle 1167, meaningful vehicle information is recorded.

Now you see braking, ABS activation, acceleration inputs, and the odometer ticks up to 12,666.

So what actually happened? Trooper Paul mislabeled his testing key cycle due to the same ODO reading. He was working off the odometer and the event data. And because both 1164 and 1167 start at the same mileage (12,665) he anchored to the wrong key cycle number.

That’s it, that is the testing key cycle broken down by odometer reading. It’s pretty simple if you take a few minutes to piece it all together using actual data.

Again, human beings are prone to error, which is why we place more weight on digital evidence than on eyewitness testimony or other human accounts. It’s plainly obvious that the testing cycle is 1167, and anyone who claims it’s 1164 is being intellectually dishonest.

Once you correct that, everything falls into place.

* The mileage lines up.
* The sequence of events lines up.
* The timing lines up.

And it aligns with everything else in the case. The Lexus shows a reverse event at 12:32:09 a.m. John’s phone stops moving at 12:32:16 and never moves again. GPS NEVER places him inside the house. All of the independent systems tell the same story.

This isn’t some unexplained inconsistency. It’s a simple misinterpretation that got turned into something bigger than it is. The data didn’t change. And once you understand it correctly, the “key cycle confusion” disappears.

The data doesn’t lie. People do.