The robot then "reversing again into the woman still on the ground."

Crash With

SUV

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Rear

SV Precrash Speed (MPH)

32

CP Pre-Crash Movement

Changing Lanes

CP Contact Area

Front Left

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On July [XXX], 2026 at 1:10 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling northeastbound in the second to the rightmost lane on [XXX] when an SUV traveling northeastbound on [XXX] at a high rate of speed, partially in the second to the rightmost lane and partially in the left lane, began to change lanes to the left lane as it approached the Waymo AV from behind. The SUV attempted to pass the Waymo AV to the left, and the front right side of the SUV made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the passenger car sustained unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

Mako Robotic-Arm — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: THE FOLLOWING INFORMATION WAS PROVIDED: I&D OF RIGHT KNEE WITH MEDIAL UNI POLY SWAP OUT DUE TO INFECTION.

Versius — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: THE REPORTER ALLEGED THAT DURING A LEFT INFERIOR LOBECTOMY PROCEDURE ON (B)(6) 2026, WHILST USING A BIPOLAR MARYLAND GRASPER PART OF THE LUNG'S TISSUE GOT STUCK IN THE JOINT AND WAS UNABLE TO REMOVE THE TISSUE. NO FURTHER INFORMATION IS AVAILABLE AT THIS TIME. CMR SURGICAL LTD DOES NOT CONSIDER THIS REPORT AND CONTENT TO BE AN ADMISSION THAT ITS PRODUCT IS DEFECTIVE OR THAT IT HAS CAUSED A DEATH OR SERIOUS INJURIES.

Crash With

Non-Motorist: Cyclist

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Right

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Proceeding Straight

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Intersection

Weather

Clear

Investigating Agency

San Francisco Police Department

Make

ZOOX

Model

Zoox

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

An occupied Zoox autonomous vehicle was proceeding southbound on [XXX] after making a full stop at a 4-way-stop at [XXX] in San Francisco, when a fast-moving cyclist ran the stop sign from a downhill section of [XXX] from the right. The Zoox vehicle came to a stop in the intersection to yield to the approaching cyclist. The cyclist lost control, went over the handlebar, made contact with the left rear corner of the stopped Zoox vehicle, and then fell to the ground. The Zoox vehicle remained stopped in the intersection following the impact. Police and emergency services were notified and arrived at the scene. The cyclist was transported to a hospital via ambulance. The Zoox vehicle then resumed operation. There was no damage to the vehicle.

Crash With

Non-Motorist: Pedestrian

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Rear Left

SV Precrash Speed (MPH)

6

CP Pre-Crash Movement

Other, see Narrative

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On June [XXX], 2026 at 6:01 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger of the Waymo AV on [XXX] near [XXX]. The Waymo AV was travelling westbound on [XXX]. While the Waymo AV was in motion, a passenger seated in the rear right of the Waymo AV removed their seatbelt and opened the right rear passenger side door. The Waymo AV detected the opened door and began to slow in-lane. While the Waymo AV was slowing, the passenger seated in the right rear passenger seat exited the vehicle through the open door, placed their feet on the ground, and the rear right tire of the Waymo AV made contact with the Waymo AV passenger, who fell to the ground as the Waymo AV came to a stop. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passenger of the Waymo AV was transported from the scene to a hospital for medical treatment with unknown injuries. A passenger in the Waymo AV was not belted at the time of the collision as they were exiting the vehicle. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Motorcycle

SV Pre-Crash Movement

Stopped

SV Contact Area

Rear Left

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Other, see Narrative

CP Contact Area

Rear Right, Front Right

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

San Francisco Police Department

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On June [XXX], 2026 at 1:07 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was involved in a collision involving a motorcycle and an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the dedicated left turn lane for a red light on [XXX] at the intersection with [XXX]. While the Waymo AV remained stopped, a motorcycle traveling in the second from the right lane came to a stop adjacent to an SUV that was stopped in the rightmost lane. After both vehicles briefly remained stopped, the SUV and motorcycle began to proceed forward when the SUV changed lanes into the second from the right lane, towards the motorcycle. The motorcycle maneuvered left towards the dedicated left turn lane, and the SUV continued to change lanes across the second from the right lane, towards the motorcycle into the dedicated left turn lane. While the SUV continued to change lanes, the front right of the SUV made contact with the rear of the motorcycle, and the front left of the SUV made contact with the right side of a passenger car that was stopped behind the Waymo AV. As a result of this initial contact with the SUV, the motorcycle continued forward and the front of the motorcycle then made contact with the rear right of the Waymo AV. The SUV also continued forward, and the front left of the SUV then made contact with the rear right of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All involved vehicles sustained damage, and the motorcyclist was transported to the hospital by ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital by ambulance. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Van

SV Pre-Crash Movement

Stopped

SV Contact Area

Front

SV Precrash Speed (MPH)

2

CP Pre-Crash Movement

Crossing into Opposing Lane

CP Contact Area

Left

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Partly Cloudy

Investigating Agency

Florida Highway Patrol

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On June [XXX], 2026 at 2:54 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] and approaching a curve in the road to the left, when a van traveling westbound on [XXX] along the curve in the road crossed the double yellow and entered the Waymo AV's lane of travel. The Waymo AV braked, maneuvered to the right and slowed to a stop as the van continued forward, and the left side of the van made contact with the front left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the van was transported to the hospital by ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

SUV

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Rear Right

SV Precrash Speed (MPH)

3

CP Pre-Crash Movement

Proceeding Straight

CP Contact Area

Front Right

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

San Francisco Police Department

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On May [XXX], 2026 at 11:59 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] with its right turn signal activated when it began to slow to yield to a passenger car stopped facing west near the north curb of [XXX] and partially in-lane. While the Waymo AV was slowing, an SUV traveling westbound on [XXX] at a high rate of speed approached the Waymo AV from behind, and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Passenger Car

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Rear, Rear Right

SV Precrash Speed (MPH)

3

CP Pre-Crash Movement

Proceeding Straight

CP Contact Area

Front Left, Front, Front Right

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

None

Make

ZOOX

Model

Zoox

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

An unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling north on [XXX], having just completed a left turn from [XXX] in Las Vegas, when it encountered debris in its path. The Zoox vehicle attempted to steer right, then executed hard braking to avoid the debris, at which point it was rear-ended by a passenger car (Vehicle 2) traveling directly behind it. Both vehicles came to a stop following the impact and were subsequently towed due to the damage sustained. Vehicle 2 suffered front-end damage and its driver-side frontal airbags deployed, while the Zoox vehicle sustained moderate damage to its rear. Law enforcement was notified of the event, but did not respond to the scene. Following the impact, Zoox staff inquired if emergency medical services should be called; the driver replied that the police had already been contacted. The driver of Vehicle 2 informed Zoox staff at the scene that they were "shaken" and "pretty bruised".

Crash With

Passenger Car

SV Pre-Crash Movement

Making Right Turn

SV Contact Area

Rear Right

SV Precrash Speed (MPH)

2

CP Pre-Crash Movement

Proceeding Straight

CP Contact Area

Front Right

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Partly Cloudy

Investigating Agency

Tempe Police Department

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On May [XXX], 2026 at 12:43 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling eastbound in the rightmost lane on [XXX] with its right turn signal activated when it began to slow to turn right into a parking lot at [XXX]. As the Waymo AV initiated the right turn, a passenger car traveling eastbound in the rightmost lane on [XXX] approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. A passenger in the passenger car was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

VELYS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: DURING LEFT TKA ROBOTICALLY ASSISTED VELYS CASE- VELYS SAW HAND PIECE BROKE. NO HARM TO PATIENT.

Versius — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: THE REPORTER ALLEGED THAT DURING A SACROCOLPOPEXY PROCEDURE ON (B)(6) 2026 THE SURGEON OBSERVED THAT THERE WAS A PIECE OF COLON TISSUE STUCK IN THE CADIERE GRASPER. IT WAS NOT POSSIBLE TO PULL IT OUT AND THE TISSUE HAD TO BE CUT LOOSE. BESIDE THIS CUTTING THERE WAS NO HARM TO THE PATIENT AND THE ISSUE DID NOT OCCUR AGAIN. THE PATIENT HAS RECOVERED WELL FROM SURGERY AND HAS BEEN DISCHARGED FROM HOSPITAL WITH NO COMPLICATIONS. AT THE TIME OF THIS REPORT, NO FURTHER INFORMATION HAS BEEN PROVIDED. CMR SURGICAL LTD DOES NOT CONSIDER THIS REPORT AND CONTENT TO BE AN ADMISSION THAT ITS PRODUCT IS DEFECTIVE OR THAT IT HAS CAUSED A DEATH OR SERIOUS INJURY

Versius — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS ALLEGED THAT THE SURGEON CONSOLE WENT INTO A MEDIUM PRIORITY ALARM DURING SURGERY AND THE RIGHT HAND CONTROLLER ARM BECAME STILL. THE SURGEON CONSOLE COULD NOT BE RECOVERED AND THE PROCEDURE WAS CONVERTED. IT IS ALLEGED BY THE REPORTER (DISTRIBUTOR) THAT THE PROCEDURE WAS CONVERTED TO OPEN APPROACH DUE TO THE FOLLOWING PATIENT CONDITIONS: HIGH BLOOD PRESSURE AND BMI OF OVER 30 WITH A LOT OF ABDOMINAL FAT. A DELAY OF APPROXIMATELY 20 MINUTES WAS ALLEGED IN RELATION TO THIS EVENT. NO PATIENT HARM WAS REPORTED IN RELATION TO THIS EVENT. PHOTOS WERE PROVIDED BY THE REPORTER (DISTRIBUTOR) TO SHOW THE MALFUNCTIONING PART. THE MALFUNCTIONING PART WAS REPLACED BY THE DISTRIBUTOR. AT THE TIME OF THIS REPORT, NO FURTHER INFORMATION HAS BEEN PROVIDED.

Mako Robotic-Arm — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: THE FOLLOWING INFORMATION WAS PROVIDED: I&D OF A LM PKA WITH AN MCK TIBIAL INSERT EXCHANGE DUE TO INFECTION.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING AN EXCELSIUS GPS SURGERY THERE WAS 4 SCREW CREO MIS BACKUP OF ALIF. THE SM ON RIGHT PSIS DRB ON LEFT PSIS, ICT PLACE ON DRB LP QUATRO SPIKE. THE INTRA OP SPIN WITH O-ARM AND FILES TRANSFERER TO EGPS VIA USB. ALL 4 SCREWS PLANNED BY SURGEON. THE ICT WAS REMOVED AND SM VERIFIED. THE POSTOP SPIN SHOWED 4 SCREWS HAD SHIFTED OF PLAN BY APPROX 2-3MM LATERAL. NO IOM ISSUES. THE SURGEON DECIDED TO REPOSITION THE L5 SCREWS BY HAND.

Crash With

Heavy Truck

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Front Left

SV Precrash Speed (MPH)

17

CP Pre-Crash Movement

Parked

CP Contact Area

Rear Left

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

Miami Dade Police Department

Make

TOYOTA

Model

Highlander

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

A Zoox vehicle in autonomous mode was traveling east on [XXX] toward [XXX] in Miami when the operator of a wrong-way-parked semi-trailer suddenly swung open the rear door of the trailer into the path of the approaching Zoox vehicle. The door struck the Zoox vehicle's right-side A-pillar, windshield, and sensor assembly. After the impact, the trailer's door rebounded and struck the operator behind it. The Zoox vehicle operator then disengaged from autonomous mode. The police and emergency personnel arrived at the scene. The operator was transported by an ambulance from the scene.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSUS GPS SYSTEM, THE SCREW MISSED TARGET AND APPEARED TOO HIGH IN PEDICLE.THEY BELIEVE THE TRAJECTORY WAS SLICED BUT NEED AN ACCURACY CHECK REGARDLESS. THEY REPLACED SCREW WITH NEW PLAN.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING AN EXCELSIUS GPS SURGERY, THE SURGEON DECIDED TO ABORT A EXCELSIUS GPS SI LOK SURGERY ON (B)(6) 2026. HE WAS NOT CONFIDENT WITH THE ACCURACY AND SAFETY CHECKS. THE ENTIRE SURGERY WAS ABORTED AND THE PATIENT WAS ALREADY UNDER ANESTHESIA.

Ion Endoluminal System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING AN ION TRANSBRONCHIAL LUNG BIOPSY PROCEDURE, THE PATIENT DEVELOPED A PNEUMOTHORAX REQUIRING PLACEMENT OF A CHEST TUBE AND HOSPITALIZATION. THE TARGETED LESION WAS A LEFT UPPER LOBE INFERIOR NODULE ABUTTING THE MOST INFERIOR PART OF THE LINGULA BEHIND THE HEART. PER THE PHYSICIAN, THERE WERE SUBOPTIMAL ANGLES AND THE DEPTH PERCEPTION WAS NOT GOOD. FINE NEEDLE ASPIRATIONS (FNA) PASSES AND FORCEPS WERE USED. THE PHYSICIAN REPORTED THAT THEY INSERTED THE FORCEPS FURTHER THAN INTENDED AND LIKELY CAUSED THE PNEUMOTHORAX. A LARGE PNEUMOTHORAX WAS IDENTIFIED DURING THE ION PROCEDURE; THEREFORE, A 14 FRENCH CHEST TUBE WAS PLACED AND THE PROCEDURE WAS ABORTED. THE PATIENT WAS HOSPITALIZED 4 DAYS THEN DISCHARGED HOME IN STABLE CONDITION. THERE WAS NO ALLEGATION THAT A MALFUNCTION OF AN ION SYSTEM, INSTRUMENT, OR ACCESSORY OCCURRED. THE DIAGNOSIS WAS MAC-NTM (MYCOBACTERIUM AVIUM COMPLEX NONTUBERCULOUS MYCOBACTERIA).

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A REVISION CASE WITH THE SURGEON WE HAD A SCREW PLACED LATERALLY OF THE INTENDED PLANNED SCREW, THE SCREW THAT WAS PLACED LATERALLY WAS THE LEFT L3 SCREW. WE ALSO HAD SOME DIFFICULTY WITH MOTION ON THE MERGE, WHICH WAS SURPRISING BECAUSE THE PATIENT HAD PREVIOUSLY IMPLANTED HARDWARE WHICH USUALLY MAKES THE PROCESS EASIER. THE LATERALLY PLACED SCREW WAS BACKED OUT AND RE-DIRECTED MANUALLY WITHOUT THE ROBOT. NONE OF THIS CAUSED ANY ISSUES WITH THE PATIENT OR PROCEDURE. THE SURGEON HAS REQUESTED THAT THE CALIBRATION OF THE ROBOT BE CHECKED.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSIUS GPS SYSTEM, A SCREW WAS MISPLACED DURING A T11-L3 PERCFUSION CASE TODAY. THE SCREW WAS REMOVED, AND WE DID THE REST UNDER FLUORO WITHOUT THE ROBOT. EVERY INSTRUMENT HE PUT DOWN THE END EFFECTOR WAS SUPER OFF EVEN THE ANATOMY CHECKS WERE ACCURATE. IT COULD'VE BEEN A SCAN ISSUE WE DON'T KNOW.

Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: AN 82-YEAR-OLD FEMALE UNDERWENT PLANNED THORACIC PERCUTANEOUS INSTRUMENTATION FOR AN UNSTABLE T5 FRACTURE USING ROBOTIC NAVIGATION. DURING THE PROCEDURE, ROBOTIC REGISTRATION WAS PROLONGED AND TECHNICALLY CHALLENGING. DURING PEDICLE SCREW PLACEMENT, LOSS OF RESISTANCE WITH CSF RETURN WAS NOTED AND INSTRUMENTATION WAS STOPPED. SHORTLY THEREAFTER, NEUROMONITORING SIGNALS WERE LOST, AND THE PATIENT EXPERIENCED A PULSELESS ELECTRICAL ACTIVITY (PEA) ARREST WITH RAPID RETURN OF SPONTANEOUS CIRCULATION FOLLOWING BRIEF RESUSCITATION. POST-EVENT EVALUATION DEMONSTRATED ACUTE MYOCARDIAL DYSFUNCTION WITH PATENT CORONARY ARTERIES AND IMAGING FINDINGS CONCERNING FOR THORACIC SPINAL CORD INJURY RELATED TO A MEDIAL PEDICLE BREACH. THE FOLLOWING DAY, THE SERVICE RECEIVED AN URGENT MANUFACTURER SAFETY NOTICE REGARDING ROBOTIC NAVIGATION SOFTWARE ACCURACY.

Crash With

SUV

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Front Left

SV Precrash Speed (MPH)

7

CP Pre-Crash Movement

Making Right Turn

CP Contact Area

Front

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Intersection

Weather

Clear

Investigating Agency

None

Make

ZOOX

Model

Zoox

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

An occupied Zoox autonomous vehicle was traveling northeast on [XXX], passing through the intersection of [XXX] in Las Vegas, with a green signal, when an SUV (Vehicle 2) violated the Zoox vehicle's right of way and abruptly entered its travel path. The Zoox vehicle braked hard and attempted to veer left, but the right front fender of the Zoox vehicle made contact with the left front fender and bumper of Vehicle 2. The driver of Vehicle 2 briefly stopped and then drove away from the scene. The Zoox vehicle was found to have sustained minor damage. At the time of the incident, the passengers did not report any injuries, and police were not notified. On March 2, 2026, the passengers notified Zoox Support that they "sustained multiple injuries and have experienced persistent and worsening pain and cognitive symptoms since the impact".

Crash With

Passenger Car

SV Pre-Crash Movement

Changing Lanes

SV Contact Area

Left

SV Precrash Speed (MPH)

56

CP Pre-Crash Movement

Other, see Narrative

CP Contact Area

Front

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Highway / Freeway

Weather

Clear

Investigating Agency

Arizona Department of Public Safety

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On February [XXX], 2026 at 7:09 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane. A passenger car traveling northbound in the second to the left lane, in front of and to the left of the Waymo AV, began to slow and change lanes to the right when a second passenger car made contact with the rear right side of the first passenger car. The second passenger car continued forward and made contact with an SUV stopped in the queue of traffic in the second from the left lane. As a result of the initial contact with the second passenger car, the first passenger car was pushed east across two lanes of travel, and entered the Waymo AV's lane of travel. The Waymo AV slowed and maneuvered to the right to avoid the oncoming passenger car and the front left side of the passenger car made contact with the left side of the Waymo AV. The Waymo AV rotated to the left and came to rest facing southwest in the second and third from the left lanes. During two subsequent maneuvers in which the Waymo AV pulled forward and to the right in an attempt to navigate off the freeway, the front left corner of the Waymo AV made contact with an "Oversized Load" sign attached to a heavy truck stopped in the second from the left lane. At the time of all impacts, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All involved vehicles sustained damage. The driver of the first passenger car was transported to a hospital by an ambulance with unknown injuries, and the passenger of the Waymo AV alleged minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHEN DOING AN SI JOINT FUSION WITH OUR SURGEON, OUR MERGE SEEMED TO BE GOOD. HOWEVER, UPON STARTING THE FIRST SCREW, THE HIGHSPEED DRILL WAS NOTICEABLY DEEPER THAN ITS ACTUAL DEPTH. WE TRIED TO FIX IT AND WHEN STANDARD TROUBLE SHOOTING WAS DONE NOTHING CHANGED BUT THE SURGEON WANTED TO PROCEED. THE SCREW PLACED WAS POSTERIOR AND INFERIOR TO THE PLAN. WE DECIDED TO COMPLETELY REMERGE. SIMILAR SHOTS WERE TAKEN AND THE SCREWS WERE PLACED TO PLAN WITH NO DEPTH ISSUES.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSIUS GPS SYSTEM, PEDICLE SCREWS WERE NOT PLACED AS PLANNED WITH THE E3D INTRAOP EXCELSIUS CASE.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT THE SURVEILLANCE HAS BEEN UNABLE TO HOLD GREEN STATUS AND DRIFTS TO YELLOW AND RED CONSTANTLY FOR THE LAST SEVERAL WEEKS. TODAY ANOTHER SCREW WAS PLACED LATERAL TO THE PEDAL SIMILAR TO WHAT HAPPENED TWO WEEKS AGO ON THE SAME UNIT EXHIBITING THE SAME PROBLEMS. THIS HAPPENED ONE OTHER TIME A FEW WEEKS EARLIER. THE SURGEON REMOVED THE BREACHED SCREW AND REPLACED USING TRADITIONAL NON-ROBOTIC/NAVIGATED MANNER. THE SURGEON HAS PUT OVER A THOUSAND SCREWS IN WITH THE ROBOT AND THIS IS THE SECOND TIME THIS HAS HAPPENED IN THE LAST TWO WEEKS WITH THE SAME UNIT EXHIBITING THE SAME ISSUE.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE E3D TO PRE OP MERGE, NAVIGATION LOOKED CORRECT BUT UPON TAKING X-RAYS, NAVIGATION WAS OFF A SIGNIFICANTLY ANTERIORLY. THE DISC PREP THAT WAS DONE BASED OFF THE GPS NAVIGATION ON THE ROBOT RESULTED IN VIOLATING THE INFERIOR ENDPLATE OF THE SUPERIOR VERTEBRAL BODY, WHICH CAUSE THE SABLE CAGE TO SUBSIDE. ON THE NAVIGATION, THE CAGE LOOKED LIKE IT WAS WELL WITHIN THE DISC SPACE, BUT UNDER X-RAY IT WAS CLEARLY NOT. WE TRIED TO RE-PLACE THE CAGE BUT HAD THE SAME RESULT.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT IN AN EXCELSIUS GPS SURGERY, IT WAS NOTICED THAT AFTER TAKING X-RAYS IN THE OR FOR THE PRE OP CT WORKFLOW AND DOING THE MERGE, THE PLANNED SCREWS WERE TOTALLY WRONG IN THE X-RAY. WE TOOK THEM OUT TO BE NOT HASSITATED. WHEN WE PLACED THE FIDUCIALS INTO THE LATERAL VIEW VERTEBRA, THE AP ONES WERE COMPLETELY OFF AND NEEDED TO BE PLACED IN THE CENTRE. THEN WE HAD AN ANATOMICAL SHIFT IN LATERAL VIEW. WE COULD NOT CHOOSE ALL THE DIFFERENT VIEWS LIKE STANDARD OR STANDARD OPTIMIZED OR L2 SEED AUTOMATICALLY.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING AN EXCELSIUS GPS SURGERY THE ROBOT WOULD NOT START. IT TURNED ON, BUT THE SCREEN WAS BLACK. THIS HAPPENED TWICE. THE THIRD TIME IT STARTED WITHOUT ANY PROBLEMS. IT UNDOCKED ITSELF DURING THE OPERATION. WE DOCKED IT MANUALLY AND CONTINUED THE OPERATION. EVERYTHING WENT WELL. HOWEVER, AFTER THE INTRAOPERATIVE CT SCAN, 3 OUT OF 8 SCREWS WERE INCORRECTLY INSERTED. WE CLOSED THE CASE IN THE ROBOT AND STARTED A NEW ONE AS IF IT WERE A NEW OPERATION. WE DID A 3D SCAN AGAIN, PLANNED THE SCREWS AND INSERTED THEM. EVERYTHING WENT WELL AND AFTER THE CONTROL SCAN THE SCREWS WERE ALREADY INSERTED CORRECTLY. THE PATIENT DID NOT SUFFER ANY HARM.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A L1-L5 OPEN TLIF, USING INTEROP WORKFLOW WITH E3D. WE PLACED L1 LEFT SCREW FIRST. THEN CHECKED ALL SCREWS WITH FLUORO AFTER THEY WERE ALL PLACED AND BOTH L1 SCREWS WERE SHIFTED TO THE LEFT. WE THEN WENT IN TO FIX THEM AND DID ANOTHER SPIN, AND IT WAS STILL OFF. WE ENDED UP PLACING BOTH TOP SCREWS FREEHAND WITHOUT NAVIGATION.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSIUS GPS SYSTEM ROBOT-PLANNED SCREWS WERE NOT ACCURATE. THE PLAN AND MERGER LOOK FINE. I CAN MAIL OR TRANSFER THE FILE LOG FROM THE ROBOT.

