DRS Howler Bangladesh-Zimbabwe Mirpur 2026: Umpire's Call

The 31st over of Zimbabwe's second innings at Mirpur was the over the match turned on - and the over the DRS algorithm decided it. Sikandar Raza, on 38, was struck on the pad by a Mehidy Hasan delivery that was, by the unaided naked eye, plumb in front. The on-field umpire said not out. Bangladesh reviewed. The ball-tracking output said three reds - hitting in line, impact in line, hitting the stumps - but the projected impact was, by less than a third of a ball-width, on umpire's call. Raza stayed. Twenty-two balls later, he was caught and bowled, but by then the asking rate had inverted, and the match was effectively decided. The howler debate is back. The umpire's-call argument is older than this match, and is not going away.

What Actually Happened

The delivery was a Mehidy off-spinner that pitched on middle, drifted slightly, and hit Raza on the pad below the knee-roll. The on-field decision was not out. The Bangladesh review came after a captaincy consultation between Najmul Hossain Shanto and the wicketkeeper, with the squad widely confident the ball was hitting.

The third umpire's output ran as follows.

DRS Check	Result
Pitching	In line, on middle
Impact	In line, just below the knee-roll
Wickets	Hitting - top of leg-stump, 47% of ball above stump zone

The 47%-above-stump-zone reading is the trigger for umpire's call - the threshold for an automatic decision overturn requires more than 50% of the ball to be inside the stump zone. The third umpire upheld the on-field not-out call, and Raza stayed.

The On-Field Read vs The Tracking Read

The on-field read was that Raza had been struck low enough on the pad that the ball might have skidded under the bails. The tracking read was that the ball was hitting the top of leg-stump - exactly the kind of marginal hit that umpire's call was designed to capture. The two reads were not in conflict. The framework was working as designed. That is exactly the part the Bangladesh dressing room found hardest to accept.

The Umpire's-Call Argument: Three Positions

Position One: Keep It

The MCC's standing position - and the ICC Cricket Committee's working majority - is that umpire's call respects the ball-tracking technology's margin of error. The projected trajectory of the ball is computed with a tolerance of approximately 5mm, and umpire's call is the framework's honest acknowledgement of that uncertainty.

Position Two: Abolish It

A vocal minority - including a number of recently-retired Test captains - argues that umpire's call is a bureaucratic complication that breeds dressing-room frustration without producing better decisions. The argument runs: if the ball is hitting, it is hitting; if the projected trajectory has any of the ball clipping the stumps, that should be out. Our umpire's call DRS rule explained 2026 controversy piece covers this argument in depth.

Position Three: Reform It

A middle-ground position - the one being floated through the ICC Cricket Committee's November 2026 review - is that umpire's call should be retained but the threshold should be tightened. The proposal floated is that the 50% threshold becomes a 40% threshold, with the soft signal weighting also increased. Neither captains nor umpires unanimously favour any of the three positions.

The Bangladesh-Camp Reaction

Najmul Hossain Shanto's post-match line was unusual for him - "We do not always agree with the system, but we have to play within it." The deeper read, sourced through the BCB media manager, was that the dressing room felt the Raza decision was the most consequential howler of the cycle so far. Mehidy Hasan, the bowler involved, was more direct in a separate broadcast interview: "The ball was hitting. The framework said it was umpire's call. That is fair. But it does not feel right."

The Zimbabwe-Camp Reaction

Sikandar Raza, naturally, took the opposite view. "The system did its job. The technology has uncertainty. The umpire was on the field; his call held." That is, almost word-for-word, the MCC line on umpire's call.

What The Tracking Showed - And Did Not Show

The tracking output showed:

• 47% of the ball inside the stump zone
• 5mm tolerance applied to the projection
• the on-field umpire's call was the decisive input

What the tracking did not show, and what the broadcast subsequently revealed via a separate mid-pitch camera, was that the seam orientation on the delivery was unusually upright for Mehidy's release - which, on a Mirpur surface that had begun to take spin, meant the ball was likely to have continued straighter than the tracking projection accounted for. That is a piece of qualitative information the framework does not currently weight.

The Wider DRS Context

The Mirpur howler is the third such case this year that has triggered the umpire's-call discussion - the others being the Brathwaite lbw in the West Indies-Pakistan first Test (where the call went the other way - umpire's call retained an out decision against the batter), and the Lyon vs India ODI lbw at Adelaide (where the call gave a not-out that the broadcast read as plumb).

Our DRS decision review system complete guide covers the framework in depth. The Bangladesh vs Zimbabwe 1st ODI Mirpur recap covers the broader Mirpur leg of the series that produced this case.

What Happens Next

The Bangladesh board has not formally appealed the framework, on the basis that the decision was not procedurally wrong. The ICC Cricket Committee will, however, take this case forward to the November 2026 review, where the umpire's-call threshold question is back on the agenda.

A more immediate consequence: the Mirpur match referee's post-match note, leaked partially to BD Cricket, indicates that the third-umpire protocol may be tightened to require the on-field umpire to also review the tracking output before the umpire's call decision is reflected. The current protocol does not require this, and the change - if implemented - would close a small but recurring gap.

The Honest Read

The Mirpur howler was not a howler. The framework worked as designed. The decision was on the margin, and the margin was the umpire's call. That does not feel right to the camp that lost out. The ICC Cricket Committee's November 2026 review will revisit the threshold question, with three live positions on the table. The likely outcome is reform-not-abolish, but the Bangladesh-Zimbabwe case is now part of the supporting argument set for whichever position prevails.

FAQ

Was the third umpire's decision wrong? No - the framework was applied correctly. The decision is not procedurally appealable.

What does umpire's call mean exactly? When the ball-tracking output shows the ball clipping the stumps without 50% or more of the ball inside the stump zone, the on-field umpire's decision stands.

Is the threshold being changed? The ICC Cricket Committee will review at the November 2026 conference. A 40% threshold has been floated, but no decision has been taken.

Was the ball hitting middle or leg stump? The output showed top of leg-stump, with 47% of the ball above the stump zone.

How many howler incidents has 2026 produced so far? Three high-profile cases - Mirpur (this), Bridgetown (Brathwaite), and Adelaide (Lyon).