Murray survives scare at Brisbane International

Top-seed sees off challenge posed by world number 91.


Afp January 03, 2012

BRISBANE:


Top-seed Andy Murray endured a tense examination from unheralded Mikhail Kukushkin to scrape into the second round of the Brisbane International.


Murray struggled for over two hours before finally seeing off the world number 91 5-7, 6-3, 6-2 in an enthralling match. Murray arrived on court with his right knee bandaged and appeared to hobble throughout the encounter.

An inspired Kukushkin had the top-seed in trouble early as he sent down a barrage of brilliant winners from all over the court. Kukushkin raced to a 5-1 lead before the Briton finally began to find his range, fighting back to 5-5 only to lose his serve and the set.

However, Murray slowly began to take grip of the match, breaking Kukushkin early and holding on to level the contest at one set apiece. In the decider Kukushkin finally ran out of steam and a relieved Murray closed out the match.

“He was hitting winners from all over the place,” said an exhausted Murray. “I was slow but I wasn’t expecting him to come out swinging like that.

“He was hitting the ball great so I was glad I was able to turn it around. You’re meant to be ready from the start and I wasn’t quite there today. But I played better towards the end.”

Meanwhile, Japan’s Kei Nishikori overhauled German Cedric-Marcel Stebe 3-6, 6-1, 6-4.

In the women’s event, Australian Open champion Kim Clijsters got the better of Ana Ivanovic 6-1, 1-6, 6-3 to march into the third round.

Li’s heroics in vain

Elsewhere, Chinese star Li Na put on a commanding show against Spain’s Annabel Medina Garrigues at the Hopman Cup, winning 6-3, 6-1.

However, Spain won the tie 2-1 when Fernando Verdasco beat Wu Di 6-3, 6-4 before the Spanish defeated the Chinese 6-0, 6-2 win in the deciding mixed doubles.

Published in The Express Tribune, January 4th, 2012.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