Advertisement
Advertisement
British FFord title to be decided in court
By alley - Oct 13, 2014, 3:15 AM ET

British FFord title to be decided in court

The 2014 British Formula Ford Championship will be decided in the Motor Sport Association's national court of appeal.

Jayde Kruger became provisional champion, the third JTR driver in a row to do so, at last weekend's Brands Hatch finale after beating Harrison Scott by just six points.

Scott's Falcon Motorsport team has protested the race stewards' decision to overturn a penalty applied to the South African following a race-two incident between the title rivals.

Kruger and Scott collided on the second lap when the Briton attempted a move for the lead at Druids. The clash resulted in retirement for the Briton while Kruger – who had trailed Scott by eight points after the 18-year-old won Saturday's race – went on to claim his 13th win of the season.

Falcon protested Kruger after the race, which was originally upheld by the clerk of the course and resulted in the 26-year-old being stripped of the 30 points he gained for the victory. JTR then appealed that decision. The stewards overturned it, handing Kruger a 22-point lead for the finale, in which victory for 2014 McLaren AUTOSPORT BRDC Award finalist Scott was not enough to win the championship.

"They deemed it to be a racing incident," Falcon boss Nick Streatfiel said, "but the clerk said it was avoidable. I've appealed that decision to the MSA.

"We're a bit deflated because we don't like it to finish that way but – in our view and the clerk's view – he [Scott] was through."

Kruger said: "We're happy and we'll be celebrating, but we know that there is an appeal pending and we'll have to deal with that when the time comes. I'm confident that the outcome will support the decision of the stewards of the meeting."

 

 

 

Originally on Autosport.com

 

Comments

Comments are disabled until you accept Social Networking Cookies. Update cookie preferences

If the dialog doesn't appear, ad-blockers are often the cause; try disabling yours or see our Social Features Support.