PIA thrash SNGPL

Former champions lose by innings and 122 runs in Quaid Trophy.


Express December 13, 2010

Former champions SNGPL were humiliated by PIA in Islamabad, losing by an innings and 122 runs on just the third day of their Quaid Trophy match.

Needing 240 to avoid an innings-defeat, SNGPL were dismissed for 118 with Aizaz bin Ilyas grabbing six wickets, the wrecker-in-chief.

Blues in danger again

Karachi Blues endured yet another difficult day in the middle as they lead Rawalpindi by just 81 runs with only two wickets remaining.

Conceding a 95-run first-innings lead, the Blues were left reeling at 176 for eight with Rashid Latif and Sadaf Hussain sharing eight wickets between them.

Sialkot humiliate Multan

Sialkot dismissed Multan for a paltry 63 in their second-innings to register a thumping 245-run win in Okara.

Needing 473 to win after Silakot were dismissed for 228 in their second-innings, Multan had no answer to Waqas Ahmed (five for 30) and Prince Abbas (four for 32).

Exciting finish on cards in Faisalabad

The match between Faisalabad and Islamabad was evenly poised with the visitors needing a further 257 runs to win on the final day with seven wickets remaining.

Earlier, Faisalabad declared at 386 for nine, setting Islamabad a target of 340 to win the match.

WAPDA in trouble

Wapda were left reeling at nine on two in their second-innings after HBL had piled up 509 for nine, a first-innings lead of 270.

Humayun Farhat and Shan Masood scored unbeaten centuries as HBL look favourites to hand Wapda an innings defeat on the final day of their match.

Draw on the cards in Sialkot

ZTBL moved along merrily to 326 for four in reply to NBP’s 370 at the Jinnah Stadium in Sialkot. Haris Sohail scored an unbeaten 101 for ZTBL with Uzairul Haq as the sole wicket-taker, grabbing all four wickets to fall in the innings.

Published in The Express Tribune, December 13th, 2010.

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