1. (a) In order to apply for an Original Driverless Testing Permit, form OL 315A (Rev. 10/2023), which is hereby incorporated by reference:

   1. (1) A manufacturer, except a manufacturer of autonomous heavy-duty commercial motor vehicles, as described in (2), must have tested a minimum of 50,000 autonomous miles with a valid Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, on public roads throughout the operational design domain. A manufacturer operating a low-speed autonomous vehicle shall have tested a minimum of 10,000 autonomous miles with a valid Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, on public roads throughout the operational design domain.

      1. (A) The manufacturer shall provide the department with the results of an assessment of operational data from testing with a valid Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, under the testing parameters described in subsection (c).
      2. (B) The department may request additional information from the manufacturer that it deems necessary to assess the safety of an autonomous vehicle capable of operating without the presence of a driver inside the vehicle.

   2. (2) A manufacturer of autonomous heavy-duty commercial motor vehicles must have tested a minimum of 500,000 autonomous miles with a valid Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, on public roads throughout the operational design domain and in all conditions under which the subject automated driving system is intended to operate with a Driverless Testing Permit, form OL 315A (Rev. 10/2023), which is hereby incorporated by reference. Up to 400,000 of these miles may occur in other jurisdictions contingent upon the manufacturer providing all the reports that California requires to cover that out-of-state testing as described in subsection (d). 100,000 miles of such testing must occur within the intended operational design domain in California.

      1. (A) The manufacturer shall provide the department with the results of an assessment of operational data from testing with a valid Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, under the testing parameters described in subsection (c).
      2. (B) The department may request additional information from the manufacturer that it deems necessary to assess the safety of an autonomous heavy-duty commercial motor vehicle capable of operating without the presence of a driver inside the vehicle.

2. (b) In order to submit a Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference:

   1. (1) A manufacturer, except a manufacturer of autonomous heavy-duty commercial motor vehicles as described in (2), must have tested a minimum of 25,000 autonomous miles with a valid Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, on public roads throughout the operational design domain. A manufacturer operating a low-speed autonomous vehicle shall have tested a minimum of 10,000 autonomous miles with a valid Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, on public roads throughout the operational design domain.
   2. (2) A manufacturer of an autonomous heavy-duty commercial motor vehicle must have tested a minimum of 250,000 autonomous miles under an existing Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, on public roads throughout the operational design domain. Up to 200,000 of these miles may occur in other jurisdictions contingent upon the manufacturer providing all the reports that California requires to cover that out-of-state testing as described in subsection (d). 50,000 miles of such testing on the Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, must occur within the intended operational design domain in California.

3. (c) In an Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, or Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, a manufacturer shall provide a report of all testing conducted with a Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, on California public roads inclusive and reflective of the operational design domain for which a Driverless Testing Permit, form OL 315A (Rev. 10/2023), which is hereby incorporated by reference, is being sought. This shall include:

   1. (1) The total number of miles each autonomous vehicle operated in autonomous mode on public roads prior to the date of application. The total number of dynamic driving task performance relevant system failures that occurred in autonomous mode in the year prior to the date of application, if any, and a full description of all contributing factors that led to or caused each dynamic driving task performance relevant system failure. The reports shall be submitted using the electronic Vehicle Miles Traveled Template (Rev. 12/2025) and the Dynamic Driving Task Performance Relevant System Failure Reporting Template (Rev. 12/2025) provided by the department, which are hereby incorporated by reference. The manufacturer shall submit the reports electronically in .csv format via the department's web page or portal.
   2. (2) Copies of collision reports submitted to the National Highway Traffic Safety Administration in the year prior to the date of application. The report shall be submitted using the electronic Collision Reporting Template (Rev. 12/2025), which is hereby incorporated by reference, provided by the department, which is hereby incorporated by reference. The manufacturer shall submit the report electronically in .csv format via the department's web page or portal.
   3. (3) Any braking event, as defined in section 227.66, subsection (a), occurring during the operation of an autonomous vehicle in autonomous mode on public roads over the year prior to application in the operational design domain that is the same or comparable to that which is intended for testing with a Driverless Testing Permit, form OL 315A (Rev. 10/2023), which is hereby incorporated by reference. The report shall be submitted using the electronic Braking Event Reporting Template (Rev. 12/2025), which is hereby incorporated by reference provided by the department, which is hereby incorporated by reference. The manufacturer shall submit the report electronically in .csv format via the department's web page or portal.

