The Fault Started Right After an Outage or Surge: Decision Tree

Why this matters

"It worked fine until the power went out" is one of the most useful sentences a customer can hand you, and one of the most misused. Handled well, it narrows your diagnostic path fast: you already know roughly when the fault started and what stressed the equipment. Handled badly, it becomes an excuse to blame the power company for a component that was already dying, or worse, to miss a genuinely surge-damaged part because the unit still limps along. This tree gets you to the right cause instead of the convenient one.

Start here: confirm the hazard is clear

Before any diagnosis, rule out an active safety issue. A surge or outage can trip a breaker for a real reason, damage insulation, or leave a component partially shorted and still drawing current. If you smell burning, see scorch marks, or the customer reports sparking at the time of the event, de-energize the circuit and inspect before you touch anything else. Only once the circuit is confirmed safe to work on do you move to cause-tracing.

Step 1: pin down the timing precisely

"Right after" means different things to different customers. Ask directly:

• Did it stop working during the event (mid-outage, mid-flicker), or only when power came back?
• Was there a single event, or has the area had repeated flickers or brownouts over days or weeks?
• Did anything else in the house or building fail at the same time?

A fault that appears the moment power returns points to a surge on restoration, which is common and often worse than the outage itself (utility reconnection and neighborhood re-energization can spike voltage briefly). A fault that appears mid-outage on backup or battery power points somewhere else entirely, often a pre-existing weakness the switchover simply exposed.

Step 2: check whether other equipment on the same circuit or panel failed too

This is the single best filter for genuine power-event damage versus coincidence.

• If multiple, unrelated devices on the same circuit or panel failed at the same time, treat it as a real power event. Move to the surge and protective-device sections in the related reference articles and inspect upstream protection.
• If only one device failed and everything else on the same circuit is fine, a true surge becomes less likely as the sole explanation, though not impossible if that device happened to be more sensitive or already marginal. Weight your diagnosis toward a component that was already weak and the event was the final push, not the sole cause.

Step 3: test the failed unit on its own merits

Do not skip straight to "surge damage" as a diagnosis. Test the equipment as you would any fault:

1. Check power is actually present and at the correct voltage at the unit's input.
2. Check the obvious protective devices first (fuses, breakers, internal thermal or electronic protection) before assuming a deeper board or motor failure.
3. If a protective device tripped and holds when reset, the event likely caused a real overcurrent and the device did its job. If it trips again immediately, something downstream is still faulted.
4. If nothing tripped and the unit is simply dead, test for continuity, correct output at each stage, and any burnt or discolored components before condemning a control board or module outright.

Step 4: separate "surge damaged it" from "surge exposed it"

A surge or outage can do two very different things, and the fix is different for each:

• Direct damage - the event overloaded a component past its rating and it failed on the spot. You will usually find a blown fuse, a tripped and unresettable protective device, or a visibly damaged part.
• Exposed a latent weakness - the component was already degraded (weak capacitor, corroded connection, aging board) and the transient simply finished it off. The failure looks identical from the outside, but the real story is "this was going to fail soon regardless."

Both are legitimate findings. The distinction matters for what you tell the customer: direct damage from an unusual event is a one-off, while an exposed latent weakness means you should also check similar-age components nearby for the same wear pattern.

Step 5: check for a documented history

Ask the customer, or check your own service history, whether the unit had any recent symptoms before the event (occasional trips, odd noises, slow performance). A unit with zero prior complaints that fails cleanly at the moment of a confirmed grid event is more likely genuine surge damage. A unit with a thin history of small symptoms that finally quit during the event is more likely the latent-weakness case.

Recap

1. Confirm no live hazard before touching anything.
2. Nail down exact timing: during the outage, or on restoration.
3. Check whether other equipment on the same circuit failed too, the strongest signal of a real event.
4. Test the unit normally, do not skip to a surge diagnosis by assumption.
5. Decide direct damage versus exposed latent weakness, and say which one you found.

References

• NFPA 70 (National Electrical Code) for overcurrent protection basics
• IEEE guidance on transient voltage surge suppression concepts
• See related: What a Brownout Does Differently Than a Full Outage; The Protective Devices That Should Have Prevented Power-Event Damage