CANADA · VEHICLE RESEARCH

2016 Mitsubishi Lancer

Canadian recalls & official vehicle records

Compact5 source configurations

Evidence updated Nov 17, 2026 · Sources

MitsubishiMitsubishi Lancer model-family photograph; generation, year and trim may differ
Model-family image · year, generation and trim may differ.Photo: Jeremy from Sydney, Australia · CC BY 2.0
3Recall campaignsTransport Canada · exact matches
UnavailableCanadian complaintsNot available in our dataset
5Efficiency configurationsNRCan · Canadian test data
Source-ledResearch approachNo unsupported reliability grades
FROM RESEARCH TO YOUR NEXT CAR

2016 Mitsubishi Lancer 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 year2016
Vehicle classCompact
TransmissionVaries by configuration
EngineVaries by configuration
Recall sourceTransport Canada
Efficiency configurations5
VIN repair statusCheck with manufacturer
View source specifications

Safety Recalls (3)

Canadian archive snapshot, including historical or superseded records.

Visual System

On certain vehicles, water may drain from the windshield cowl area onto the front wiper link ball joint. Over time, this could result in corrosion and/or wear to the joint, which could result in the separation of the wiper link ball. If separation were to occu…

Read the complete source summary

On certain vehicles, water may drain from the windshield cowl area onto the front wiper link ball joint. Over time, this could result in corrosion and/or wear to the joint, which could result in the separation of the wiper link ball. If separation were to occur, the windshield wipers could become inoperative, which could limit the driver’s visibility under certain operating conditions which may increase the risk of a crash causing injury and/or damage to property. Correction: Dealers will replace the wiper link rod with a countermeasure one, and will replace the wiper motor crank arm with a new one.

Transport Canada 2018588 · Oct 26, 2018Official notice ↗

Engine

On certain vehicles, defective electrical relays may have been installed in the power distribution center. This could cause various electrical circuits to fail, potentially resulting in engine stalling, reduced engine power, or loss of engine cooling fan funct…

Read the complete source summary

On certain vehicles, defective electrical relays may have been installed in the power distribution center. This could cause various electrical circuits to fail, potentially resulting in engine stalling, reduced engine power, or loss of engine cooling fan function potentially resulting in engine overheating. These issues could increase the risk of a crash causing injury and/or damage to property. Correction: Dealers will replace affected relay(s) with updated parts.

Transport Canada 2017475 · Sep 29, 2017Official notice ↗

Powertrain

On certain vehicles equipped with a continuously variable transmission (CVT), the range switch could momentarily experience a loss of signal. If this occurs, the driver may experience an unexpected reduction of vehicle acceleration which could, in conjunction …

Read the complete source summary

On certain vehicles equipped with a continuously variable transmission (CVT), the range switch could momentarily experience a loss of signal. If this occurs, the driver may experience an unexpected reduction of vehicle acceleration which could, in conjunction with traffic, road conditions and the driver's reactions, increase the risk of a crash causing injury and/or damage to property. Correction: Dealers will reprogram the CVT-ECU.

Transport Canada 2016379 · Jul 27, 2016Official notice ↗

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 Mitsubishi Lancer 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 2016 Mitsubishi Lancer.

1. Check recall repairs

3 matched Canadian recall campaigns. Start with the notices below and confirm applicability and repair completion for your VIN.

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
3
Canadian complaint records
Unavailable
Efficiency configurations
5
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
Lancer
AV6
X 2.0 L engine7.8 L/100 kmData unavailable
Lancer
M5
X 2.0 L engine8.4 L/100 kmData unavailable
Lancer
AV6
X 2.4 L engine8.8 L/100 kmData unavailable
Lancer
M5
X 2.4 L engine9.2 L/100 kmData unavailable
Lancer 4WD
AV6
X 2.4 L engine9.1 L/100 kmData unavailable

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.