4. (d) A manufacturer of autonomous heavy-duty commercial motor vehicles may provide a summary of out-of-state testing conducted over the year prior to application in autonomous mode on public roads in an operational design domain that is the same or comparable to that which is intended for testing with a Driverless Testing Permit, form OL 315A (Rev. 10/2023), which is hereby incorporated by reference. This shall include:

   1. (1) The total number of miles each autonomous vehicle operated in autonomous mode on public roads prior to the date of application. The total number of dynamic driving task performance relevant system failures that occurred in autonomous mode in the year prior to the date of application, if any, and a full description of all contributing factors that led to or caused each dynamic driving task performance relevant system failure. The reports shall be submitted using the electronic Vehicle Miles Traveled Template (Rev. 12/2025), which is hereby incorporated by reference, and Dynamic Driving Task Performance Relevant System Failure Reporting Template (Rev. 12/2025), which is hereby incorporated by reference, provided by the department. The manufacturer shall submit the reports electronically in .csv format via the department's web page or portal.
   2. (2) Copies of collision reports submitted to the National Highway Traffic Safety Administration in the year prior to the date of application. The report shall be submitted using the electronic Collision Reporting Template (Rev. 12/2025), which is hereby incorporated by reference, provided by the department. The manufacturer shall submit the report electronically in .csv format via the department's web page or portal.
   3. (3) Any braking event, as defined in section 227.66, subsection (a), occurring during the operation of an autonomous vehicle in autonomous mode on public roads over the year prior to application in the operational design domain that is the same or comparable to that which is intended for testing with a Driverless Testing Permit, form OL 315A (Rev. 10/2023), which is hereby incorporated by reference. The report shall be submitted using the electronic Braking Event Reporting Template (Rev. 12/2025), which is hereby incorporated by reference, provided by the department. The manufacturer shall submit the report electronically in .csv format via the department's web page or portal.

5. (e) In an Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, or Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, the manufacturer certifies that the local authorities, as defined in Vehicle Code section 385, within the jurisdiction where the vehicle will be tested have been provided a written notification, a copy of which must be submitted to the department, that contains all of the following:

   1. (1) The operational design domain of the test vehicles.
   2. (2) A list of all public roads in the jurisdiction where the vehicles will be tested.
   3. (3) The date that testing will begin.
   4. (4) The days and times that testing will be conducted on public roads.
   5. (5) The number of vehicles to be tested and the types of vehicles to be tested.
   6. (6) Contact information, including name, telephone number, address, and email for the contact person for the manufacturer conducting the testing.

