Cricket Australia confirm 12-month bans on Steve Smith, David Warner

Agencies
March 28, 2018

Johannesburg, Mar 28: Sacked Australia captain Steve Smith and David Warner have both been banned for 12 months for their roles in the ball-tampering scandal in Cape Town, Cricket Australia (CA) announced on Wednesday.

Cameron Bancroft, who was caught on camera scuffing up the ball with improvised sandpaper, was banned for nine months following the scandal, which has outraged the fans, jolted the sponsors and prompted CA to send the trio home from South Africa.

"David Warner will not be considered for team leadership positions in the future," CA said in the statement. The cricket body in its statement mentioned that Warner's role in this event and an apparent lack of contrition contributed towards the sanctions.

Warner was held responsible for carrying out the exercise to artificially tamper the ball and then guiding a young player to carry out the plan. The statement said that Warner was charged for not just advising a junior how to tamper with the ball but was also found guilty for the demonstration to how it could be done.

In a series of charges slapped on Warner, one of them was the concealment of such an activity from match officials and failing to report it voluntarily.

On the other hand, Steve Smith's fault was similar, saying that despite knowing it fully, the skipper didn't take steps to prevent the ball from getting tampered. Further, he was also charged for directing Bancroft to hide the incriminating evidence, which in this case was the yellow-coloured sandpaper tape, in his trousers rather than informing the officials about it.

Lastly, Cricket Australia made it clear that despite the crime, Smith and Bancroft will be eligible for leadership roles in the future but their comebacks will depend on current form, their stature in the team and most importantly, the acceptance of fans and public.

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 12,2020

New Delhi, Jul 12: Former India batsman Sachin Tendulkar has urged the International Cricket Council (ICC) to do away with 'umpire's call' whenever a team opts for a review regarding a leg-before wicket (LBW) decision.

The Master Blaster has also said that a batsman should be given out if the ball is hitting the stumps.

Whether more than 50 per cent of the ball is hitting the stumps or not should not be matter, he further stated.

"What per cent of the ball hits the stumps doesn't matter, if DRS shows us that the ball is hitting the stumps, it should be given out, regardless of the on-field call," Tendulkar tweeted.

With this tweet, the former India batsman also shared a video, in which he has a discussion with Brian Lara regarding the working of DRS.
"One thing I don't agree with, with the ICC, is the DRS they have been using for quite some time. It is the LBW decision where more than 50 per cent of the ball must be hitting the stumps for the on-field decision to be overturned," Tendulkar said in the video.

"The only reason they (the batsman or the bowler) have gone upstairs is that they are unhappy with the on-field decision, so when the decision goes to the third umpire, let the technology take over, just like in tennis, it's either in or out, there's nothing in between," he added.

This call for doing away with umpire's call has been recommended by many former players.
Whenever a verdict pops up as 'umpire's call, the decision of the on-field umpire is not changed, but the teams do not lose their review as well.

ICC recently introduced some changes to the game of cricket, and they gave all teams liberty of extra review as non-neutral umpires will be employed in Test matches due to the coronavirus pandemic.

As a result, all teams will now have three reviews in every innings of a Test match. 

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
June 13,2020

Islamabad, Jun 13: Pakistan cricket team’s former captain Shahid Afridi, who has tested positive for coronavirus,  appears to have contracted the virus during his recent visit to Muzaffarabad city of Pakistan occupied Kashmir (PoK) where Pakistan has been sending its corona positive patients.

The former Pakistan cricketer was seen attending gatherings in Muzaffarabad last month without wearing a mask and not maintaining social distancing. He spewed venom against India during his rallies. 

Afridi visited PoK to also express his solidarity with the people there who have been left to fend for themselves in combating COVID-19 as Pakistan has refused to provide any COVID fighting equipment like PPE kits and ventilators to the area’s handful of hospitals. 

In fact, Pakistan has been using the PoK as a “dumping ground” for COVID-19 affected persons from all across the country as authorities want to keep Punjab province free of corona positive persons. 

The locals held massive protests against Pakistan for setting up quarantine centres and shifting patients from parts of Pakistan to PoK. 

People are immensely suffering in Pakistan occupied Kashmir due to spread of coronavirus as the region lacks proper medical facilities and has a handful of COVID-19 testing labs. There is also lack of expert medical staff to conduct COVID-19 tests. 

A large number of people here are presumed asymptomatic and they are fast spreading the virus because of lack of medical care. 

Pakistan has reported over 1,25,000 coronavirus cases and 2,463 casualties. In Pakistan occupied Kashmir, the COVID-19 cases have increased to 534, whereas in Gilgit-Baltistan 1,030 have been  reported. 

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
February 7,2020

New Delhi, Feb 7: It was on February 7, 1999, that Anil Kumble became just the second bowler in the history of cricket to take all ten wickets in an innings of a Test match.

He achieved the feat against Pakistan at Feroz Shah Kotla Stadium, now known as Arun Jaitley cricket stadium in Delhi during the second Test of the two-match series.

India had set Pakistan a target of 420 runs in the match and the visitors got off to a steady start as openers Shahid Afridi and Saeed Anwar put on 101 runs for the first wicket.

It was then Kumble who came into the attack and wreaked havoc on the Pakistani batting line-up.

The spinner, also known as 'Jumbo' first dismissed Afridi (41) in the 25th over. After the right-handed batter's dismissal, India kept on taking wickets through Kumble and Pakistan was reduced to 128/6 in no time.

Kumble then kept on taking wickets at regular intervals and he got his tenth scalp in the 61st over after dismissing Wasim Akram.

This effort enabled India to register a win by 212 runs, and Kumble became the second bowler after England's Jim Laker to take all ten wickets in a single Test inning.

Kumble finished with the bowling figures of 10-74 from 26.3 overs.

Kumble announced his retirement from international cricket in 2008 and finished with 619 wickets in the longest format of the game.

He has the third-highest number of wickets in Tests, only behind Sri Lanka's Muttiah Muralitharan (800) and Australia's Shane Warne (708).

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.