Model-level range presence is a source-coverage check. It does not confirm that a repair fits every engine or model year.
Vehicle problem research
2013 Lexus ES 350 problems and repair guidance
Read 1 documented issue file for the 2013 Lexus ES 350, including symptoms, source-defined vehicle scope and the published repair or diagnostic steps. A matching model name does not diagnose your car or confirm VIN eligibility.
This profile contains problem research. Model-specific service-contract price estimates are not included. The federal record table below identifies available counts and any unmatched model years.
Choose the exact year
Lexus ES 350 model-year research
Model-year coverage varies. Each page shows the available problem files and identifies whether warranty estimates and federal report counts are included.
Problem research and repair guidance
2013 Lexus ES 350: symptoms, affected vehicles and documented fixes
Match the symptom and the exact vehicle scope before arranging work. The imported catalogue is an editorial index of source documents, not an independent safety authority. Recall text is checked against NHTSA; each record links to the evidence that supports its scope and remedy.
1 recall file · 0 other manufacturer files. These are editorial file counts, not distinct campaign totals, failure rates or a complete recall history.
FORWARD COLLISION AVOIDANCE
Official safety recall2013, 2014, 2015Campaign 15V728000FORWARD COLLISION AVOIDANCE: CRASH IMMINENT BRAKING: recall 15V728000
A vehicle that unexpectedly brakes increases the risk of a crash.
Toyota Motor Engineering & Manufacturing (Toyota) is recalling certain model year 2013-2015 Avalon and Avalon Hybrid vehicles manufactured October 19, 2012 to October 27, 2015 and 2013-2015 Lexus ES350 and ES300h vehicles manufactured June 18, 2012 to July 6, 2015. The affected vehicles are equipped with a Pre-Collision System (PCS) as optional equipment. In these vehicles, the PCS may unexpectedly activate and apply the brakes when the radar detects a steel joint or plate in the roadway as an object.
Condition in the official record
Toyota Motor Engineering & Manufacturing (Toyota) is recalling certain model year 2013-2015 Avalon and Avalon Hybrid vehicles manufactured October 19, 2012 to October 27, 2015 and 2013-2015 Lexus ES350 and ES300h vehicles manufactured June 18, 2012 to July 6, 2015. The affected vehicles are equipped with a Pre-Collision System (PCS) as optional equipment. In these vehicles, the PCS may unexpectedly activate and apply the brakes when the radar detects a steel joint or plate in the roadway as an object.
Which vehicles the source covers
- NHTSA model names: ES350. Model years: 2013, 2014, 2015.
- NHTSA campaign 15V728000
- The complete campaign lists 30,812 potentially affected units across all listed vehicles.
- A make, model and year match does not establish VIN eligibility.
Safety recall eligibility is based on the VIN and campaign scope, not ordinary warranty mileage. Check the complete VIN even when the vehicle is outside its original warranty.
Component in the source: FORWARD COLLISION AVOIDANCE: CRASH IMMINENT BRAKING
Published recall remedy
Toyota will notify owners, and dealers will replace certain PCS components, free of charge. The recall began on July 28, 2016. Owners may contact Toyota at 1-888-270-9371. Toyota's numbers for this campaign are F1V and F2E.
Consequence in the NHTSA record: A vehicle that unexpectedly brakes increases the risk of a crash.
Toyota will notify owners, and dealers will replace certain PCS components, free of charge. The recall began on July 28, 2016. Owners may contact Toyota at 1-888-270-9371. Toyota's numbers for this campaign are F1V and F2E.
Limit: Confirm VIN eligibility and current remedy instructions with the manufacturer.
Check the 17-character VIN at NHTSA.gov/recalls and ask the manufacturer whether this campaign remains open for the vehicle.
Limit: The model-year list is not proof that an individual vehicle is affected.
Evidence for this issue
- 15V728000: NHTSA campaign 15V728000
NHTSA safety recall · 2015-11-03
Official component, defect, consequence and remedy; checked 2026-10-18.
Confirm who pays before authorizing work
A recall remedy follows the campaign and VIN eligibility. A service bulletin provides diagnosis or repair instructions; it does not by itself promise payment. Manufacturer warranty extensions and support programs have their own conditions.
Compare recalls, bulletins and warranty extensions →Keep a current problem separate from future coverage
These files do not supply a shop quote. Ask for a diagnosis and written estimate, then check recall remedies or existing coverage. A new vehicle service contract generally excludes pre-existing conditions.
Prepare a useful description for the mechanic →Each file retains its original source review date. Historical remedy wording can change; check the current manufacturer notice and NHTSA VIN lookup for your vehicle. The separately dated NHTSA counts elsewhere on this page use a different dataset and scope.
Read the evidence for this vehicle
What can the data tell you about 2013 Lexus ES 350?
No model-specific individual-repair price keys are retained for Lexus ES 350 in this library. Generic parts and labor estimates, public records and separate annual cost references may still be available.
An unmatched specification is an information gap. Do not borrow an engine or drivetrain from another year.
Recall and communication counts describe records. They cannot establish a breakdown probability or current VIN status.
Price-key audit reviewed October 18, 2026; EPA source snapshot 2026-08-07. Individual-repair ranges and annual repair-budget references are different datasets.
Cost-library audit
The evidence behind a repair estimate
30 of 44 repair categories have verified national benchmarks; 14 retain planning assumptions. Old model-specific ranges were removed because this refresh did not reverify them.
44 repair categories; a content audit, not a market survey
See the analysis, charts and method →Campaign-reference audit
One campaign can create many entries
1,200 selected recall files resolve to 780 distinct campaign IDs after compact references are normalized and checked against official NHTSA records. Files and campaigns are different counting units.
1200 selected recall files; normalized references checked against official NHTSA records
See the analysis, charts and method →