6. (f) In an Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, Driverless Testing Permit Renewal Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, or Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, thehe manufacturer must certify that the autonomous test vehicle(s) complies with all of the following:

   1. (1) There is a communication link that enables the autonomous vehicle to seek and receive remote operations support, as applicable, and includes communication of information on the vehicle's location and status. For autonomous vehicles designed for passenger service, there is a method to enable two-way communication for purposes of providing remote operations support to any passengers if the vehicle experiences any failures or other conditions that would endanger the safety of the vehicle's passengers or other road users, or otherwise prevent the vehicle from functioning as intended without a driver physically located in the driver's seat of the vehicle. The certification shall include:

      1. (A) That the manufacturer has a system and process, which includes use of a redundant communications network to continuously monitor the status and functionality of the vehicle and the two-way communication link while the autonomous test vehicle is being operated without a driver physically located in the driver's seat of the vehicle.
      2. (B) A description of how the manufacturer will continuously monitor the status of the vehicle and communication link, and what type of data will be monitored.
      3. (C) A description of what redundancies and automated driving system capabilities are in place if there is a loss or degradation of the communication link.
      4. (D) A description of how the manufacturer will address situations where the autonomous vehicle achieves a minimal risk condition, including, but not limited to, when the automated driving system executes an automated fallback to a minimal risk condition, a minimal risk condition is triggered by a remote driver or remote assistant, the communication network fails or is degraded, vehicle hardware or software failures. The description should include, but not be limited to, roles and responsibilities of personnel.
      5. (E) A description and photographic evidence of the type of control output (e.g., screens, speakers, haptic feedback, etc.) input devices (e.g., steering wheels, joysticks, keyboards, microphones, etc.) utilized to provide remote operations support, as applicable.
   2. (2) There is a process to display or communicate vehicle owner or operator information as specified in Vehicle Code section 16025 in the event that the vehicle is involved in a collision or if there is a need to provide that information to a law enforcement officer for any reason.

   3. (3) Commencing July 1, 2026, for autonomous vehicles with a gross vehicle weight rating of less than 10,001 pounds, a manufacturer submitting an Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, Driverless Testing Permit Renewal Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, or Driverless Testing Permit Operational Parameters Modification Application form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, shall certify:

      1. (A) That there is a dedicated emergency response telephone line available for emergency response officials during all hours when the autonomous vehicle is on a public road and is available at no cost to public agencies.
      2. (B) That the dedicated emergency response telephone line is equipped and staffed to ensure calls are picked up within 30 seconds by remote operations support personnel who have situational awareness of the autonomous vehicle.
      3. (C) That there is a two-way voice communication device that enables emergency response officials that are near the vehicle to communicate effectively with remote operations support personnel that have situational awareness.
      4. (D) That an emergency response official is able to reach remote operations support personnel within 30 seconds after making a request through the two-way voice communication device.
      5. (E) That there is remote operations support personnel with the ability to immobilize the autonomous vehicle, allow an emergency response official to move the vehicle, or cause the autonomous vehicle to move as directed by an emergency response official.
      6. (F) A manufacturer whose autonomous vehicle is operating under a Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, or Driverless Testing Permit, form OL 315A (Rev. 10/2023), which is hereby incorporated by reference, must issue direction to its fleet to leave or avoid the identified area within two minutes of receiving an emergency geofencing message from an emergency response official. The avoidance area shall remain in place for the initial duration provided by the emergency response official or for an extended duration, when specified by the emergency response official.
      7. (G) Within 30 business days of receiving a notice that an emergency response official wishes to begin issuing emergency geofencing messages, a manufacturer shall provide the emergency response official with all information necessary for the emergency response official to begin issuing and for the manufacturer to receive and respond to emergency geofencing messages.

      8. (H) If the autonomous vehicle is equipped with an override system, it shall allow law enforcement and firefighters to immobilize or cause the vehicle to move as necessary to respond to an emergency.

         1. (1) The manufacturer shall provide training to law enforcement and firefighters on the use of the override system. The training shall be reviewed on a regular basis and updated by the manufacturer as changes are needed.
   4. (4) The autonomous vehicle has a visual indicator inside the cabin to indicate when the autonomous technology is engaged.
   5. (5) The subject autonomous vehicles comply with all required Federal Motor Vehicle Safety Standards (FMVSS), Title 49 Code of Federal Regulations, Part 571 and the California Vehicle Code, Division 12 (Equipment of Vehicles), except for manufacturers exempt from such requirements pursuant to 49 U.S.C. § 30112(b)(10). If exempt, the manufacturer shall describe how the vehicle materially deviates from the FMVSS. The manufacturer shall provide the exemption that has been issued by the National Highway Traffic Safety Administration or the Federal Motor Carrier Safety Administration for an autonomous heavy-duty commercial motor vehicle. The manufacturer shall provide a copy of the exemption to law enforcement upon request.
   6. (6) The automated driving system is designed to detect and respond to roadway situations in compliance with all provisions of the California Vehicle Code, California Code of Regulations, and local ordinances applicable to the performance of the dynamic driving task in the vehicle's operational design domain, except when necessary to enhance the safety of the vehicle's occupants and/or others.