VELYS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT THE SURGEON BELIEVED A DISTAL FEMUR FRACTURE MAY HAVE BEEN CAUSED BY BICORTICAL VELYS ARRAY PINS, WHICH CREATED A STRESS RISER. HE STATED THAT HE PLANNED TO PLACE PINS MORE DISTALLY AND UNICORTICALLY PER VELYS RAS STANDARD PIN PLACEMENT. ONE PATIENT WAS TREATED NONOPERATIVELY. ONE PATIENT WAS TREATED WITH A RETROGRADE NAIL. AS STATED IN THE REPORT, LOT NUMBERS WERE NOT AVAILABLE. PINS WERE DISCARDED AT THE CONCLUSION OF THE SURGERY. THE FRACTURES OCCURRED AT A LATER TIME. THERE WAS NO SIGNIFICANT DELAY. ALL AVAILABLE INFORMATION HAS BEEN DISCLOSED.

Crash With

Passenger Car

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Right

SV Precrash Speed (MPH)

15

CP Pre-Crash Movement

Parked

CP Contact Area

Left

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

San Francisco Police Department

Make

ZOOX

Model

Zoox

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

An occupied Zoox autonomous vehicle began to proceed on a fresh green traffic signal on westbound [XXX] at [XXX] when the driver of a stationary passenger vehicle (Vehicle 2), parallel-parked in the curb lane, rapidly opened the driver door into the path of the approaching Zoox vehicle. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The right side front fender, wheels, bodyside, and door panels made contact with the outside edge of the opening door of Vehicle 2. The Zoox vehicle came to an immediate stop and was later towed from the scene to be inspected for damage. First responders arrived at the scene. The passenger of the Zoox vehicle did not report any injuries. Later media stories reported the driver of Vehicle 2 had a "smashed hand" and his "hand was hurting, and that he was also experiencing pain to his neck area and lower back" based on a third party's account, and that the driver "declined their offer to take him to the hospital." Zoox vehicle camera footage shows clearly that no part of the robotaxi came into contact with the driver themselves, and that their hands, leg, and body did not interact with either the robotaxi or the parked vehicle's door at any moment during the contact event.

VELYS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: SURGEON BELIEVES FRACTURE OF A DISTAL FEMUR MAY HAVE BEEN CAUSED BY BICORTICAL VELYS ARRAY PINS CAUSING STRESS RISER. HE MENTIONED THAT HE WOULD PLAN TO PLACE PINS MORE DISTAL AND UNICORTICAL AS PER VELYS RAS STANDARD PIN PLACEMENT. ONE PATIENT TREATED NON OPERATIVELY, ONE PATIENT TREATED WITH RETROGRADE NAIL. NO OTHER INFORMATION CURRENTLY AVAILABLE, NO LOT NUMBERS ARE AVAILABLE. LIST ANY J&J PRODUCTS THAT WERE UTILIZED DURING THE CASE BUT DID NOT CONTRIBUTE TO THE REPORTED EVENT. J&J EQUIPMENT INCLUDED ALL INSTRUMENTS, IMPLANTS AND DISPOSABLE NECESSARY TO COMPLETE A CEMENTLESS ATTUNE PRIMARY KNEE WITH THE VELYS ROBOT. WAS THERE ANY REPORTED PATIENT OR USER HARM? UNKNOWN. WAS THERE A SIGNIFICANT DELAY? NO.

VELYS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: It was reported that the surgeon believes fracture of a distal femur may have been caused by bicortical VELYS array pins causing stress riser. He mentioned that he would plan to place pins more distal and unicortical as per VELYS RAS standard pin placement. One patient treated non operatively, one patient treated with retrograde nail.

Crash With

Passenger Car

SV Pre-Crash Movement

Stopped

SV Contact Area

Left

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Other, see Narrative

CP Contact Area

Front

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

