A scheduled inspection week is really an access exercise

A scheduled inspection week is really an access exercise

On 30 September, Hawaiian Electric said it would fly drone inspections of power lines, poles and electrical equipment across Maui and Lanai through the whole of October, concentrating on areas the utility treats as elevated wildfire risk. The community list is long, running from Lanai City and Wailuku to Kahului, Kihei and Wailea, and on to Haiku, plus the settlements strung along the Hana Highway. Most coverage of a notice like this stops at the aircraft. The operational content sits in the rules published alongside it, because an overhead line inspection is not a flight over empty land. It happens in easements, alleys, back yards, and the strip between a fence line and a feeder.

What the utility told the public

The notice carries five commitments that are worth copying into any scheduled inspection program: - Work happens on weekdays, starting at 7 a.m. and finishing at 5 p.m., if the weather allows. - Crews travel in marked utility or contractor vehicles. - Operators on foot wear branded hard hats and safety vests, and every worker carries a contractor or employee identification badge. - The scope is poles and overhead lines. Nobody will ask to enter a home or business. - Where a pole sits inside a yard, the crew announces itself before touching the equipment, and the flights do not interrupt service. None of that is glamorous. All of it decides whether an inspection week survives contact with the public.

Why the access page matters more than the payload

The first question from a resident is never about sensor resolution. It is who the person in the vest is, why they are standing in the yard, what the camera is pointed at, and where images of private property end up. A published answer removes most of the reason to call someone, and one complaint can cost a crew more of a day than any flight planning ever does. There is a harder edge too. Interference with a scheduled utility flight is not a private property debate. Program material for the same utility notes that damaging drone equipment or interfering with operations can attract federal enforcement.

Build the same page for your own program

The publishable version fits on one page: 1. A schedule envelope: dates, working hours, and the weather caveat. 2. A scope statement: what the aircraft inspects, and what happens to the imagery afterwards. 3. An identification rule: vehicle marking, branded outerwear, a badge on every worker. 4. A property rule: the boundary you will not cross, and the announcement step when a pole or a guy wire forces you into someone's yard. 5. An impact statement, if your work touches anything a customer depends on. 6. A phone number a resident can reach during working hours, answered by someone who has the schedule. Hand the same page to the customer service desk, the local detachment, and any landowner group along the route before the first sortie. Then brief it in the tailgate meeting, because the crew at the pole is the one who has to explain it.

Operational takeaway Write those six lines now and treat them as a release requirement rather than a communications task.

In a fall inspection campaign, aircraft availability is rarely the constraint. Public cooperation is, and it is cheaper to earn on paper than to recover in the field.