7. (g) The manufacturer certifies that the autonomous vehicles are capable of operating without the presence of a driver physically located in the driver's seat of the vehicle and that the autonomous technology meets the description of a level 4 or level 5 automated driving system under SAE International's Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles, standard J3016 (APR2021), as may be revised, which is hereby incorporated by reference.

8. (h) The manufacturer informs the department of the intended operational design domains of the autonomous vehicle. The manufacturer shall identify all commonly-occurring or restricted conditions, including, but not limited to: inclement weather conditions and a description of how inclement weather affecting performance in a manner that requires achieving a minimal risk condition is identified, traffic, roadway characteristics, and other known domain constraints, and geo-fencing by location or roadway type, under which the vehicle is unable to operate reliably in autonomous mode, and state the mechanism for safely disengaging autonomous mode in the event the vehicle encounters conditions outside of its prescribed operational design domain.

   The operational design domain shall identify how an autonomous heavy-duty commercial vehicle will operate when detours or alternate routing is required by emergency incidents, weather conditions, road construction, other road closures, or other conditions or circumstances.

9. (i) The manufacturer shall develop a First Responder Interaction Plan, publish and maintain the plan, and provide automated driving system content to support first responder training development. The First Responder Interaction Planshall include information that instructs first responders on how to interact with the vehicle in emergency and traffic enforcement situations.

   1. (1) The First Responder Interaction Plan shall include, but not be limited to the following:

      1. (A) A description of the operational design domain, including, but not limited to geographical area description, road types, speed range, weather condition, time of day.
      2. (B) A description of remote operations support -- roles and responsibility, types of services and hours of operation.
      3. (C) A telephone number dedicated for emergency response officials to directly contact and communicate with a remote operations support personnel who has situational awareness of the vehicle and is available at all times that the vehicle is in operation and how to use the two-way voice communication link enabling communication between emergency response officials and the remote operations support personnel.
      4. (D) The manufacturer's address.
      5. (E) A description and pictures, diagrams, or other means to identify the autonomous vehicle.
      6. (F) Instructions on how to safely approach the autonomous vehicle; how to determine the vehicle's mode (e.g., autonomous mode); and how to immobilize the autonomous vehicle when equipped with an override system.
      7. (G) Instructions for accessing registration, permit, and proof of insurance information.
      8. (H) Instructions on the vehicle's electrical power source and instructions for safely disconnecting or otherwise disabling electrical power on the vehicle.
      9. (I) Instructions that enable first responders to act independently or in concert with remote operations support personnel to drive or otherwise safely remove the autonomous vehicle from the active portion of the roadway. Instructions shall include how first responders will move the autonomous vehicle from the roadway, if the vehicle is equipped with an override system.
      10. (J) The means for determining the presence of passengers and how first responders may assist them with exiting the vehicle.
      11. (K) Any special considerations for extricating passengers from the autonomous vehicle, including any appropriate or inappropriate cut points or cut zones in the vehicle body/structure.
      12. (L) A description of any unique hazards or special considerations for extinguishing fires on or around the vehicle, if applicable.
      13. (M) Instructions for coordinating with remote operations support personnel and safety considerations for first responders needing to tow the autonomous vehicle from the roadway.
      14. (N) How to recognize whether the vehicle is in autonomous mode, description of the visual indicator inside the cabin that indicates when the autonomous technology is engaged, description of automated driving system marker lamps as described in Vehicle Code 38750(d)(4)(i), if applicable, and, how to safely deactivate the autonomous mode; and validate that the autonomous mode has been deactivated.
      15. (O) Any additional information the manufacturer deems necessary regarding hazardous conditions or public safety risks associated with the operation of the autonomous vehicle.

   2. (2) In addition to the requirements of subsection (i)(1), notwithstanding a two-way voice communication link, the First Responder Interaction Plan for autonomous heavy-duty commercial motor vehicles shall include the following:

      1. (A) Description of how the vehicle will maneuver to the designated location for a vehicle inspection without posing any unreasonable risk to traffic safety, other vehicles being inspected, or pedestrians.
      2. (B) Certification that the automated driving system and remote driver and/or remote assistant is able to recognize, respond to, and comply with law enforcement and vehicle inspectors during a vehicle inspection.
      3. (C) Description of how the automated driving system will recognize and respond to a vehicle inspection, including, but not limited to, directions by law enforcement and vehicle inspectors, traffic control devices (e.g., signal lamps, changeable message signs, etc.), pavement markings, and zones designated for vehicle inspection without posing any unreasonable risk to traffic safety, other vehicles being inspected, or pedestrians.
      4. (D) Certification that each remote assistant and remote driver shall comply with an officer's commands during a vehicle inspection or traffic stop and will not cause the vehicle to move unless directed by a law enforcement officer.
      5. (E) A dedicated emergency response telephone line available for emergency response officials during all hours when the autonomous vehicle is on a public road and is staffed to ensure calls are picked up within 30 seconds by remote operations support personnel who have situational awareness of the autonomous vehicle.
   3. (3) The First Responder Interaction Plan shall be reviewed at least annually and updated based on incidents involving interactions with first responders, including, but not limited to, traffic stops and emergency response scenes that occur on public roads, as changes are needed. Such reviews shall be documented including by the issuance of a new version of the training program following the review.
   4. (4) Within 10 business days of the approval of the application, the manufacturer shall submit the First Responder Interaction Plan to the California Highway Patrol by E-mail to, [email protected].
   5. (5) In an Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025, which is hereby incorporated by reference, or Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, the manufacturer shall provide a copy of the First Responder Interaction Plan that will be made available to law enforcement agencies and other first responder agencies located within the operational design domain. No later than 10 business days prior to commencing testing, manufacturers shall provide the department and all law enforcement agencies and first responder agencies located in the operational design domain where testing of driverless autonomous vehicles is being conducted the internet web site address where the First Responder Interaction Plan may be accessed.
   6. (6) If the manufacturer intends to make any changes to their autonomous vehicle or testing operations that include a material change to how law enforcement and other first responders interact with the autonomous vehicle, the manufacturer shall submit a revised plan, prior to posting the plan, to the department and the California Highway Patrol prior to operation of autonomous vehicles on public roads pursuant to the changes.

