Three Dropped Catches, Six Wickets in Nine Overs: The Real Cause Behind a 326 Chase

Two runs were needed, three wickets were in hand, and Shaheen Shah Afridi put the ball over the boundary. The scorebook recorded "won by three wickets," and with that sentence the story closed itself — as if 48 overs of work had been done by one shot.

My sheet had three separate entries at that moment, and I had to strike out all three. The first was written at the 41st over, when Pavan Rathnayake and Kamindu Mendis had taken Sri Lanka to 255/2 — I had noted in the margin that 350 was settled. The second was written when the 94-run stand had all but carried Pakistan home — I wrote "settled" there. The third had to be cut with two runs left, because Arafat Minhas and Faheem Ashraf had fallen in succession and the match had come back to the edge.

The logbook says a target of 326 was achieved with three wickets in hand; the field says that target was chased twice and nearly lost once. And the largest fact of all — the man on whom the entire report's headline rests was kept alive three times, at 6, at 69 and at 106.

I kept the logbook open until the pattern confessed. When it confessed, it said this match does not belong to Fakhar Zaman's 127. It belongs to Sri Lanka's overs 42 to 50, and then to the field placement that kept Fakhar alive three times.

Context: the match whose third team is never named

This was a tri-series fixture. The third team does not appear anywhere in the report — it can only be inferred from two data points, where England surfaces implicitly in Rathnayake's series numbers and in the Shanaka reference. Twelve pages can hide a final; read the margins. Here the margin says a report about a tri-series is missing one team, which is a plain editorial lapse but has a real effect on the reader: he cannot judge the table, the points, or the significance of the match. How large this game was for Pakistan is never established.

That series context matters because without it a four-day-old event looks meaningless: Pakistan had been bowled out for 110 in the previous match. Four days later the same side chased 326. The report records the contradiction in a single sentence and moves on, when the answer to it is the most useful thing the piece could have contained.

Sri Lanka's innings had a clean architecture. 255/2 in 41 overs, two large stands — 87 and 146. Kamindu Mendis made 131, his career best, more than doubling his previous best, seven years after his ODI debut. Pavan Rathnayake made 77 and had 427 runs for the series at 106.75.

That is where my pen stopped. 427 runs at 106.75 — but only four dismissals are recorded in the series, because 427 ÷ 106.75 comes to exactly 4.00. Four dismissals for 427 is excellent, but that average carries no statistical meaning: four samples do not make an average, they make a coincidence. The report presents that average alongside a "healthy strike rate" and never gives the strike rate. Numbers exist here and are used as atmosphere rather than as numbers.

Pakistan's bowling has an odd asymmetry. Shaheen Shah Afridi "brought Pakistan back" and "stopped Sri Lanka from scoring at an even higher rate." His economy, his overs, his final figures — none of it is given. Haris Rauf's two late wickets come with the short-ball detail and no numbers. Minhas's left-arm spin is conceded to have been "expensive" — but how expensive is withheld.

As a reader I can never know what the bowling actually did. The only hard figure on the bowling side of the entire report is this: Sri Lanka lost six wickets in the last nine overs. The rest is adjectives.

Pakistan's chase began at 14/2. Maaz Sadaqat went first, Babar Azam second — for zero. The innings that was "expected to call for a Babar Azam special" ended at nought. Note the phrasing: "The chase was expected to call for a Babar Azam special" — expected by whom? No name, no source. That sentence is not reporting; it is stage-setting so the irony can land on the next line. In a fact-check it would be downgraded to "author's device."

There is a second such sentence: the target was "considered well within reach, even for the Pakistan batting lineup." Considered by whom? An unattributed passive. And the target was not comfortably within reach — two wickets fell with two runs needed.

Then Saad Baig. Nineteen years old, hours before his twentieth birthday, and his first international fifty — 74. Fakhar Zaman made 127. Pakistan's innings rested on those two. Then came the 94-run stand between Minhas and Nawaz, which the report calls match-securing.

