CANADA · VEHICLE RESEARCH

2026 Tesla Model 3

Canadian recalls & official vehicle records

Mid-sizeA14 source configurations

Evidence updated Nov 17, 2026 · Sources

TeslaTesla Model 3 model-family photograph; generation, year and trim may differ
Model-family image · year, generation and trim may differ.Photo: Alexander-93 · CC BY-SA 4.0
0Recall campaignsTransport Canada · exact matches
UnavailableCanadian complaintsNot available in our dataset
4Efficiency configurationsNRCan · Canadian test data
Source-ledResearch approachNo unsupported reliability grades
FROM RESEARCH TO YOUR NEXT CAR

2026 Tesla Model 3 for sale

Explore matching dealer listings in Canada. CAD prices · kilometres · Quebec excluded.

Search listings
Show matching dealer listings

Open this section to check available listings. No listing request is made until you open it.

Source: Car Handshake and participating dealerships. Year, make and model must match to appear here; trims and specifications can differ. Listings do not establish vehicle condition or recall repair status.

Canadian owner complaints

Coverage, without substituted US totals.

Canadian complaint totals are not available in Recheck’s current dataset. This does not mean there are no complaints.

Canadian recalls come from Transport Canada and efficiency ratings from NRCan. US complaints and bulletins are optional context below; they do not establish Canadian applicability.

Report a Canadian safety concern ↗

At a Glance

Source configurations, without assumed specifications.

Research marketCanada
Model year2026
Vehicle classMid-size
TransmissionA1
Motor outputVaries by configuration
Recall sourceTransport Canada
Efficiency configurations4
VIN repair statusCheck with manufacturer
View source specifications

Safety Recalls (0)

Canadian archive snapshot, including historical or superseded records.

No exact make/model/year matches in this dataset snapshot. Spelling and configuration differences can exclude records. This is not confirmation that a vehicle is free of recalls.

Check your individual VIN

Model-year recalls do not establish repair completion.

Confirm open recalls with the manufacturer and ask a dealer whether the repairs are complete. Recheck’s VIN decoder identifies the vehicle; it does not provide recall repair status.

Canadian recall and VIN lookup guidance ↗
RECHECK EVIDENCE LAB

Your annual energy budget

Use official test estimates with your own distance and prices.

Enter a price to estimate your annual energy budget.

Scenario estimate, not a live price quote or total cost of ownership. Uses the selected source configuration’s combined test consumption. Weather, speed, battery condition, charging losses, taxes, maintenance, depreciation and insurance can change actual cost. Plug-in hybrids are excluded from this simple calculator because fuel and electricity use depend on charging behaviour. Your inputs stay in your browser.

Compare Model Years

Explore documented Tesla Model 3 records.

Totals reflect different time on the road and configurations. Fewer reports do not establish greater reliability.

Compare vehicles side by side →

RECHECK EVIDENCE LAB

Your vehicle’s evidence passport

What to investigate first for the 2026 Tesla Model 3.

1. Check recall repairs

No exact recall matches in this snapshot. Check your VIN with the manufacturer; a model-year search cannot establish recall status.

2. Know the reported themes

Canadian owner complaint totals are not available in our dataset. This is not a zero-complaint finding.

Research Canadian recalls below. Optional US complaint context is separate and does not establish Canadian experience.

Take a tailored checklist to your mechanic →
Coverage, sources and what remains unknown
Recall source
Transport Canada
Matched campaigns
0
Canadian complaint records
Unavailable
Efficiency configurations
4
Canadian investigations
Not imported
Repair completion
Not established

Coverage boundary: Canadian archive snapshot Exact normalized make/model/year safety matches. Efficiency retains explicitly named source configurations; spelling/configuration differences may exclude records. US complaint counts do not establish Canadian experience or the probability of a defect.

Accident history, current mechanical condition, ownership, liens, individual recall applicability, repair completion and battery health are not established by this model-year report. No failure rate or reliability score is calculated from raw complaint totals.

Specifications & Efficiency

Official source configurations. No trim is assumed.

