Kurt Angle Injury Forcing Him To Miss This Sunday’s TNA Lockdown PPV


Kurt Angle injuryTNA superstar Kurt Angle will miss this Sunday's Lockdown pay-per-view due to a "torn MCL".

It was reported last month that Kurt Angle was working through a knee injury and had been for some time. In fact, the report stated that Angle had been working with no ACL at all. Today, ImpactWrestling.com posted the following update on Kurt's status for Lockdown this Sunday:

TNA Wrestling officials have been informed that Kurt Angle has a torn MCL in his knee as a result of the attack by Ethan Carter on Thursday on IMPACT. Angle is scheduled to undergo surgery to repair his MCL today (Friday). As a result of this unfortunate injury, Kurt Angle will be unable to compete at Sunday's Lockdown Pay-Per-View event against EC3. Stay tuned to ImpactWrestling.com for more updates on Kurt Angle.

You will likely notice, as I did, that TNA is reporting Angle suffered a torn "MCL", which is different than the original report last month about his "ACL". I did some digging on the differences between ACL and MCL, and rather than bore you with details, I'll share my thoughts on the matter:

Kurt Angle report from last month suggested that his ACL wasn't torn, but rather missing altogether. History has proven that many athletes have competed at high levels with diminished ACL's or no ACL's at all. While athletes are more at risk for knee injuries when they are missing an ACL, other muscles can start adapting and picking up the slack, so to speak, allowing athletes to continue playing their respective sports.

In Kurt Angle's case, although not verified, the original report could very well be accurate and Angle has been competing all this time with no ACL. This torn MCL that TNA is confirming via report is likely a new injury forcing Kurt Angle to repair by surgery. Angle tweeted the following about the injury: 

We will keep you updated as more information becomes available.

Have a news tip? Attended an event and want to send a live report? Submit it now!
monitoring_string = "851cc24eadecaa7a82287c82808f23d0"