Arlington, TX

On August [XXX], 2026, at 2:17 p.m. CT, a May Mobility autonomous vehicle (AV) operating northbound in autonomous mode stopped at a stop sign on [XXX] in Arlington, Texas. The May Mobility AV began to make a right turn into the curb lane of eastbound [XXX], but stopped mid-turn to yield to a crossing vehicle. A passenger vehicle trailing the May Mobility AV advanced into the crosswalk at three mph, making contact with the May Mobility AV's rear left corner, causing moderate damage to the May Mobility AV’s rear left-side bumper and quarter panel, and damaging the passenger vehicle’s front right tire. No injuries were reported, no towing was needed, and no airbags were deployed. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available.

On July [XXX], 2026, at 1:04 p.m. CT, the May Mobility autonomous vehicle (AV), operating in autonomous mode, was traveling west on [XXX] in Arlington, Texas, when it came to a complete stop for a moving mail delivery van attempting to pull away from the curb. The AV remained stationary, in the lane, and in autonomous operation, as an SUV approached traveling east on [XXX]. As the SUV passed on the passenger side, the right side of the SUV made contact with the stationary AV's right-side mirror and right-side sensor pod, causing minor damage to the sensor pod and minor scuff marks to the mirror. The SUV continued traveling east without stopping. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available.

On May [XXX], 2026 at 4:38 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX]. The May Mobility AV was traveling Eastbound on [XXX]. As the May Mobility AV passes [XXX] a loop of an unsecured, low-hanging utility cable that was dangling above the right lane of travel struck the windshield and roof of the May Mobility AV. At the time of impact, the May Mobility AV was in autonomous mode, traveling at 32 MPH. The May Mobility AV sustained damage on the top, front, and right side of the vehicle that is estimated to be more than $1,000. Damage to the utility cable beyond the original state of disrepair is unknown. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available.

On May [XXX], 2026 at 4:11 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX] The May Mobility AV was traveling Eastbound on [XXX]. As the May Mobility AV passes [XXX] a loop of an unsecured, low-hanging utility cable that was dangling above the right lane of travel made contact with the front right A-pillar near the windshield of the May Mobility AV. At the time of impact, the May Mobility AV was in autonomous mode, traveling at 33 MPH. The impact left scuffs on the May Mobility AV that were buffed out, not requiring repair. Damage to the utility cable beyond the original state of disrepair is unknown. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available.

On March [XXX], 2026, at 10:18 am, a third-party vehicle collided with a May Mobility Autonomous Vehicle (Ego) in Arlington, Texas, at the intersection of [XXX] and [XXX]. The May Ego was traveling north on [XXX], making a right turn at a yield sign onto eastbound [XXX]. with its automated driving system engaged in autonomy mode. The May Ego stopped at the yield sign then held its position in order to confirm its prediction that an oncoming vehicle was not making a left turn across the ego's path. The third-party vehicle, traveling north on [XXX] behind the Ego, failed to stop at the yield sign and rear-ended the Ego. Vehicle telematics confirm the Autonomous Vehicle Operator intervened using the accelerator to avoid the collision; however, the collision was unavoidable.

The May Mobility vehicle (Ego) is stopped at a red light, then the Ego begins to accelerate and turn right when the traffic light changes to green. As the Ego accelerates, a pedestrian begins moving and enters the crosswalk from the other side of the intersection. This activates the rule-based crosswalk logic. Ego determines that it is able to stop before the crosswalk without exceeding our max deceleration threshold, which triggers an in-policy stopping reaction for the crosswalk. The Ego brakes to yield for the pedestrian. The vehicle trailing the Ego accelerates, making contact with the rear-end of the Ego. In the 2.5 seconds between the start of the Ego braking and the collision, the rear vehicle accelerated from 0.2 to 6.1 m/s (0.4 to 13.6 mph) without slowing until after the collision occurred. In response to this incident, immediate mitigations were made, in that the vehicle operators (AVOs) operate all intersections in manual mode. This remained in place until January 12, when we received a solution which instituted a reduction of the 3.5 m/s2 parameter, in order to prevent the Ego from yielding to pedestrians in crosswalks that are still far from the Ego’s lane if such yielding would induce braking.

The May Mobility vehicle (Ego) approaches a turn with a trailing vehicle following closely behind. The May planner initially selects a trajectory it believes will safely complete the turn. However, as the Ego begins the turn, it re-evaluates the situation and detects a significant risk of striking the curb. At that point, the planner shifts focus from avoiding the curb entirely to minimizing the severity of a potential curb strike. To reduce speed before the expected contact, the Ego brakes at €"3.5 m/s²). Because the trailing vehicle is following so closely, this deceleration makes a rear-end collision likely. The Ego predicts a potential rear-end collision and elects to reduce brake force to lessen the impact severity. Moments later, the trailing vehicle strikes the rear driver-side bumper of the Ego and then drives away. Future improvements are underway to give the planner a policy option to steer away from curbs. This new capability will help the vehicle avoid situations where braking becomes the only remaining way to manage close curb proximity.