Auto Recall Watch
U.S. public vehicle records

1999 Saturn EV1: complaints, problems and recalls

Explore the records behind recurring owner reports.

Key facts

0 owner complaints analyzed

4 distinct recall campaigns

Not available median reported failure mileage

Scope: 1999 model year. Data updated: . 0 complaints include usable failure mileage. View data status.

Owner-reported patterns

Most common problems

No owner complaints are recorded for this selection. A complaint can name multiple components.

Component breakdown

Number of unique complaints naming each component. Top eight shown.

No usable records for this chart.

Component breakdown data
CategoryCount

No records.

Reported problems by failure mileage

Complaint counts in mileage bands. These are not failure rates per vehicle or mile.

Under 25,000
0
25,000 to 49,999
0
50,000 to 74,999
0
75,000 to 99,999
0
100,000 to 149,999
0
150,000 and above
0
Reported problems by failure mileage data
CategoryCount
Under 25,0000
25,000 to 49,9990
50,000 to 74,9990
75,000 to 99,9990
100,000 to 149,9990
150,000 and above0

Under 25,000: 0; 25,000 to 49,999: 0; 50,000 to 74,999: 0; 75,000 to 99,999: 0; 100,000 to 149,999: 0; 150,000 and above: 0

No usable failure mileage is recorded. 0 complaints have missing, zero or invalid mileage.

Complaints over time

Year the complaint was filed, not the vehicle model year or incident year. The snapshot year is partial.

No usable records for this chart.

Complaints over time data
CategoryCount

No records.

Pattern summary

There is not enough complaint evidence to summarize patterns.

Calculated from recorded counts. An AI narrative has not been published for this selection.

Examples from the source records

Examples provide context, not a representative sample or a verified diagnosis.

Recall history

4 distinct campaigns affect this selection. Announcement dates below are different from vehicle model years. A campaign may cover multiple years.

00V369000 · Service Brakes, Hydraulic

Reported: 2000-11-13 (November 13, 2000)

VEHICLE DESCRIPTION: ELECTRIC VEHICLES. THESE VEHICLES WERE PRODUCED WITH WHEEL SPEED CIRCUITRY IN THE BRAKE TORQUE CONTROL MODULE (BTCM) WHICH CAN CEASE TO OPERATE PROPERLY.

Consequence: IF THIS OCCURS, INVOLVED VEHICLES WILL EXHIBIT ONE OR MORE OF THE FOLLOWING: A LOSS OF FRONT BRAKE ASSIST, A DISABLED REAR BRAKE SYSTEM, A DISABLED ANTI-LOCK BRAKE SYSTEM, AND/OR A DISABLED REGENERATIVE BRAKE SYSTEM. THIS COULD INCREASE BRAKE PEDAL TRAVEL AND VEHICLE STOPPING DISTANCE.

Remedy: DEALERS WILL REPLACE THE BTCM, THE BALLSCREW ASSEMBLIES IN THE BRAKE PRESSURE MODULATOR VALVE, AND INSTALL NEW SOFTWARE.

NHTSA campaign record ↗
00V370000 · Interior Lighting

Reported: 2000-11-13 (November 13, 2000)

VEHICLE DESCRIPTION: CERTAIN GENERATION II ELECTRIC VEHICLES FAIL TO COMPLY WITH THE REQUIREMENTS OF FMVSS NO. 101, "CONTROLS AND DISPLAYS." THESE VEHICLES WERE PRODUCED WITH A COURTESY LAMP CONTROL CIRCUIT IN THE RIGHT-HAND JUNCTION BLOCK WHICH CAN FAIL. IF THIS OCCURS, THE INTERIOR LAMPS WILL REMAIN ILLUMINATED AND CANNOT BE CONTROLLED BY THE DRIVER ONCE THE DOORS ARE CLOSED AND THE VEHICLE IS IN MOTION.

