Sri Lanka squad leaves for Pakistan despite security concerns

Agencies
September 24, 2019

Sept 24: Sri Lanka’s depleted national cricket squad left for Pakistan on Tuesday expressing confidence in security promises by the hosts despite reports that the team could be targeted by militants.

The Sri Lanka team were attacked in Lahore in 2009. Since then most international teams have refused to tour the South Asian country, leaving Pakistan to play nearly all their “home” games in the United Arab Emirates.

Ten senior players citing security concerns have opted out of the tour comprising three one-day internationals and three Twenty20 matches beginning on Friday.

But the captain of the Twenty20 squad, Dasun Shanaka, said Tuesday he had no misgivings about returning to Pakistan after they played a Twenty20 international in Lahore in October 2017, their first since the 2009 attack.

“I have been there before,” Shanaka told reporters just before the team left Colombo where they were blessed by saffron-robed Buddhist monks.

“I am satisfied with the security arranged for us and I am happy to lead my team to Pakistan. We hope to give a good fight to our very strong hosts.”

ODI skipper Lahiru Thirimanne said he also had no concerns and they had been given assurances of a very high degree of protection in Pakistan, usually reserved for visits by heads of state.

Sri Lanka’s cricket board received the all-clear from the defence ministry last week to go ahead with the tour after establishing that there was no threat.

The 2009 attack left six players injured when gunmen attacked their bus. Six Pakistan policemen and two civilians were killed.

Tour schedule:

One-day internationals (all in Karachi): September 27, 29, October 2.

Twenty20 internationals (all Lahore): October 5, 7, 9

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
February 21,2020

Wellington, Feb 22: shant Sharma's lion-hearted bowling effort met its match in Kane Williamson's elegance as New Zealand ended an attritional second day of the opening Test against India with a slight upper-hand, here on Saturday.

After another lower-order collapse that saw India get bundled out for 165, Ishant, coming straight back from an ankle injury, took three for 31 in 15 overs despite Williamson's effortless 89 in New Zealand's day-end score of 216 for 5.

New Zealand now lead by 51 runs.

Mohammed Shami (1/61 in 17 overs), during his final spell of the day, removed Williamson, who couldn't check an uppish drive. Henry Nicholls' (17 off 62 balls) struggle seemed to have hampered Williamson's rhythm.

During the final hour, Ravichandran Ashwin (1/60 in 21 overs), who also bowled beautifully throughout the day, relieved Nicholls' of his agony with a delivery that had drift and a hint of turn as India skipper Virat Kohli snapped the low catch at second slip.

Williamson looked good as he hit some delightful strokes square off the wicket. The square drive on the rise off Jasprit Bumrah (0/62 in 18.1 overs), followed by a cover drive, showed his class.

In all, the New Zealand skipper hit 11 boundaries off 153 balls.

Bumrah, in particular, was punished by Williamson, who also back-cut him for a boundary and Taylor then punished another half volley through the covers.

There were quite a few loose deliveries on offer from the Indian pacers and in between a few did beat the bat. With the 'Basin' baked in sunshine, batting became lot more easier and Black Caps seized the initiative.

Bumrah, in particular, failed to find his length consistently. Either he bowled too full and drivable length deliveries or too short that even Rishabh Pant failed to gather with the ball going a couple feet over his head.

This is where Ishant came into the picture. While he was lucky to get opener Tom Latham out with a delivery drifting on leg-stump, the other opener Tom Blundell (30) had a typical Ishant dismissal written all over it.

The ball was full on the off-stump channel and jagged back enough to find the gap between his bat and pad.

Williamson and Taylor then had a partnership of 93 runs during which New Zealand also got the lead before Ishant, coming back for his third spell, bowled one that reared up from good length and proved to be an easy catch for Cheteshwar Pujara at short-leg.

Once Nicholls came in, Williamson, who was batting fluently, suddenly had a player at the opposite end who scored only 4 off 34 balls.

Looking good for his 22nd Test hundred, Williamson, in his bid to get another boundary, couldn't check a cover drive and the low catch was taken by substitute fielder Ravindra Jadeja.

