Crash With

Passenger Car

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Front

SV Precrash Speed (MPH)

17

CP Pre-Crash Movement

Making Right Turn

CP Contact Area

Rear Left

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Intersection

Weather

Cloudy

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 September [XXX], 2025 at 11:22 AM 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 in the right lane on [XXX] with its right turn signal activated in preparation to make a right turn onto [XXX]. As the Waymo AV approached the intersection at [XXX] while it was in the right half of the right lane, a passenger car traveling northeastbound in the left half of the right lane in front of the Waymo AV entered the intersection and slowed. The passenger car initiated a sudden right turn without activating its turn signal, crossing in front of the path of the Waymo AV. The AV braked with significant force, but the rear right side of the passenger car 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. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Passenger Car

Highest Injury Severity Alleged

Property Damage. No Injured Reported

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

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 September [XXX], 2025 at 3:48 PM 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 on [XXX] with its right turn signal activated in a queue of traffic for a red light at the intersection with [XXX]. After an SUV directly in front of the Waymo AV turned right onto [XXX], the Waymo AV briefly proceeded forward and then stopped for the red light. While the Waymo AV was stopped to yield to the red light and northbound traffic, a passenger car that was initially stopped behind the Waymo AV proceeded forward and the front of the passenger car made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Non-Motorist: Cyclist

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Stopped

SV Contact Area

Right

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

NM Moving Alongside Roadway

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

None

Make

TESLA

Model

Model Y

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.

Summary: This updated report does not report a new incident or make any material changes to the factual record. It only removes confidential or personally identifying information to make the incident narrative publicly available. The Tesla ADS was stopped in a straight through lane with other vehicles stopped at a red light. A pedicab, approaching from behind in the bike lane on the right, made contact with the right side mirror of the stopped ADS as it rode by. Safety monitor was present and no passengers were inside the vehicle.

Crash With

SUV

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Stopped

SV Contact Area

Front

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Crossing into Opposing Lane

CP Contact Area

Front

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Cloudy

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 September [XXX], 2025 at 9:50 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing southeast on [XXX] for a queue of traffic ahead. While the Waymo AV remained stopped, an SUV that was stopped at the curb on the north side of [XXX] with its hazard lights activated maneuvered out of its parking spot and proceeded northwestbound on [XXX]. As the SUV approached the Waymo AV, still with its hazard lights activated, it crossed the center double yellow line and the front left of the SUV made contact with the front left of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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.

Crash With

Animal

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Front Right

SV Precrash Speed (MPH)

26

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 September [XXX], 2025 at 11:34 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a domestic animal on [XXX] near [XXX]. The Waymo AV was traveling eastbound on a narrow portion of [XXX] with vehicles parked at the curb in both directions. A domestic animal emerged from behind a vehicle that was parked on the north side of [XXX] and entered the Waymo AV's lane of travel, and the front of the Waymo AV made contact with the domestic animal, which appears to be a cat. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The domestic animal sustained injuries. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Animal

Highest Injury Severity Alleged

No Injured Reported

SV Pre-Crash Movement

Stopped

SV Contact Area

Front Left

SV Precrash Speed (MPH)

27

CP Pre-Crash Movement

NM Crossing Roadway

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Intersection

Weather

Partly Cloudy

Investigating Agency

None

Make

TESLA

Model

Model Y

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.

Summary: This updated report does not report a new incident or make any material changes to the factual record. It only removes confidential or personally identifying information to make the incident narrative publicly available. The Tesla ADS was proceeding straight in the center lane of the three lane street. As the Tesla ADS was approaching a green light at an intersection, a dog perpendicular to the Tesla vehicle is seen running into the intersection from the right. The Tesla ADS reduced vehicle speed and steered to the left. The dog proceeded to run onto the main road and toward the Tesla ADS's lane and path. The Tesla ADS continued to reduce vehicle speed and biased left in lane. The dog ran toward the Tesla and made contact with the bottom of the Tesla ADS's front right bumper which caused the dog to be pushed to the right, into the lane and path of an approaching van. As the Tesla ADS continued to proceed forward, the dog appeared behind the van and was seen running away from the street, only to turn around and run back toward the street. Safety monitor was present and no passengers were inside the vehicle.

Crash With

Heavy Truck

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Stopped

SV Contact Area

Rear

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Passing

