CANADA · VEHICLE RESEARCH

2013 SRT Viper

Canadian recalls & official vehicle records

Two-seaterM62 source configurations

Evidence updated Nov 17, 2026 · Sources

SRT
SRT ViperMatching photograph not available
Model-family image · year, generation and trim may differ.
1Recall campaignsTransport Canada · exact matches
UnavailableCanadian complaintsNot available in our dataset
2Efficiency configurationsNRCan · Canadian test data
Source-ledResearch approachNo unsupported reliability grades
FROM RESEARCH TO YOUR NEXT CAR

2013 SRT Viper 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 year2013
Vehicle classTwo-seater
TransmissionM6
Engine8.4 L
Recall sourceTransport Canada
Efficiency configurations2
VIN repair statusCheck with manufacturer
View source specifications

Safety Recalls (1)

Canadian archive snapshot, including historical or superseded records.

Airbag

On certain SRT model vehicles, the front seat position sensors may have been incorrectly installed. As a result, frontal airbags could deploy with a lower velocity than intended, increasing the risk of injury to the seat occupant. Correction: Dealers will m…

Read the complete source summary

On certain SRT model vehicles, the front seat position sensors may have been incorrectly installed. As a result, frontal airbags could deploy with a lower velocity than intended, increasing the risk of injury to the seat occupant. Correction: Dealers will measure the air gap between the seat track position sensor and the seat track detection plate. Seat tracks with an excessive air gap will have a metal shim installed onto the track detection plate.

Transport Canada 2014384 · Sep 9, 2014Official 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 SRT Viper 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 2013 SRT Viper.

1. Check recall repairs

1 matched Canadian recall campaign. 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
1
Canadian complaint records
Unavailable
Efficiency configurations
2
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
Viper
M6
Z 8.4 L engine16.9 L/100 kmData unavailable
Viper GTS
M6
Z 8.4 L engine16.9 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.

Viper · M6 — source specification details
Vehicle classTwo-seater
Engine displacement8.4 L
Cylinders10
City fuel consumption20.0 L/100 km
Highway fuel consumption13.0 L/100 km
Tailpipe CO₂ emissions389 g/km
Viper GTS · M6 — source specification details
Vehicle classTwo-seater
Engine displacement8.4 L
Cylinders10
City fuel consumption20.0 L/100 km
Highway fuel consumption13.0 L/100 km
Tailpipe CO₂ emissions389 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 Airbag campaign (2014384).
  • 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 2013 SRT Viper, 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 2014384 (Airbag). A model-year match does not establish that this VIN is affected.
  3. 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 2013 SRT Viper.

VISIBILITY
2
ELECTRICAL SYSTEM
1
SEATS
1
VISIBILITY/WIPER
1

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
2013-121
2014-031
2014-071
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 mi3
25,000–49,999 mi0
50,000–99,999 mi0
100,000–149,999 mi0
150,000+ mi0
Missing or excluded mileage0

3 of 3 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 flagged0US complaint allegations
Fire flagged0US complaint allegations
Towed flagged0US 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.

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

RQ15004 · Software security vulnerability

On July 23, 2015, Fiat Chrysler Automobiles (FCA) launched Safety Recall 15V-461 to remedy security vulnerabilities in approximately 1.4 million model year (MY) 2013 through 2015 vehicles equipped with Uconnect head units (HU) 8.4A (RA3 radio) and 8.4AN (RA4 radio) manufactured by Harman International.On July 24, 2015, the Office of Defects Investigation (ODI) opened Recall Query, RQ 15-004, to investigate HU security vulnerabilities and remedy effectiveness in the recalled population and to determine whether similar units have been supplied for use in other FCA vehicles.In an August 11, 2015 letter, FCA submitted a second Part 573 safety recall report expanding the scope of the Uconnect RA4 model radio to include additional 7,810 MY 2015 Jeep Renegade vehicles manufactured from September 18, 2014 through June 25, 2015 (Recall 15V-508).Scope analysis indicated that Uconnect radios installed in FCA vehicles not included in recalls 15V-461 or 15V-508 (subject recalls) are not equipped with built-in cellular access or short range wireless communication features and, thus, do not contain the security vulnerabilities addressed by the subject recalls. SUBJECT VEHICLES: MY2014 through 2015 Dodge Durango, Jeep Grand Cherokee and Jeep Cherokee sport utility vehicles; MY2013 through 2015 Ram 1500, 2500, 3500 and 4500/5500 pickup trucks; MY2013 through 2015 Dodge Viper vehicles; and MY2015 Chrysler 200, 300, Jeep Renegade, Dodge Charger and Challenger vehicles.According to FCA, long and short range wireless vulnerabilities identified in the recalled vehicles could allow unauthorized third-party access to, and manipulation of, networked vehicle control systems.Successful exploitation of the vulnerabilities, coupled with reverse engineering of networked microprocessor control modules, could result in unauthorized manipulation of vehicle control systems. This unauthorized manipulation of vehicle controls and systems could expose the driver, vehicle occupants or other highway users to an increased risk of injury.FCA and its network provider, Sprint, conducted a nationwide campaign to block access to a radio communications port that was unintentionally left open.On July 27, 2015, short range wireless vulnerabilities were also blocked.Finally, third party security evaluation and regression testing identified vulnerabilities that were either remedied by Sprint or through updates to the FCA Uconnect software.ODI identified a total of 30 complaints or field reports on unique vehicles submitted by FCA (29) or received by NHTSA (1) alleging incidents of theft from a vehicle or anomalous performance that the owner alleged were caused by, or may have been caused by, remote hacking.Twenty-six (87%) of these reports were submitted after a magazine article was published on July 21, 2015, describing the remote hacking of an FCA vehicle by researchers who were able to affect the operation of various vehicle control systems, including the service brakes, steering, throttle and ignition.Most of the complaints involved vehicle systems that were not safety critical (e.g., complaints related to radio, navigation system, or air-conditioning control) and did not affect vehicle control.Three complaints reported engine stalls.One owner reported sudden unintended acceleration allegedly related to hacking.None of the complaints or field reports reviewed involved the steering and braking vehicle control effects demonstrated by the research hackers prior to the recall.There were no confirmed incidents of hacking in any of the records reviewed by ODI.The remedies completed by Sprint and FCA appear to have eliminated vulnerabilities that mi

Opened 20150724 · Closed 20160105

Official investigation archive ↗
Communication 10248517

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 10248509

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 10244356

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 10244348

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 10243209

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 10243208

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 10242717

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 10239957

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.