होमWorld CricketThe Non-Striker Run-Out: The Clause That Was Due to Change Seven Days After Lord's

The Non-Striker Run-Out: The Clause That Was Due to Change Seven Days After Lord's

**मुख्य उत्तर:** नॉन-स्ट्राइकर एंड रन-आउट अब MCC की 2022 संहिता (दूसरा संस्करण) के कानून 38.3 के अंतर्गत आता है, जो 1 अक्टूबर 2022 से लागू हुआ। इससे पहले यह 2017 संहिता के कानून 41.16 में 'अनफेयर प्ले' के तहत था। **मुख्य तथ्य:** - 24 सितंबर 2022, लॉर्ड्स: दीप्ति शर्मा ने चार्लोट डीन को नॉन-स्ट्राइकर एंड से रन आउट किया; भारत 16 रन से जीता। - MCC ने पुनर्वर्गीकरण मार्च 2022 में घोषित किया; प्रभावी तिथि 1 अक्टूबर 2022 रही। - 25 मार्च 2019, जयपुर: आर अश्विन द्वारा जोस बटलर का रन आउट, IPL इतिहास का पहला ऐसा मामला। - असफल कोशिश पर गेंद डेड होती है और ओवर में नहीं गिनी जाती; गेंदबाज़ कोई वैध गेंद नहीं खोता। - स्कोरकार्ड में यह सामान्य रन आउट के रूप में दर्ज होता है; अलग श्रेणी नहीं है। **स्रोत:** MCC Laws of Cricket, 2017 संहिता (1 अक्टूबर 2017 से प्रभावी); MCC 2nd Edition 2022 (1 अक्टूबर 2022 से प्रभावी); घटना तिथियाँ यथावत। | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर:** प्रश्न: क्या नॉन-स्ट्राइकर एंड रन-आउट से पहले चेतावनी देना कानूनी रूप से ज़रूरी है? उत्तर: नहीं, MCC की 2017 या 2022 किसी भी संहिता में चेतावनी का कोई क्लॉज नहीं है; यह केवल प्रथा है। प्रश्न: लॉर्ड्स की घटना किस कानून के तहत adjudicate हुई? उत्तर: उस दिन 2017 संहिता का कानून 41.16 लागू था, क्योंकि 2022 संहिता 1 अक्टूबर 2022 से प्रभावी हुई। प्रश्न: असफल कोशिश पर गेंद का क्या होता है? उत्तर: गेंद डेड हो जाती है और ओवर में नहीं गिनी जाती, इसलिए गेंदबाज़ को कोई वैध गेंद नहीं खोनी पड़ती।

The ball that was never bowled at Lord's on 24 September 2026 became the most argued-about ball in Indian cricket. Deepti Sharma stopped in her delivery stride, the ball stayed in her hand, Charlotte Dean was out of her ground, and the finger went up. The scorebook recorded one line: run out, bowler Deepti Sharma. India won by 16 runs, Dean was left unbeaten on 47, and what followed was not cricket but a season of speeches.

What the commentary box did not say that evening was this: the clause under which Dean was dismissed had seven days left to live. Under the MCC's 2026 code, in force from 1 October 2026, the provision sat at Law 41.16 — inside the Unfair Play chapter. Under the MCC's second edition in 2026, announced in March 2026 and effective 1 October 2026, the same provision was reclassified as Law 38.3 — inside the Run Out chapter. Lord's fell into the seven-day window between the announcement and the commencement.

The Non-Striker Run-Out: The Clause That Was Due to Change Seven Days After Lord's

That is not a technicality. It decides what the two sides were actually arguing about, and why the argument cannot close.

The version history

I keep a ring-bound file of BCCI circulars and MCC amendments, every page dated at the top. The habit dates to October 2026, when I was scoring a DDCA Under-19 league match at the Feroz Shah Kotla and a bowler ran out the non-striker in the 46th over. Both umpires reached for the rewritten laws, then three weeks old. I spent three days in the Delhi University library checking Law 41.16 against the 2026 code, because the only useful question was what had actually changed.

The chain is clean. The 2026 code carried the provision in the Unfair Play chapter too. The 2026 rewrite made the bowler's permission explicit and settled the consequence of a failed attempt — dead ball, not counted in the over. The 2026 edition moved it out of Unfair Play and into Run Out.

Changing the chapter changes the question. Under Law 41 the umpire's first question is whether the act was unfair, and that chapter hands him a vocabulary of management: warn, hold the game, speak to the captain. Under Law 38 the question is only whether the batter was out of her ground and whether the ball was dead. One chapter makes the official a manager; the other makes him a surveyor. On the night of Lord's, broadcasters argued about morality while the umpires held a clause with no column for morality in it.

