Automated and Electric Vehicles Bill — House of Lords, 2018-02-20
Topic: Mixed Topics
Dale Norman Campbell-Savours (Labour, Centre-left): My Lords, I apologise to the House because my voice is a little frail today, after a rather difficult week I regret to say that I have mixed feelings over the introduction of the Bill, although I particularly welcome provisions dealing with battery technology. I believe that the moment the industry can claim 450 or 500-mile ranges for vehicles, particularly motor cars—with adequate charging points at home, on the roadside and in commercial areas—the market will take off However, I see two impediments. First, the price of home-charging units will inevitably go up because the Exchequer will have to compensate for the revenue loss on hydrocarbons, particularly taking into account the fact that some people will use their electric vehicles far more regularly than others. We need a little more information about how hydrocarbon revenues will be made up. Also, if home-charging rates are put up, we might get tax evasion—as we have with pink diesel, which has been a major area of tax evasion over the years. Secondly, the introduction of electric vehicles has consequences for west African and Middle Eastern politics: oil-producing countries that are dependent on hydrocarbon production will be in a rather difficult position. I am not opposing it at all, but I am not sure that we have altogether thought through the political consequences for those parts of the world Although I welcome the provisions on battery usage, I take a very different view on driverless vehicles. From the 2017 Budget report, I understand that the Government want to see some of them on the road by 2021. That worries me. I regard the development of driverless car technology as premature and, in the main, probably unnecessary—a huge black hole down which millions, perhaps billions, of pounds will be lost as promoters increasingly experience regulatory problems, software failure problems, contested legal liability—despite the first-instance arrangements that the Minister referred to—roadside vehicle control technology problems, road pricing arguments, public expenditure or infrastructure constraints, traffic delays leading to congestion and, most of all, driver frustration, which does not appear to have been considered to date. I foresee huge driver frustration with the technology. I am not suggesting that driverless vehicles will never happen; they will come one day, but only after the increasing problem of congestion has been resolved—particularly as every year there are more and more vehicles on our roads— public transport has been hugely improved, and there have been developments in as yet unexploited overhead transport systems in inner-city areas. The high-speed agenda currently being pursued is premature I will take two areas where the Bill seeks to reassure us. On insurance, we had a report from the Science and Technology Committee in February 2017. Paragraphs 54 to 59 of that excellent report are on liability and insurance and describe occasions, "when an accident occurs and the car is in fully autonomous mode. In this case the ‘driver’ is not necessarily liable and liability could lie with the manufacturer of the vehicle" The report goes on to state that there were, "some remaining issues, particularly around product liability" That is the understatement of 2017. The whole approach to vehicle liability will turn into a legal nightmare in the end despite the assurances given by the Minister. It is a lawyer’s dream, with different legal jurisdictions internationally drawing up different protocols, law, appeal arrangements and perhaps even immunities If noble Lords want more evidence of that, we need do no more than examine the provisions in the Bill. Clause 3(2) states: "The insurer or owner of an automated vehicle is not liable under section 2 to the person in charge of the vehicle where the accident that it caused was wholly due to the person’s negligence in allowing the vehicle to begin driving itself when it was not appropriate to do so" "Inappropriate to do so" will be very expensive words, because the lawyers will make a mint out of it. They will love that one. How about this one "An insurance policy in respect of an automated vehicle may exclude or limit the insurer’s liability … for damage suffered by an insured person arising from an accident occurring as a direct result of …a failure to install safety-critical software updates that the insured person"— once again we are into an area that the lawyers will love— "knows, or ought reasonably to know, are safety critical" That is also worth a few bob We will end up in trench warfare between the likes of Microsoft, Tesla, Dyson, Ford, Mitsubishi and the big insurance companies and poor old Joe Bloggs, the innocent man caught in the middle, with 100 cars barping and beeping behind him as he sits at a congested roundabout with two software systems in two separate cars screaming and arguing with each other over who should go first. If the wrong one proceeds and clouts the other, there will be some very angry queueing drivers behind. It will be like a road traffic accident in Italy in the 1950s and 1960s—some noble Lords may recall them. Whenever there was an accident there would be a huge crowd of people surrounding the cars. The reason was of course because there was only third-party insurance and someone was going to pay. That is the kind of argument that I see us getting into I have another example on software conflict. Clause 2(2)(d) states that: "Where … an accident is caused by an automated vehicle when driving itself", and, "a person suffers damage as a result of the accident", the insurer is liable for the damage. But which car’s insurer? I heard insurance companies referred to, but will they stand up at the end of the day? People pay premiums to insurance companies and there comes a point where someone has to take a decision on conditions of software conflict I ask myself a simple question. Should a vehicle owner who is not driving, an attendant driver, a passenger or any other person be held responsible in law in any way for a software malfunction beyond their knowledge or control that leads to damage to another vehicle or injury to others? By others I mean people in the car allegedly at fault, persons in another vehicle, pedestrians in the street or persons on private property. What about a multiple accident on a motorway? That will be an interesting one for the lawyers That brings me to the equally important issue of offences under the road traffic Acts. Again, I ask a simple question: who is liable when the software leads the vehicle to drive down a cycle lane, which is punishable in law? Who is liable if the vehicle turns right at a "No right-hand turn" sign, which is punishable; or exceeds the speed limit, which is punishable; passes through a red light, which is punishable; or enters a one-way street the wrong way—punishable? I have no reason to believe that these issues have been sorted out Finally, I have been referred to case law which is based on a House of Lords decision of 1925: Donoghue v Stevenson, known as the "snail in the bottle" case. It established the civil tort of negligence and obliged manufacturers to observe a duty of care towards customers. I should make it clear that I am not a lawyer; I am simply referring to the comments of others. In that decision, it was established that a manufacturer owes a duty to the consumers who it intends to use its products. This arose out of the need for negligence to be dependent on contract. It enforced the concept of a duty between the parties concerned. The lawyers will argue that in the case of the driverless car the software manufacturer, or even the vehicle manufacturer, stands in the front line of responsibility in both accidental damage and injury, and perhaps even in the unimaginable circumstance of road traffic Acts penalty fine payments. As I say, I am most unhappy about this latter part of the Bill. I know that the noble Baroness has given us assurances on first-instance responsibility, but I do not believe that it is going to work, or at least not yet.