The Unfinished Route: A Delivery Driver’s Endless Night Shift

🕐7 min read

You know how some nights feel heavier than others? Not the weight of exhaustion, but something else—a pressure in the air, a stillness that makes the hairs on your forearms stand up. For overnight delivery drivers, that heaviness is part of the job description. The hours between midnight and dawn are when the roads belong to the few: the truckers, the emergency crews, and the men and women in brown uniforms or blue vests, sorting packages by the glow of a dome light. I’ve been one of them. I drove a FedEx Ground route out of a small distribution hub in central Ohio for six years, from 2017 to 2023. My shift started at 11:30 PM and ran until the last package was dropped, usually around 6:00 AM. I knew every curve of my 45-mile loop, every pothole, every dog that barked from behind a fence. But one night in late October 2019, I learned that knowing a road isn’t the same as understanding it. That night, my route became something else—a loop that shouldn’t exist, leading to addresses that had been erased from the earth years before. And I wasn’t the one driving it. The route was driving me.

The Route That Shouldn’t Have Been

My regular run covered the rural outskirts of a small town called Millbrook—population 3,200, according to the 2010 census. The houses were spaced far apart, set back from two-lane roads lined with cornfields and stands of oak. On a typical night, I’d deliver between 110 and 130 packages, using a Panasonic Toughpad FZ-G1 running FedEx’s DRO (Delivery Route Optimization) software. The scanner—a Symbol LS3578 attached to a belt holster—logged each stop with a barcode scan. The system was reliable, or so I thought.

That October night, the manifest showed 117 stops. The first 40 went smoothly: a box of auto parts for a mechanic on County Road 12, a case of pet food for a farmhouse on Hickory Lane. Then, around 2:17 AM, I pulled up to 1427 Maplewood Drive. The address was listed as active in the system—a residential delivery, signature required. But there was no house. The lot was empty, a rectangle of bare dirt overgrown with thistle and ragweed. A concrete foundation slab lay cracked and weather-worn, the only sign that a structure had ever stood there. I checked the Toughpad. The GPS dot sat squarely on the lot. I drove a quarter-mile down the road and turned around, thinking I’d missed a driveway. Nothing. The road ended at a cul-de-sac, and the only other house was a boarded-up ranch at 1403, clearly abandoned for years.

I called dispatch. No answer. I left a note on the package—”No house at address, unable to deliver”—and moved on. But the next stop, 1431 Maplewood, was the same story. Empty lot. Then 1435. Empty. By the time I reached 1443, I had seven packages for addresses that existed only in the system. The houses had been demolished. I knew because I’d driven this route for three years and never once seen a home on that stretch. Later, I’d learn that the entire Maplewood Estates subdivision—47 homes built in the early 2000s—had been condemned and razed in 2016 after a methane leak from an abandoned landfill beneath the development. The neighborhood was gone. But my scanner still told me to deliver.

The Loop Tightens

At 3:12 AM, I finished the Maplewood stops—or tried to. I marked each one as “undeliverable” and scanned the barcodes. The system accepted the scans, but the manifest didn’t update. The same addresses reappeared on my next screen, as if I hadn’t touched them. I refreshed the Toughpad. Nothing. I rebooted it. The list remained identical: 1427, 1431, 1435, 1439, 1443. All requiring delivery. All leading to empty lots.

I made a decision. I would skip those stops and drive to the next section of my route, a cluster of homes on Cedar Lane, five miles east. I pulled onto the main road—Route 37—and drove for what felt like ten minutes. The odometer showed 4.7 miles. But when I looked at the GPS, I was back on Maplewood Drive. The same empty lots. The same cracked foundations. The dashboard clock read 3:47 AM. I hadn’t turned around. I hadn’t taken a wrong turn. The road had simply bent itself into a circle. I sat in the idling truck, the heater blowing warm air that smelled of diesel and cardboard, and I listened to the silence. No wind. No distant dogs. Just the low hum of the alternator and the ticking of the engine cooling.

I tried again. I drove east on Route 37, then north on County Road 9, a detour that should have taken me to the next town. The GPS showed me moving, but the landmarks were wrong. A grain silo I passed three times. A billboard for a tractor dealership that I’d seen at 2:00 AM, then again at 3:30, and now at 4:05. The roads were the same, but the order was off, like a song stuck on a skipping record. I pulled over and checked the manifest. The stop count read 117, but the list only showed eight addresses—the seven Maplewood lots and one more: 1403 Maplewood, the boarded-up ranch. I hadn’t seen that one on the original list. It had appeared while I was driving.

