In the office where she reviewed the initial case, Navarro had leaned over a table crowded with printouts and placed two receipts side by side.
"Look at the time stamps," Navarro said. "Eleven forty-one on one. Eleven forty-three on the other. Same dispenser, different Army accounts, enough diesel to fill a delivery truck. But both of those units were accounted for at the installation. Nobody took their vehicles out. I checked twice."
"Could a contractor be using the accounts under an approved agreement?"
"I asked procurement. They couldn't find one. And whoever is doing it knows the restricted override codes."
Danielle studied the documents. Each of the suspicious transactions bore the identification of pump six. A separate administrative field carried an authorization marker that should never have appeared on a routine purchase. The marker was not a customer PIN. It was a service-side override, supposedly reserved for approved exception handling after a fleet card was rejected.
"Who owns the exception credentials?" Danielle asked.
"The provider maintains the system. The station's authorized manager can request a review. But look at this other field."
Navarro pointed to a line of characters repeated in the transaction metadata. It resembled a vehicle identifier rather than a staff login. At first glance, it meant nothing to Danielle. When she cross-referenced it with county patrol location data supplied through a preliminary records request, it took on a very different significance.
Patrol unit 74-Alpha. Regularly assigned to Officer Nolan Voss.
A police car had been in the immediate area during nearly every suspicious late-night transaction.
That alone did not prove corruption. A patrol officer might stop for coffee at the same station for years. A shared code might be compromised. A contractor might make an innocent mistake when processing fleet purchases. Danielle was careful about the difference between an irregularity and evidence of guilt. She had seen investigations ruined by an agent who fell in love with the first explanation and stopped looking for the others.
She built two timelines. One traced the reported location of government vehicles. The other traced activity around the station. She asked for meter reconciliation reports, the station's maintenance history, fuel deliveries, contract billing data, and identification logs from the fleet card processor. She contacted state weights-and-measures personnel to understand how the dispensers recorded actual delivery. She spoke with a digital-forensics specialist who explained the ways a service controller could be manipulated and the ways an investigator could mistake a legitimate recalibration for tampering.
In the middle of this work, one name kept appearing in the station's service notes: Everett Shaw.
Shaw was the captain responsible for the district that included the highway station. His signature appeared on two local incident summaries involving supposed false-alarm calls from the business. Both reports had been filed shortly after the manager contacted police to complain about unfamiliar tanker trucks near the diesel island. Each report concluded that the manager had misunderstood routine commercial deliveries. Neither identified the trucks. Neither documented an interview with a driver. Both recommended that patrol personnel make periodic reassurance visits to the station.