Vendors will happily sell you a "fire-damaged homes" list. What they won't tell you is that the underlying data is public, free, and sitting in your fire department's incident records, which almost nobody in real estate reads.
I pull it as one of the distress signals that feeds a distress score. In Seattle, where I track this, that's 2,651 fire incidents on 1,992 properties. Most investors have never once looked at fire data as a lead source. That's exactly why it works.
A fire incident record is the fire department's log of a call to a property: a structure fire, a rubbish fire, an encampment fire. For an investor it's a distress signal, because a property that catches fire almost always belongs to an owner facing a sudden, expensive decision, and because the smaller fires often flag a property nobody is maintaining.
What fire records actually tell you
Not every fire is a burned-down house. The incident type matters, and it splits into two different signals. In Seattle the breakdown is roughly:
- Rubbish fires (about 1,900). Debris, garbage, or brush igniting on a property. On its own it's minor, but a property that accumulates enough junk to catch fire is a property nobody is maintaining. It's a neglect signal, close cousin to an overgrown-lot or illegal-dumping complaint.
- Fires in buildings (about 565). The classic "fire-damaged house." Real structural damage, an insurance claim, and an owner staring at a repair bill or a decision to sell as-is. This is the highest-intent version of the signal.
- Encampment fires (about 180). A fire at a homeless encampment, which usually means a vacant lot or an abandoned building someone moved into. That's a strong vacancy tell.
So "fire damaged property" is really three different leads wearing one label. The structure fires are the obvious ones. The rubbish and encampment fires are the sleepers, because they quietly point at the same thing a vacant-building violation does: a property the owner has stopped caring for.
Why it's a good lead
A structure fire forces a decision. After a fire, an owner has to either sink money into repairs or sell. Plenty choose to sell, and they often want it fast and as-is, which is exactly the deal a wholesaler or flipper wants. The insurance payout can even fund the seller's next move, so the sale isn't as distressed for them as it looks.
Almost nobody competes for it. Every wholesaler works pre-foreclosure and absentee lists. Fire incident data isn't packaged by the big vendors as a clean feed, so it stays unworked. That's the same friction-is-your-edge story behind code violation leads: the data is public, it's just annoying enough to pull that the crowd skips it.
It's an early, real-world event. A fire is a catalyst. It shows up the day it happens, months or years before any financial filing would. That's the leading-indicator advantage in its purest form.
How to find fire incident data
Fire incidents are public records. Two routes:
- Open data portals. Many big-city fire departments publish incident data. Seattle publishes real-time fire 911 dispatch data on its open data portal, which is where our numbers come from. Search for your city's "fire 911" or "fire incident" dataset.
- Public records request. If your fire department doesn't publish a feed, request incident records for a date range under your state's public records law.
The raw data gives you an address and an incident type. To turn that into a lead you still need to identify the owner, which from an address alone is a skip trace by address, and ideally check whether other signals stack on the same property.
Where the real signal is: stacking
A lone fire record is a lead, but a noisy one. A rubbish fire might be a one-time thing. The signal sharpens when a fire lands on a property that's already flagged.
In our Seattle data, 549 properties have both a fire incident and an open code violation. That's a property that caught fire and has the city on its back about condition. Add a 311 complaint or a long vacancy and you're looking at a house that is very clearly in trouble. That convergence is the whole idea behind signal stacking, and fire is one of the strongest layers to stack because it's a concrete event, not just a status.
One honest note: I only track fire incidents in Seattle right now. The code violation data spans seven Puget Sound markets, but fire, permits, and 311 are Seattle-only so far. If you're working another market, the method still holds, your fire department's records are public too.
Frequently asked questions
How do I find fire-damaged properties to buy?
Pull fire incident records from your city fire department, most publish them on an open data portal, then filter to building fires and skip trace the owners. The smaller rubbish and encampment fires are also worth watching, since they often flag a neglected or vacant property. It's public data, so it costs nothing at the source.
Are fire incident records public?
Yes. Fire department incident and dispatch records are public in the United States. Many large cities publish them on open data portals; where they don't, you can request them under your state's public records law.
Is a fire-damaged house a good investment?
It can be. After a fire, many owners would rather sell as-is than manage a rebuild, and an insurance payout can make them flexible on terms. The deal depends on the extent of the damage and the after-repair value, but fire-damaged houses are a classic below-market source because most buyers won't touch them.
What does a rubbish or encampment fire tell an investor?
That a property is likely neglected or vacant. A property with enough accumulated debris to catch fire, or one where an encampment has formed, usually has an owner who has stopped maintaining it. Those are weaker signals than a structure fire on their own, but strong when they stack with a code violation or a vacancy.
Do you cover fire data outside Seattle?
Not yet. FlaggedLeads tracks fire incidents, expired permits, and 311 complaints in Seattle only right now; code violations cover seven Puget Sound markets. The same public records exist in other cities, so the approach transfers even where our data doesn't reach yet.