Earlier, New Zealand's debutant Kyle Jamieson and veteran Tim Southee took four wickets apiece as Indian innings folded in 68.1 overs.

Jamieson (4/49 in 16 overs) and Southee (4/49 in 20.1 overs) took four of the five wickets that fell on the second morning with India adding only 43 runs to their overnight score of 122 for 5.

Rishabh Pant (19) started with a six but then a horrible mix-up with senior partner Ajinkya Rahane (46) resulted in a run-out and the little chance of recovery was gone for good.

It was a poor call from the senior player and Pant had to sacrifice his wicket in the process.

Ashwin then received a beauty from Southee, pretty similar to what Prithvi Shaw got, while Rahane inside edged one while trying to leave it alone.

With India at 132 for 7, Rahane knew that time was running out as he played a square drive off Trent Boult to get him a boundary.

Southee then got rid of Rahane when he tried to shoulder arm a delivery that made a late inward movement. Mohammed Shami's entertaining 21 then enabled the visitors to cross the 150-run mark.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
July 2,2020

Jul 2: Cricket Australia has decided to not use the Dukes ball from this summer's Sheffield Shield, having used it alongside Kookaburra for four seasons.

CA has confirmed that the Kookaburra ball will be used for the entire 2020-21 first-class season.

Australia has been using Dukes ball since the 2016-17 season in Shield matches with an aim to help its cricketers prepare for the hostile English conditions.

CA's Head of Cricket Operations, Peter Roach, said the decision to axe the Dukes was the right call. "The introduction of the Dukes ball has been a worthwhile exercise, particularly in the lead up to overseas Ashes series where the Dukes is used so well by our English opponents," Roach said.

"We have been happy with how the ball has performed when used in Australian conditions over the past four seasons. We do, however, feel that reverting to one ball for 2020-21 will provide the consistent examination of our players over a full season that CA and the states are presently seeking. The Kookaburra is the ball used for international cricket in Australia and many parts of the world and we see benefits this season of maximising our use of it," he added.

Roach said the ineffectiveness of spinners in first-class cricket in recent times played a role in CA's decision to do away with the Dukes. "We have noted that spin bowlers in the Sheffield Shield have been playing less of a role in recent seasons, most notably in games when the Dukes ball is in use. We need spinners bowling in first-class cricket and we need our batters facing spin. We hope that the change to one ball will have a positive benefit here," he said.

The CA official, however, didn't rule out the possibility of re-introducing it later.

"We see a definite opportunity to reintroduce the Dukes ball at some stage in the future."

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
Agencies
January 5,2020

Mumbai, Jan 5: All-rounder Irfan Pathan on Saturday announced his retirement from all forms of cricket, ending an injury-ridden career that prevented him from realising his true potential.

The 35-year-old's retirement was on expected lines, considering he last played a competitive game in February 2019 during the Syed Mushtaq Ali trophy for Jammu and Kashmir.

He did not even put himself in the IPL auction pool, last month.

The left-arm seamer's bowling was like a breath of fresh air when he made his India debut against Australia at the Adelaide Oval in 2003.

He never had express pace but his natural ability to swing the ball into the right-handers got him instant success, also drawing comparisons with the great Kapil Dev.

It seemed India had found the all-rounder they were looking for since Kapil left the scene. Pathan, who last played for India in October 2012, featured in 29 Tests (1105 runs and 100 wickets), 120 ODIs (1544 runs and 173 wickets) and 24 T20 Internationals (172 runs and 28 wickets).

He was part of the victorious Indian team at the 2007 World Twenty20 and was the man-of-the-match in the final against Pakistan.

One of his best performances came on the tour of Pakistan in 2006 when he became the second Indian after Harbhajan Singh to take a Test hat-trick, removing Salman Butt, Younis Khan and Mohammad Yusuf during the Karachi game.

He also played a big role in India winning a Test match against Australia on a tough Perth wicket, which offered steep bounce.

Injuries and lack of form troubled him thereafter and his ability to swing the ball deteriorated.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.