Amir fined 150% match fee for verbal spats

SSGC fast-bowler punished for taunting Faisal during Quaid Trophy qualifiers


Our Correspondent October 14, 2015
PHOTO: AFP

KARACHI: Disgraced fast-bowler Mohammad Amir has been slapped with a 150% match-fee fine after he was caught up in controversy where he was called a ‘thief’ in domestic cricket by Test batsman Faisal Iqbal during a Quaid-e-Azam Trophy qualifier match between SSGC and PIA.

While playing for SSGC, Amir repeatedly took digs at the PIA batsmen, especially at Faisal, taunting the latter on his alleged backing by his legendary uncle Javed Miandad.

According to the footage made available, Faisal then responded with a boundary and reportedly shouted ‘go away thief’ at Amir.

Read: ‘World will see a different Muhammad Amir on my return’

“Amir has been fined 150% match fee for two incidents of misbehaviour against PIA,” a Pakistan Cricket Board official confirmed to The Express Tribune. “First he was fined 50% of his match-fee for misbehaving and then was slapped with a 100% match-fee ban after a spat with Faisal, who has been warned.”

Amir, Salman Butt and Mohammad Asif, have been allowed by the International Cricket Council to return to competitive cricket after serving out their respective bans following conviction in a spot-fixing incident of 2010.

Meanwhile, in another incident, SBP manager Zaheer Ahmed has been fined 75% of his match fee for failing to prove charges of ball tampering against Mohammad Irfan during a match with KRL at the Gaddafi Stadium in Lahore.

On the other hand, Irfan was slapped with a 50% match fine after he was involved in a heated argument with players and officials when umpires decided to check the condition of the ball.

Published in The Express Tribune, October 15th, 2015.

Like Sports on Facebook, follow @ETribuneSports on Twitter to stay informed and join in the conversation.

 

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