10. (j) When applying for an Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, or Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, the manufacturer shall provide:

    1. (1) Certification that the automated driving system is designed to detect and respond to an active emergency vehicle, or first responder as necessary to comply with applicable provisions of the California Vehicle Code, including Sections 21806, 21809, and 21706.
    2. (2) Regular training to first responders located within the operational design domain on how to safely interact with the autonomous vehicle in the event of a collision, traffic violation, or other traffic enforcement situation, and any incident whereby the vehicle is stopped in an active lane of traffic and unable to proceed. In an Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, Driverless Testing Permit Renewal Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, or Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, the manufacturer shall provide the course outline and description of the training program, and the dates and agencies where training has been provided.
    3. (3) A training program for first responders, including training on how to access and use the override system referenced in the Vehicle Code section 38751(b)(3). The training program shall be reviewed at least annually and updated based on incidents involving interactions with first responders, including, but not limited to, traffic stops and emergency response scenes that occur on public roads, and as changes are needed. Such reviews shall be documented, including by the issuance of a new version of the training program following the review.
11. (k) The manufacturer shall disclose to any passenger in the vehicle that is not an employee, contractor, or designee of the manufacturer what personal information, if any, that may be collected about the passenger and how it will be used.
12. (l) In an Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, or Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, the manufacturer shall describe how the automated driving system achieves a minimal risk condition, and how the vehicle uses a failure mitigation strategy to bring the vehicle to a controlled stop in the event of a system failure in which the automated driving system is unable to perform the dynamic driving task fallback and achieve a minimal risk condition.
13. (m) The manufacturer shall submit the fee of three thousand six hundred dollars ($3,600) for the processing of the Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, which will accommodate up to 10 driverless autonomous test vehicles. The manufacturer may add more than 10 vehicles to the application by submitting the additional fee of fifty dollars ($50) for each set of 1 to 10 vehicles.
14. (n) Any change to the contact information or the name of the manufacturer provided to the department shall be accomplished by meeting the requirements specified in section 227.28(b).