The House That Waited

1403 Maplewood was different from the others. The ranch house stood at the end of the cul-de-sac, its windows dark, the front porch sagging under a roof of rusted tin. A single porch light flickered—not with a bulb, but with a sickly yellow glow that seemed to pulse in time with my heartbeat. I didn’t want to stop. Every instinct told me to turn the truck around and drive until I hit a main road, a gas station, anywhere with lights and people. But the package for 1403 was a small box, about the size of a shoebox, wrapped in brown paper and sealed with tape that had yellowed with age. The label was smudged, the ink blurred as if it had been wet. The recipient’s name was barely legible: “E. M. Harlow.” The return address was a P.O. box in a town I didn’t recognize.

I parked the truck at the curb, leaving the engine running and the headlights on. The beam cut through the fog that had settled over the lawn, illuminating a patch of dead grass and a rusted mailbox hanging askew. I walked to the front door, the package cold in my hands. The porch steps groaned under my weight. I knocked. No answer. I knocked again, harder, and the door swung inward a few inches. The interior was black, but I could smell dust and mildew and something else—a sweet, chemical odor like antifreeze. I called out, “FedEx delivery.” My voice sounded thin, swallowed by the silence. I set the package just inside the doorway and stepped back. As I turned, I saw a figure standing at the edge of the headlights. A woman, or the shape of one, wearing a long coat. She didn’t move. She didn’t speak. I got in the truck and drove.

This time, the road led me out. Within ten minutes, I was on Route 37 heading east, the dashboard clock reading 4:52 AM. The remaining stops on my manifest—the real ones—appeared one by one. I finished the route at 6:23 AM, delivered every package, and returned to the hub. I checked the scanner logs. The Maplewood stops were marked as delivered, each with a timestamp of 3:47 AM. I hadn’t scanned them. The system had done it on its own.

The Aftermath and the Unanswered Questions

I didn’t tell my supervisor. What would I say? That I’d driven in circles for two hours? That I’d delivered a package to a house that shouldn’t exist? I kept my head down and worked the rest of my shifts. But something changed. I started noticing other anomalies: addresses that appeared on my manifest but not on the map, packages with labels that seemed older than the system allowed, recipients whose names I recognized from the Maplewood list. I checked the county auditor’s records online. The 1403 Maplewood property was listed as “vacant, structure condemned.” No owner on file. The last recorded sale was in 2014, to a woman named Eleanor Harlow. She’d died in 2015, the same year the methane leak was discovered. The house should have been demolished with the others. But it remained.

I also found a news article from the Millbrook Gazette, dated October 23, 2019—the same week as my encounter. It mentioned that a FedEx driver had reported a suspicious package at 1403 Maplewood, but police found nothing. No package. No evidence of entry. The article quoted a dispatcher saying, “We get calls about that address every few months. People see lights. They hear knocking. But there’s never anyone there.” I was the driver who made that call. I don’t remember making it.

I quit my job three weeks later. I couldn’t shake the feeling that the route wasn’t finished with me. Sometimes, late at night, I still check my email. I don’t know why. But last month, a package arrived at my own doorstep. No return address. Just my name, written in the same smudged ink as the one I’d left at 1403 Maplewood. I haven’t opened it. I don’t plan to. Some deliveries are better left undelivered.

What the Data Says About Ghost Addresses

My story isn’t unique—at least, not the part about addresses that shouldn’t exist. In a 2020 study by the United States Postal Service Office of Inspector General, 4.7% of rural addresses in the national database were found to be inaccurate or obsolete. For private carriers like FedEx and UPS, the error rate is similar, especially in areas where subdivisions were built and then abandoned. The USPS maintains a master list called the Delivery Point Validation (DPV) database, but it’s only updated quarterly. If a house is demolished between updates, the address can remain active for up to three months. In the case of Maplewood Estates, the demolitions happened in 2016, but the addresses were still in FedEx’s system in 2019—three years later. That’s a data lag of 1,095 days.

But data errors don’t explain the loop. They don’t explain the GPS rerouting, the unchanged manifest, the figure in