Source configurationFuel / powertrainCombined efficiencyRange
Model 3 Premium-I
A1
B 15.3 kWh/100 km463 km
Model 3 Premium AWD-I
A1
B 16.4 kWh/100 km570 km
Model 3 Performance
A1
B 18.4 kWh/100 km497 km
Model 3 Performance AWD
A1
B 18.8 kWh/100 km505 km

Official test estimates vary with configuration, driving and weather. Fuel codes are retained as published; US and Canadian test measures are shown in their source units. Plug-in hybrid source ranges and operating modes are shown separately; they are not added together.

More from the official configuration records

Figures belong to each source configuration. Test conditions and charging assumptions apply; tailpipe emissions exclude fuel and electricity production. No missing specifications are inferred.

Model 3 Premium-I · A1 — source specification details
Vehicle classMid-size
Motor output208 kW
City electricity consumption14.6 kWh/100 km
Highway electricity consumption16.1 kWh/100 km
Source recharge time8 h
Tailpipe CO₂ emissions0 g/km
Model 3 Premium AWD-I · A1 — source specification details
Vehicle classMid-size
Motor output280 kW
City electricity consumption15.7 kWh/100 km
Highway electricity consumption17.3 kWh/100 km
Source recharge time8 h
Tailpipe CO₂ emissions0 g/km
Model 3 Performance · A1 — source specification details
Vehicle classMid-size
Motor output380 kW
City electricity consumption17.4 kWh/100 km
Highway electricity consumption19.5 kWh/100 km
Source recharge time8 h
Tailpipe CO₂ emissions0 g/km
Model 3 Performance AWD · A1 — source specification details
Vehicle classMid-size
Motor output380 kW
City electricity consumption17.9 kWh/100 km
Highway electricity consumption19.8 kWh/100 km
Source recharge time8 h
Tailpipe CO₂ emissions0 g/km

Canadian defect investigations

Check the current official Transport Canada register.

Canadian investigation records are not imported into this report. Check the official register for affected vehicles, investigation details and current status; no match or status is implied here.

Look up Canadian investigations ↗

Before You Buy

Questions to take to a seller or qualified mechanic.

  • Verify the VIN and ask the manufacturer to confirm applicability and completion of recall repairs.
  • Ask a mechanic to investigate any symptoms associated with reported categories; complaints alone are not a diagnosis.
  • Review service records and arrange an independent pre-purchase inspection.
Read the complete inspection checklist →
RECHECK EVIDENCE LAB

Take this to your mechanic

A research brief for the 2026 Tesla Model 3, built from this report.

  1. Record the VIN, market and exact powertrain. Confirm open recalls and completed remedies with the manufacturer.
  2. Compare service records with the manufacturer’s schedule and arrange an independent pre-purchase inspection. This checklist is not a diagnosis or an expert inspection.
Optional US contextNHTSA complaints, communications and investigations · not Canadian records

These are US records. Models, equipment, campaigns and driving conditions can differ. Counts are not Canadian complaint totals, verified reviews or reliability ratings.

Reported Problem Categories

US NHTSA complaints for the 2026 Tesla Model 3.

UNKNOWN OR OTHER
10
FORWARD COLLISION AVOIDANCE
8
STEERING
7
BACK OVER PREVENTION
5
LANE DEPARTURE
4

US context, not Canadian complaint counts. NHTSA documents known discrepancies in its bulk complaint file. Consumer allegations are not confirmed defects. One complaint can mention several categories. Counts are not failure rates.

Reports Over Time

US complaints by filing month, latest 12 observed months.

A month with no bar is not evidence that no problems occurred. Publication and reporting delays affect totals.

Read chart data
2026-011
2026-043
2026-051
2026-062
2026-076
2026-086
2026-097
2026-104
2026-111
RECHECK EVIDENCE LAB

The mileage lens

Where the available US complaint records fall by reported mileage.

Reported mileage at incidentMatched complaint records
Below 25,000 mi2
25,000–49,999 mi0
50,000–99,999 mi1
100,000–149,999 mi0
150,000+ mi0
Missing or excluded mileage28

3 of 31 matched complaints have positive, usable mileage. Source zero values can represent missing information and are excluded; values above 1.5 million miles are excluded. These are selected allegations with no vehicle-population denominator. The table cannot predict when your vehicle will fail. Mileage is retained in US source miles.