Lancer · AV6 — source specification details
Vehicle classCompact
Engine displacement2.0 L
Cylinders4
City fuel consumption8.6 L/100 km
Highway fuel consumption6.8 L/100 km
Tailpipe CO₂ emissions181 g/km
Lancer · M5 — source specification details
Vehicle classCompact
Engine displacement2.0 L
Cylinders4
City fuel consumption9.6 L/100 km
Highway fuel consumption7.0 L/100 km
Tailpipe CO₂ emissions198 g/km
Lancer · AV6 — source specification details
Vehicle classCompact
Engine displacement2.4 L
Cylinders4
City fuel consumption9.8 L/100 km
Highway fuel consumption7.6 L/100 km
Tailpipe CO₂ emissions204 g/km
Lancer · M5 — source specification details
Vehicle classCompact
Engine displacement2.4 L
Cylinders4
City fuel consumption10.5 L/100 km
Highway fuel consumption7.7 L/100 km
Tailpipe CO₂ emissions217 g/km
Lancer 4WD · AV6 — source specification details
Vehicle classCompact
Engine displacement2.4 L
Cylinders4
City fuel consumption10.2 L/100 km
Highway fuel consumption7.8 L/100 km
Tailpipe CO₂ emissions210 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 for documentation related to the official Visual System campaign (2018588).
  • Ask for documentation related to the official Engine campaign (2017475).
  • 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 2016 Mitsubishi Lancer, built from this report.

  1. Record the VIN, market and exact powertrain. Confirm open recalls and completed remedies with the manufacturer.
  2. Ask for repair documentation for campaign 2018588 (Visual System). A model-year match does not establish that this VIN is affected.
  3. Ask for repair documentation for campaign 2017475 (Engine). A model-year match does not establish that this VIN is affected.
  4. Ask for repair documentation for campaign 2016379 (Powertrain). A model-year match does not establish that this VIN is affected.
  5. 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 2016 Mitsubishi Lancer.

POWER TRAIN
21
ELECTRICAL SYSTEM
4
VEHICLE SPEED CONTROL
4
ENGINE
3
UNKNOWN OR OTHER
3

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
2022-091
2022-121
2023-041
2023-051
2023-072
2024-081
2024-091
2024-101
2025-021
2025-051
2025-071
2026-081
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 mi2
50,000–99,999 mi7
100,000–149,999 mi1
150,000+ mi0
Missing or excluded mileage18

12 of 30 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 flagged1US 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.

36 matched manufacturer communications · 1 matched investigations. Communications are not necessarily recalls or technical service bulletins.

EA19001 · Electrical overstress

