Building the World of Falcon Hollow
How a fictional setting gradually became a community with its own geography, history, businesses, and residents.
I never set out to create an entire fictional town.
In fact, when I first started thinking about what would eventually become Father's Day, I wasn't even thinking about Falcon Hollow. There were no maps, no town history, no police department, and certainly no plans for a fictional community with its own newspaper, businesses, and residents.
There was just a character and a single sentence.
Her name was Detective Candace Price, although I always called her Candy. She originally came out of a college project involving digital game-based learning. I was supposed to be developing a game, not writing a mystery novel. But somewhere during that project, one particular image came to mind:
“Candy walked out of the back of the courthouse to avoid the horde of reporters out front.”
I couldn't tell you exactly why that sentence stayed with me. There wasn't much of a story attached to it yet. I didn't know what had happened in that courtroom, why the reporters were waiting, or where Candy was going next. But I kept coming back to it, and years later, that little courthouse scene would become the starting point for something much larger than I ever imagined.



Finding Somewhere for the Story to Live
When I finally began developing Father's Day, I needed somewhere to put the story. Florida was the natural starting point because it was familiar. I knew the atmosphere, the communities, and the general geography, so I didn't have to spend much time imagining what the surroundings might look like. At that stage, I wasn't thinking about worldbuilding. I was trying to figure out how to write a novel.
As the story developed, though, I began realizing that I didn't necessarily want to set it in an actual town. Real locations come with established streets, landmarks, distances, and expectations. I wanted the freedom to create places that served the story without constantly trying to make everything fit an existing community.
Eventually, my attention shifted toward Western Maryland. That wasn't an entirely unfamiliar area either. During my time in the Maryland National Guard, I'd become familiar with parts of the region, and the mountains, wooded roads, smaller communities, and overall landscape had stayed with me. The more I thought about it, the more I realized that Western Maryland offered exactly the kind of atmosphere I was looking for.
That's when Google Earth became part of the process.
I began studying satellite imagery of Western Maryland, looking for an area that might serve as the foundation for my fictional town. Eventually, I settled on a location west of Hancock, in the mountains near Sideling Hill. It was an area I could connect with through my familiarity with the region, and what appealed to me most was that much of what I needed was already there. The mountains, wooded landscape, existing roads, and Maryland Route 68 running through the area gave me a geographical foundation to work with.
I didn't have to completely redesign the landscape. The biggest change was adding Falcon Lake. Using the Google Earth imagery as a starting point, I placed the fictional lake into the existing terrain and began imagining how a small community might develop around it. That became the foundation for what would eventually become Falcon Hollow.
That's something I've always found interesting about the town. Its geography is based on an actual place in Western Maryland. You can look at the original satellite imagery and recognize the landscape that inspired it, but the lake, the town, its streets, businesses, and residents belong to a fictional world. In a way, Falcon Hollow exists in a real location without actually existing there, and that was exactly the kind of freedom I wanted when I started moving away from setting my stories in an actual town.
For a while, I called that community Falcon Lake. The name worked well enough, but something about it never quite settled into place. I knew I wanted to keep the falcon. The question was what to put after it. While experimenting with ideas and using AI as a brainstorming tool, I came across the name Falcon Hollow.
Something clicked.
Falcon Lake sounded like a place. Falcon Hollow sounded like a story.
Almost immediately, I could picture the community differently.
A Town That Started Growing on Its Own
Once Falcon Hollow had a name and a setting that felt right, I began noticing something unexpected. The town was becoming more than a collection of locations needed for a murder investigation.
I started thinking about where Detective Duke Mantz might stop for coffee, which roads he would take to get across town, what the older neighborhoods looked like, and where people gathered in the mornings. I wondered what businesses had been around for generations and how familiar those places might be to the people who lived there.
Cedar Street Café became more than somewhere a character could walk into for a conversation. It became a familiar gathering place. The police department became an institution with its own history and working relationships, while streets and neighborhoods began developing identities of their own.
Before long, I was asking questions that had absolutely nothing to do with the investigation in Father's Day. Who else lived in Falcon Hollow? What happened around town when Duke wasn't working a case? What did people do on a Saturday afternoon, and what had the town looked like fifty or a hundred years earlier?
Those questions weren't part of some carefully organized master plan. They simply appeared as I spent more time imagining the community, and each answer seemed to lead to another question. What had started as a setting for one mystery was gradually becoming a place with a life of its own.


Making the Pieces Fit Together
Of course, there's a difference between imagining a town and keeping that town consistent. As Falcon Hollow expanded, I found myself needing to keep track of details I hadn't expected to worry about.
If Cedar Street Café was on a particular corner, it needed to stay there. If a character traveled from the police department to the Riverwalk, the streets and distances needed to make sense. If someone had lived in town for thirty years, the town's history needed to support that. Details that might seem insignificant on their own could become important when they appeared in more than one story.
That's where the maps, character records, reference bibles, and geographic guides gradually became important. They weren't documents I created before writing the first chapter. They developed because I needed them. What began as a way to remember where things were eventually grew into a much more detailed system for maintaining continuity.
The same thing happened with Falcon Hollow's history. A town doesn't simply appear the moment a novel begins. It has a past. Its businesses have changed hands, buildings have been renovated or replaced, and families have lived there for generations. People remember things differently depending on how long they've been around.
I wanted Falcon Hollow to have that same sense of history, not because every detail would eventually appear in a novel, but because knowing those details helped me understand the place I was writing about. The more I understood the town, the easier it became to imagine the people living and working there.
Beyond the Pages of a Novel
Perhaps the biggest surprise was discovering that I enjoyed developing Falcon Hollow even when I wasn't working on a manuscript. That realization led to projects I hadn't imagined when I first started writing Father's Day.
The town developed its own history publications. The Falcon Hollow Gazette became a way to explore everyday community life, while the website began giving readers an opportunity to discover businesses, locations, people, and institutions beyond what appeared in the mysteries.
Eventually, Falcon Hollow began to feel less like a setting I visited whenever I wrote a novel and more like a place that continued existing between stories. That changed the way I thought about the entire project. I was no longer creating locations simply because the next chapter needed them. I was developing a community where different stories could take place, sometimes connected to Duke Mantz and sometimes having very little to do with him at all.
What made that especially interesting was realizing that not every story about Falcon Hollow needed to be a mystery. Some belonged in the town's history. Others were better suited to a newspaper article or a feature on the website. They were all connected by the same community, even when they had very little else in common.


Still Building
One of the things I've learned through this process is that Falcon Hollow will probably never feel completely finished. There's always another question to answer, another location to develop, or another piece of history waiting to be explored.
Sometimes those discoveries make their way into a novel. Sometimes they become Gazette articles or website features, and sometimes they're simply details that help me understand the town a little better. Not everything needs to become part of a published story to have value in the world I've created.
Looking back, it's difficult to believe that all of this grew out of a single sentence about a detective leaving a courthouse. At the time, I had no idea where that sentence might lead, and I certainly wasn't imagining an entire fictional community built around the stories that would eventually follow.
I didn't begin with a town and then look for stories to tell inside it. I began with the possibility of a story, and Falcon Hollow came later. Somewhere along the way, building the town became just as much a part of the creative experience as writing the mysteries themselves.

