Kevin Pietersen slams ECB selectors for dropping a senior player a few years ago

England is currently struggling in the ongoing third Test against India at Trent Bridge. For the third time since 2016, they were bundled out inside a session and the trend has left worrying many now. The batting line-up hasn’t fared well in this series as well and they won the first couple of matches because of the all-rounders and bowlers. However, Kevin Pietersen has slammed the selectors for dropping a senior player a few years ago and felt that his experience would’ve been crucial for the youngsters.

Currently, only Alastair Cook and Joe Root are the experienced batsmen in the line-up and apart from Jonny Bairstow every other player in the top 5 are changing. The continued absence of Ben Stokes also hasn’t helped their cause. Moreover, Cook has batted with 12 different partners since 2012 and now even his place in the side is being questioned after scoring only 252 runs in 13 innings this year.

Who is the batsman?

Kevin Pietersen came down hard at the selectors for dropping Ian Bell who was one of the rock-solid batsmen in the middle-order for them. He highlighted his importance in the line-up and felt that Bell would’ve guided the youngsters during the fag end of his career. But the way selectors dropped him and didn’t consider him later despite playing well has irked the South Africa-born cricketer.

“Huge ECB mistake was getting rid of Ian Bell when he had a few good years left in him to help the youngsters. It’s not the batters fault! It’s the selectors who THANK GOODNESS have been moved on. Youngsters need senior batters to look up to!” he tweeted.

As far as the Test match is concerned, India are in the driver’s seat right now with the lead of 292 runs in the second innings and they still have eight wickets in hand. It will take an unimaginable effort from here from England to make a comeback and stop their opponents from pulling one back on them and make it 2-1 in the series.

Here’s his tweet:

[interaction id=”5b7a82efb2f5086c1efc7e2b”]

Keep following CricTracker for more news and updates.