- May 4: 2024 Nissan Sentra Driveshaft Recall Announced recalls | 0 days ago
- March 24: Nissan Pathfinder Radiator Cooling Fan Recall Needed, Alleges Lawsuit news | 41 days ago
- March 20: Nissan LEAF Backup Camera Recall Affects 70,000 Cars recalls | 45 days ago
- March 11: Nissan Versa Cars Lose Power While Driving: Investigation investigations | 54 days ago
- March 10: Nissan Pathfinder and Infiniti QX60 SUVs Recalled recalls | 55 days ago
Fuel Cover Won't Close
2013 Nissan Altima
This problem may be covered under warranty. Ask your Nissan dealer.
CarComplaints.com Notes: The 2013 Nissan Altima has multiple problem trends including the CVT transmission, and now that this model is out of warranty, it earns our "Avoid Like The Plague" badge.
Owners complain about vibration and transmission failure related to the CVT (Continuously Variable Transmission), a whining noise from the power steering pump, and constant windshield problems that appear to be the result of poor design.
Be warned: the 2014 & 2015 Nissan Altima appears to share these same problems.
2.0
hardly worth mentioning- Typical Repair Cost:
- No data
- Average Mileage:
- 11,600 miles
- Total Complaints:
- 1 complaints
Most Common Solutions:
- replaced fuel cover release plunger (1 reports)
fuel system problem
Helpful websites
- No one has added a helpful site for this 2013 Altima problem yet. Be the first!
A D V E R T I S E M E N T S
This problem just started a couple weeks ago when I was at a gas station fueling up. Pulled the auto-release of the fuel cover. Worked like normal. After fueling up - the cover would not close. It was as if something was blocking it.
I was going to the Dealer the next week to look at my CVT problem anyway and pointed it out. They ended up replacing the fuel cover release plunger. Even though it felt free ... it was not free enough. Covered under warranty (my car was at 23 months).
Update from Jan 21, 2016: Dealer replaced the cover release plunger under warranty. Even though it seems like it was free, it was not free enough. This fixed the problem.
- Perry F., Winnipeg, MB, Canada