Your LiDAR Map Says the Power Line Is Clear. What Happens When the Trees Grow?

Your LiDAR Map Says the Power Line Is Clear. What Happens When the Trees Grow?

The LiDAR survey you carried out indicates that the power line has adequate clearance; however, the following heatwave might show that this is not the case.

Here’s the reason. The LiDAR vegetation clearance for power lines reflects the situation on a given day: the conductor at the temperature and load it was experiencing when the aircraft passed overhead, and the trees at the height they had reached that season. The figure contains no information regarding the condition of the line at the end of a hot afternoon when the circuit is under heavy load. It also gives no indication of what a rapidly growing canopy will be like by the following spring.

Then the post sets out to show you what the report does tell you and what it omits. That is its purpose. We’ll examine conductor sag, consider the trees that lie outside your analysis buffer, look at the ways in which the point cloud itself can mislead you, and then look at a validation workflow that you can carry out before any crew is dispatched. If you are responsible for managing vegetation on transmission or distribution lines or if you prepare such reports for someone who is, then this article is intended for you.

A clearance number is a snapshot, not a forecast

Begin by looking at what the survey actually measured. The aircraft noted the positions of the conductors on that day. Conductors are not stationary objects; when current passes through them, they heat up, expand, and sag. A slight change in the length of the conductor results in a considerable change in sag, since the line hangs in the form of a curve between two structures.

Allow me to give you a simple example. This is our own back-of-the-envelope calculation, so regard it as illustrative rather than as design data. Suppose the span is 300 m with a sag of 6 m on the day of the survey. If the conductor is warmed by 60 °C, using a typical expansion coefficient for an aluminium-steel conductor of about 19 millionths per degree, it becomes roughly 0.34 m longer, and the sag increases from 6 m to about 8.6 m. That means that more than 2.5 m of clearance has been lost, even though the conductor has done nothing out of the ordinary. Real conductors do not behave in such a simple manner because the tension changes, the steel core carries the load in a different way at high temperature, and the conductors creep slowly over their lifetime. That is the very reason why line design software has been developed. What matters here is the direction and the approximate magnitude of the effect.

Suppose wind is taken into account. In that case, the conductors swing sideways and move towards the trees situated alongside the line rather than towards the trees underneath it. The industry has been aware of this for a long time: the technical comments concerning the NERC vegetation standard state that the line modelling should include full rated conditions as well as wind swing, and that simple ‘danger tree’ algorithms are not sufficient for calculating the clearance distances. The standard is in fact based on three methods by which vegetation can come into contact with the line: growth from below, falling in from inside or outside the right-of-way, and conductors being blown into adjacent vegetation.

There’s one further complication, and it’s easy to overlook. In order to determine the clearance under hot conditions, you have to know the conductor temperature on the day of capture. In practice, this temperature is generally calculated from weather and loading data rather than being measured, so the clearance figure already has that uncertainty built into it before anyone has even touched the point cloud.

Does a LiDAR clearance report show that a line meets its vegetation requirements?

Not on its own, and I should be careful to use the word ‘prove’. In the United States, the current transmission vegetation standard, FAC-003-5, came into effect on 1 April 2024 and mandates that owners take steps to ensure that vegetation does not intrude upon a minimum clearance distance. The standard applies to transmission lines at 200 kV and above, as well as to some lower-voltage lines that have been designated as critical. It does not include distribution lines, where most vegetation-related outages are caused by trees outside the right-of-way falling in. A LiDAR report can serve as evidence in support of a vegetation management programme. It is up to your compliance team and your regulator to determine whether it meets the requirements in your area, not the point cloud.

The tree that causes the outage is often not in your buffer

Here is the interesting part, and that is actually the primary reason I wanted to write this post.

When someone thinks about vegetation clearance, they imagine a tree growing up into the wire. That kind of growth is genuine. However, examine what utilities discover when they compare outage records with LiDAR data. A Texas electric co-op stated that over 95% of its vegetation-related outages were due to trees outside the right-of-way, including live trees and not just dead ones. In Kentucky, a helicopter-based LiDAR and imagery programme recorded more than 125,000 vegetation risk observations, and almost 95% of the spans under analysis had some kind of grow-in or fall-in exposure.

Go through it once more; if the clearance inspection only checks the area right next to the conductors, it may show clear results even though the tree that ends up bringing the line down is 20 metres away.

Can a LiDAR detect trees outside the corridor?

It can, provided that the flight and the analysis are arranged for this. For instance, a distribution programme in Eastern Canada identifies trees within a 30 m buffer as possible fall-in hazards, not just the vegetation that is already in the clearance zone. The simple question for you to answer is this: what width did the analysis include, and how tall are the trees at the edge in comparison with the distance to the conductor? A tree that is 25 m tall and 18 m from the line is a fall-in candidate no matter what the clearance table states.

Terrain is also a factor here. On a slope, the trees on the uphill side have greater height acting against the line. Kentucky Power therefore shifted its emphasis on clearance to the upslope side of the corridor while keeping the total width unchanged, since it is there that gravity, the slope and tree height all combine. A symmetrical buffer treats both sides as being equal, but the ground does not.

Where the point cloud itself can mislead you

Until now I have taken it for granted that the data is correct. Let us verify that assumption, since the clearance figure is only worth as much as the classification that supports it.

Conductors, vegetation and everything else

