Misoperation: What Do You Need to Know?
Case Study # 5
A 138 kV substation experienced a fault on the 138 kV local bus. The bus differential protection operated correctly and tripped the bus-connected breakers. One downstream transformer-feeder breaker also tripped, and at first this was reported as a feeder relay misoperation because the fault was not on the feeder itself.
However, the event analysis showed that the transformer-feeder breaker had been intentionally included in the bus differential trip matrix. It did not trip because its own feeder relay made an incorrect decision. It tripped because the station protection philosophy required it to open in order to isolate the faulted bus zone.
Was this a misoperation?
No.
This was not a misoperation. It was a correct trip according to the intended bus-clearing philosophy.
What the engineer should do next
Even though this was not a misoperation, the engineer still has work to do. If operations or maintenance personnel initially believed it was a feeder relay error, that means the trip philosophy is not being communicated clearly enough.
Corrective action/engineering remedy
Review and document the full trip matrix for bus differential, breaker failure, and intertripping logic.
Improve event report labeling so the true initiating protection element is easier to identify.
Train operations and maintenance teams on station-wide trip philosophy.
Ensure relay target interpretation distinguishes between local element operation and external trip logic.
Update one-line diagrams and protection narratives to show which breakers participate in bus clearing.
If needed, improve HMI or SER labeling so “bus differential trip” is more obvious than just “breaker opened.”
Final lesson
Not every surprising trip is a misoperation. Sometimes the real problem is not in the relay logic, but in how the trip philosophy is understood by people reviewing the event.