Permitting
Fire access pathways and setbacks: IFC 1205 in practice
Short answer
Fire access requirements for rooftop solar come from the fire code edition the jurisdiction adopted, not the newest one published. In the 2021 IFC they sit at Section 1205; in the 2018 and 2015 editions the same material is at 605.11. Typical residential requirements are 36-inch pathways and an 18-inch ridge setback, widening to 36 inches where the array covers more than a third of the roof — but state and local amendments change these numbers often enough that the adopted edition has to be confirmed per job.
Section numbers below are IFC 2021. The 2018 and 2015 editions carry equivalent material at 605.11. California, and several individual jurisdictions, amend it.
What the requirements are for
Two things. A firefighter needs a route across the roof that is not covered in modules, and needs somewhere to cut a ventilation hole without cutting through live conductors. Everything in the section follows from those.
The usual residential shape
- Pathways. Clear routes from eave to ridge, typically 36 inches wide, placed so a crew can reach the ridge without crossing the array.
- Ridge setback. Clear space below the ridge along its length — commonly 18 inches where the array occupies a third or less of the total roof plane area, and 36 inches where it occupies more.
- Perimeter. Clearance at eaves and rakes, which varies more between editions and amendments than any other dimension here.
Detached structures, small arrays and low-slope roofs are treated differently, and most editions carry exceptions for roofs with a slope at or below 2:12.
Why the same roof gets two answers
This is the part that costs installers time. Three things vary independently:
- The edition adopted. Jurisdictions adopt on their own cycle. A county may be on the 2021 IFC while a city inside it is still on 2018.
- State amendments. Several states amend the fire code wholesale. California's residential requirements and its smoke-ventilation provisions are the most familiar example.
- Local amendments. Individual jurisdictions add their own, often after an incident. These are the ones that do not show up in a code book at all.
So "what are the setbacks" has no national answer. It has a per-jurisdiction answer, and the only reliable way to get it right is to check the adopted edition and amendments for that jurisdiction before the array is laid out — not after the correction notice.
How it should appear on the drawing
Dimensioned on the site plan, hatched, and labelled with the dimension and the code basis. Not a note saying pathways will be provided — the actual clear widths, drawn to scale, measured from the module edge rather than the rail end.
Where an exception is being relied on — a small array, a low slope, a detached structure — state the exception on the sheet. A reviewer who has to work out why your setback is 18 inches instead of 36 will often just write the correction.
The common rejections
| What happens | Why |
|---|---|
| Setback drawn to the wrong edition | Designed to the newest published code, not the adopted one |
| Pathway measured from the rail | Clear width is to the module edge |
| Exception used but not stated | Reviewer cannot see the basis for the smaller dimension |
| Array percentage not shown | The ridge setback depends on it, so it has to be on the sheet |