A transmission corridor includes terrain, trees, towers, conductors and at times buildings, all of which are within a few metres of each other in the point cloud. The software has to determine which points correspond to wire and which to leaves. A paper by FIG on the classification of power lines from airborne LiDAR is straightforward in this regard: there is no perfect automatic classification, so manual or semi-automatic editing is usually necessary. The difficulty increases in urban areas since power lines are situated close to both vegetation and buildings. In the case where a conductor point is classified as vegetation, a section of the wire is lost; and if a branch is classified as conductor, false clearance is created that does not actually exist.

Density, occlusion and thin wires

A thin line serves as a conductor, and an aircraft can hit it with as few as a few returns per span. The problem of occlusion makes the situation even more serious since leaves above the wire or the wire’s own group of sub-conductors can create gaps. Researchers who are dealing with high-voltage bundle conductors point out that both occlusion and gaps caused by point density have an impact on power line extraction, and as a result they develop algorithms to reconstruct the missing parts. The reconstructions involved are fitted curves, which implies that an assumption has been made regarding the clearance value. Lower point density also generally leads to lower classification accuracy, a fact which one supervised classification study explicitly states in the case of lower-density airborne data. The scan angle and the direction of flight in relation to the line also influence the quality with which the wires are sampled. I would not provide you with a universal threshold in any of these cases since it will depend on the sensor, the type of conductor, and the terrain.

What to ask your data provider

Before trusting a report, I should ask four questions: what point density was achieved over the conductors, not just over the ground? How was the conductor class verified, and on what sample was it checked? What conductor temperature and wind condition does the clearance table assume? And how wide was the analysis corridor? If the provider is unable to give answers to these questions, then the figure might still be correct, but you would not be able to tell.

A validation workflow that does not trust any single dataset

What I would do when dealing with a clearance report before taking any action.

  1. Compare a classification sample with the imagery by selecting areas that vary in terms of terrain and canopy type, and then check the classified conductors and vegetation against the photographs. The mindset is explained in our post on why QA/QC is the real bottleneck in drone mapping.
  2. Carry out the clearance check under design conditions and request the results at the maximum operating temperature and with wind swing, not just at the conditions existing on the day of capture.
  3. Check the accuracy of the survey yourself. A survey can appear neat and yet still be wrong. You can verify it using checkpoints, as we explained in the post on why an RTK flight still needs checkpoints.
  4. Check the highest-risk spans in the field, since it’s not necessary to walk every kilometre—just go to those spans where the model indicates the clearance is smallest and to those where the data was of poorest quality.
  5. Repeat the measurements and assess the growth. The second survey shows how quickly the vegetation actually moved. Comparison between epochs is only valid when the two datasets are really comparable, which is the same kind of trap that we mentioned in the change-detection maps, which showed changes that the ground had not in fact made.

How frequently should a corridor be re-surveyed?

There is no one definitive solution. In the United States, FAC-003 calls for transmission lines to be inspected annually, but this refers only to the inspection duty and not to a requirement that LiDAR be flown every year. Some utility companies do carry out frequent flights: Florida Power & Light takes LiDAR measurements throughout the state each year, covering 50,000 miles of line. Others use longer intervals. My recommendation is that the growth rate should determine the frequency. In cases where the species is growing quickly, the climate is wet, and the ground is steep, shorter intervals should be adopted, while in areas with slow-growing vegetation, dry conditions, and flat terrain, longer waiting periods can usually be tolerated.

Not every conflict deserves the same crew

If your report includes a few thousand cases of vegetation conflict and you treat all of them the same, the budget disappears while the dangerous ones have to wait their turn.

A method which is based on risk involves putting a number of additional questions to each conflict. Specifically, how near is it, in terms of rings or distance bands, to the conductor? What effect would occur if this span failed, that is to say, how many customers does it serve, whether it is a main feeder or a lateral, and has the line previously failed? How quickly does this type of tree grow at this site? Does the tree lean downhill in the direction of the line? The utility literature gives a precise description of this kind of approach using proximity rings and priority categories together with factors such as the number of customers served, and previous work carried out on the line.

The following two examples illustrate the outcome. FPL is testing growth models on its multi-year LiDAR data in order to adjust for local growth rates rather than applying the same treatment to the entire circuit, since palms and bamboo do not strictly adhere to a fixed cycle. Furthermore, the Texas co-operative referred to before states that the removal of hazard trees identified by its model helped reduce vegetation outages by 60%. These are the results reported by one utility, not a guarantee for every network, but the trend is evident: it is better to target areas rather than distributing the effort evenly.

That’s one further point regarding regulation, as the subject is likely to arise. A draft report by NERC on wildfire risk from April 2026 is said to suggest that FAC-003 should be extended to lines rated between 100 and 199 kV. However, since it is only a draft, the specifics could be different, so it is important to verify the present status before making any plans on the basis of it.

What then should you take away from all this?

A LiDAR clearance report is a very useful tool, even though it can’t indicate what the line will do next month.

Start by finding out what conditions the figure refers to—such as the temperature on the day of capture, the wind, and the season. Next, verify where the analysis ends, since a great many outages begin outside of that point. Then regard the classification as something you should sample and check rather than something you should accept. Finally, use your field time and crew funds in the areas where the risk actually is.

Should you be carrying out a corridor study or looking at one that has already been carried out, our remote sensing services can provide support with this type of task. The question I want to leave you with is a simple one: when your most recent clearance report was issued, did anybody ask what conductor temperature it had assumed?

Back to blog

Leave a comment