ColdDutch
From the Low Lands
- Joined
- Sep 10, 2025
- Messages
- 16
- Reaction score
- 80
Ken did call Daniel’s supervisor right after Daniel drove off. He said he then worked the rest of the day by himself until around 2:30–3:00 PM, when he finally went out looking for Daniel by following his tire tracks.
The lithology logs are really only incriminating if Daniel was still around to say they’d been altered. David has a photo of those logs himself, so the existence of the data isn’t in question, the issue would have been Daniel pointing out discrepancies. That also makes it a good theory for why someone might have been on Daniel’s laptop after he went missing.
Ken’s account is interesting because it essentially closes the possibilities. If he’s telling the truth, then Daniel simply drove off and only his tire tracks continued, meaning no one else physically followed him into the desert. If he’s not telling the truth, then that contradiction itself points to motive.
I’m not sure whether Stephen was ever actually questioned by police. What I do know is that it’s not in the police report, and David has even referred to people like Stephen as “ghosts” on his YouTube channel.
One detail left out of the police report is that Stephen called Daniel at 8:33 AM, and Daniel called him back at 8:35. That call happened after Daniel had already left the first well site and was headed toward the second one. The timing matters, because it was that call that caused Daniel to turn around earlier that morning.
This is one of the only parts of the police report timeline where they don't explain where Daniel was when it is easy to do so. Had they questioned Stephen, he would have told them.
Regarding Ken’s story, it’s actually quite simple. Either it’s true or it’s not. If you suspect foul play in this case, that automatically means you have to distrust Ken’s words. As far as we know, he’s the last person to have seen Daniel.
The idea that Daniel was completely off track that day is theoretically possible, but it’s not really supported by his earlier activities that day. He seemed to have gone to work that morning according to his usual routine. If he was on the edge, he managed to hide it fairly well up until the moment he disappeared.
Ken’s timeline is a double-edged sword. On the surface, calling Daniel’s supervisor right after he drove off seems responsible. But when paired with his decision to wait hours before tracking Daniel’s tire marks, it starts to feel more like a performance of concern than genuine urgency. If his story is true, it isolates Daniel. If it’s not, then the delay becomes suspicious. Especially given the desert conditions and Daniel’s behavior.
Stephen’s call at 8:33 AM could be very important. It altered Daniel’s route. Yet Stephen is absent from the police report. That doesn’t seem just an oversight, but more like a structural flaw in the investigation. David Robinson calling him a “ghost” is an interesting metaphor. It certainly leaves room for speculation.
If I understand you correctly, the lithology logs themselves aren’t necessarily incriminating, but their significance depends on Daniel’s interpretation. So, if he had noticed discrepancies and was preparing to raise concerns, then his insight becomes the threat, not the data. That’s makes the theory about laptop access even more compelling. It suggests someone may have wanted to understand what Daniel knew and if he recorded it somewhere.