Tempe Police Department

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On January [XXX], 2026 at 3:53 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west in the rightmost lane of [XXX] in a queue of traffic for a red light at the intersection with [XXX]. A passenger car, traveling eastbound in the leftmost westbound travel lane at a high rate of speed, entered the intersection against a red light, and made contact with the front left of a second passenger car traveling northbound on [XXX] through a green light. As a result of this contact, the airbags in both passenger cars deployed. The initial eastbound passenger car continued to exit the intersection after contact, proceeded towards the rightmost westbound lane on [XXX], and the front left of the passenger car made contact with the left side of the stationary Waymo AV, resulting in airbag deployment in the Waymo AV. After making contact with the Waymo AV, the passenger car continued eastbound and the left side of the passenger car then made contact with an additional Waymo AV (VIN [XXX]) that was stopped behind the initial Waymo AV in traffic. At the time of the impact, both Waymo AVs' Level 4 ADS were engaged in autonomous mode. The two passenger cars and the initial Waymo AV (VIN [XXX]) sustained damage. An occupant of the northbound passenger car was transported from the scene for medical treatment with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSIUS GPS SYSTEM THERE WAS AN ISSUE WHILE CONNECTED TO A DESIGNATED RED (EMERGENCY POWER) OUTLET, THE ROBOT UNEXPECTEDLY SHUT DOWN WITHOUT WARNING. AFTER ATTEMPTING TO POWER THE SYSTEM USING MULTIPLE OUTLETS THROUGHOUT THE HOSPITAL, WE WERE STILL UNABLE TO MAINTAIN POWER. THE PLUG INDICATOR LIGHT DOES NOT ILLUMINATE WHEN CONNECTED, AND THE BATTERY INDICATOR ONLY FLASHES. AS A RESULT, THE ROBOT CANNOT BE KEPT POWERED ON. WE WERE FORCED TO ABORT THE PROCEDURE AND CANCEL MULTIPLE SCHEDULED CASES OVER THE NEXT SEVERAL DAYS.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING AN EXCELSIUSGPS SURGERY A S2AI SCREW WAS PLACED MEDIAL AND INFERIOR. THE NAVIGATION IMAGES SHOWED THAT THE SCREW WAS ON PLAN AND IN THE PROPER PLACE HOWEVER THAT WAS NOT THE CASE. UPON X-RAY IMAGES TO CONFIRM, THE SURGEON NOTICED THAT THE SCREW WAS MEDIAL AND INFERIOR. THE SURGEON REMOVED THE SCREW AND REPLACED THE SCREW IN THE CORRECT SPOT WITHOUT TO USE OF THE ROBOT OR NAVIGATION.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A EGPS SURGERY THAT THE SCREW WAS FIGHTING US AS IT ADVANCED. WE DECIDED TO BACK OUT SCREW. THE SCREW WAS FIGHTING US. THERE WAS A STABILIZER FAILURE. THE SURGEON REMOVED POWER BLOCK AND USED T. WE STILL COULDN'T BACK OUT. WE NOTICED STAR TIP OF CUP DRIVER LODGED INTO THE FEMALE STAR OF SCREW. WE REMOVED ROBOT FROM FIELD. WE TOOK AN X-RAY AND THE L4 WAS LOW AND MEDIAL AND NOT IN THE PLANNED TRAJECTORY. THE SURGEON TESTED DRB RIGIDITY WITH FINGERS AND IT WAS COMPLETELY OUT OF BONE. THE SURGEON PROCEEDED TO REMOVE SCREW VIA DRILLING AROUND IT. THE SCREW WAS REMOVED. WE PROCEEDED WITH LAMI/DECOMPRESSION. WE PLACED SCREWS NON ROBOTICALLY POST DECOMPRESSION.

VELYS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT A PATIENT WITH A LIGHT OSTEOPOROSIS SUFFERED A FEMORAL FRACTURE 2.5 WEEKS AFTER A TOTAL KNEE ARTHROPLASTY PROCEDURE PERFORMED WITH THE VELYS ROBOTIC ASSISTED SURGERY SYSTEM; THE FRACTURE OCCURRED WHEN SHE STOOD UP FROM A SEATED POSITION, AND THE SURGEON SUSPECTED IT WAS CAUSED BY THE HOLES MADE BY THE VELYS ARRAY PINS. ALL AVAILABLE INFORMATION HAS BEEN DISCLOSED.