Consequence: IF THIS WERE TO OCCUR DURING A NIGHT-TIME DRIVING SITUATION, THE DRIVER'S VISION COULD BE IMPAIRED.

Remedy: DEALERS WILL REPLACE THE RIGHT-HAND JUNCTION BLOCK.

NHTSA campaign record ↗
00V373000 · Electrical System:Propulsion System:Charging:Cable/Cord:Onboard | Electrical System:Wiring

Reported: 2000-11-13 (November 13, 2000)

VEHICLE DESCRIPTION: GENERATION II ELECTRIC VEHICLES. SOME REPLACEMENT CHARGER RECEPTACLE ASSEMBLIES USED FOR WARRANTY REPAIRS WERE BUILT WITH INTERNAL COMPONENT VARIATION. THIS VARIATION CAN GENERATE ARCING DURING THE CHARGE CYCLE.

Consequence: EXTENDED ARCING DURING THE CHARGE CYCLE COULD LEAD TO A VEHICLE FIRE AND/OR PERSONAL INJURY.

Remedy: DEALERS WILL INSPECT THE SERIAL NUMBER ON THE CHARGE RECEPTACLE AND, IF NECESSARY, REPLACE THE CHARGE RECEPTACLE ASSEMBLY.

NHTSA campaign record ↗
00V374000 · Electrical System:12v/24v/48v Battery

Reported: 2000-11-13 (November 13, 2000)

VEHICLE DESCRIPTION: ELECTRIC PASSENGER VEHICLES AND PICKUP TRUCKS CONTAINING A NICKEL METAL HYDRIDE (NIMH) BATTERY PACK. THESE VEHICLES CONTAIN SOFTWARE WITHIN THE BATTERY PACK MODULE INTENDED TO DISABLE THE VEHICLE FROM BEING DRIVEN IF THE ELECTRICAL RESISTANCE WITH THE BATTERY PACK EXCEEDS A PRESCRIBED VALUE. AFFECTED VEHICLES WILL ILLUMINATE THE "SERVICE NOW" AND "REDUCED PERFORMANCE" TELLTALES AND CONTINUE TO FUNCTION IN A REDUCED PERFORMANCE MODEL INSTEAD OF BEING DISABLED.

Consequence: IF THE TELLTALES ARE IGNORED AND THE AFFECTED VEHICLE CONTINUES TO BE DRIVEN, HEAT COULD BUILD UP AND A FIRE COULD RESULT.

Remedy: DEALERS WILL INSTALL REVISED SOFTWARE IN THE BATTERY PACK MODULE.

NHTSA campaign record ↗
Explore the data

Vehicle analysis explorer

Inspect model-year patterns, reported mileage, monthly activity and the evidence behind each signal.

Data completeness

0 unique complaints in this selection. Analysis snapshot: 2026-09-30.

UnavailableUsable mileage0 / 0 records
UnavailableValid incident date0 / 0 records
UnavailableValid filing date0 / 0 records
UnavailableOrdered incident and filing dates0 / 0 records

Missing, zero and invalid mileage is excluded. Dates after the snapshot are excluded. Examples are limited selections, not a representative sample.

Problems by model year

Model-wide comparison of the eight most reported components across the model. Cells show counts and shares within each model year. Open a cell for source examples.

Component complaint heatmap
Component199519971999
Electrical System:12v/24v/48v Battery
00.0%

No examples available for this selection.

375.0%
ODI 551566

EVI VEHICLE IS ON RECALL BECAUSE A DEFECT IN THE CHARGE PORT COULD CAUSE TO OVERHEAT (00V-069), HOWEVER CONSUMER IS NOT HAPPY WITH IT. YH

Look up ODI 551566 at NHTSA ↗

0Unavailable

No examples available for this selection.

Electrical System
00.0%

No examples available for this selection.

125.0%
ODI 553152

