2011 Preakness Predictions: Why Mucho Macho Man Is Dangerous At Preakness
Jamie Squire/Getty Images
2011 Preakness Predictions Should Give Mucho Macho Man An Edge
The 2011 Preakness Stakes are as wide open a horse race as we have seen since...well, since The Kentucky Derby two weeks ago. Animal Kingdom was able to win that race, but there is one horse who isn't getting a lot of publicity heading into the second leg of the Triple Crown. That is Mucho Macho Man, who finished the Derby strong and looks poised to make a lot of noise at Pimlico.
From Jason Shandler (via BloodHorse.com):
Reeves Thoroughbred Racing and Dream Team Racing’s Mucho Macho Man (6-1) has not run a bad race in his nine-start career, and there are many that think he is the one to beat. He didn’t find his best stride until late in the Derby, but still was beaten only three lengths.
Must Read: Latest Odds For Preakness Stakes 2011
Mucho Macho Man finished third in the Derby and was one of the favorites in that race. He clearly didn't have his best stuff on that day, but he is more than capable of winning this race.
The Preakness Stakes runs at a faster pace than the Derby. Mucho Macho Man is a very fast horse, as evidenced by his charge up the leaderboard down the stretch at the Derby. If the weather holds up, and the forecast for tomorrow calls for sunny skies all day, this race will be over in a hurry.
Rajiv Maragh will take the reins for Mucho Macho Man in the Preakness. He rode him in the Kentucky Derby and really seemed to find his mojo with the horse at the end of the race. It was too little too late on that day, but it will serve the horse well at the Preakness.
Mucho Macho Man isn't the favorite to win the race, but it will not be a shock if he is in the winner's circle at 6:20 pm est on Saturday evening.
Most recent updates:
What is the duplicate article?
Why is this article offensive?
Where is this article plagiarized from?
Why is this article poorly edited?


5 Comments
Loading comments...
This comment and all replies have been deleted This comment has been deleted Undo delete