What is life like with your car? Let us know and win £500 in John Lewis vouchers | No thanks
Motorway services parking 'fine' from parking eye
My wife and daughter met at the Welcome Break services at Charnock Richard North on 22nd September so my daughter could pass over some of her belongings which we would take to her student house. My wife was travelling from Colwyn Bay to Devon, my daughter from her home outside Preston. As my wife was facing a long journey they had coffee and lunch at the Starbucks. They were each unaware of the 2 hour limit on parking and both have since received a Parking Charge Notice from Parking Eye, demanding £100 or £60 if paid within 14 days - they had been there for 3 hours 6 minutes. What is our best course of action? The charge seems unreasonable - the charge for staying more than the 2 hours allowed according to the Welcome Break website is £11.
Asked on 4 October 2015 by Jon Davies
Answered by
Honest John
Unfortunately the Appeal Court has ruled that this type of penalty is totally legal and "reasonable" despite the fact that Government warnings on the motorway tell you "Tiredness can kill. Take a break." If that break is longer than 2 hours you have to pay a penalty. Britain is the only country in the world that allows this to happen in a motorway service area. The Appeal Court Case went to the Supreme Court in July and a ruling is expected this month that might reverse the Appeal Court ruling, but meanwhile the Appeal Court ruling is the law.
Similar questions
Yesterday I got stuck at Clacket Lane services on the M25 as there was an accident and it was gridlocked. I stayed at the services for about three hours. Am I likely to get a penalty ticket and can I challenge...
I recently received a parking charge notice from Parking Eye for 21 minutes over their two hour time. I didn't realise there was a time limit. Do I need to pay?
I recently received a parking charge notice from parking eye at burtonwood services on the M62. This was not a pay and display car park and it was dark so the driver could not be identified. After looking...
.jpg)