Crash flagged10US complaint allegations
Fire flagged0US complaint allegations
Towed flagged3US complaint allegations

Positive source flags are counted per deduplicated complaint, not verified incidents. Categories and flags can overlap; an unflagged or missing value does not prove an incident did not occur.

Bulletins & Investigations

US official records; applicability in Canada is not established.

2 matched manufacturer communications · 3 matched investigations. Communications are not necessarily recalls or technical service bulletins.

AQ25002 · Compliance with Standing General Order 2021-01 Reporting Requirements

The Office of Defects Investigation (“ODI”) has identified numerous incident reports submitted by Tesla, Inc. (“Tesla”) in response to Standing General Order 2021-01 (the “SGO”), in which the reported crashes occurred several months or more before the dates of the reports. The majority of these reports involved crashes in which the Standing General Order in place at the time required a report to be submitted within one or five days of Tesla receiving notice of the crash. When the reports were submitted, Tesla submitted them in one of two ways. Many of the reports were submitted as part of a single batch, while others were submitted on a rolling basis. Preliminary engagement between ODI and Tesla on the issue indicates that the timing of the reports was due to an issue with Tesla’s data collection, which, according to Tesla, has now been fixed. NHTSA is opening this Audit Query, a standard process for reviewing compliance with legal requirements, to evaluate the cause of the potential delays in reporting, the scope of any such delays, and the mitigations that Tesla has developed to address them. As part of this review, NHTSA will assess whether any reports of prior incidents remain outstanding and whether the reports that were submitted include all of the required and available data. The SGO reports cited in the Opening Resume, can be found at NHTSA.gov/SGOCrashReporting under the following SGO 2021-01 report IDs: 13781-11020-1 13781-10844-1 13781-10843-1 13781-10530-1 13781-10160-1 13781-10159-1 13781-10157-1 13781-10146-1 13781-10122-1 13781-10098-1 13781-10097-1 13781-10096-1 13781-10095-1 13781-10094-1 13781-10093-1 13781-10023-1 13781-10022-1 13781-10021-1 13781-10020-1 13781-10017-1 13781-10016-1 13781-10015-1 13781-10014-1 13781-10013-1 13781-10012-1 13781-6047-1 13781-9930-1 13781-9917-1 13781-9928-1 13781-9925-1 13781-9924-1 13781-9923-1 13781-9922-1 13781-9835-1 13781-9834-1 13781-9833-1 13781-9832-1 13781-9831-1 13781-9830-1 13781-9829-1 13781-9827-1 13781-9818-1 13781-9780-1 13781-9779-1 13781-9778-1 13781-9777-1 13781-9775-1 13781-9774-1 13781-9773-1 13781-9772-1 13781-9771-1 13781-9770-1 13781-9728-1 13781-9688-1 13781-9715-1 13781-9714-1 13781-9713-1 13781-9712-1 13781-9711-1 13781-9710-1 13781-9709-1 13781-9696-1 13781-9695-1 13781-9694-1 13781-9693-1 13781-9692-1 13781-9691-1 13781-9690-1 13781-9687-1 13781-9686-1 13781-9342-1 13781-9319-1 13781-9019-1 13781-8910-1 13781-8732-1 13781-8712-1 13781-8310-1 13781-7897-1 13781-7895-1 13781-7835-1 13781-7798-1 13781-7797-1 13781-7758-1 13781-7757-1 13781-7756-1 13781-7755-1 13781-7667-1 13781-7399-1 13781-7398-1 13781-7397-1 13781-7396-1 13781-7395-1 13781-7394-1 13781-7393-1 13781-7389-1 13781-7388-1 13781-7387-1 13781-7386-1 13781-7385-1 13781-7383-1 13781-7187-1 13781-7186-1 13781-7185-1 13781-7184-1 13781-7181-1 13781-7023-1 13781-6399-1 13781-6389-1 13781-6388-1 13781-6387-1 13781-6386-1 13781-6379-1 13781-6378-1 13781-6377-1 13781-6375-1 13781-6214-1 13781-6172-1 13781-6155-1 13781-6154-1 13781-6122-1 13781-6120-1 13781-6118-1 13781-5800-1

Opened 20250820 · No closure date in source