15. (o) The manufacturer shall submit a Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, and submit the fee of seventy dollars ($70) to process implementing changes to:

    1. (1) Make the vehicle capable of operation at a SAE International level that is different than the level in the approved permit.
    2. (2) Make the vehicle capable of operation on a roadway type that is different than those in the approved permit.
    3. (3) Increase the maximum speed of the vehicle by more than 15 miles per hour above that on the approved permit.
    4. (4) Make the vehicle capable of operation in geographic areas different than those in the approved permit.
    5. (5) Modify the days of the week or hours of operation that were identified on the approved permit.
    6. (6) Remove or modify any restricted conditions that were identified on the approved permit.
    7. (7) Add a vehicle make and/or model different than the vehicle(s) identified on the approved permit.

16. (p) The manufacturer shall provide the following information by submitting a Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, and the fee of seventy dollars ($70) to process implementing changes to:

    1. (1) The training program, as described in sections 227.38(c)(5) and 227.40(b)(5).
    2. (2) Remote driver licensing information.
    3. (3) Vehicle registration information (e.g., replacing license plates that are lost or stolen, converting registration from auto to commercial).
    4. (4) Add any vehicles, or remote drivers that were not previously identified in the Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, and issued a permit by the department.
    5. (5) Remove any vehicles from the Driverless Testing Permit, form OL 315A (Rev. 10/2023), which is hereby incorporated by reference.
    6. (6) Remove any remote drivers from the Driverless Testing Permit, form OL 315A (Rev. 10/2023), which is hereby incorporated by reference, in compliance with section 227.38(b)(7).
    7. (7) Remove any remote assistants from the Driverless Testing Permit form OL 315A (Rev. 10/2023), which is hereby incorporated by reference, in compliance with section 227.40(a)(7).

A manufacturer desiring to conduct testing of autonomous vehicles designed to be capable of operating on public roads in California in a specific operational design domain without the presence of a driver physically located in the driver's seat of the vehicle shall submit an Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference,, which is hereby incorporated by reference. At all times, a valid Drivered Testing Permit, form OL 315 (Rev. 9/2024), which is hereby incorporated by reference, is a condition for maintenance of a Driverless Testing Permit, form OL 315A (Rev. 10/2023), which is hereby incorporated by reference. A manufacturer submitting an Original Driverless Testing Permit Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, a Driverless Testing Permit Renewal Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, Driverless Testing Permit Operational Parameters Modification Application, form OL 318 (Rev. 2/2025), which is hereby incorporated by reference, may also choose to submit the form electronically via the department's web page or portal. Notwithstanding the requirements of Sections 227.04(b), 227.22, 227.24(a) and (b), 227.32, 227.34, and 227.36, a manufacturer may conduct testing of autonomous vehicles designed to be capable of operating on public roads in California in a specific operational design domain without the presence of a driver physically located in the driver's seat of the vehicle only if all of the following requirements are met:

Note: Authority cited: Sections 1651 and 38750, Vehicle Code. Reference: Sections 385, 2410, 16025, 21367, 21461 and 38750, Vehicle Code; and Title 49 Code of Federal Regulations, Part 571.

History

1. New section filed 5-19-2014; operative 9-16-2014 pursuant to Vehicle Code section 38750(f) (Register 2014, No. 21).

2. Renumbering of former section 227.42 to section 227.46 and new section 227.42 filed 2-26-2018; operative 4-1-2018 (Register 2018, No. 9).

3. Renumbering of former section 227.42 to section 227.48 and renumbering of former section 227.38 to section 227.42, including amendment of section heading, section and Note, filed 4-28-2026; operative 4-28-2026 pursuant to Government Code section 11343.4(b)(3) (Register 2026, No. 18).