Breaker failure protection, designated 50BF, is a backup scheme that answers a dangerous question: what happens when a breaker is told to open on a fault but does not actually clear it. Protection has correctly detected the fault and sent the trip, yet the breaker sticks, its mechanism jams, or its contacts fail to interrupt, and current keeps flowing. The 50BF scheme watches for exactly this. When it sees that a trip was issued but current is still present after a short timer expires, it trips the surrounding breakers to isolate the fault another way, keeping one stuck breaker from letting a fault burn on a critical bus.
Breaker Failure Relay (50BF) in one line: A breaker failure relay (50BF) is a backup scheme that detects when a breaker has been commanded to trip but has failed to interrupt the fault current. After a set timer confirms current is still flowing, it initiates tripping of adjacent breakers to clear the fault, preventing a single stuck breaker from prolonging a fault on the bus.
Every protection scheme assumes that when it sends a trip, the breaker opens. Almost always it does, but breakers are electromechanical devices and they occasionally fail to operate. A trip coil can be open, a mechanism can bind, a control circuit can be broken, or the interrupting contacts can fail to clear the arc. When any of that happens on a real fault, the primary protection has done its job and the fault is still there, feeding energy into the system through a breaker that will not open.
The consequences escalate quickly. Fault current that should have been cleared in a few cycles keeps flowing, so the damage at the fault grows, the arc-flash energy released climbs with every additional cycle, and the equipment carrying the fault heats and stresses far beyond its rating. Upstream protection may eventually trip on a longer time delay, but that means clearing a much larger portion of the system after a much longer delay, turning a contained fault into a wide outage.
Breaker failure protection exists to close this gap deliberately rather than leave it to slow upstream backup. It is a last line of defense, layered on top of the primary protection, whose entire purpose is to recognize a failed breaker fast and take a defined action to clear the fault regardless. Because it must operate only in the rare case where a breaker truly fails, it has to be both fast enough to matter and secure enough not to fire when the breaker was actually going to open on its own.
The scheme has three parts working together. First, it is initiated whenever the primary protection issues a trip to the breaker, so the breaker failure logic starts watching at the exact moment the breaker was told to open. Second, a short timer runs, sized to give a healthy breaker enough time to clear the fault normally, plus a small margin. Third, and most importantly, a current check confirms whether fault current is still flowing. If the breaker cleared, the current is gone before the timer expires and the scheme resets quietly. If the timer expires while current is still present, the breaker has failed and the scheme fires.
The current check is what makes the scheme secure, because current is the most reliable evidence of whether a fault was actually interrupted. Rather than trusting a breaker's auxiliary contact, which only reports the mechanism's intended position, the 50BF logic looks directly at whether current is still crossing the breaker. Current still flowing after the trip and after the timer means the fault was not cleared, full stop, and that unambiguous test keeps the scheme from either missing a real failure or firing on a breaker that opened normally.
When the scheme does fire, its action is to clear the fault by other means. Because the failed breaker cannot isolate the fault, the 50BF trips all the other breakers connected to that same bus or zone so the fault is fed from nowhere, and in many designs it also sends a transfer trip to the remote end of the line so that source is opened too. Setting the timer is the key design decision: long enough that it never beats a slow but healthy breaker, short enough that a genuine failure is caught before the escalating damage and arc-flash energy get out of hand.
Breaker failure protection is applied where a stuck breaker would be most costly, which in practice means important buses, generator and transformer connections, and any point where losing the whole bus to slow upstream backup is unacceptable. It fits into the broader coordination scheme as the local, fast backup for a single breaker's failure, complementing the remote and time-delayed backup that upstream devices provide. Well coordinated, the two ensure a fault is always cleared: quickly by the primary breaker, quickly by 50BF if that breaker fails, and eventually by upstream protection if all else fails.
Because a 50BF operation trips several breakers and takes down a bus section, it is a significant event that engineers want fully documented. Which breaker failed, whether the initiation came in, whether the current check saw persistent current, and which breakers the scheme tripped in response all matter for the follow-up, since the stuck breaker itself must be found and repaired before the bus is restored. A raw report that the bus went dark is not enough; the sequence tells the real story.
A cloud SCADA platform such as Merobix reads breaker statuses, protection trips, and the 50BF operation from the switchgear's protection relays and PLCs, timestamps them, and trends them together. That gives operators a clear alarm when a breaker failure scheme has operated and a historized record of the sequence, so a crew arrives knowing a breaker failed and which one. On remote and unmanned facilities, where no one is present to see the switchgear act, that immediate, sequenced visibility is what lets the site respond to a rare but serious event instead of discovering it hours later.
50BF is the designation for breaker failure protection, combining the ANSI device number 50 for instantaneous overcurrent with the BF suffix for breaker failure. It refers to a scheme that detects when a breaker was commanded to trip but current is still flowing, meaning the breaker failed to clear the fault. The scheme then trips adjacent breakers to isolate the fault by another path.
It watches whether fault current is still flowing after the breaker was told to trip. When primary protection issues a trip, the 50BF scheme starts a short timer, and it checks the current at the end of that timer. If current is still present, the breaker did not interrupt the fault and has failed, so the scheme fires. Using current rather than the breaker's position contact makes this test reliable.
It clears the fault by tripping the other breakers around the failed one, since the stuck breaker cannot isolate the fault itself. That usually means tripping all breakers on the same bus or zone and often sending a transfer trip to the remote end of the affected line. This isolates the fault from every source feeding it, at the cost of taking down that bus section.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.