And the warning. It is repeated in every debate and it is wrong every time. No edition of the code — 2026 or 2026 — contains a clause requiring a warning. It is convention, coaching habit, an unwritten deal between captains. Convention has no version history, so it cannot be cited, only remembered. The side without a document always retreats into the language of feeling. That retreat is the whole argument.

Back to the scorer

Open the Lord's scorecard. The dismissal column reads: run out. Bowler: Deepti Sharma. Nowhere does it record that this was the contentious variety, that the bowler stopped in her stride, or how far the batter had advanced.

The scorebook has no column for this controversy, which is why every argument about it restarts from zero. Every other disputed decision accumulates paper — referrals, soft signals, review outcomes. This one files itself away as a plain run out, and thirteen months later, when it happens again, nobody can say how often it has already happened, at what level, or how often a warning was given.

The Non-Striker Run-Out: The Clause That Was Due to Change Seven Days After Lord's

I understood that gap in 2026, when the Russia World Cup handed me its least glamorous job: logging every VAR review. The tournament produced a then-record 29 penalties and I built a forty-page ledger — minute, on-field call, review, reversal, outcome. When India toured England that August I rebuilt the same ledger around the soft signal. It worked because FIFA published a register. No board has published one for this.

The Non-Striker Run-Out: The Clause That Was Due to Change Seven Days After Lord's

Through the 2026 IPL in the UAE I logged every Level 1 code-of-conduct sanction against the IPL Code, clause by clause. That ledger still updates weekly, because the code numbers its levels. This dismissal has no level. What is not recorded does not accumulate; what does not accumulate cannot be adjudicated.

Three angles of replay

The dead-ball question comes first. Someone always says the ball was not live because the bowler had not bowled. The code does not say that. The ball is dead when it is finally settled in the hands of the wicketkeeper or the bowler; it is live from the first movement of the run-up. Clear that one sentence and half the argument evaporates.

Second, the warning convention — already dealt with, and structurally unwinnable for the side that relies on it.

Third, the part nobody discusses. The 2026 rewrite ruled that a failed attempt is a dead ball and does not count in the over. The cost of trying is therefore close to zero: the bowler loses no delivery. The batter's exposure is a full wicket. That asymmetry sits not in the law but in the consequence of failure, and it is the real incentive. No captain has written a line about it.

Data and rhythm

Watching from the ground and from the scorer's table over the past decade, one pattern repeats. Analytics answers, with great confidence, a question nobody asked. Release-point data tells you where a bowler actually lets go; models estimate the batter's average lead in centimetres. The code does not ask where the bowler released. It asks at what instant the bowler would normally have been expected to release. Expectation is a judgement, not a measurement. The data hands you the actual; the law wants the normal.

That is where the analyst walks into the dressing room and separates from the rhythm of the match. The arithmetic can be flawless and still irrelevant, because the umpire is not weighing what is being weighed. I have watched enough broadcast graphics collapse against the official scorecard three overs later to distrust the confident version of any number.

One date belongs in the record and is not there. 25 March 2026, Jaipur: R Ashwin ran out Jos Buttler this way, the first such dismissal in IPL history. It appeared in no match referee's report under any level, because no rule had been broken. The controversy lived in newspapers and never entered the institution's archive. Four years later it happened again at Lord's and the argument resumed exactly where it had been abandoned.

The contrarian read

The 2026 reclassification was sold as clarity: stop moralising, it is a run out. On the ground the effect ran the other way. Under the Unfair Play chapter an umpire could manage — stop the game, talk to the bowler, call the captain, give the warning convention some legal air to breathe. Law 38 removed all of it. Out or not out. A law with no room to manage produces incidents instead of conversations.

The spirit-of-cricket side cannot win a documentary argument, because the spirit has no edition, no author, no date. You can cite 38.3; you cannot cite a feeling. The debate is rigged toward the code by its own architecture, which is why the losing side escalates into moral language. That escalation is not anger. It is the only move left.

The real preventive fix is not in the law at all. Captains are briefed in writing on DRS protocol, on over rates, on the levels of the code of conduct. Nobody is briefed on this. Coaches teach a convention with no clause behind it. That gap is the cause.

Takeaway

The next flashpoint will arrive in a knockout decided by a single run, and the argument will restart from zero. If the MCC revisits Law 38.3 in its next edition the terms of debate will shift again — and the archive will still be unable to tell us how often this has happened in Indian domestic cricket. The useful reform is documentary, not moral: a mandatory note in the match referee's report, and a defined expected-release frame in the playing conditions so the third umpire has something fixed to look at. The question is not whether the run out is fair. It is whether the paperwork can reach the argument in time.

संबंधित खिलाड़ी