Investigations
Actually Smart Summon sessions resulting in low-speed impacts.
NHTSA Preliminary Evaluation PE24033 - closed, opened 2025-01-06 and involving the SMART.
Vehicle: SMART
Among 2,329 NHTSA Preliminary Evaluation files in PlainCars' ODI extract, this record (PE24033) is one published case in that type class , and one of 2 investigation files attributed to SMART.
NHTSA investigation PE24033 is a Preliminary Evaluation opened on 2025-01-06 and currently closed. The subject of record is SMART, which places this file inside the Office of Defects Investigation queue for SMART. Latest activity on this investigation was logged on 2026-04-03 - NHTSA updates that field whenever an Information Request goes out, a supplement is filed, or a status change is recorded in the public docket.
A Preliminary Evaluation like PE24033 is the entry point of the federal defect-investigation process. NHTSA engineers scan complaint databases, field reports, and manufacturer data to decide whether an Engineering Analysis is warranted, whether a voluntary recall is already sufficient, or whether the pattern does not rise to a defect finding.
Investigators summarized the matter as follows: "On January 6, 2025, the Office of Defects Investigations (ODI) opened Preliminary Evaluation 24003 (PE24033) to investigate Actually Smart Summon (Summon) sessions resulting in crashes during active sessions. According t..." Investigations are the early-warning layer of the federal auto-safety system, sitting upstream of formal recalls and defect orders. Whether this one closes without action or escalates into an Engineering Analysis, the full history stays in the ODI archive so researchers, litigators, and buyers can pull the paper trail at any time. Related SMART files, listed below, give context on whether this is an isolated concern or part of a broader pattern across the brand.
Investigation Summary
On January 6, 2025, the Office of Defects Investigations (ODI) opened Preliminary Evaluation 24003 (PE24033) to investigate Actually Smart Summon (Summon) sessions resulting in crashes during active sessions. According to Tesla, Summon is a short-distance SAE Level 2 system, controlled by the user from a cell phone within a certain distance and intended for use in parking lots and on private property. ODI analyzed complaint data provided by Tesla as well as complaints submitted to ODI from consumers to identify Summon incidents resulting in crashes. ODI's analysis indicates that almost all Summon reported crashes involved minor property damage claims with no reported incidents involving a vulnerable road user, injury, fatality, or major property damage as indicated by an air bag deployment or vehicle tow away. Out of millions of Summon sessions, a fraction of 1% resulted in an incident. Almost all those incidents took place where, typically early in a Summon session, the system or person using the app failed to fully detect or respond appropriately to vehicle surroundings resulting in minor impacts. Incidents took place when app users did not have a complete 360-degree view of the surroundings in the app to assess situational awareness. This limited the app user’s ability to determine whether an impact was imminent during initial vehicle maneuvers such as reversing in close proximity to an obstacle or a curb. ODI found that the impacts most often occurred with parking gates, adjacently parked vehicles, and short parking bollards. During this investigation, ODI identified two Summon crashes related to camera blockages. In both crashes, Summon attempted to navigate a snowy parking lot with snow partially or fully obstructing the forward-facing cameras. Summon did not detect the camera blockage and the vehicles collided with unoccupied parked vehicles while navigating the parking lot. App users in both instances did not command a vehicle stop or pause despite the obstr
About This Investigation Type
A Preliminary Evaluation (PE) is the first phase of NHTSA's investigation process. It is opened when the agency identifies a potential safety defect pattern, usually triggered by consumer complaints, manufacturer reports, or field monitoring. During a PE, NHTSA gathers information to determine whether a formal engineering analysis is warranted.
Other SMART Investigations
Data from NHTSA Office of Defects Investigation. Cross-references: NHTSA recall campaign API and NHTSA FARS where fatality records overlap. PlainCars does not rate or recommend vehicles. about how PlainCars sources NHTSA data.
Read our methodology - how this data is sourced, computed, and verified.