|
|
|
|
|
by theamk
1070 days ago
|
|
No, the driver is the one pressing accelerator and brakes, and this is the computer in the car and algorithms in it. Saying "driver is a corporate entity" makes as little sense as saying "driver of this regular bus is AC Transit". It's like: imagine someone hates AC Transit, so they started approaching the busses and putting huge, obscuring stickers on the windshield. Would AC transit suffer from that? Sure. And so would the passengers and other vehicles on the road. |
|
I looked up some relevant regulations for California. So the following arguments are probably only relevant in the state of California. I would be surprised if they are not subject to change in the near future. Also, I am not a lawyer, so not only is the following not legal advice, it might also be totally incorrect. But it’s interesting to think about.
I found there are at least three relevant sections of the California Vehicle Code, namely Section 227, Section 228, and Section 38750.
Section 38750(a)(4) states:
How is this operator relevant? Well, the presence of a remote operator is mandatory for both testing (Section 227) and deployment (Section 228) of autonomous vehicles on public streets in the state of California. Section 228.06(c)(3) states that a manufacturer applying to deploy autonomous vehicles must provide: Section 227.38(e)(1)(A) states that the law enforcement interaction plan shall include: Further, Section 227.02(n) does define the remote operator as a natural person.So, there is a remote operator available at all times, in both testing and deployment of autonomous vehicles. This remote operator can operate the vehicle remotely, and presumably one remote operator can be responsible for many autonomous vehicles, because otherwise the business plan breaks.
I would be interested to see if in the future there is a mandated ratio of vehicles per remote operator. My guess is the ratio will approach one.