_Incident · Collision_

# ADS crash report in Houston, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-16287)

Canonical ID: `9fc2c297-97ef-4927-bfe5-24a4b97b6631`

- **Occurred:** 2026-08-01
- **Kind:** `collision`
- **Status (derived):** active
- **Company:** [Waymo](/companies/waymo.md) (id: `2128addc-20c8-4c31-aef5-be5ada97aede`)

On August [XXX], 2026 at 6:17 AM CDT a [Waymo](/companies/waymo.md) Autonomous Vehicle ("Waymo AV") operating in [Houston](/locations/houston.md), [Texas](/locations/texas.md) was in a collision involving a raised section of pavement in a parking lot at [XXX].

The Waymo AV was traveling east on [XXX]. As the Waymo AV approached the intersection with [XXX], the Waymo AV slowed to a stop for a stop sign with its right turn signal activated. The Waymo AV then turned right onto [XXX] and subsequently initiated a left turn into an adjacent parking lot at [XXX]. As the Waymo AV entered the parking lot, the Waymo AV drove over a raised section of pavement, and the undercarriage of the Waymo AV made contact with the raised section of pavement. 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](/regulations/nhtsa-av-framework.md) because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

## Sources (1)

1. https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30270-16287

## Common questions

### What happened in ADS crash report in Houston, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-16287)?

On August [XXX], 2026 at 6:17 AM CDT a [Waymo Autonomous Vehicle](/models/alphabet-waymo.md) ("[Waymo](/companies/waymo.md) AV") operating in [Houston](/locations/houston.md), [Texas](/locations/texas.md) was in a collision involving a raised section of pavement in a parking lot at [XXX].

The Waymo AV was traveling east on [XXX]. As the Waymo AV approached the intersection with [XXX], the Waymo AV slowed to a stop for a stop sign with its right turn signal activated. The Waymo AV then turned right onto [XXX] and subsequently initiated a left turn into an adjacent parking lot at [XXX]. As the Waymo AV entered the parking lot, the Waymo AV drove over a raised section of pavement, and the undercarriage of the Waymo AV made contact with the raised section of pavement. 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](/regulations/nhtsa-av-framework.md) because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

### When did this incident occur?

The incident is recorded as occurring on August 1, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.

### Who was involved in ADS crash report in Houston, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-16287)?

The incident is recorded as involving [Waymo](/companies/waymo.md) on the DEPLOY registry. No specific robot model is linked to this incident in the registry.

### Has anyone responded to ADS crash report in Houston, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-16287)?

No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.

### What is the current status of ADS crash report in Houston, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-16287)?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.


_API: GET /v1/incidents/9fc2c297-97ef-4927-bfe5-24a4b97b6631 · sources: /v1/incidents/9fc2c297-97ef-4927-bfe5-24a4b97b6631/sources · responses: /v1/incidents/9fc2c297-97ef-4927-bfe5-24a4b97b6631/responses · status: /v1/incidents/9fc2c297-97ef-4927-bfe5-24a4b97b6631/status · canonical URL: /incidents/nhtsa-sgo-30270-16287_