Lilian Garcia Injury Update; Possible Torn ACL

Ryan Clark

Lilian Garcia has posted a blog on her official website updating fans on the severity of her injury. There are also photos of her skiing accident at

Hi everyone,

Yes, it is true, I was in a skiing accident in Killington, VT on March 17th. I have been a skier since I was six years old and decided to go skiing that weekend because of a huge snow storm that hit the Northeast. Normally that would mean the conditions for skiing would be great but unfortunately that was not the case. The snow that fell was also mixed with sleet which made the snow very heavy. Since it had snowed all night, none of the trails were groomed and the powder was very thick. I was skiing down a black diamond run and when I was landing from a jump, my ski got caught underneath a big pile of snow. Normally the binding would release my boot but unfortunately, the ski kept turning to the left and twisted my knee and that’s when I felt a pop! I went down really fast and couldn’t move. I knew right away I was in trouble. The stretcher came to get me and normally I would try and tough it out and ski down but I knew my knee would not let me.

At the clinic, I was informed by Dr. Russell that the x-rays were negative for any broken bones but that he suspects I have a torn ACL on my right knee. I had an MRI taken Monday, March 19th but will not find out results until March 20th.

While I was in the clinic, I found out that four other skiers had come in right after me with the same injury. As well, there were also lots of patients there with bloody noses, concussions and broken bones. Not a very good day for any of us!

I want to thank everyone that has written or called me with their concerns. It really means a lot to me. As soon as I find out my results, I will let all of you all know. I do however hope to be back on Monday Night Raw next Monday the 26th even if I am hobbling a bit!!

I love you all!

Lilian 🙂

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