Tuesday, August 6, 2013

Rain ruined an exciting match: FNCC vs Basel CC

FNCC remains undefeated by Basel CC, but this match promised surprises the way Basel started the chase but alas... rain stole an exciting finish. While we wanted to ensure our place in semi-finals, Basel wanted to break the jinx and get their first points but when you play against rain, only cricket looses.

FNCC innings:
Vijay opened with Rehan, who returned after a gap of few weeks. Both looked solid. They gave us a very solid and attacking start. They dominated the new ball attack and that gave them some breathing space when spinners came on. Just as we failed to get a wicket for 26 overs againsta GenevaSLCC, our openners remained unseparated until 20th over. Vijay made 40+ and Rehan showd his class in making 80+. Saghir did not have much time but he is in a great touch these days. These three stand performances covered the failure of the rest of the batting. Feyas and Arpit did show some courage to score runs. But our inexperience against good slow bowling of Adeel and Toufeem was clearly exposed.

210 runs was an imposing total for 30 overs. This score however does not reflect the lopsided performances by the FNCC batsmen. Twice Basel bowlers were looking for hattricks. At one point perhaps they did but the umpire (i.e. me) declined a very enthusiastic appeal against Balaji. So if at all we only learned partly.


Basel Inning:
Basel started in an attacking mode. I was struck for two fours in my first over. Saghir was in better form and he contained runs. But Zaheer and Umer gave Basel CC a started that they needed to chase a score of 210 in 30 overs. My shin splints started to bother me already in the second over and I was sitting outside already in the eigth over. Score was cruising along at a healthy rate of 6 runs and importantly Zaheer was in full flow. An exciting match was underway.

But by this time the clouds were already coming to watch (ruin) the match. Umer lost his patience to Rehan's bowling (yes he can bowl -- at times very effectively). On one end Zaheer was driving the score and other end was kept in solid defence. It was a strategy that was working well. But then came a turning point. Zaheer was adjudged out hitting the ball twice [see below for more on this]. This was over number 13th and we needed to bowl at least 15 overs to call it a legal match.

With the rain rule, Basel CC needed to have scored 105 runs at the end of 15th over. They were 82 ot 85 in 14.4. Rain was getting stronger and we wanted to get over with the remaining two balls. It should have happened. But then had a great idea. In a giant stroke of genius he got himself run-out -- meaning the match had to interrupted for the change in batsman and with rain getting string by the drop, it was just not possible to continue.

While, Rehan, Vijay, Saghir set the match up and Zaheer made it exciting, it was the conspiracy of rain and Shubhu that saved Basel from facing another defeat ;) 

Rain rule:
I wonder why Swiss league decided for a simple rule. They should know that simple does not mean correct. I had argues for Duckworth-Lewis method. Now mobile phone apps are there two calculate D-L par scores but the applicable rain rule only care for scoring rate without considering the wickets. After 15 overs at any point if the match is interrupted then only net-average run rate is used to calculate the score. At one point Basel CC needed about 130 runs on 17 overs with 7 or 8 wickets in hand. With about eight overs lost, they needed 81 runs in 11 overs with same number of wickets in hand -- clearly an easier thing to do. DL would have given a different par-score. Something to change in the next round as we do expect the clouds to watch some of our cricket... I mean, its not really 'cricket' if some time is not lost because of rain.


Out hitting the ball twice:
I was hurt, less because of my injury, more because I had to sit out. But I was acutely aware of the importance of the wicket of Zaheer. So when I saw him touching the ball again after he had played a defensive shot, I suggested for an appeal for 'hitting the ball twice'. Our team duly complied and umpire  (from Basel CC) after some discussion adjudged the batsman out. It was disappointing end of a beautiful innings.

Then comes rain (for the first time) and in the break we had a chance to see the rules again? It turned out that the rule of very ambiguous, that is there is no clear way to say whether the batsman is saving the wickets or not. In Zaheer's case we immediately realised that he was dealt with unfairly. So FNCC decided to invite him to bat again. But Zaheer is a very proud man and a great sportsman and understand cricket. He, in the true spirit of the game accepted the decision (albeit wrong). Thats how cricket should be played. Thus, he may not add runs to his name but certainly increased his respect among his peers.

The league semifinal will be on 25th Aug. Few teams are already out i.e. Basel CC, Eagel CC. But other six are still in the fray. FNCC needs to win at least two of the three remaining match but we want to push to top the league phase to get the semi-final in Freiburg. But lot was exposed in the rain ruined match. Batting lapses are easily visible but more worrisome were the cracks in the bowling. I need to to work on my fitness, this is not fair to anyone if I play with injuries and we need a second spinner. At the same time out batting needs more practice against slow/spin bowling.

right arm over
Arvind