Pakistan's paceship crashes in front of Table Mountain
Sans Naseem and Afridi, Pakistan’s pace attack failed to inspire on a surface where elite quicks will get wickets
Danyal Rasool04-Jan-2025It would not strictly be true to say no Pakistan bowler delivered a single ball over 140kph today. The broadcasters have recorded it as such, and it’s certainly a fact South Africa did not have to face a single delivery which challenged them at that pace. However, it probably wasn’t just Kagiso Rabada and Marco Jansen, whose high pace was so potent it produced three wickets in under nine overs, who cranked it up to 140kph today.When tea had been taken and Pakistan were resting indoors, having been ground into the dust under a blistering Newlands sun, Naseem Shah was on a practice pitch a few strips over from the real thing, new ball in hand. There was no speed gun to monitor him, but it didn’t take one to know no Pakistan bowler who actually started this Test matched that speed. The action was regular, the follow-through earnest, the shape on the ball exquisite. One delivery landed on a length, moved late at speed and knocked back the solitary stump at the other end. Even if there was a batter stood there, it might have been tricky keeping that out.For a bowler who’s officially out with back stiffness and chest congestion, Naseem – who has also been out there as substitute fielder and helped Saim Ayub onto a stretcher yesterday – wouldn’t exactly have been a liability to this attack.Related
-
Upgraded Verreynne becomes Conrad's beloved devil
-
Rickelton's marathon 259, Verreynne century thump hapless Pakistan
-
Stats – Verreynne emulates de Villiers; Rickelton follows Amla
-
Ayub ruled out of Cape Town Test after suffering ankle injury
But this is not an individual selection gripe. Naseem was, after all, part of the side for the first Test, and while he sent down a long, impressive spell in South Africa’s first innings, he never truly came close to matching Rabada or Jansen’s threat. As Shan Masood has said in the past, Pakistan don’t often take 20 wickets, and though they managed 18 in Centurion, it didn’t quite get them over the line.At the same time, though, when Pakistan selected this attack, it is difficult to imagine they truly believed they had a realistic shot of 20 wickets on this surface. For clarity, Pakistan were remarkably open about the tradeoffs they had to assess before naming a squad, which they waited right to the morning of the Test to do. Any XI they named, spinner or not, Naseem or not, will likely have found wicket-taking hard inserted in to bowl for two hot sunny days.And, in truth, each of Pakistan’s four seamers did what they had been asked to do. They bowled hard lengths; it was the most common delivery for every one of the four bowlers by some distance. They resisted the temptation to pitch it up, as they might have done in Pakistan. They picked up two early wickets with the new ball, and another one with the second new ball. South Africa may have taken them to the cleaners once the scorecard had soared into silly numbers by the afternoon of the second day, but it was a product of the lack of pressure and a flatness of the wicket rather than a drop in Pakistan’s efforts or quality. And Pakistan continued to take it seriously to the last, at no point did we see them go through the run order for who else could bowl; one over from Kamran Ghulam aside, every over was bowled by a specialist quick or their assigned spinner, Salman Agha.Pointing all that out doesn’t add to the mystery of how an under-scrutiny South African top six ended up with 615; it strips away the veneer, leaving you looking directly at the answer. A Pakistan attack that lacks high pace on a pitch that doesn’t offer the bowlers assistance will not get on top of an international batting line-up, no matter how well they might do whatever they can do. Much like expecting to win a marathon when you can’t afford running shoes, Pakistan found themselves compromised in fundamental non-negotiable ways, and no change in extraneous reality could have compensated for that.Shaheen Afridi, arguably Pakistan’s best bowler in the ODI series last month, was not selected for the Tests and allowed to go off to play the Bangladesh Premier League; he has played two games in Mirpur in the past week. Naseem, as we saw, couldn’t quite make the cut for this Test, and there are no other bowlers at high pace, in this squad or indeed in all of Pakistan, who the selection committee truly feel comfortable throwing into a Test match. There may very well be merit to that position, but it meant Pakistan had a bad hand, and South Africa were aware of it. What followed for over the last two days was merely an inevitable consequence of it all.Perhaps that was more instructively obvious in the 21 overs South Africa bowled than the more than 141 Pakistan did. The pitch was just as flat when Rabada and Jansen bowled but you might have been fooled over ten overs of high-class, high pace bowling. Pakistan had to battle to keep them at bay every delivery, without success; they were 20 for three on a surface where, just yesterday, South Africa were 307 for three at one point.But when Wiaan Mulder, operating around the high 120s, and debutant Kwena Maphaka, not quite at Rabada and Jansen’s level, entered the attack, this Newlands strip reverted to its bashful, docile self of the last two days. Babar Azam had done well to dig in, and for the last half hour, he and Mohammad Rizwan had little trouble keeping South Africa out, or scoring runs at a decent clip.But on a surface where elite, fast bowlers will get you out, South Africa have at least two of them, and Pakistan none. With Pakistan still 552 runs behind, this Test match hasn’t exactly kept its cards hidden.