The Vegetation Clearance Blog

Four calendars run across a California utility corridor: the declared fire season that switches the Public Resources Code clearance duty on, the burning permit period that puts tools on the truck, the air district's burn day, and the nesting bird statutes that carry no dates at all.

How a fire-injured tree becomes a dead tree under PRC 4293 and GO 95 Rule 35, where the assessment criteria actually come from when no California rule supplies any, when the wood becomes a timber operation, and what a post-fire tree record has to name.

Why "very high fire hazard severity zone" is a defined term in two separate California codes, which instrument adopts each one, how the two move on different clocks, and why neither of them changes a clearance distance on a conductor.

A plowed or cultivated orchard is the only crop California's clearance rules name by name. What GO 95 Table 1 footnote (jjj) does inside the High Fire-Threat District, what 14 CCR 1255(c) and 1257(a)(2) switch off in a State Responsibility Area, and why both answers turn on how the orchard floor was farmed on the day somebody looked.

The retention clocks running on a single California vegetation file, when each one starts, which party the rule actually names, the Commission records order from 1912 that does not reach any of it, and the three clauses anywhere in the stack that stop a deletion.

GO 95 Rule 18 makes an imminent vegetation hazard a Level 1 and gives it the only immediate deadline in the stack. This is what actually authorizes the cut, what each authority costs, and what the file has to show afterward.

On a pole shared by an electric utility and a communications attacher, GO 95 assigns the vegetation duty facility by facility rather than pole by pole: Rule 35 binds both companies, Appendix I prices the same tree differently in each column, Rule 18-A sets the notice clock, and the Public Resources Code never reaches the attacher at all.

Which species close a clearance faster than a cycle can restore it, the three places California law lets a species into a clearance decision, and what a record has to carry when the specification on one tree is larger than the route default.

A palm owes the same GO 95 and PRC 4293 clearance as any other vegetation, but the exemptions, the felling duties and the trim cycle are all drafted around trunks, limbs and branches. What that changes on a real span, and what the record has to say instead.

Where growth rate sits in a clearance specification, which regulations require a utility to account for it, why the rate that matters is the rate of approach to the conductor, and what a record has to carry for the assumption to be defensible.

Every enforceable vegetation clearance in California is measured from the conductor. What each rule names as the two endpoints, why a height above ground is a different quantity, and what a defensible measurement record has to say.

How NERC establishes a right-of-way width from engineering documents, why that number is capped by but rarely equal to the recorded easement, what the California clearance rules use instead of a width, and what a span file has to name.

The Fire Incident Data Collection Plan approved in D.14-02-015, the three-line test that puts an ignition in it, the twenty-three fields it asks for, and why the entire vegetation record of a vegetation-caused fire is the word Vegetation in one drop-down.

The FAC-003-5 quarterly Sustained Outage report, the two federal definitions of Sustained Outage that disagree, what footnote 4 removes from the count, and why California's annual reliability report has no vegetation line in it.

The four tests in FAC-003-5's Applicability section, what puts a line below 200 kV in scope and what takes it out, the two gates a generator lead has to pass, and the dates on either end of a designation.

The exact words of GO 95 Rule 35 Exception 2, the two artifacts it requires, who has to refuse before a refusal counts, and every obligation that keeps running after one is on file.

Which body can issue what, against whom, on a California vegetation finding: CPUC audits and citations, Energy Safety notices of violation, CAL FIRE inspections and the misdemeanor behind them, WECC settlements under FAC-003, and the utility's own program.

The four separate content standards a California vegetation record is written to, what a CPUC records request actually asks for, why the correction due date in the file is the utility's own number, and the fields that let a stranger close a finding years after the crew has gone.

How PRC 4125 through 4128 draw the State Responsibility Area, why neither Local nor Federal Responsibility Area is defined anywhere in the Public Resources Code, and which vegetation obligations actually change when a span crosses the line.

What moved under Requirement R1 when FAC-003-5 reserved R2 on April 1, 2024, why the severity of a finding did not change, the sentence about non-IROL lines the standard stopped saying, and the places the current standard still names a requirement that no longer exists.