Australia were decimated for 60 by England in a remarkable display of bowling by Stuart Broad on the first day of the fourth Test. Broad's match-winning eight wickets for 15 runs gave England the chance they needed to regain the urn they had to give up after being whitewashed 20 months earlier Down Under.
"There could be up to eight guys who might not ever play Test cricket again in this touring squad. That's a big number... half the squad," Ponting was quoted as saying by a cricket website.
Read: Australia's Clarke to retire after Ashes finale
The legendary Australian batsman said the current team was just not up to the task.
"You've got to break it down and look at the deficiencies. The cold, hard facts are there. If we got bowled out for 60 then England batted on the same pitch and (declared) for 391 (is indicative that), one, we didn't bat well, and two, we probably didn't bowl well either," Ponting said.
"Now, here we are again at 7-241, which actually should be the best batting conditions for the whole game," said Ponting, adding that "They just haven't been good enough. I don't care what they want to say or why they want to blame or whatever."
Read: Australia 60 all out against England
The former captain praised Australia openers Chris Rogers and David Warner for staying at the crease and making a century partnership in the second innings but said that they got out playing silly shots.
"They [Rogers and Warner] seemingly got through the hard times against the new ball, and then both of them probably played shots they wouldn't be that proud of," Ponting explained.
"The moving ball again today just found our batsmen (out), brought them undone again. Rogers' was a wide one swinging away, (Michael) Clarke's was a decent outs-winger as well (but) maybe didn't have to go as hard at as he did."
"Tough day at the office - and most of them have been for the Aussies over the past few weeks," the former captain concluded.
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