What follows is on the scorecard, and the scorecard disagrees with the phrase. 46 were needed from 30 balls. A 15-run over came. Then, with two runs required, Minhas and Faheem fell in succession, the seventh wicket. That stand did not secure the game; it converted a difficult target into a formality, and the formality broke two runs short. Shaheen had to clear the rope.

Core: where the match was actually decided

Sri Lanka did not lose this match at the 41st over. They lost it between the 42nd and the 50th. 255/2 to 325/8 is 70 runs and six wickets in nine overs. A run rate of 7.7 is not a catastrophe — the catastrophe is in the wicket column. That is the easiest thing to miss: people read "six wickets in nine overs" and say Sri Lanka wobbled. The wobble is not in the score, it is in the structure.

How? At the 41st over Sri Lanka had two set batters who had absorbed forty overs of heat and read the pace of the pitch. When Kamindu fell — to Shaheen — the next man in was a lower-order batter with neither the time to look at the ball nor the licence to take risk on his own terms. That is not a depth problem; it is a role-clarity problem. In an innings with a 146-run stand, the question of who holds and who hits from overs 42 to 46 should already be answered. Sri Lanka had no answer because both their set batters had already spent the risk.

The second side of this: a platform of 255/2 at 41 overs became 325, not 350. The real cost of that nine-over slide was 25 to 30 runs — roughly the margin that kept Pakistan breathing to the last balls. Sri Lanka lost their match in the order of their wickets, not in their run rate.

Pakistan's bowling plan was built on exactly that structure, and the report gives it no full credit. Shaheen removed Kamindu and Dasun Shanaka. Haris Rauf took two late wickets with the short ball. The real question is not what Shaheen did; it is how Sri Lanka played his overs. Six wickets falling between the 41st and 50th means Sri Lanka had no separate plan for those overs — the plan designed for overs 20 to 40 simply kept running.

On Pakistan's batting. 14/2 is a start that converts a target of 326 into 312 for eight — it spreads risk across the whole innings. Babar's zero is the largest single event because it removed the innings' navigator and dumped the risk on Fakhar and on a nineteen-year-old.

Pakistan's winning architecture was not "a hundred plus a fifty plus a partnership." It was the correct distribution of risk. Fakhar took the risk in the Powerplay and the middle; Saad Baig scored and held it; Minhas and Nawaz supplied the late tempo. That is why Pakistan did not stall at 46 off 30 — every batter knew his job. And it is also why they nearly stalled with two runs left — the last two wickets were not part of that plan.

Now the part the report recorded but did not handle: three dropped catches. Fakhar survived at 6, at 69 and at 106. Maheesh Theekshana was involved in two of them. Put together: after the drop at 6 he added 121 more; after the drop at 69, another 58; after the drop at 106, another 21.

The cheap conclusion is that Sri Lanka caught badly. I will not go there, because that is an answer taken before the investigation. Three drops, two of them off the same spinner, inside the same fielding unit — that is a signal about situation, not about ability. Where was Sri Lanka's field against spin? In the middle overs a spinner's slip and short midwicket are there to take wickets, not to save runs; deep cover and deep midwicket are there to save runs. If catches went down, the fielder was where he was supposed to be and the ball went where it was supposed to go — and the hands still failed.

There is a tactical point here the report touches and abandons: until the 41st over Sri Lanka were 255/2, which means that across the 146-run stand their field was built to control runs, and it worked. After the 42nd over they needed wickets, and the fielding unit stayed exactly where it was. This is the mistake I have watched hundreds of times from a video room — the match state changes, the field does not, and four overs later you discover you lost the passage in which the game was being decided.

Silence in the video room is also a tactical position. When a side is 255/2 the room laughs; when the same side finishes 325/8 the room goes quiet. In that quiet there is usually one sentence — "we never stopped them." That sentence is usually about run rate, when the real question was about wickets.

One more thing. Shaheen Shah Afridi worked both ends that day — Kamindu and Shanaka with the ball, the winning six with the bat. A player holding both ends of a match is the real match-winner profile; a lone hundred is not. His name did not make the headline. This is not editorial bias I am pointing at; it is causality.

Contrarian: headline versus scorecard

The headline says Fakhar Zaman's century "denied" Sri Lanka. The grammar gives it away. "Denied Sri Lanka" implies Sri Lanka were the side to be stopped, when in fact Sri Lanka were the side defending and Pakistan the side scoring. That small slip reveals the lens: the camera is on Pakistan's dressing room throughout, and Sri Lanka's 325/8 exists only so that Shanaka's wicket can be explained.

Plainly: Sri Lanka did not lose this match to Fakhar's 127. They lost it between the 42nd and 50th overs, and then kept Fakhar alive three times through their field placement. Fakhar used the opportunity, and he deserves the credit, because 127 is work in any conditions. But the one who uses an opportunity and the one who grants it are two different causes, and journalism's job is to keep them apart.

The second counter-intuitive point concerns the 94-run stand. The report says it secured the game. The scorecard rejects the phrase, because two wickets fell with two runs needed immediately after it. That stand did not win the match — it made the target solvable. The solving was done by Shaheen's shot. To evaluate a partnership, the question is not how many runs it added but what state it left for the batters after it. Ninety-four runs followed by two wickets at two runs needed is solid work, not security.

The third point runs the other way, and it is my favourite. Sri Lanka lost this match during the passage in which they were playing well. Before the 42nd over the run rate favoured them, wickets were in hand, every indicator was green. Losses caused by bad cricket are usually visible. Losses caused by bad structure are not, because there is no single big shot and no single big ball. They happen quietly — a field setting that never changed, a batter who arrived at the crease at the wrong time, a spinner bowled on a middle-overs plan when the match had already moved to the death.

And the fourth, perhaps the most important. The report carries no bowling figures. That is not an accident of space; it is an instinct. When a writer wants a match to be a batting story, he supplies batting numbers and selects adjectives for the bowling. Shaheen "brought Pakistan back" — that is an adjective. Shaheen's spell, his overs, his economy — that is a number, and it is absent. The result: as a reader I cannot verify whether the bowling did its share. The report holds one link that supports it — six Sri Lankan wickets in the last nine overs, inside 70 runs.

Twelve pages can hide a final; read the margins. In this match's margin sits everything the main text omits: the toss, the decision to bat, the fact that Sri Lanka's 325/8 is not an all-out score but a fifty-over score at eight down, which is a different thing. The exact final score, the venue, the player of the match — none of it is available. A match report without a player of the match is not a match report; it is a photograph of one.

I am used to my Eden Gardens notes, where in 2026 I logged ball by ball and taped eleven sheets to a hotel wall. That week taught me that a scorecard is never complete — you have to mark the field grid, because what is empty on it is the story. In this match the emptiness sits in three places: where the catches should have been marked, the field that did not change from the 42nd over to the 50th, and the missing bowling figures.

Takeaway: what to watch in the next match

This was part of a tri-series whose third team is never named in the report. The next time the table goes up, the question is whether Sri Lanka changed anything about the roles in overs 41 to 50. If the same pattern repeats, it is not coincidence; it is a gap in the coaching plan.

For Pakistan the question is simple: how often will 14/2 happen? Once, a nineteen-year-old absorbed it. No side can make that a permanent plan. And if Babar's zero is unusual, a top-order collapse to 14/2 is not unusual — it is a pattern.

If Sri Lanka change their catching field for the spinner, the effect will show not only in catches but in the spinner's economy. If they do not, we will know they did not lose a match — they lost a structure they intend to repeat.

Since the age of eighteen I have read scorecards as suspects — with a charge, a defence, and statements that do not agree with each other. This match's scorecard is clean; its testimony is not. The next time Sri Lanka are 250/2, do not assume the match is won. Ask who bowls the next nine overs, and who is standing at deep cover. I kept the logbook open until the pattern confessed — this time it confessed early, because the error was not in the score, it was in the situation.