5 reasons why South Africa, for the first time in a decade, struggled in a Test series in India

Over the years, South Africa has been one of the most intimidating visitors to India. Not many teams have breached the fortress, the Final Frontier over two decades for many seemingly invincible teams. South Africa’s glorious run of 9 years has come to an end finally, as they lost a series away from home, an incredible feature already.Like Australia’s winning streak of 16, this great streak too had to end in India, showing how tough it usually is for visiting teams to unfurl their flags. It comes as no surprise that in the last 10 years, only one team, England, has managed to win a series in India – in 2012.England drew a series once, South Africa did it twice but beyond that, it has been India all the way, winning 12 out of the 16 Test series played in the last 10 years.South Africa has been by far, the best visiting team based on facts.1996: India beat South Africa 2-12000: South Africa beat India 2-02004: India beat South Africa 1-02008: India drew with South Africa 1-12010: India drew with South Africa 1-1With one Test to go, this is by far South Africa’s worst performance.Here are 5 reasons why South Africa struggled in the series against India, handing over the Freedom Trophy.

#1 Collective Batting failure

South Africa managed to post their three lowest cumulative Test totals in India, in the current series. Their totals of 293 and 264 in Mohali and Nagpur are the lowest totals across both innings for them in India. The average in these two Tests was 14.65 and 13.20, easily their lowest. Until then, their previous lowest was 17.85 and 17.45 way back in 1996, when they lost 1-2 to India.

Even in 2004, when they lost a series in India, their average was an impressive 26.35. This clearly shows how their batting has failed collectively in this series. Their lowest total in India, 79 also came in this series. It is also the lowest total for which India has dismissed any opposition.

South Africa crossed 200 only once in five innings so far in this series, the lone innings in Bangalore which was washed out by rain. Only one South African managed to get past 50. AB de Villiers did it twice, with scores of 85 and 63 in Bangalore and Mohali respectively.

#2 Viciously turning tracks

Mohali and Nagpur tracks were both prepared with a clear mission – to give India a home advantage. The jury is out on whether rank turners are just as justifiable as green tops. There are raging debates over whether teams should mutually cooperate for the sake of Test cricket and prepare sportive pitches that have something in them for everyone.

For now though, it is obvious that South Africa’s dismal performance was caused by rank turners on which none of their batsmen barring AB de Villiers could thrive for even one session. Proof of how tough the pitches were could be seen in the fact that even Indian batsmen didn’t do too well either.

They have Murali Vijay and Cheteshwar Pujara to thank, two reliable players proving to be the difference between the two sides. These tracks are clearly the most treacherous that South Africa has encountered in India. South Africa had some really low scores in 1996, when they repeatedly failed to cross 200, but even in that series, they managed 300 and 400 once.

#3 Absence of opening partnerships

South Africa didn’t have even a single stable opening partnership in this series so far and that came to hurt them badly. In the first Test, they had partnerships of 9 and 8 in the two innings. At Bangalore, they had an opening partnership of 15. At Nagpur, they had partnerships of 4 and 17.

Although Dean Elgar was impressive, showing resilience and the persistence and stubbornness needed to survive on vicious tracks, Stiaan van Zyl was clearly not in his element at any point of time. His highest score of 36 came when he batted at No. 6. His other four scores at the top read 5, 10, 0 and 5, clearly something that you don’t want from your opening bat.

Elgar did manage to get starts but lost his concentration or got an unplayable delivery each time. He couldn’t carry on even on a single occasion.

#4 Injuries to key players

South Africa were afflicted with injuries in all three Tests. That proved to be decisive. In fact, they went into the third Test without two of their first choice seam-bowlers, Dale Steyn and Vernon Philander. The absence of Steyn was a major blow considering how instrumental he has been in the previous tours to India.

Morne Morkel missed a Test, Philander and Steyn missed two and Kagiso Rabada, although impressive is still taking baby steps in international cricket. South Africa’s feared pace bowling attack was therefore taken out of the equation especially on tracks that didn’t really support a lot of swing and seam bowling. Morkel could coax quite a bit in the third Test by changing his length, but South Africa had, to a great extent, been demoralised by the absence of Steyn and Philander.

Even JP Duminy wasn’t available in the first Test, a major blow considering the southpaw was a lower middle order stalwart and a handy off-spinner.

#5 Spin twins didnt match their opponents

You don’t come to India without quality spinners in your repertoire. South Africa had Imran Tahir but the leggie couldn’t do what Monty Panesar and Graeme Swann did to India on turning tracks in 2012. Tahir picked up 12 wickets in 5 innings at an unbelievable average of 13.25. Sounds great right? But he was a distant third, compared to Ashwin, who picked 24 wickets and Ravindra Jadeja who picked 16. Harmer was fourth with 10 wickets in 2 Tests.

Although it was not a bad performance from South African tweakers, with Dean Elgar chipping in with 5 wickets including a four-wicket haul at Mohali, there was daylight between them and the Indian spin contingent. That proved to be a big difference on tracks that made spinners virtually unplayable right from Day 1.

In fact, in Bangalore, India’s opening stand on Day 1 of 80 was unbroken showing how spinners couldn’t get the crucial breakthroughs at key moments for South Africa. Tahir got a five-wicket haul in the second innings of the third Test but by then the damage had been done.