CP Contact Area

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 September [XXX], 2025 at 1:08 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling southbound on a narrow portion of [XXX] with vehicles parked at the curb in both directions when it slowed to a stop to yield to a heavy truck traveling northbound on [XXX]. As the heavy truck passed the stationary Waymo AV, the left side of the heavy truck trailer 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. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Passenger Car

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Stopped

SV Contact Area

Rear

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Proceeding Straight

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 September [XXX], 2025 at 10:35 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in South San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] when it came to a stop behind a heavy truck that was parked in-lane, yielding to oncoming northbound traffic before passing the heavy truck. After traffic cleared, the Waymo AV began to maneuver around the heavy truck, but stopped as a forklift operating at the rear of the heavy truck and to the right of the Waymo AV began to move. A passenger car that was traveling directly behind the Waymo AV approached the Waymo AV from behind and the front right of the passenger car made contact with the rear left of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passenger car sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Animal

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Front Left

SV Precrash Speed (MPH)

16

CP Pre-Crash Movement

Entering Traffic

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 September [XXX], 2025 at 2:45 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a domestic animal on [XXX] near [XXX]. The Waymo AV was traveling northwestbound on a narrow portion of [XXX] with vehicles parked at the curb in both directions when a domestic animal emerged from in front of a parked vehicle and entered the Waymo AV's lane of travel. The front right tire of the Waymo AV made contact with the domestic animal. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The domestic animal sustained injuries. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Pickup Truck

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Right

SV Precrash Speed (MPH)

17

CP Pre-Crash Movement

Backing

CP Contact Area

Rear

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Intersection

Weather

Clear

Investigating Agency

Atlanta 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 September [XXX], 2025 at 8:01 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling westbound in the left lane on [XXX]. A pickup truck that was traveling eastbound in the left turn lane on [XXX] initiated a U-turn onto westbound [XXX] at the intersection with [XXX]. As the pickup truck was completing its U-turn, it stopped facing northwest in the right lane on [XXX], unable to complete the turn due to the north side sidewalk. As the Waymo AV continued through the intersection with [XXX] and began to passed the pickup truck, the pickup truck began to reverse into the Waymo AV's lane of travel and the rear left side of the pickup truck made contact with the front right 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. 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.

Crash With

SUV

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Making Left Turn

SV Contact Area

Left, Right

SV Precrash Speed (MPH)

14

CP Pre-Crash Movement

Proceeding Straight

CP Contact Area

Right

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Intersection

Weather

Clear

Investigating Agency

Austin 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 September [XXX], 2025 at 6:41 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northwestbound on [XXX] with its left turn signal activated in the second from the left lane, which is a designated left turn and through lane. An SUV was traveling northwestbound in the adjacent leftmost lane, which is a designated left turn-only lane. As the Waymo AV and the SUV entered the intersection at [XXX], the Waymo AV began to turn left and the SUV in the left turn-only lane continued to proceed forward without turning left. The right side of the SUV made contact with the left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. 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.

da Vinci Surgical 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 A DA VINCI-ASSISTED VENTRAL HERNIA REPAIR PROCEDURE, THE MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY THAT WAS INSTALLED ON AN MCS INSTRUMENT FELL OFF INSIDE THE PATIENT. THE MCS TIP COVER ACCESSORY WAS INSPECTED PRIOR TO USE AND NO ABNORMALITIES WERE REPORTED. THE TIP COVER FELL INSIDE THE PATIENT DURING A DISSECTION, AND THE CAUSE OF ITS DETACHMENT IS UNKNOWN. IT HAD BEEN IN USE FOR 20 TO 30 MINUTES BEFORE THE INCIDENT, WITH NO ISSUES NOTICED IN THE SCISSORS' FUNCTIONALITY. THE TIP COVER APPEARED TO BE PROPERLY INSTALLED DURING THE PROCEDURE, WITH NO PART OF THE ORANGE SURFACE VISIBLE AFTER INSTALLATION, AND THE INSTALLATION TOOL WAS USED. NO ELECTROLUBE OR OTHER LUBRICANT WAS APPLIED TO THE MCS INSTRUMENT BEFORE INSTALLING THE TIP COVER, AND NO REDUCER WAS USED. THERE WAS NO COLLISION WITH OTHER INSTRUMENTS OR HARD MATERIALS DURING THE PROCEDURE. DURING REMOVAL OF THE MCS INSTRUMENT THROUGH THE CANNULA, NO RESISTANCE WAS FELT. THE SURGICAL STAFF DID NOT NOTICE ANY DAMAGE TO THE CANNULA OR ANY OTHER DAMAGE TO THE MCS INSTRUMENT AFTER THE INCIDENT. THE MCS TIP COVER ACCESSORY WAS RETRIEVED FOLLOWING A CONVERSION OF THE CASE TO A LAPAROTOMY. THE P

