← New search

1982 Toyota Celica

Owner reports · Recalls · Investigations

Limited comparison data

There is not enough comparable history to draw a useful model-year comparison.

About this comparison →

How this year compares

Owner complaints by model year

Other model years Selected year
Compare all Celica years →

Counts vary with age, sales and reporting. They are not failure rates.

What owners reported most

Tap a category to read its complaints. One report may name several components.

When problems were reported

Mileage at the reported incident

Limited mileage data: 2 of 4 reports include usable mileage. There isn’t enough coverage to show a useful chart.

NHTSA’s mileage field refers to the reported incident, not necessarily the filing date. This shows report counts, not the likelihood of a failure.

What to inspect

Issues worth paying extra attention to based on owner reports.

  • Seat Belts. Review the 2 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →
  • Power Train. Review the 1 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →
  • Structure. Review the 1 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →

NHTSA owner reports · September 18, 2026 snapshot.

1 crash reports0 fire reports1 injury reports

Structure complaints

1 reports
Clear category filter
Mileage unknown · Oct 30, 2003
StructureCrashInjury

SOMEONE NEEDS TO TELL OFF. [XXX] THERE ARE PENALTIES FOR FILING A FALSE POLICE REPORT. MY NAME IS [XXX]. ON 23 OCT 03 1530 HRS I WAS DRIVING E ON W. WASH. BLVD. AND INTO THE L T/L INTO THE INTERSECTION WHILE THE ARROW WAS G. TRAFFIC KEPT ME FROM TURNING UNTIL THE LIGHT WAS R. WHILE TURNING THE LIGHT FLASHED FROM ONE OF 4 CAM…

Read full complaint

SOMEONE NEEDS TO TELL OFF. [XXX] THERE ARE PENALTIES FOR FILING A FALSE POLICE REPORT. MY NAME IS [XXX]. ON 23 OCT 03 1530 HRS I WAS DRIVING E ON W. WASH. BLVD. AND INTO THE L T/L INTO THE INTERSECTION WHILE THE ARROW WAS G. TRAFFIC KEPT ME FROM TURNING UNTIL THE LIGHT WAS R. WHILE TURNING THE LIGHT FLASHED FROM ONE OF 4 CAMERAS AND A WEST BOUND DRIVER RAN THE RED LIGHT AT 70 MPH, DIDN'T TRY TO STOP AND B/S MY CAR BEHIND THE PASS. D/P, SPINNING MY CAR UNTIL IT WAS FACING THE SOUTH EAST CORNER OF THAT INTERSECTION. THE S B/L OF BEETHOVEN ST. WAS OCC. BY A 1 TN VAN THAT WAS STOPPED, WAITING TO TURN R AFTER THE LIGHT TURNED G. IT WASN'T DAMAGED. THE DRIVER LEFT HIS VAN, APPROACHED ME AND SAID "GET YOUR [XXX] OUT OF MY WAY!". I SAID I HAD TO STAY THERE UNTIL THE POLICE ARRIVED. WHEN THEY DID THE OFF ASKED ME WHAT HAPPENED. I TOLD HIM EVERYTHING I STARTED THIS MESSAGE WITH. THE OFF TOLD THE PM I'M A VET (WITHOUT LOOKING IN MY WALLET) AND TAKE ME TO THE VA. HE DIDN'T ASK ME WHERE I WANTED MY VEHICLE TOWED TO(UNLIKE WHAT IS STATED IN THE REPORT) OR LOOK AT THE REG. AND INS. CARD, BUT DID ASK ABOUT MY NAME, ADDRESS, PHONE NUMBER, AND IF I WAS INJURED. THE REPORT STATES I'M THE OWNER, CA [XXX](NOT); MY INSURANCE AGENT IS MERCURY (NOT), IT'S 21ST CENTURY, POLICY #[XXX]; MY CAR WAS FACING NW AFTER THE ACCIDENT(NOT); THE VAN WAS [XXX]. ON THE L SIDE(NOT); MY CAR WAS DAM. ON THE R SIDE(NOT); THE OTHER DRIVER DIDN'T RUN THE R LIGHT, I TURNED L INTO OC TRAFFIC ON A Y LIGHT AND I CAUSED THE ACCIDENT(NOT). THE POLICE DIDN'T TAKE PHOTOS OF THE ACCIDENT SCENE. I TOLD THE P/M ABOUT THE CHEST, HEAD, NECK, LOWER BACK AND L ARM PAIN. WHEN I WENT TO CULVER CITY PD TO PICK UP THE REPORT I ASKED TO GET A COPY OF THE PHOTO AND THE OFF. SAID THERE WASN'T ONE. MY INSURANCE AGENT SAID I HAVE TO DISCUSS REPORT WITH THE OFFICER WHO FILED IT," IT IS SOLELY THE BUSINESS BETWEEN YOU AND THAT POLICE OFFICER." I DON'T AGREE. *LA INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6). *TR

NHTSA ODI #10045117

Official recalls

1

86V132000 · Vehicle Speed Control

Oct 2, 1986

SOLDERED TERMINALS OF THE CRUISE CONTROL COMPUTER MAY DEVELOP CRACKS DUE TO IMPROPER APPLICATION OF THE COATING TO THE PRINTED CIRCUIT BOARD. CONSEQUENCE OF DEFECT: CONTINUED USE OF CRUISE CONTROL COULD LEAD TO COMPLETE SEPARATION OF SOLDERED TERMINALS AND CIRCUIT FAILURE; ENGINE SPEED WOULD INSTANTLY RACE AND VEHICLE COULD SUDDENLY ACCELERATE, POSSIBLY RESULTING IN AN ACCIDENT.

Consequence & remedy

Consequence: Not supplied

Remedy: REPLACE CRUISE CONTROL COMPUTER, IF NECESSARY.

Model-level recall history does not show whether a particular VIN is affected or has received a repair. Check a VIN with NHTSA ↗

NHTSA investigations

1

EA85045 · Sudden Acceleration

Opened Aug 30, 1985 · Closed Feb 18, 1988

Status: closed (inferred from source dates) · Vehicle Speed Control:linkages

SUMMARY:TOYOTA RECALLED APPROXIMATELY 5,000 1982 CRESSIDA, CELICA, ANDSUPRA MODELS TO REPLACE POTENTIALLY DEFECTIVE CRUISE CONTROL COMPUTERSIN SEPTEMBER 1986. THEY REPORT THAT NO OTHER DEFECT OR PROBLEM HAS BEENFOUND THAT WOULD CAUSE SUDDEN ACCELERATION.ANALYSIS:THE CRUISE CONTROL SYSTEM IN THE SUBJECT VEHICLES MAY HAVEPROBLEMS OTHER THAN THE DEFECT FOR WHICH TOYOTA RECALLED. HUMAN ERRORIS ALSO CONSIDERED TO BE A PRIMARY CAUSE IN MANY OF THESE INCIDENTS.STATUS:INVESTIGATION OF THE CRUISE CONTROL AND OTHER VEHICLE SYSTEMSCONTINUES AMONG THE SUBJECT VEHICLES WHICH HAVE NOT BEEN RECALLED.PEDAL GEOMETRY AND OTHER HUMAN FACTORS FOR THE SUBJECT VEHICLES ARE BEINGCOMPARED TO PEER GROUP VEHICLES. CLOSED 2/18/88. RECALL 86V-132.===