Official investigation archive ↗
EA26002 · FSD Collisions in Reduced Roadway Visibility Conditions

The Office of Defects Investigation (ODI) is opening this Engineering Analysis to evaluate Tesla’s Full Self Driving Beta and Full Self Driving (Supervised) (collectively, FSD) degradation detection system. The focus of this investigation will be to assess the system’s ability, when encountering reduced roadway visibility conditions, to detect degradation and alert the driver with sufficient time to respond. ODI will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications by Tesla to the degradation detection system, including the timing, purpose, and capabilities of the updates, and Tesla’s assessment of their safety impact. Tesla’s FSD is an advanced driver assistance system (ADAS) that relies exclusively on vision-based cameras and the related FSD software to detect and respond to the roadway ahead, projecting a path forward based on traffic control devices, vehicles, pedestrians, and the roadway itself. When Tesla began transitioning away from using both cameras and radars to an exclusively camera-based approach, known as Tesla Vision, in mid-2021, it developed and implemented a degradation detection system that it deployed by a software update to existing and new Tesla vehicles. On June 28, 2024, the day after Tesla submitted the SGO report of the November 28, 2023 fatal crash listed in this document, Tesla began developing an update to the degradation detection system. At this time, ODI does not have information on when the update was deployed and which vehicles have the updated system. ODI discussed individual incidents and its initial findings during the PE phase of its investigation with Tesla. As part of those discussions, Tesla’s post-incident analysis indicated that the update to the degradation detection system, had it been installed on the vehicles at the time, may have affected 3 of the 9 incidents identified by ODI. Tesla also described internal data and labeling limitations that prevented a uniform identification and analysis of crash events with the subject system engaged. ODI believes this limitation could have led to under-reporting of subject crashes over portions of the defined time-period. Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred. Review of Tesla’s responses revealed additional crashes that occurred in similar environments and where the system either did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path. In upgrading PE24031 to an Engineering Analysis (EA), ODI will gather further information on the updated degradation detection system, including the status of updating vehicles and scope of compatible vehicles, the system’s visibility degradation detection capability, and alerts or warnings to the driver. Lastly, ODI will conduct analysis on six recent potentially related incidents. These incidents can be found at NHTSA.gov under the following SGO report identification numbers: 13781-11937, 13781-13211, 13781-13569, 13781-13633, 13781-13693, 13781-13788. The crashes included in the failure report summary can be found at NHTSA.gov under the following SGO report identification numbers: 13781-8004, 13781-7181, 13781-7381, 13781-7767, 13781-7964, 13781-8977, 13781-9267.

Opened 20260318 · No closure date in source

Official investigation archive ↗
PE25012 · Traffic safety violations while Full Self Driving ("FSD") is engaged

