During the fourth T20 match between South Africa and India, an unfortunate incident occurred when a ball hit by Indian cricketer Sanju Samson struck a female spectator in the stands.
The incident took place in the 10th over of the first innings as Samson, playing an aggressive innings, hit a six off Tristan Stubbs' delivery. The ball sailed out of the ground and struck the woman in the face, injuring her.
Samson had earlier played a brilliant knock, scoring 109 runs off 56 balls, including 6 fours and 9 sixes. His performance helped India secure a dominant 135-run victory over South Africa.
He slammed a second successive Twenty20 international century to set up a 61-run win for India in the first of four matches against South Africa at Kingsmead in Durban on November 15.
Opening batter Samson hit 10 sixes and seven fours in a spectacular innings of 107 off 50 balls in an Indian total of 202-8.
His only two previous international centuries have come in the past 12 months - 108 in a one-day international against South Africa last December and 111 in a T20I against Bangladesh in Hyderabad last month.
Suryakumar Yadav, captaining an India team missing many of the country's leading players, either preparing for a Test series in Australia or representing India A in Australia, praised his team for their attacking approach.
He said he was not concerned by the only blemish in the Indian performance - losing six wickets and scoring only 35 runs in the last 5.2 overs of their innings after Tilak Varma (33) and Samson fell in quick succession.
Following the incident, the injured woman was immediately attended to, with ice applied to the injury. Samson, visibly distressed, offered an apology for the incident.
The video of the event quickly went viral on social media, with many expressing concern for the injured fan.
India defeated South Africa by 135 runs in the fourth and final T20I on Friday to secure a 3-1 series victory.
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