The Office of Defects Investigation (ODI) opened this investigation to determine if the failure of airbags to deploy during severe crashes, in certain vehicles, was the result of a safety related defect.  During the investigation a complex failure was studied that can result in non-deployment of subject vehicle air bags and other restraint system devices in severe crash events. The subject vehicles may be equipped with an airbag control unit (ACU) for the supplemental restraint system (SRS) Electronic Control Unit (ECU) manufactured by ZF-TRW.  The ECU receives signals from crash sensors mounted in the vehicle and deploys the vehicle air bags and seat belt pretensioners in accordance with manufacturer design specifications.  The ECU in the subject vehicles contains a model DS84 application-specific integrated circuit (ASIC) which controls the communication of the crash sensor signal, firing commands (i.e., when to deploy the airbag(s) and/or pretensioners), and fault information (e.g., diagnostic trouble codes). In September 2016, FCA announced recall 16V-668 for certain model year (MY) 2010 to 2014 Chrysler, Dodge and Jeep products manufactured with the subject ZF-TRW ACU.  In this recall, FCA discussed an EOS condition that resulted in a failure of the subject DS84 ASIC, which caused air bag non-deployment.  FCA noted that the defect condition had only been observed in vehicles equipped with sensor harnessing routed across the front of the vehicle.  Other FCA vehicles that also used the subject ACU, but were not equipped with cross-car harnessing, had not experienced EOS failures, despite similar time in service. During the course of this investigation, ODI sent two separate Information Request (IR) letters to six vehicle manufactures (including FCA, Hyundai, Honda, Kia, Mitsubishi, and Toyota) and one IR letter to ZF-TRW.  These IR letters resulted in ODI receiving comprehensive data from these manufacturers and suppliers. Studies of this data found that the DS84 ASIC does not have sufficient protection against negative electrical transients or electrical overstress (“EOS”) that can be generated in certain severe crashes.  An electrical transient occurs when the electrical power supplied to a circuit changes momentarily over a short duration of time.   In these severe crash cases, the crash sensors and other powered wiring can be damaged and short circuited so as to create a negative electrical transient of sufficient intensity and duration (that are outside the vehicle manufacturer's specification) to damage the ASIC before the restraint device deployment signal is received by the SRS ECU.  This damaged signal can lead to incomplete or nondeployment of the air bags and/or pretensioners.  Airbag non-deployment and/or lack of pretensioner operation can increase the risk or severity of injury in a crash.A total of 8 fatalities and 14 injuries were associated with known EOS events. The common element in all investigated manufacturers vehicles is the SRS ECU containing a DS84 ASIC manufactured by ZF-TRW.  The risk associated with the ASIC is equally shared among all OEMS involved in the investigation.  The actual real-world risk can be mitigated by other factors which were assessed by ODI during this investigation. The first mitigating factor involves protections built into the ACU design which protect the DS84 ASIC from damage.  There are multiple strategies and levels of protection employed by different OEMs that provide effective EOS mitigation.  The two most common strategies at the ACU level are circuit protection diodes on the remote senor signal lines, and current limiting resistors that protect critical components. The second mitigating factor is found at the vehicle level and involves the location and routing of the wires leading from the crash sensors to the SRS ECU.  If the wires are well protected in a crash and are not routed with other power wires carrying large currents, the risk for an EOS event is significantly reduced or eliminated. These design specific factors combine to produce a spectrum of risk for the vehicles equipped with ACUs using the DS84 ASIC.  Given the many of years of field exposure, it is possible to divide the subject population into two groups; vehicles which have experienced EOS events, and vehicles which have not experienced EOS field events. Four of the six OEMs involved in this investigation have experienced EOS field events on at least one of their models equipped with a DS84 ASIC.  All vehicle models (including the Toyota models identified in the Failure Report Summary of the opening resume for this investigation) with field events have been recalled.  In an abundance of caution, ODI kept this investigation open five years to monitor field performance and did not identify any field events on vehicles not included in existing safety recalls. Given the spectrum of risk identified in this investigation and that all vehicles with a demonstrated unreasonable risk have been recalled, ODI is closing this investigation. ODI is closing this investigation with the following manufacturer safety recalls: 16V-668, 18E-043, 18V-137, 18V-363, and 20V-024.  With the recall actions taken by the subject vehicle and equipment manufacturers, this investigation is closed. The closing of this investigation does not constitute a finding by NHTSA that a safety-related defect does not exists on other model or model year vehicles outside of the recall scopes. The agency reserves the right to take further action if warranted by the circumstances.

Opened 20190419 · Closed 20240919

Official investigation archive ↗
Communication 11026481

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 11003536

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

Source received period 2020-2024 · Publication date unavailable in export.

Official source archive ↗
Communication 10252691

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

Source received period 2020-2024 · Publication date unavailable in export.

Official source archive ↗
Communication 10252683

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

Source received period 2020-2024 · Publication date unavailable in export.

Official source archive ↗
Communication 10250860

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

Source received period 2020-2024 · Publication date unavailable in export.

Official source archive ↗
Communication 10240443

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

Source received period 2020-2024 · Publication date unavailable in export.

Official source archive ↗
Communication 10235611

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

Source received period 2020-2024 · Publication date unavailable in export.

Official source archive ↗
Communication 10235609

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

Source received period 2020-2024 · 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.