VELYS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT A PATIENT WITH A LIGHT OSTEOPOROSIS SUFFERED A FEMORAL FRACTURE 2.5 WEEKS AFTER A TOTAL KNEE ARTHROPLASTY PROCEDURE PERFORMED WITH THE VELYS ROBOTIC ASSISTED SURGERY SYSTEM; THE FRACTURE OCCURRED WHEN SHE STOOD UP FROM A SEATED POSITION, AND THE SURGEON SUSPECTED IT WAS CAUSED BY THE HOLES MADE BY THE VELYS ARRAY PINS. ALL AVAILABLE INFORMATION HAS BEEN DISCLOSED.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSIUS GPS SYSTEM, T10-L2 OPEN FUSION INSTRAOP MERGE WITH E3D, T10/T11/T12 WERE ALL MEDIAL/LATERAL MISSED SCREWS, T12 RIGHT AND LUMBAR SCREWS WERE PERFECT. T10 BILATERAL AND T11 RIGHT WERE REMOVED AND REPLACED AFTER THE SECOND E3D SPIN.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSIUS GPS SYSTEM, THERE WAS AN ISSUE WITH THE END EFFECTOR AND ACCURACY, AND THERE WAS ALSO AN ISSUE WITH REHOMING AFTER INITIAL ACCURACY CONCERNS. WE PLANNED LEVELS L4, L5, AND S1 BUT ONLY COMPLETED THE LEVELS L4, L5 DURING THE PROCEDURE. ALL 4 SCREWS WERE NOT PLACED AS PLANNED; THEY WERE ALL CONSIDERED LOWER THAN THE INITIAL PLAN THE SURGEON CREATED. THEN WE DID X-RAYS AND CONFIRMED THE SCREWS WERE OUT OF PLACEMENT. ROBOT WAS REMOVED FROM THE PROCEDURE ARE BUT STILL IN THE OR UNTIL THE CASE WAS COMPLETED.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT THERE WAS A RADIAL ERROR OF GREATER THAN 1.5MM AT MULTIPLE TRAJECTORIES. THE RIGHT OF ELECTRODE WAS REMOVED AND NO OTHER ELECTRODE WAS PLACED ALONG THIS PLANNED TRAJECTORY. NO FURTHER REVISION IS NEEDED.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE PLACING CRANIAL LEADS WITH THE EXCELSIUS GPS THE LEFT SIDE LEAD SHIFTED SUPERIOR AT THE VENTRICLE. THE SURGEON STATED THAT THE LEAD RAN ALONG THE SUPERIOR EDGE OF THE HIPPOCAMPUS BUT DECIDED TO PLACE THE LEAD AGAIN. THE EGPS WAS PUSHED BACK IN AFTER LMCS VERIFIED CONTINUED ACCURACY. THE EGPS ARM WAS ALIGNED TO THE LEFT TRAJECTORY AND THE PROCESS REPEATED. THE O-ARM WAS BROUGHT BACK IN AND THE SPIN WAS PERFORMED AND TRANSFERRED. THE LEAD WAS FOUND TO HAVE HIT THE VENTRICLE AND SHIFTED SUPERIOR AGAIN BUT WAS INFERIOR TO THE PREVIOUS LEAD PLACEMENT AND WAS THUS MORE ON TRAJECTORY. THE SURGEON WAS SATISFIED WITH THE PLACEMENT AND CLOSING BEGAN.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING AN EXCELSIUSGPS SURGERY THE FIRST SCREW LOOKED TO PLAN. THE SECOND SCREW, L4R, LOOKED LIKE IT WAS TO PLAN, BUT THE OFFSET WAS RED, AND DOC WAS WORRIED. THERE WERE NO NAV SHIFTS AFTER LANDMARK CHECK. HE DIDN'T LIKE, CAME BACK IN WITH DURA PRO, PUT IN SCREW AGAIN, BUT THIS TIME WAS LATERAL. HE DID A LANDMARK CHECK, EVERYTHING ACCURATE. HE DID THE SCREW FREEHAND NAV, WHICH WAS TO PLAN. THE L4L SCREW OFFSET WAS RED, AND SCREW LOOKED LATERAL, BUT DOC SAID THAT IT FELT GOOD TO HIM AND DURA PRO WAS GREEN AND RIGHT ON TRAJECTORY. THE SCREW WAS LATERAL. IT WAS POSSIBLY LATERAL DUE TO RETRACTOR, OR PATIENT MOVEMENT. THE DR. TOOK OUT SCREW, AND REPLACED SCREW FREEHAND WITHOUT NAVIGATION USING FLOUROSCOPY. ALL SCREWS TO PLAN AT END.

Crash With

Passenger Car

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Rear Right

SV Precrash Speed (MPH)

2

CP Pre-Crash Movement

Proceeding Straight

CP Contact Area

Front Right

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Cloudy, Rain

Investigating Agency

Los Angeles Police Department

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On November [XXX], 2025 at 4:52 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northeastbound on [XXX], with its right turn signal activated, when it slowed to a stop for a stop sign at the intersection with [XXX]. The Waymo AV proceeded forward slowly as it was yielding to vehicles traveling southeastbound on [XXX] and preparing to turn right onto [XXX]. While the Waymo was proceeding forward, a passenger car traveling northeastbound on [XXX] approached the Waymo AV from behind and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV was not belted at the time of the collision. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Passenger Car

SV Pre-Crash Movement

Stopped

SV Contact Area

Rear Right

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Proceeding Straight

CP Contact Area

Front Right

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Intersection

Weather

Clear

Investigating Agency

San Francisco Police Department

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On November [XXX], 2025 at 10:09 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in the right lane on [XXX], southwestbound for a red light at the intersection with [XXX]. While the Waymo AV remained stopped, a passenger car that was initially stopped directly behind the Waymo AV proceeded forward, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Neither vehicle sustained damage. The driver of the passenger car was transported from the scene to a hospital with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.