Crash With

SUV

Highest Injury Severity Alleged

Property Damage. No Injured Reported

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

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 September [XXX], 2025 at 7:37 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing west in the left turn lane on [XXX] for a red light at the intersection at [XXX], preparing to make a protected left turn. While the Waymo AV remained stopped, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Non-Motorist: Cyclist

Highest Injury Severity Alleged

Minor W/ Hospitalization

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Rear

SV Precrash Speed (MPH)

19

CP Pre-Crash Movement

Entering Traffic

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

Atlanta 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 September [XXX], 2025 at 2:56 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a cyclist on [XXX] near [XXX]. A Waymo AV was traveling north on [XXX] near the intersection with the [XXX] when it approached the [XXX] shared use bicycle/pedestrian trail. As the AV approached the crossing with the trail, a cyclist traveling east on the trail approached the crossing with the roadway and continued into the roadway without stopping at the stop sign controlling bicycle traffic from the trail. The bicycle then made contact with the rear driver side of the Waymo AV and the impact caused the cyclist to fall from their bicycle. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV and the bicycle sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and 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

Heavy Truck

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Entering Traffic

SV Contact Area

Front

SV Precrash Speed (MPH)

2

CP Pre-Crash Movement

Parked

CP Contact Area

Rear Left

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Cloudy

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 September [XXX], 2025 at 10:57 AM PT a Waymo Autonomous Vehicle ("Waymo AV" operating in San Francisco, California was in a collision involving the loading ramp of a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped at the curb facing northwest on [XXX] for a passenger drop-off behind a heavy truck parked at the curb with its attached rear loading ramp lowered and hazard lights activated. After the drop-off was completed, the Waymo AV proceeded to maneuver around the right side of the heavy truck and enter the leftmost lane, and the front left side of the Waymo AV made contact with the rear right corner of the loading ramp of the heavy truck. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. 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.

Crash With

SUV

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Stopped

SV Contact Area

Front Right

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Backing

CP Contact Area

Rear Right

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 September [XXX], 2025 at 4:51 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in a queue of traffic facing northwest in the left lane on [XXX] for the red light at the intersection with [XXX]. An SUV that was stopped directly in front of the Waymo AV activated its hazard lights. The SUV then reversed and the rear of the SUV made contact with the front of the stationary Waymo AV. The driver and passenger of the SUV then exited their vehicle and at 4:54 AM the passenger of the SUV tore off the Waymo AV's right side mirror. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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.

Crash With

Motorcycle

Highest Injury Severity Alleged

Fatality

SV Pre-Crash Movement

Making Right Turn

SV Contact Area

Rear

SV Precrash Speed (MPH)

8

CP Pre-Crash Movement

Proceeding Straight

CP Contact Area

Front Left, Front Right

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 September [XXX], 2025 at 1:21 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was traveling north in the rightmost lane on [XXX] and began slowing with its right turn signal activated in preparation for a right turn into a parking lot at [XXX], yielding to a pedestrian crossing the driveway entrance to the parking lot on the right-hand sidewalk. While the Waymo AV was slowing with its right turn signal activated, a motorcycle in the rightmost lane approached the Waymo AV from behind and the front of the motorcycle made contact with the rear left corner of the Waymo AV. The impact with the Waymo AV resulted in the motorcyclist falling from the motorcycle and into the roadway to the left of the Waymo AV. Immediately afterwards, a passenger car in the second-from-the-rightmost lane passed the Waymo AV on the left and struck the motorcyclist in the roadway. The passenger car did not stop and left the scene. The motorcyclist was transported from the scene to a hospital, where they were declared deceased. At the time of impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and the Waymo AV was not carrying passengers. Following contact with the motorcycle, the Waymo AV came to a complete stop and remained stopped until the vehicle was towed away several hours later. The Waymo AV and the motorcycle sustained damage. The extent of the damage to the passenger car that left the scene is unknown at this time. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because of a fatality. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Heavy Truck

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Rear, Top

SV Precrash Speed (MPH)

1

CP Pre-Crash Movement

Making Left 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 unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling northeast on a green traffic light on [XXX] at [XXX] in San Francisco. At that time, a box truck (Vehicle 2), heading southwest on [XXX], suddenly attempted an unprotected left turn onto [XXX]. The Zoox vehicle braked hard to yield to the rapidly approaching Vehicle 2, when the left side mirror assembly of Vehicle 2 made contact with the roof-mounted left rear sensor pod of the Zoox vehicle. The Zoox vehicle stopped after the contact, and the Vehicle 2 operator completed the turn onto [XXX] and pulled over. Shortly afterward, the Zoox vehicle cleared the intersection, pulled over, and then returned to base. The Zoox vehicle sustained sensor damage, and no injuries were reported.

Crash With

SUV

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Left

SV Precrash Speed (MPH)

20

CP Pre-Crash Movement

Making Left Turn

CP Contact Area

Front

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Intersection

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 September [XXX], 2025 at 6:59 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing northwest on [XXX] for a red light at the intersection at [XXX], while an SUV was stopped facing southeast on [XXX] with its left turn signal activated. When the light turned green, the Waymo AV proceeded forward into the intersection. The SUV then began an unprotected left turn onto northeastbound [XXX], and the front left of the SUV made contact with the 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. 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.

Crash With

Other Fixed Object

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Making Left Turn

SV Contact Area

Front Right

SV Precrash Speed (MPH)

6

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Parking Lot

Weather

Partly Cloudy

Investigating Agency

None

Make

TESLA

Model

Model Y

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.

Summary: This updated report does not report a new incident or make any material changes to the factual record. It only removes confidential or personally identifying information to make the incident narrative publicly available. The Tesla ADS was stopped in the bi-directional turn lane (or center left turn lane) of a five lane road with its left indicator active. When the two lanes of oncoming traffic were clear, the ADS made an unprotected left turn into an entrance of a parking lot. As the ADS entered the parking lot, the ADS made contact with a metal chain. The ADS had a safety monitor present with one passenger in the vehicle. On 03/20/2026, while submitting this report and removing confidential or personally identifying information, the report was submitted in error indicating airbag deployment and tow for the subject vehicle. This is in error and the reports were updated to reflect that no airbags were deployed and no tow of the Tesla vehicle was conducted.

da Vinci Surgical 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 A DA VINCI-ASSISTED SURGICAL PROCEDURE, AN ENDOSCOPE PLUS STOPPED WORKING AND A FRAGMENT FELL INSIDE THE PATIENT. IT IS UNKNOWN IF THE FRAGMENT WAS RETRIEVED. THE PROCEDURE WAS COMPLETED ROBOTICALLY.

da Vinci Surgical 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 A DA VINCI-ASSISTED SURGICAL PROCEDURE, THE SURGEON SIDE CONSOLE (SSC) WENT BLACK ON BOTH THE VIEWER AND THE TOUCHPAD. THE CUSTOMER CONTACTED AN INTUITIVE SURGICAL, INC. (ISI) TECHNICAL SUPPORT ENGINEER (TSE) FOR ASSISTANCE. TROUBLESHOOTING FIRST CONSISTED OF CHECKING THE SYSTEM LOGS, WHICH SHOWED THE SSC WAS NOT CONNECTED TO THE VISION SIDE CART (VSC). THE TSE INSTRUCTED THE CUSTOMER TO SHUT DOWN THE SYSTEM, CLEAN THE BLUE FIBER CABLE AT BOTH THE SSC AND VSC, AND RESTART. DESPITE THESE EFFORTS, THE SSC REMAINED DISCONNECTED ACCORDING TO THE VSC, WITH THE POWER BUTTON BLINKING BLUE AND NO DISPLAY ON THE SCREENS, THOUGH FAN NOISE REMAINED PRESENT. ATTEMPTS TO START IN STAND-ALONE MODE DID NOT RESTORE FUNCTION. THE SURGEON THEN ELECTED TO ABORT THE PROCEDURE.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: During dissection along the superior border of the left renal vein, a minor arterial bleed was encountered. Initial maneuvers with monopolar and bipolar energy were attempted but unsuccessful. Direct pressure was easily able to achieve hemostasis while a suture was prepared. Post procedure, the patient recovered uneventfully. The robotic-assisted procedure led to complete resection with an uncomplicated hospital course, and discharge home on postoperative day one.Intuitive Surgical Inc. (ISI) has made multiple attempts to obtain additional information; however, as of the date of this report, no new information has been obtained.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: This clinical study article reviewed a total of 44 adult patients who underwent robotic completion cholecystectomy (CC) between August 2020 and March 2025. The article noted the following: One patient with a retained common bile duct stone requiring a postoperative ERCP, one patient with a perihepatic collection treated with antibiotics, and one patient with a wound infection.It was concluded that robotic CC is a safe and technically feasible approach with high success and low complication rates.Intuitive Surgical Inc. (ISI) has made multiple attempts to obtain additional information; however, as of the date of this report, no new information has been obtained.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: MEDTRONIC RECEIVED INFORMATION REGARDING A GUIDANCE SYSTEM. IT WAS REPORTED THAT THERE WAS INACCURATE REFERENCE, WHICH LED TO PATIENT HARM.

Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: MEDTRONIC RECEIVED INFORMATION REGARDING A GUIDANCE SYSTEM. IT WAS REPORTED THAT THERE WAS INACCURATE REFERENCE, WHICH LED TO PATIENT HARM.

da Vinci Surgical 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 A DA VINCI-ASSISTED SURGICAL PROCEDURE, THE ACCESS PORT'S RUBBER LINING FELL OFF DURING INTRODUCTION OF A LAPAROSCOPIC STAPLER. THE FRAGMENTS DID NOT FALL INSIDE OF THE PATIENT DURING AN INSTRUMENT TIP/ACCESSORY COLLISION. THE FRAGMENT WAS RETRIEVED DURING THE SAME PROCEDURE. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE ACCESSORY WAS INSPECTED PRIOR TO USE, AND NO DAMAGE WAS NOTED. THE SURGICAL TASK PERFORMED AT THE DEVICE BREAKAGE WAS INSERTION OF LAPAROSCOPIC STAPLER. IT IS UNKNOWN WHAT THE SURGEON BELIEVED WAS THE CAUSE OF THE ACCESSORY BREAKAGE. THE ACCESSORY WAS IN USE FOR LESS THAN AN HOUR WHEN THE ISSUE OCCURRED. THE SURGEON DIDN'T NOTICE ANY ISSUES WITH THE FUNCTIONALITY OF THE ACCESSORY. THE INSTRUMENT DID NOT COLLIDE WITH ANY OTHER INSTRUMENTS OR OTHER HARD MATERIAL DURING THE PROCEDURE. THE FRAGMENT DIDN'T FALL INTO THE PATIENT DURING AN INSTRUMENT TIP, OR ACCESSORY COLLISION. THE INSTRUMENT WAS NOT REMOVED DURING THE PROCEDURE PRIOR TO THE BREAKAGE. THE SURGICAL STAFF DIDN'T FEEL ANY RESISTANCE UPON REMOVING THE INSTRUMENT THROUGH THE C

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

da Vinci Surgical 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 A SINGLE PORT (SP) DA VINCI-ASSISTED NIPPLE-SPARING MASTECTOMY (NSM) SURGICAL PROCEDURE, THERE WAS A CONVERSION BACK TO OPEN (THE PROCEDURE HAD BEGUN OPEN) TO ADDRESS EXCESSIVE BLEEDING AT THE MEDIAL EDGE OF THE BREAST DUE TO PATIENT ANATOMY AND FOR USER EFFICIENCY. THIS CONVERSION WAS ALREADY ANTICIPATED AS A FEASIBLE AND EXPECTED ALTERNATIVE. THE PROCEDURE WAS DESIGNED TO COMBINE BOTH OPEN AND ROBOTIC TECHNIQUES. THE EXACT AMOUNT OF BLOOD LOST IS UNKNOWN, BUT INTERVENTIONS TO CONTROL THE BLEEDING INCLUDED THE USE OF FLOSEAL, BIPOLAR COAGULATION WITH SP FENESTRATED BIPOLAR, AND LIGASURE DURING THE OPEN PROCEDURE. NO BLOOD TRANSFUSIONS WERE ADMINISTERED.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A PATIENT IN A STUDY UNDERWENT A DA VINCI-ASSISTED BILATERAL NIPPLE SPARING MASTECTOMY (NSM). AT THE 42-DAY FOLLOW-UP, A NEUROPATHY WAS REPORTED. THE EVENT ONSET DATE HAS BEEN REPORTED AS POST-OPERATIVE DAY #14. THE NEUROPATHY WAS LOCATED BILATERALLY, IN THE RIGHT AND LEFT BREASTS. THE NEUROPATHY PAIN WAS IDENTIFIED BY THE PATIENT AND REPORTED TO THE PLASTICS TEAM THAT SHE WAS UNABLE TO GET AHEAD OF THE PAIN IN HER BREASTS AND ASKED FOR RELIEF. IT WAS DESCRIBED AS "PERSISTENT, SEARING PAIN LOCALIZED TO THE BREAST AREA ABOVE THE NIPPLE AND INCISION LINE, WHICH WORSENS WITH ACTIVITY. THE PAIN IS CONSTANT, NON-RADIATING, AND NOT ASSOCIATED WITH INCISIONAL SITES. THE SKIN IS NUMB, AND ACTIVITIES SUCH AS WALKING OR CAR RIDES EXACERBATE THE PAIN. THE PAIN DOES NOT RADIATE AROUND THE CHEST WALL, ARMS, OR LEGS." THE TISSUE EXPANDERS WERE REPORTED AS UNCOMFORTABLE BUT NOT ATTRIBUTED TO THE CURRENT PAIN. TREATMENT CONSISTED OF REFERRAL TO A PAIN CLINIC AND PRESCRIPTIONS FOR IBUPROFEN, TYLENOL, DICLOFENAC AND GABAPENTIN. A BILATERAL PECS I/II BLOCK IN-CLINIC PROCEDURE WAS SCHEDULED; HOWEVER, THE PATIENT INDICATED THAT THE PRESCRIBED MEDICATIONS HAD RELIEVED THE PAIN AND CANCELED THE NERVE BLO

da Vinci Surgical 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 A DA VINCI-ASSISTED BILATERAL NIPPLE-SPARING MASTECTOMY PROCEDURE, THE INTEGRATED ELECTROSURGICAL UNIT (IESU) GENERATOR DISPLAYED MONOPOLAR ENERGY SHIELD ERRORS. DESPITE REPLACING THE MONOPOLAR CABLE AND GROUNDING PAD, THE ERROR MESSAGES PERSISTED. THE IESU ALSO FAILED WHEN USED WITH A HANDHELD BOVIE PEN. AN INTUITIVE SURGICAL, INC. (ISI) TECHNICAL SUPPORT ENGINEER (TSE) WAS CONSULTED AND RECOMMENDED A HARD RESTART OF THE DEVICE; HOWEVER, THE ERRORS CONTINUED. WITH NO BACKUP IESU AVAILABLE AT THE FACILITY, THE SURGEON DECIDED TO CONVERT THE CASE TO OPEN SURGERY.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A REVIEW OF AN ARTICLE THAT EVALUATED THE PERIOPERATIVE, ONCOLOGIC, AND FUNCTIONAL OUTCOMES OF PATIENTS WITH RECURRENT OROPHARYNGEAL SQUAMOUS CELL CARCINOMA TREATED WITH TRANSORAL ROBOTIC SURGERY (TORS) AND SUBMENTAL FLAP RECONSTRUCTION WAS PERFORMED. THE STUDY RETROSPECTIVE COHORT DESIGN ANALYZED 8 PATIENTS UNDERGOING SALVAGE TRANSORAL ROBOTIC SURGERY (TORS) WITH SUBMENTAL ISLAND FLAP RECONSTRUCTION BETWEEN DECEMBER 2019 AND FEBRUARY 2024. TWO PATIENTS WERE READMITTED TO THE HOSPITAL POSTOPERATIVELY, ONE WITH FAILURE TO THRIVE AND DEHYDRATION 6 DAYS AFTER DISCHARGE, AND THE OTHER DUE TO ALTERED MENTAL STATUS 8 DAYS AFTER DISCHARGE. ONE PATIENT HAD A NECK HEMATOMA DURING THEIR HOSPITAL ADMISSION ON POSTOPERATIVE DAY 1 THAT NECESSITATED INCISION AND DRAINAGE. PER THE AUTHOR, NO COMPLICATIONS WERE RELATED TO THE ISI DEVICE.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome.

da Vinci Surgical 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 A DA VINCI-ASSISTED DISTAL SUBTOTAL GASTRECTOMY SURGICAL PROCEDURE, THERE WAS NO OCCURRENCE OF INSTRUMENT COLLISION, BUT THE METAL SHEET OF THE HARMONIC ACE CUTTER HEAD BROKE. THE BROKEN FRAGMENTS WERE REMOVED FROM THE PATIENT'S BODY, CAUSING NO DAMAGE TO THE PATIENT. THE SUBSEQUENT SURGERY WAS COMPLETED USING A NEW INSTRUMENT. THE PROCEDURE WAS COMPLETED.

da Vinci Surgical 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 A DA VINCI-ASSISTED SUBTOTAL GASTRECTOMY SURGICAL PROCEDURE, THE FRONT END OF THE HARMONIC ACE INSTRUMENT WAS FRACTURED. THE FRACTURED PART WAS COMPLETELY REMOVED, AND NO FRAGMENT REMAINED IN THE PATIENT. THE PROCEDURE WAS COMPLETED.

da Vinci Surgical 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 A DA VINCI-ASSISTED SUBTOTAL GASTRECTOMY PROCEDURE, THE FRONT END OF THE HARMONIC ACE INSTRUMENT FRACTURED AND A FRAGMENT FELL INSIDE THE PATIENT. THE PROCEDURE WAS COMPLETED ROBOTICALLY USING A BACKUP HARMONIC ACE INSTRUMENT.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A PATIENT IN A STUDY UNDERWENT A DA VINCI-ASSISTED MALIGNANT NIPPLE SPARING RIGHT BREAST SUBCUTANEOUS MASTECTOMY WITH CONCURRENT AXILLARY SENTINEL LYMPH NODE BIOPSY AND BREAST RECONSTRUCTION. TWO DAYS LATER, IT WAS REPORTED THAT THE PATIENT WAS EXPERIENCING POST-OPERATIVE ABNORMAL FLUID DRAINAGE, DESCRIBED AS SANGUINEOUS BLEEDING. ON THE 1ST, 2ND, AND 3RD POST-OPERATIVE DAYS, THE VOLUME OF RED OR LIGHT RED DRAINAGE FLUID WAS 130 ML, 60 ML, AND 115 ML, RESPECTIVELY. THE PATIENT RECEIVED AN INJECTION OF BATROXOBIN (A DEFIBRONGENATING AGENT) AS TREATMENT. THE EVENT WAS REPORTED AS RESOLVED THE SAME DAY AND THE PATIENT WAS DISCHARGED ON POST-OPERATIVE DAY EIGHT. THERE WAS NO REPORT OF A DA VINCI DEVICE MALFUNCTION DURING THE PROCEDURE. THE STUDY INVESTIGATOR THOUGHT THAT THE ADVERSE EVENT IS CERTAINLY NOT RELATED TO THE DA VINCI INVESTIGATIONAL MEDICAL DEVICES.

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 A L4 ACCURACY ISSUE WITH PLACEMENT OF THE SCREW. THE SCREW WAS REMOVED AND REPLACED.

Monarch Platform — 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 MONARCH BRONCHOSCOPY PROCEDURE, THE PHYSICIAN ENCOUNTERED NAVIGATION ISSUES AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT

da Vinci Surgical 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 A DA VINCI-ASSISTED PANCREATODUODENECTOMY PROCEDURE, THE FRONT END OF THE HARMONIC ACE INSTRUMENT FRACTURED AND A FRAGMENT FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED DURING THE SAME SURGICAL PROCEDURE. THE CUSTOMER USED A BACKUP HARMONIC ACE INSTRUMENT TO COMPLETE THE PROCEDURE ROBOTICALLY.

da Vinci Surgical 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 A DA VINCI-ASSISTED PANCREATODUODENECTOMY PROCEDURE, THE FRONT END OF THE HARMONIC ACE INSTRUMENT FRACTURED AND A FRAGMENT FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED DURING THE SAME SURGICAL PROCEDURE. A BACKUP HARMONIC ACE INSTRUMENT WAS USED TO COMPLETE THE PROCEDURE ROBOTICALLY.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

da Vinci Surgical 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 A DA VINCI-ASSISTED PANCREATODUODENECTOMY PROCEDURE, THE FRONT END OF THE HARMONIC ACE INSTRUMENT FRACTURED AND FRAGMENT FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED DURING THE SAME SURGICAL PROCEDURE. A BACKUP HARMONIC ACE INSTRUMENT WAS USED TO COMPLETE THE PROCEDURE ROBOTICALLY.

da Vinci Surgical 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 A DA VINCI-ASSISTED NEPHRECTOMY SURGICAL PROCEDURE; THE MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY FELL IN THE PATIENT. THE TIP COVER WAS RETRIEVED DURING THE SAME PROCEDURE. THERE WAS NO ADDITIONAL HARM TO THE PATIENT. THE TIP COVER IS NOT AVAILABLE FOR RETURN. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE MCS INSTRUMENT AND THE MCS TIP COVER ACCESSORY WERE INSPECTED PRIOR TO USE NO DAMAGE WAS OBSERVED. THE MCS TIP COVER ACCESSORY WAS OBTAINED DURING STERILIZATION PROCESS (IT WAS NOT PREVIOUSLY REPROCESSED). THE FRAGMENT FELL INSIDE OF THE PATIENT DURING THE INSTRUMENT REMOVAL THROUGH THE TROCAR. THE SURGEON BELIEVES THERE WAS FRICTION BETWEEN THE CUFF OF THE SCISSORS AND THE TROCAR. THE INSTRUMENT WAS USED THE ENTIRE PROCEDURE FOR APPROXIMATELY 3.5 HOURS. THE SURGEON DID NOT NOTICE ANY ISSUES WITH THE FUNCTIONALITY OF THE INSTRUMENT. THE INSTRUMENT DID NOT COLLIDE WITH ANY OTHER INSTRUMENT DURING THE SURGICAL PROCEDURE. THE MCS TIP COVER WAS PROPERLY INSTALLED BY AN EXPERIENCED OPERATING ROOM NURSE. NO ORANGE SURFACE WAS VISIBLE AFTER THE

da Vinci Surgical 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 A DA VINCI-ASSISTED PANCREATODUODENECTOMY SURGICAL PROCEDURE, THE FRONT END OF THE HARMONIC ACE INSTRUMENT WAS FRACTURED. IT WAS CONFIRMED THAT THE FRACTURED PART HAS BEEN COMPLETELY REMOVED, AND NO FRAGMENT REMAINED IN THE PATIENT. THE PROCEDURE WAS COMPLETED.

da Vinci Surgical 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 A DA VINCI-ASSISTED SURGICAL PROCEDURE, THE WOUND PROTECTOR FOR THE ADVANCED ACCESS PORT REQUIRED TO BE SUTURED TO THE PATIENT'S DIAPHRAGM AND CHEST WALL IN ORDER TO MAINTAIN THE DESIRED PLACEMENT AND SECUREMENT TO PROCEED WITH THE CASE. THE SURGEON STATED THIS TASK TOOK AN ADDITIONAL 50 MINUTES. THE PROCEDURE WAS COMPLETED ROBOTICALLY AS PLANNED WITH NO REPORTED PATIENT INJURY.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

da Vinci Surgical 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 A DA VINCI-ASSISTED MALIGNANT WITH RECONSTRUCTION NIPPLE SPARING MASTECTOMY SURGICAL PROCEDURE, THE MONOPOLAR CURVED SCISSORS (MCS) TIP WAS SEPARATED FROM THE INSTRUMENT DURING THE PROCEDURE. THE METAL PART AND PLASTIC PART WAS SEPARATED. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE CUSTOMER CLARIFIED THAT THE SCISSORS TIP ACCESSORY DID FALL INTO THE PATIENT AND WAS RETRIEVED. THE METAL SCISSORS WERE SEPARATED FROM THE PLASTIC COVER OF THE TIP ACCESSORY. THE CUSTOMER DID NOT OBSERVE ANY DAMAGE ON THE SP MONOPOLAR CURVED SCISSOR TUBE ADAPTER AND USED ANOTHER SCISSORS TIP ACCESSORY TO CONTINUE THE CASE.