Skip to content

Kentucky Sports Radio

University of Kentucky Basketball, Football, and Recruiting news brought to you in the most ridiculous manner possible.

Mark Stoops issued a statement regarding Ashely Lowery


Mark Stoops went down to Georgia this afternoon to check on Ashely Lowry, the star of his secondary. Stoops issued a statement through UK after the visit:

“I went to see Ashely today and was glad to see him and spend some time with him. We’re thankful for the progress he’s made and are hopeful he will continue that improvement. He’s heard from a lot of teammates and is grateful for all the good wishes and prayers that so many people are offering on his behalf. We ask the Big Blue Nation to join Ashely’s football family in continuing to pray for a speedy recovery.”

Ashely’s family also released a statement thanking Big Blue Nation for its love and support:

“On behalf of the Lowery family, we’d like to thank everyone for their concerns and prayer. From Georgia to Lexington, we can’t thank everyone enough. You are like family to us.

“The only official comment from the hospital is that his condition has been upgraded from stable to satisfactory and his injuries are no longer life threatening. We expect a full recovery. Again, thank you so much for all the prayers and support.”

It’s great to hear he’ll eventually get back to 100% and continue chasing his dream on the gridiron. What a lucky, lucky guy.

Article written by Drew Franklin

I can recite every line from Forrest Gump, blindfolded. Follow me on Twitter: @DrewFranklinKSR

4 Comments for Mark Stoops issued a statement regarding Ashely Lowery

  1. Cats Chris
    4:48 pm May 6, 2013 Permalink

    If he doesn’t have any serious injuries and only has cuts and bruises, why in the world is he still in the ICU?

  2. RICK
    4:55 pm May 6, 2013 Permalink


  3. BBN
    5:28 pm May 6, 2013 Permalink

    Get well soon Ashley!

  4. Chicago Chris
    5:54 pm May 6, 2013 Permalink

    Why does he have blue eyes in the pic that KSR posted a few posts prior to this?