THESE VEHICLES WERE PRODUCED WITH A CHARGE PORT ASSEMBLY THAT MAY FAIL DURING A CHARGING EVENT, RECALL ISSUED HOWEVER OWNER HAS NOT BEEN ABLE TO RECEIVE NEW VEHICLE AT THIS TIME, RECALL SOLUTION IS NOT SUFFICIENT. *ET

Look up ODI 553152 at NHTSA ↗

0Unavailable

No examples available for this selection.

Power Train:Automatic Transmission
1100.0%
ODI 744280

THE CAR FAILS TO ENGAGE INTO REVERSE. I FOUND OUT A LOT OF PEOPLE HAVE THIS PROBLEM WITH THE PRESSURE REGULATOR VALVE IN THE VALVE BODY. *AK

Look up ODI 744280 at NHTSA ↗

00.0%

No examples available for this selection.

0Unavailable

No examples available for this selection.

Darker cells indicate a larger share of submitted complaints. Components overlap. This measures complaint composition, not failure probability.

Failure mileage by component

Median and middle 50% of usable owner-reported mileages. Ranges require at least five records.

Component failure mileage distribution
ComponentMileage range (25th–75th percentile)MedianUsable recordsExamples
No usable records for this analysis.

Complaint and recall timeline

Explore monthly filing activity alongside recall announcements. Up to ten years of monthly history is available.

1 reports2024-102026-09

Solid line: filed complaints. Dashed amber lines: recall announcement dates for this vehicle selection; markers include all recall components. The latest month is partial. Temporal proximity does not establish causation.

Monthly counts, recall campaigns and complaint examples
Monthly complaint and recall timeline
MonthComplaintsCampaigns announcedExamples
2024-100None

No examples available for this selection.

2024-110None

No examples available for this selection.

2024-120None

No examples available for this selection.

2025-010None

No examples available for this selection.

2025-020None

No examples available for this selection.

2025-030None

No examples available for this selection.

2025-040None

No examples available for this selection.

2025-050None

No examples available for this selection.

2025-060None

No examples available for this selection.

2025-070None

No examples available for this selection.

2025-080None

No examples available for this selection.

2025-090None

No examples available for this selection.

2025-100None

No examples available for this selection.

2025-110None

No examples available for this selection.

2025-120None

No examples available for this selection.

2026-010None

No examples available for this selection.

2026-020None

No examples available for this selection.

2026-030None

No examples available for this selection.

2026-040None

No examples available for this selection.

2026-050None

No examples available for this selection.

2026-060None

No examples available for this selection.

2026-070None

No examples available for this selection.

2026-080None

No examples available for this selection.

2026-09 (partial)0None

No examples available for this selection.

Emerging complaint spikes

Complete months in the latest six months with at least 10 complaints, at least twice the preceding 12-month average, and at least three square-root deviations above that average.

This is a descriptive screening rule, not a statistical defect finding. Publicity and reporting changes can increase submissions.

No complete months meet the spike thresholds for this selection.

Equal-age model-year comparison

Model-wide cumulative reports during the first three or five calendar years, starting with the model year (age 0). Only fully elapsed windows are compared.

Age 0Age 1Age 21 reports

1997: 0 complaints · 1999: 0 complaints

Equal observation windows
Model yearThrough age 0Through age 1Through age 2
1997000
1999000
Date coverage across each selected cohort
Date basis for all complaints in selected model years
YearIncident dates usedFiling date fallbacksExcluded dates
1997040
1999000

Incident date is preferred when valid and no later than filing; otherwise filing date is used. Model year approximates age. Equal observation time does not adjust for sales, distance driven or reporting delays. One complaint linked to multiple model years can appear in each cohort.

Components reported together

Each cell counts unique complaints naming both components. Open a nonzero cell for examples.

Component co-occurrence matrix
Component
No usable records for this analysis.

Co-reporting does not establish that one component caused another concern.

Recurring narrative patterns

Specific keyword mentions beyond broad component labels. Matching includes negations and comparisons and does not confirm a diagnosis.

0 patterns with matching reports.

No narratives match the published patterns.