Engine began knocking, brass colored shaving in drained oil due to bearing damage. This vin is not covered by the recall scope
NHTSA ODI 11749666
Home · 2016 Acura MDX Sport Hybrid · Complaints
These are the actual owner complaints behind this car’s reliability verdict, filed with the federal government, unedited. They’re unverified reports, not confirmed defects: read them as leads for your pre-purchase inspection, not a diagnosis.
153 of 359 complaints match · Engine · clear filters · page 1 of 7
Engine began knocking, brass colored shaving in drained oil due to bearing damage. This vin is not covered by the recall scope
NHTSA ODI 11749666
I am filing a safety and compliance complaint regarding execution of Federal Recall Campaign #26V365 by Valley Stream Acura and sales fraud by Paragon Acura. I purchased this 2016 Acura MDX from Paragon Acura on May 29, 2026. I have driven it only 550 miles, placing it strictly within the statutory New York State 60-Day Used Car Lemon Law Warranty window. A certified 6-page independent ASE forensic report documents that Valley Stream Acura bolted the federal recall brackets directly onto severely cracked rear control arms and rusted struts without disclosure. Furthermore, Paragon Acura forced a brand-new front control arm link onto a deeply pitted, scaling, and structurally compromised front steering knuckle to mask pre-sale defects, signing a false NYS highway safety certification. The vehicle was released to me with a bone-dry, empty engine cooling loop, creating an immediate fire hazard. Acura Corporate (Case #16437213) refuses to issue a corrective directive, willfully leaving a non-compliant vehicle on public roads.
NHTSA ODI 11749008
Started (first noticed)check engine light flashing turned radio down right of way and noticed engine knocking with no warning still 40% engine oil life left. Had test done P0303 misfire on cylinder 3 and rod bearing knock was told need an engine . Had all oil changes and maintenance done on time. ran my vin and unfortunately was told it is not covered under recall.
NHTSA ODI 11748232
My 2016 Acura Max sha awd has 124 k on it and the other day I was driving down the road and my engine light went on than I lost power down to 20 mph and heard a knocking noise from the engine like the rod bearing broke or something I’ve noticed the recall on the engine for some Acura 2016-2025 3.5v6 engines but Acura is saying my model car was not in the recall list which I can’t understand why if it has the same engine 3.5 v6 with the same rod barring issue as the ones on the list being recalled . The issue is with all 2016-2025 Acura Mdx models that have the 3.5 v6 in it .
NHTSA ODI 11747775
I was driving on the highway. All of a sudden, my engine started making knocking noises. Shortly after that, the car started to lose power, and immediately the low engine oil light came on. I pulled over immediately to check the engine oil level. Oil level was normal. I restarted the car, but the mechanical knocking noise was evident and did not sound right. Towed the car to the closest Acura Dealership. Diagnostics states that engine has ceased and would not crank. Replacements engine is required and would costs approx. $4200. Acura has a recall on some 2016-2020 MDX for similar engine issues, but my VIN did not qualified. The symptoms i exprienced is very similar to what was described in the recall. Acura representative denied any goodwill support/help.
NHTSA ODI 11746710
Our 2016 Acura MDX SH-AWD has the exact same engine problem/damage caused by the Connecting Rod Bearing recall. Our vehicle displayed the exact symptoms described by countless other MDX owners including owners who have vehicles both on & not included on the current recall list.
NHTSA ODI 11746102
This make and model has the same problems with the engine rod bearings it’s the v6 3.5L
NHTSA ODI 11745072
FOUND #4 CYLINDER MISFIRE - METAL CONTAMINATION SPUN A BEARING INTERNALLY INSIDE THE ENGINE. RECOMMEND REPLACING THE ENGINE. SEE QUOTES BELOW: RECOMMEND AT THE SAME TIME AS THE ENGINE REPLACEMENT - STARTER, TIMING BELT, SPARK PLUGS, AND VALVE. Found #4 cylinder misfire – metal contamination – spun a bearing internally inside the engine. Recommend replacing the engine.” After researching this issue, I became concerned that this failure appears very similar to the widely reported connecting rod bearing failures associated with Acura/Honda 3.5L V6 engines and Recall 23V-751. The symptoms in my vehicle closely match the issues described in the recall and related investigations, including: connecting rod bearing failure, spun bearing, internal engine damage, metal contamination, cylinder misfire, and complete engine failure. Additionally, I understand that the National Highway Traffic Safety Administration (NHTSA) has expanded investigations into similar engine failures affecting Acura and Honda vehicles outside the original recall VIN population.
NHTSA ODI 11740745
The contact owns a 2016 Acura MDX. The contact stated while driving at an undisclosed speed, the transmission independently shifted into neutral. The vehicle was driven to the shoulder of the road. The contact stated that several unknown warning lights were illuminated. The contact stated that the event was scary. The contact stated that the vehicle was so hot inside. The contact crawled to the passenger's seat and exited the vehicle. The vehicle was towed to an independent mechanic where it was diagnosed with a failed engine. The contact was informed that the engine needed to be replaced. The vehicle was not repaired. The vehicle was towed to the dealer, however the vehicle was not inspected. The contact was informed that the repair was not covered under any unknown recall. The manufacturer was made aware of the failure. The contact was informed that the repair was covered under an unknown recall which had a similar failure description. The contact was advised to take the vehicle to the dealer. The failure mileage was approximately 150,000.
NHTSA ODI 11738155
When driving at highway speeds there randomly is a full loss of engine power for 3 to 5 seconds. Each time this has occurred I was on the highway and depressing the gas pedal further to either pass another car or because I'm driving up and incline. For several seconds the car looses all power and begins slowing. Traffic approaching rom behind may have to apply brakes. I am unsure whether it's the transmission disconnecting from the engine, or the engine dropping to idle speed, I have tried pressing the gas pedal further and also tried the paddle shifters to force a downshift, and neither has any effect. I have been to the dealer multiple times and they can't re-create the issue so they dismiss it.
NHTSA ODI 11737458
The contact owns a 2016 Acura MDX. The contact stated that upon start of the vehicle, the engine entered limp mode as a check engine light appeared on the instrument panel. The vehicle failed to accelerate above 35 MPH as the contact was forced to restart the vehicle. The vehicle resumed normal driving after restart and the contact called the dealer for an appointment. While driving the vehicle to the dealer, the failure returned as an abnormal, banging sound began to emit from the vehicle. Due to the failure, the vehicle was towed to the dealer where the vehicle was diagnosed with rod bearing connector failure which resulted in engine failure. Upon investigation, the contact discovered NHTSA Action Number:PE25008(Engine) which the contact linked to the failure. The manufacturer was also notified of the failure where he was informed that the vehicle was not included in the recall and was offered the chance to apply for a goodwill financial assistance for the repair of the engine. The vehicle was not repaired and remained in the dealer's possession. The failure mileage was approximately 148,000.
NHTSA ODI 11735571
My 2016 Acura MDX (purchased new January 2016) has a confirmed failure of the 9-speed automatic transmission warmer (ATF warmer), causing engine coolant and ATF fluid to cross-contaminate. The failed warmer is still in the vehicle and available for inspection. In the last week of March 2026, I noticed the engine cooling fan continuing to run after shutting off the vehicle — an abnormal symptom that prompted me to bring the car in for service. No check engine or transmission warning lights were illuminated. On March 28, 2026, Blue Sky Tire and Auto (Cumming, GA) performed a diagnostic inspection confirming coolant and ATF cross-contamination. The technician also physically inspected the transmission warmer manufacturing date stamp, confirming it falls within the defective manufacturing date range identified in Acura Service Bulletin 17-009 (October 6, 2017), which states that improperly manufactured warmers allow coolant and ATF to mix, potentially causing permanent engine and transmission damage. The vehicle has not been inspected by an Acura dealership for this failure. However, an American Honda Customer Relations case has been opened (Case # XXX) with a case manager assigned to evaluate the warranty claim under the 10-year/unlimited mileage warranty extension issued by American Honda for this exact defect. This failure poses serious safety risks — loss of transmission lubrication can cause sudden transmission failure at speed, and coolant-ATF mixing can cause engine overheating, both potentially resulting in loss of vehicle control. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA ODI 11734011
I was driving down the interstate, the engine started making noise, a saw big puff of Blue smoke in the vehicle. Lost all power
NHTSA ODI 11732226
Customer reports: - vehicle will not start - died while backing up and wouldn't restart - no warning in car and safety at risk as a result - towed car to auto mechanic who provided this information below Check and advise: - Found starter motor tries to crank the engine over but never completes more than a partial engine revolution during each starting attempt, using jumper packs do not help, fully charged and tested battery and found battery tests bad, installed tester battery for diagnostic purposes and found engine still wont crank, attempted to rotate engine via crank pulley bolt and pry bar and found engine will not rotate indicating engine is seized due to some sort of internal engine issue, suspect possible connecting rod bearing failure but cannot confirm without significant engine disassembly. - This issue (apparently its a widely known problem on this engine and there is an active recall campaign developing): Acura MDX 2016 has a recall but my VIN # is not showing up in it. However, I strongly believe it is the same issue and Acura should expand their recall to include more vehicles, including my own.
NHTSA ODI 11726781
My car shuts off when idling and goes into neutral when stopping at stop signs or yeilding in a rotary
NHTSA ODI 11725038
Engine has 97,000 miles and has been meticulously maintained with current rod bearing failure.
NHTSA ODI 11724350
I have a 2016 Acura MDX with a 3.5 engine that had a #2 connecting rod failure. I took the information to my local Acura dealer and they had told me that the engine was outside of the recall on the bearing failures on other 3.5 engines. Due to the related failure patterns, I believe that the engine should have been replaced in accordance with the failed engine connecting rod recall 24-001. I had to bear the cost of a used engine to install into the vehicle . I have attached a photo of the failed #2 connecting rod and the engine code.
NHTSA ODI 11721708
We have a 2016 Acura MDX. The connecting rod bearing caused the engine to be damaged, resulting in a knocking noise, and decreased engine output. This resulted in the engine needing to be replaced. The reason for the engine failures was the exact issue in NHTSA Recall 23V-751. While our vehicle is the same year, make and model of the recall, we are being told that because our manufactured date falls a few months outside of this recall, Honda will not pay for the repairs. We therefore had to pay for the repairs out of pocket in the amount of $6,170.59. We are asking the NHTSA to expand the recall as this failure obviously occurred outside the previously issued recall window.
NHTSA ODI 11711926
I was driving my Acura MDX(2016 7900 miles) on a multi-lane highway, the vehicle experienced a sudden and significant loss of engine power without prior warning. This occurred during normal traffic conditions and reduced the vehicle’s ability to accelerate and maintain speed, creating a safety risk for my family and surrounding vehicles. After the loss of power, a rattling/knocking noise from the engine became apparent. A check engine light appeared after the initial event which later went away. The vehicle was first inspected by an authorized dealer, who recommended replacement of spark plugs and later a timing belt as part of the diagnostic process. These actions did not address the underlying issue. The vehicle was subsequently inspected by an independent repair facility. The independent mechanic confirmed internal engine damage by finding metal shavings in the oil and diagnosed rod bearing failure, requiring complete engine replacement. The failed engine is available for inspection upon request. The independent mechanic also referenced an Acura/Honda technical service bulletin related to rod bearing failures affecting similar engines and model years. The vehicle has been routinely serviced at authorized Acura dealerships, including regular oil changes, prior to the failure. No external damage, misuse, or lack of maintenance was identified during the inspection by the dealership. The issue was later inspected by the manufacturer’s authorized dealer. The manufacturer declined assistance, stating the failure was not considered a defect. There were no warning lamps, messages, or noticeable symptoms prior to the initial loss of power.
NHTSA ODI 11711246
The engine failed and acura tech said it was connecting rod failure. There is a Safety recall from Acura 23-036 and an investigation by NHTSA # RQ24013. Acura stated my VIN is not part of the recall although it's the same issue.
NHTSA ODI 11710401
NHTSA Incident Report Vehicle: 2016 Acura MDX Date of Incident: [XXX] Location: Oregon (Oregon Coast to Portland) Mileage: 110, XXX Incident: During a 60-mile road trip, the vehicle unexpectedly shut off and shifted into neutral. The car coasted safely to a stop. Earlier, we had noticed a slight knocking sound when starting the engine, but no other issues were present. A tow truck attempted to jump-start the vehicle without success. Ron Tonkin Acura later confirmed engine failure. The vehicle has been regularly maintained, with documentation, and had no prior engine problems. Acura has stated that this failure is not part of their rod bearing recall. No warning lights appeared before or during the incident. Safety Concern: The sudden engine shutdown created a serious safety risk while driving. Requested Action: Investigation into potential defect causing unexpected engine shutdown in the 2016 Acura MDX. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA ODI 11709567
While my teenage son was driving on busy interstate highway the engine began making extremely loud noises and smoking while losing power. Driver was unable to make it to a safe exit and had to pull over with limited shoulder, in a very dangerous spot. All oil leaked out of the engine an onto the roadway, also a hazardous and dangerous situation. Car was towed to Acura dealership and inspected. Catastrophic engine damage - part of the engine rod assembly was launched through the oil pan and lodged in the air conditioning compressor. Vehicle had 87K miles and all service was performed. Complaints that the engine was lagging and making noises at low RPM's had been expressed to Acura for years. I was told that unless a check engine light came on there was no way to know what was wrong.
NHTSA ODI 11707361
I purchased a 2016 Acura MDX during the summer of 2025. I am the second owner. In November 2025, the engine starting experiencing engine knock later to be confirmed as rod bearing knock. This vehicle if a 2016 MDX and the manufacturing date is October 2015. There is a rod bearing recall for 2016 MDX's however, my VIN is not included in this recall which is ludicrous as it is experiencing the same issues as the recall with only 80,000 miles on the engine. I urge you to widen the recall to include 2015 MDX vehicles as there is no way this Acura MDX should be experiencing rod bearing issues on a well taken care of vehicle.
NHTSA ODI 11704408
On November 28th at 10:00 AM, my 2016 Acura MDX suffered a catastrophic and sudden engine failure that resulted in a total loss of motive power. I was driving on Scott Boulevard in Santa Clara, just after exiting the Central Expressway. I first heard a loud metallic noise, and the engine immediately seized and shut down. The vehicle started slowing rapidly on a busy street, creating a life-threatening safety hazard for myself and other drivers. The car spontaneously shifted into Park and it was difficult to manually shift into Neutral for towing. Thankfully, no accident occurred. The failure is due to a connecting rod bearing failure and engine seizure. This is the identical safety-related manufacturing defect acknowledged in Safety Recall 23V-751 and is currently the subject of the ongoing NHTSA Preliminary Evaluation (PE25008), which covers the same 3.5L V6 engine in vehicles outside the original recall, including the 2016 MDX. I feel responsible to report the incident to NHTSA to take precautions on the matter. Regards, [XXX] INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA ODI 11702235
The contact owns a 2016 Acura MDX. The contact stated that while driving approximately 15 MPH, there was an abnormal sound coming from the engine compartment. There were no warning lights available. The vehicle was taken to a dealer, where it was diagnosed with a fractured connecting rod bearing, and the engine needed to be replaced. The vehicle was not repaired. The manufacturer was notified of the failure. The failure mileage was approximately 97,000.
NHTSA ODI 11700400
Working with the data? Download all 359 complaints as CSV · fetched from NHTSA July 20, 2026