The Office of Defects Investigation (“ODI”) is opening this Preliminary Evaluation (PE) to assess the scope, frequency, and potential safety consequences of FSD executing driving maneuvers that constitute traffic safety violations. This investigation concerns versions of FSD that Tesla has labeled as "FSD (Supervised)" and "FSD (Beta)." Tesla characterizes FSD as an SAE Level 2 partial automation system requiring a fully attentive driver who is engaged in the driving task at all times. Level 2 partial automation systems are designed to support and assist the driver in performing certain aspects of the driving task, requiring a driver to supervise and intervene as necessary.  The driver remains fully responsible at all times for driving the vehicle, including complying with applicable traffic laws. ODI’s investigation will therefore focus, in particular, on whether certain driving inputs within the control authority of FSD forestall the driver’s supervision when they are unexpectedly performed. ODI has identified a number of incidents in which the inputs to the dynamic driving task commanded by FSD induced vehicle behavior that violated traffic safety laws. Although reports of this nature span a variety of behaviors, the reports appear to most commonly involve two types of scenarios. The first type of scenario involves a vehicle operating with FSD proceeding into an intersection in violation of a red traffic signal. The second type of scenario involves FSD commanding a lane change into an opposing lane of traffic. With respect to the first type of scenario, ODI has identified 18 complaints and 1 media report alleging that a Tesla vehicle, operating at an intersection with FSD engaged, failed to remain stopped for the duration of a red traffic signal, failed to stop fully, or failed to accurately detect and display the correct traffic signal state in the vehicle interface. Some complainants also alleged that FSD did not provide warnings of the system's intended behavior as the vehicle was approaching a red traffic signal. ODI has identified six Standing General Order ("SGO") reports in which a Tesla vehicle, operating with FSD engaged, approached an intersection with a red traffic signal, continued to travel into the intersection against the red light and was subsequently involved in a crash with other motor vehicles in the intersection. Of these incidents, four crashes resulted in one or more reported injuries. At least some of the incidents appeared to involve FSD proceeding into the intersection after coming to a complete stop. ODI's pre-investigative work, including coordination with the Maryland Transportation Authority and State Police, indicated that the problem may be repeatable, given that multiple subject incidents occurred at the same intersection in Joppa, Maryland. NHTSA understands that Tesla has since taken action to address the issue at this intersection. With respect to the second type of scenario, ODI has identified 2 SGO reports, 18 complaints, and 2 media reports alleging that a Tesla vehicle, operating with FSD engaged, entered opposing lanes of travel during or following a turn, crossed double-yellow lane markings while proceeding straight, or attempted to turn onto a road in the wrong direction despite the presence of wrong-way road signs. Likewise, ODI has identified 4 SGO reports, 6 complaints, and 1 media report alleging that a Tesla vehicle, operating with FSD engaged, proceeded straight through an intersection in a turn-only lane or executed a turn at an intersection in a through lane despite the presence of lane markings or signals. Complaints also alleged that FSD did not provide warnings of the system's intended behavior. Some complaints alleged that more than one of these failures occurred and, as such, the numbers are not cumulative. Some of the reported incidents appeared to involve FSD executing a lane change into an opposing lane of travel with little notice to a driver or opportunity to intervene. ODI’s review will assess whether there was prior warning or adequate time for the driver to respond to the unexpected behavior or to safely supervise the automated driving task. This review will assess any warnings to the driver about the system's impending behavior; the time given to drivers to respond; the capability of FSD to detect, display to the driver, and respond appropriately to traffic signals; and the capability of FSD to detect and respond to lane markings and wrong-way signage. NHTSA's review will also consider any updates or modifications to the system(s) that may affect the performance of FSD with respect to obeying traffic safety laws and signals. This assessment will focus, in particular, on the types of traffic safety violations described above, as most reports identified thus far have centered around those behaviors. While the behaviors under investigation appear to occur most frequently at intersections, NHTSA’s investigation will encompass any other types of situations in which this behavior may arise, such as when traveling adjacent to a lane of opposing traffic or when approaching railroad crossings. If other evidence received during this investigation involve other types of traffic safety violations, those may be considered as part of this assessment as well. To review the ODI reports cited in the Opening Resume ODI Report Identification Number document, go to NHTSA.gov. The SGO reports cited in this Resume are listed below by report ID and are available for download at NHTSA.gov/laws-regulations/standing-general-order-crash-reporting. 13781-8739-1, 13781-8995-1, 13781-9623-1, 13781-10333-1, 13781-10872-1, 13781-10930-1, 13781-10939-1, 13781-10941-1, 13781-11069-1, 13781-11305-1, 13781-11579-1 Media reported allegations included as a separate attachment.

Opened 20251007 · No closure date in source

Official investigation archive ↗
Communication 11034277

Official source metadata matches this vehicle. Read the document in the NHTSA archive for its contents and applicability.

Source received period 2025-2026 · Publication date unavailable in export.

Official source archive ↗
Communication 11033171

Official source metadata matches this vehicle. Read the document in the NHTSA archive for its contents and applicability.

Source received period 2025-2026 · Publication date unavailable in export.

Official source archive ↗

Showing up to 8 communication summaries and 4 investigations. Export coverage: communications received 2020–2026 only. Canadian applicability is not inferred. Consult NHTSA for full records.

Sources & Last Updated

Trace the evidence behind this report.

Transport Canada Vehicle Recalls Database · Original source · Evidence updated Nov 17, 2026
US NHTSA complaints · optional US context only · Original source · Retrieved Nov 17, 2026 · Counts deduplicated by ODI number.
US communications & investigations · Official datasets · Communications received 2020–2026, exact matches; investigations full-history export.