Off-spinner Ashwin took three for 30 and left-arm spinner Pragyan Ojha bagged two wickets as New Zealand struggled to reach 106 for five in their first-innings at stumps in reply to India’s 438.
The tourists now need 133 more runs to avoid the follow-on with five wickets in hand. James Franklin was unbeaten on 31 with Kruger van Wyk who had yet to open his account.
Earlier, Cheteshwar Pujara cracked a solid 159 and skipper MS Dhoni hit 73 as India added 131 runs to their overnight total of 307 for five before being bowled out at the stroke of tea.
“I thought we bowled well and we should be eyeing a follow-on,” said Ashwin. “If you put 440 on the board, you expect to be in a dominant position.
“I think the new ball was a little bit hard and the seam was a little more upright when we spinners started bowling. That helped us get a bit of bounce and get a few wickets up front. We have to be patient to get wickets tomorrow.”
Ashwin and Ojha got a wicket in their opening overs, removing Brendon McCullum (22) and Martin Guptill (two).
Dhoni pressed Ojha into the attack after only seven overs of pace and the spinner struck with his third delivery when he had McCullum caught by Virat Kohli in the covers.
Ashwin got a wicket with his first delivery when he had Guptill caught by Kohli before removing captain Ross Taylor (two) in his next over.
New Zealand’s batting woes continued in the last session when the floodlights were on as Daniel Flynn (16) was trapped by Ashwin.
Ojha got his second wicket when he had Kane Williamson (32) caught by Virender Sehwag.
“They bowled some good balls and we nicked them,” said New Zealand spinner Jeetan Patel, who finished with four for 100.
“The pitch is starting to take turn, probably a little bit earlier than we expected. Obviously getting four-for is nice, but I will have to get more than that to get us over the line.”
Published in The Express Tribune, August 25th, 2012.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