By ROWENA JOY A. SANCHEZ
MANILA, Philippines – Azkals striker Phil Younghusband hopes to recover from the hamstring injury he sustained during the Azkals’ triumphant game against Mongolia in time for their upcoming match against Myanmar.
In a phone patch report by ABS-CBN sportscaster Dyan Castillejo on “Umagang Kay Ganda,” March 16: “He’s [Phil] hoping that makakapag-recover siya for the game on Monday… he has scheduled [to undergo] an MRI (magnetic resonance imaging) to check kung ano talaga ‘yung condition ng hamstring niya.”
Castillejo said the Fil-Brit player is still in pain after suffering a pulled hamstring in his right leg in the 65th minute of the game held at the Ulan Bator Stadium in chilly Mongolia on Tuesday. He was replaced by Yanti Barsales.
“Si Phil actually kagabi… nahirapan siyang maglakad, he was limping. Mas masakit na ‘yung hamstring niya… Kasi diba malamig, so he was just running and then it snapped, he felt it. So kagabi masakit talaga siya, much more painful than when it just happened,” she related.
Castillejo added that Younghusband already did some stretching and had his leg examined by the Azkals’ physical therapist. He is also set to undergo checkup upon return to the Philippines on March 17.
The Azkals advances to the qualifying tournament of the AFC Challenge Cup---despite losing to Mongolia’s Blue Wolves (1-2)---with the aggregate score of 3-2, which includes the Azkals’ win in their first game in Bacolod.
Younghusband himself related through Twitter that his injury still hurts and he is anxious that he might not be able to play for the Myanmar match. He also apologized on Tuesday for the Azkals’ loss, but is grateful that they qualified for the next round.
And in his post on Wednesday, Younghusband said: “Magandang umaga! Masakit pa rin ang injury ko. Malungkot pa rin kasi na talo kami kahapon pero yung goal natin was reached, to qualify :).”
In his tweet to Azkals goal keeper Neil Etheridge, he also noted: “I have a scan tomorrow but not sure.”
Manila Bulletin
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment