You’ve been developing utility-scale solar for years. You know the permitting playbook: wetlands, setbacks, stormwater, maybe a noise study. Your civil engineer has relationships with the county. Your environmental consultant knows which state agencies to call. You’ve done this dozens of times.

Now the market is telling you to add storage. The interconnection queue is punishing solar-only projects. Your offtaker wants dispatchable capacity. The IRA economics are compelling. So you hire your usual team, add some battery blocks to the site plan, and submit for permits.

Six weeks later, the Fire Marshal rejects your application.

The reason? Your battery containers are spaced 10 feet apart. The Fire Marshal—citing NFPA 855 and local fire code amendments you’ve never heard of—requires 20 feet. Your 100 MW project just became 60 MW, and your financial model just died.

Welcome to the fire code trap.

The Complexity You Didn’t Know Existed

Solar permitting is fundamentally a land use exercise. You’re asking the county to approve a change in zoning or a conditional use permit. The technical review is straightforward: can you manage stormwater, will you screen the neighbors, do your setbacks comply with code?

BESS permitting is fundamentally a fire safety exercise layered on top of land use. You’re asking the county to approve a facility that stores megawatt-hours of electrochemical energy—energy that, under fault conditions, can release flammable gases, toxic vapors, and sustained heat that water cannot extinguish.

The Fire Marshal isn’t reviewing your site plan for aesthetics. They’re reviewing it for thermal runaway propagation risk—the possibility that a single cell failure cascades into adjacent containers, creating an uncontrollable event.

This is not a theoretical concern. Fire departments have responded to BESS incidents where standard suppression tactics failed, where first responders had to establish defensive perimeters and let systems burn out over days. Every Fire Marshal in America has seen the photos. Many have adopted local amendments that exceed national standards.

The UL9540A Problem

At the heart of BESS fire safety is a test standard called UL9540A: the Standard for Test Method for Evaluating Thermal Runaway Fire Propagation in Battery Energy Storage Systems.

Here’s what most developers don’t understand: UL9540A is not a pass/fail certification. It’s a test method that produces data specific to each battery technology, configuration, and installation scenario. The test measures what happens when a cell is forced into thermal runaway—how much gas is released, whether fire propagates to adjacent cells, whether the event can be contained.

The test report determines everything downstream:

• Separation distances: How far apart must containers be to prevent propagation?
• Explosion control: Does the system require deflagration venting per NFPA 68, or can it use prevention strategies per NFPA 69?
• Water supply: What flow rate (GPM) and duration are required for fire suppression?
• Setbacks: How far must the system be from property lines and occupied buildings based on heat flux modeling?

Different OEMs, different chemistries, different container configurations produce different UL9540A results. A battery that passes with 10-foot spacing in one configuration may require 25 feet in another. And here’s the critical point: the Fire Marshal interprets the test report against local code, not against the OEM’s marketing claims.

The Sequencing Mistake That Kills Projects

The trap closes when developers select their battery OEM before validating fire code compliance.

The typical (flawed) sequence looks like this:

1. Developer issues RFP to battery vendors
2. Vendors submit pricing based on their standard configurations
3. Developer selects OEM based on $/kWh economics
4. Civil engineer develops site plan using OEM-provided spacing
5. Developer submits for permits
6. Fire Marshal reviews against local code and UL9540A data
7. Fire Marshal requires different spacing than OEM specified
8. Site plan no longer fits the parcel—or requires costly redesign

By the time you discover the problem, you’ve already spent six figures on engineering. You’ve already told your investors you have 100 MW of capacity. You’ve already signed an option on a parcel that can’t fit the revised layout.

The mistake isn’t selecting the wrong OEM. The mistake is selecting any OEM before you understand what the Fire Marshal will require.

What the Fire Marshal Actually Reviews

When a BESS permit application lands on a Fire Marshal’s desk, they’re looking for a Hazard Mitigation Analysis (HMA)—a comprehensive document required by NFPA 855 that demonstrates how the project addresses fire and explosion risks.

The HMA must include:

• Failure Mode and Effects Analysis (FMEA): What can go wrong with this specific battery chemistry, and what are the consequences?
• Consequence Modeling: Gas dispersion analysis, thermal radiation calculations, and—if required—toxic plume modeling for nearby sensitive receptors
• Layers of Protection: Documentation of the Battery Management System (BMS) controls, suppression systems, passive barriers, and emergency response protocols

The Fire Marshal compares this analysis against:

1. NFPA 855 (Standard for the Installation of Stationary Energy Storage Systems)
2. Local fire code amendments (which frequently exceed NFPA requirements)
3. The specific UL9540A test report for the proposed equipment

If your civil engineer submitted a site plan without an HMA, you didn’t submit a complete application. If your HMA was prepared without the unredacted UL9540A report—many OEMs only provide summaries—your consequence modeling may not reflect actual test data.

The Local Amendment Problem

Even if you’ve correctly interpreted NFPA 855, you may not have correctly interpreted local code.

Fire code adoption varies dramatically by jurisdiction. Some counties adopt the International Fire Code (IFC) with NFPA 855 incorporated by reference. Others adopt older code editions that don’t address BESS at all—leaving Fire Marshals to improvise. Still others have adopted specific BESS amendments that impose requirements beyond national standards: larger setbacks, additional suppression systems, mandatory decommissioning bonds.

We track local fire code activity across roughly 90 jurisdictions with active BESS restrictions. The pattern is clear: as more projects enter permitting, more jurisdictions adopt restrictive amendments. The Fire Marshal who approved your last project may have since adopted new rules.

There is no centralized database for this. There is no state clearinghouse. The only way to know what a specific jurisdiction requires is to engage with that jurisdiction directly—before you commit to a site, before you commit to an OEM, before you spend capital on engineering.

The Leeward Rule

At Carina, we’ve codified this lesson into an operating principle we call The Leeward Rule:

We never select a Design Basis OEM without the Fire Protection Engineer validating the UL9540A test report against local code first.

The name references the “leeward” side of a BESS array—the downwind direction where thermal radiation and gas dispersion present the greatest risk. It’s a reminder that fire safety analysis must precede equipment selection, not follow it.

In practice, this means our development sequence looks different:

1. Phase 100 (Feasibility): Fire Protection Engineer drafts a “Fire Safety Design Basis” memo defining required spacing, blast walls, and setbacks for the target jurisdiction—before any OEM is selected
2. Technical RFI: We query OEMs for their UL9540A data and compare it against the Design Basis
3. Design Basis Selection: Only OEMs whose technology fits the site constraints and local code requirements advance to detailed engineering
4. Commercial RFP: Final pricing negotiations happen after permits are secured—not before

This sequencing prevents the trap. You know what the Fire Marshal requires before you commit capital. You select technology that fits reality, not technology that looked good on a spreadsheet.

The 48-Hour Screen

For developers evaluating new sites, we recommend a Fatal Flaw Analysis before signing any option agreement. This is a rapid desktop screen—typically 48 hours—that identifies project killers before you commit.

The fire code component of this screen asks three questions:

1. What fire code does this jurisdiction enforce? (IFC edition, NFPA 855 adoption, local amendments)
2. Are there known BESS-specific restrictions? (Moratoria, enhanced setback requirements, conditional use triggers)
3. What is the site’s “fire access” reality? (Apparatus width, turning radii, water supply proximity)

If the answers reveal a hostile regulatory environment—or a site that can’t physically accommodate fire code requirements—you’ve saved yourself six figures and six months.

The Takeaway

The fire code trap catches solar developers because they assume permitting is permitting. It’s not. BESS permitting introduces a discipline—Fire Protection Engineering—that most solar teams have never needed.

The solution isn’t to avoid storage. The solution is to sequence your development correctly: fire code analysis before OEM selection, local jurisdiction engagement before site plan submission, and a clear-eyed assessment of what your parcel can actually accommodate.

The developers who understand this will build projects. The developers who don’t will spend capital learning expensive lessons.

Carina Energy provides BESS development services including Fatal Flaw Analysis, Owner’s Representative services, and full Development-as-a-Service for utility-scale storage projects. Contact us to discuss your project.

Related Reading:

• The 504-Task Reality: Why BESS Development Isn’t “Solar Plus Batteries”
• The RFI vs. RFP Split: Why Locking Your OEM Too Early Destroys Economics