general problems of the 2016 Acura MDX - part 1

I was driving down the interstate, the engine started making noise, a saw big puff of blue smoke in the vehicle. Lost all power.

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.

My car shuts off when idling and goes into neutral when stopping at stop signs or yeilding in a rotary.

Engine has 97,000 miles and has been meticulously maintained with current rod bearing failure.

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 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).

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.

?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).

The Mdx drove perfectly until out of sudden there as a stall, knocking and ticking sound in the engine. It is diagnosed with the connecting rod failure and needs a new engine replacement. The car was well and regularly maintained with oil changes and services as recommended. The following codes were pulled from the ecm: code p0301, p32638.

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.

I have a 2016 Acura Mdx with 87,000 miles that has bad rod knock. Service bulletin 23-036 talks about it. Even though my Mdx's VIN is not listed in the recall, I am having the exact same problem the recall is supposed to be for. I feel this recall should be expanded to cover my vehicle as it is listed in several places that the recall is for all 2016 Acura Mdx's which is what my vehicle is. ------------------------ subject: safety recall: 2015–20 multi-model connecting rod bearing stop sale. Affected vehicles: certain 2015–2020 Acura tlx v6 and 2016–2020 Acura Mdx models. Cause: a manufacturing defect in the crankshaft can lead to connecting rod bearing wear due to lack of lubrication and excessive heat, potentially causing engine damage and failure. Action: the bulletin initiates a stop-sale order for affected vehicles and provides instructions for inspection and repair, which may include replacing the connecting rod bearings, crankshaft, or short/long block. Status: the bulletin has been revised. Version 1 was issued on November 9, 2023, and was replaced by version 2 on February 9, 2024. Parts availability: parts and repair kits became available in early 2024, with repairs being prioritized for vehicles showing symptoms like engine rod knock or stalling.

Started hearing a "knocking" sound from the engine compartment, whose frequency clearly was proportional to engine rpm. Took vehicle to local trusted mechanic who diagnosed that it was likely related to known crankshaft bearing issue, which is the subject of a widespread recall on Acura vehicles. Found that the vehicle does not fall within the recall window. Sent vehicle by tow truck to nearest dealer who confirmed diagnosis. They claim poor maintenance, but all required maintenance, and definitely all engine oil changes were completed at required intervals with proper fluids and filters. Since dealer is 60 miles away, most maintenance was done with local trusted mechanic, although some oil changes were done personally or at a quick lube service. The vehicle is a 2016 model year, consistent with the model years affected by the known defect and recall. Dealer is advising that a new engine is required. There is no reason a properly maintained vehicle with only 150,000 miles should have a failed engine.

When car is started, attempting to slowly accelerate in reverse or forward you will experience a loss of drive power, transmission does nothing. Then all of a sudden transmission responds and you lurch forward or reverse. Very unsafe situation. Other cars not sure if your moving or stationary.

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.

Car broke down driving from dallas to oklahoma on the highway while at cruising speed. We were able to pull over safely and after towing the car home, the engine produced a knocking sound. Upon further investigation, there is a recall for rod/bearing issues with 2016-2020 Acura Mdx's and other various models like the Acura tlx, Honda pilot, etc. This only extended to certain models and there has been more affected by it than what the recall covers. Maintenance such as regular oil changes to big services like timing belt and water pump was done according to the service manual interval. Investigation rq24013 was open on 11/08/2024 by investigator richard lawrence, reviewer sharon yukevich, and approver tanya topka. There have been about 173 incidents and pose a great safety hazard. Once the car is stopped, the car is not able to go into neutral without the engine on. The only way to override this is through the engine bay with a tool of some sort to manually engage the neutral switch. If the car stops in the middle of the road with this engine failed, this could lead to a more severe casualty.

Engine cut out on the middle of a pitch black highway in virginia. Few seconds lights flashing on dashboard check engine light started flashing then low engine oil and then the rest of the standard "christmas tree lights" experience as I was finally able to pull the vehicle over. Vehicle seemed as if it was dead. When got vehicle jumped 2 hours later I started engine because it wouldn't start. It was making all the noises consistent with engine recall that my engine was so conveniently not included in the recall. Acura won't do anything for me. I was stuck on the side of the highway in the pitch black with cars and trucks flying by at 70+mph with my 3 kids and spouse. Engine is chattering and has no power. Almost about to seize. I was stranded in a small town for 2 days with no way to get home no rental companies with cars available. All videos online consistentfor engine recall consistent with my experience. No lights no hestitation perfect engine oil level filled tank of gas minutes with 93 as always not even 2 minutes before this situation. Engine was perfect. Was glad I wasn't apart of recall initially. I thought I had a "good one" then boom complete catastrophe. Nhtsa needs to expedite this. This is not rocket science! Acura knows the issue they are running form it. I spent over $1,100 to tow my vehicle home and get my family home safely.

The contact owns a 2016 Acura Mdx. The contact stated that while driving at various speeds, the vehicle stalled. The contact was unable to veer to the side of the road. The contact was able to push the vehicle to the side of the road with assistance on each occasion. The vehicle was able to restart, and the check engine warning light was illuminated. The contact was able to resume driving. The vehicle was taken to an independent mechanic several times, and the vehicle was diagnosed with emissions failure. The mechanic reset the computer and the check engine warning light; however, the failure persisted. The dealer was notified of the failure and informed the contact that the VIN was not included in a related recall. The vehicle was not repaired. The manufacturer was not notified of the failure. The failure mileage was approximately 80,000.

Hello. I went to the Acura dealership because I got a recall letter. I lost the letter itself a few days ago. I also had the check engine light come on once while driving. But then it went out on its own during the same trip. At the moment of checking my car by my foreman, he heard a knocking noise in the engine. He said that they will check my car on the recall and see what's wrong with the engine. After some time, he called me and said: I am very sorry, but you need to replace the complete motor as this knock is caused by a problem in the bearing. And alas your car does not fall under the recall to replace this bearing. I asked him which bearing he was talking about. And they answered that it was the one that goes into the recall under which my car did not fall. I clarified that its name sounds like: connecting rod bearing? he said: yes. I've had all my maintenance done on time. Engine oil changes every 5,000 miles. Even before the 8,000 to 10,000 miles. I have all the paperwork with receipts and dates in my car paperwork bag. At every oil change no one has ever told me there was an engine problem. The car was purchased from a dealership in libertyville, illinois. The car is currently at a dealership in naperville, illinois. I wrote a complaint to Acura of California on 9/26/2025. To date, all I have gotten is a response: we have a lot of work to do, we will respond when we can. Very rude and disrespectful. Considering I could have been in an accident if the engine had seized up. That's what my foreman at the dealership said. Or even worse, my daughter could have had an accident. I was planning to give this car to my daughter since she got her driver's license. She really liked this car. Now I don't know what to tell her. I am asking for your help to resolve this problem. They still haven't contacted me or told me what to do. Appreciate it.

No prior issues with vehicle when all of a sudden/out of the blue the check engine light started flashing and felt decreased power. Pulled over, had it towed to dealership. After it was diagnosed they advised of a rod bearing failure, crankshaft failure and metal shavings in the oil which went through the engine. There is a recall for 2016 Acura Mdx for this exact issue, however for some reason my VIN is not included?? the recall was effective Nov of 2023. I purchased vehicle Feb of 2023. Vehicle is still at shop as a complaint has been filed with Acura.

On 9/12/2025 driving on the highway in stop and go traffic, the idle stop feature engaged, but the engine would not restart upon taking foot off break. Put vehicle into park and held start/stop button for couple seconds to turn off, then was able to restart vehicle by pushing start button. Couple days later went to start vehicle while parked and accessories came on, but engine wouldn’t start. After a few attempts, got vehicle to start.

I have a 2016 Acura Mdx, recently took it to OH Acura in temecula for a check due to a noise coming from the engine. Acura determined I need a new engine. . The issue being rod bearing failure Acura determined I need a new engine. . The issue being rod bearing failure. Upon research, this is a known issue from 2023. Also, a new investigation with engine failures in Honda and Acura vehicles linked to the rod bearings has been opened.

While driving on the freeway with my children, the vehicle started to shake and the emission system problem, transmission system problem and blind spot problem lights came on. The safety of myself and children were at risk due to being on the freeway and having to pull over on the side of the road. There were zero signs leading to this.

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.

The contact owns a 2016 Acura Mdx. The contact stated while driving 65 mph, the vehicle stalled. Additionally, there was loud popping noise coming from the engine compartment, with the check engine warning light illuminated. The vehicle was able to restart. The vehicle was towed to the dealer, where it was diagnosed and determined that the connecting rod inside cylinder #2 had failed and needed to be replaced. The vehicle was not repaired. The manufacturer was made aware of the failure. The failure mileage was approximately 109,311.

One morning I noticed the engine in 2016 Acura Mdx was making a loud knocking noise. The check engine light immediately came on. As such, I immediately drove to Acura of baton rouge to report the problem to get it fixed. They ran a diagnostic on the car and didn't find anything. For some reason they said they needed to take the oil pan off to see if there was metal in the oil pan. I said ok. I got a call a few days later from the service department stating that I needed a new engine at the price of $8,000 because they said a connecting road bearing had failed which destroyed the 6th cylinder. The vehicle only had 78,000 miles on it. The oil had always been timely changed. There is no reason the connecting rod bearing should fail on an engine with 78,000 miles on it. I contacted Honda and Honda eventually came back to me and said they would not do anything to help replace the engine because the car was not under warranty, despite the office of defect having an ongoing investigation into connecting rod bearing failures in 2016 Acura Mdx's. Honda has not operated in good faith, this is a major safety issue and the federal government must do something before people are hurt as a result of Honda's negligence.

The contact owns a 2016 Acura Mdx. The contact stated while driving approximately 40 mph, there were several unknown warning lights flashing on the instrument cluster. The contact stated that the vehicle stalled. The vehicle was coasted over to the side of the road; however, while attempting to shift into park(p), the transmission was unable to be shifted into park(p). The contact stated that the vehicle failed to restart. The vehicle was towed to the residence. The contact had not taken the vehicle to a dealer or independent mechanic. The vehicle was not diagnosed or repaired. The contact researched online and related the failure to NHTSA campaign number: 23v751000 (engine and engine cooling); however, the VIN was not included in the recall. The manufacturer was not informed of the failure. The failure mileage was approximately 120,000.

While driving on the highway this vehicle shifted into neutral and lost power. Once pulled to the side of the road, the vehicle was able to be turned off and re started. This happened to my teenage daughter without warning.

On Sunday, while driving approximately 70 mph on the highway with my two young children in the car, the check engine light began flashing, the vehicle suddenly lost power, and would not accelerate past 60 mph. The engine then began producing loud clanking or knocking noises. I pulled over as quickly as I could and had the vehicle towed to my local Acura dealership. The technician who inspected the vehicle indicated it is in the early stages of catastrophic engine failure—likely due to a spun rod bearing. These symptoms are nearly identical to those described in NHTSA recall 23v751000, which addresses rod bearing failure, sudden loss of power, and potential engine seizure in certain Acura models. A less severe version of this issue occurred a few days earlier, on Thursday, also while driving on the highway. The check engine light began flashing and the vehicle experienced a noticeable loss of power. I pulled over and restarted the vehicle, and that resolved the issue. I drove the vehicle multiple times—including on the highway—between Thursday and Sunday with no further issues until the much more severe failure occurred. Despite the clear safety concerns—and the fact that both incidents closely mirror the description in recall 23v751000—my VIN is not currently included in the recall. The vehicle has fewer than 90,000 miles and has been maintained exclusively at Acura dealerships. I’ve reported this to Acura, and my case has been escalated for internal review. An Acura representative encouraged me to contact NHTSA directly, as your agency is responsible for determining whether the scope of the recall should be expanded. This is a serious safety issue that occurred without warning—at highway speeds, with children in the car – and put my family at risk. I respectfully request that NHTSA investigate and consider expanding recall 23v751000 to include similarly affected vehicles like mine. Thank you for your attention to this matter.

Catastrophic engine failure occurred while driving on July 4, 2025, resulting in the car briefly stopping at 60mph skidding tires on I-70 (a major highway in colorado), then tires unlocked and now engine moving again but with a check engine light, and acceleration was sluggish. It freaked out the family and we pulled over at the next exit to find the engine was knocking like crazy. No injuries occurred, but the sudden engine failure while driving created a serious safety hazard. Complete loss of power could have resulted in accident if this had occurred in traffic, on highway, or during emergency maneuver. We later found out engine the rod bearing failed on cylinder 4 and shattered in several pieces. We took it to both independent auto repair shop, then the dealer, both confirmed rod bearing problem, and engine replacement now required. Dealer is quoting us $24000. Failure was due to connecting rod bearing failure - a known defect currently under NHTSA investigation rq24-013. This failure is consistent with NHTSA investigation rq24-013 covering connecting rod bearing failures in 1. 4 million Honda/Acura vehicles including 2016 Mdx. The failure appears related to unaddressed atf warmer defect covered under Acura's kg9 warranty extension (service bulletin 17-026) that compromised cooling system in December 2024, leading to thermal stress and bearing failure. Acura was aware this defect was serious enough to warrant 10-year unlimited mileage warranty coverage but failed to honor it. We had the car serviced June 25th 2025 at the dealer just 9 days prior to the July 4th 2025 incident for its regular maintenance oil change, brake fluid flush, and valve adjustment.

Driving on freeway at 65mph and check engine light flashed as vehicle started to studder and turned off while driving. Vehicle would not even try to start afterwards. Vehicle got towed off freeway to my home. I continued to try to start, it sounded like a bad starter or dead battery, so I charged the battery and got the vehicle to crank and start. Engine was knocking and squealing and pinging. Immediately turned off and did some research. Found out about recall and my engine is not on it . I found a local shop and had it towed there. It ended up being a bad rod/bearing in the engine. I had to have the engine replaced.

The contact owns a 2016 Acura Mdx. The contact stated while driving 75 mph, the accelerator pedal was depressed, and the vehicle failed to accelerate as intended. In addition, the contact stated that the engine and low oil pressure warning lights were illuminated. The contact stated the vehicle was shaking abnormally, and the vehicle failed to exceed 30 mph. The vehicle was driven to a nearby parking lot. The vehicle was then towed to an independent mechanic to be inspected. The contact was informed that the engine was covered in engine oil. The contact stated that the vehicle had recently received an oil change. The contact was advised to have the vehicle towed to the dealer. The vehicle was towed to the dealer where it was diagnosed with fractured bearings and engine failure. The contact was informed that the engine and the bearings needed to be replaced. The vehicle was not repaired. The manufacturer was made aware of the failure and a case was filed. The contact referenced NHTSA campaign number: 23v751000 (engine and engine cooling); however, the VIN was not included in the recall. The contact was advised to contact the NHTSA hotline to report the failure. The failure mileage was approximately 83,000.

While driving southbound on I-5 from san francisco to anaheim, the vehicle began making rattling and squeaking noises from the engine compartment. Within minutes, multiple warning systems activated, including alerts for power steering, brake system, abs, and other critical components. The vehicle quickly lost power and could no longer shift gears. We were forced to exit the highway near kettleman city, but the engine completely shut off as we were exiting. Brake pressure was lost, and the vehicle could not be stopped using the primary braking system. We had to use the emergency brake to avoid a collision. The vehicle was towed by roadside assistance to a dealership for inspection. The dealer confirmed that the engine had spun a connecting rod bearing in cylinders #3 and #4, which caused piston damage and full engine seizure. The service department acknowledged this failure matched a known recall (recall no. 23v-751), but stated the vehicle was not eligible for repair due to its VIN not being listed. Despite this, the failure is identical in cause and outcome to those covered by the recall and poses the same safety risks.

The contact owns a 2016 Acura Mdx. The contact stated while driving 65 mph, the contact felt a big bang with an abnormal sound coming from the engine compartment before the vehicle lost motive power. The contact stated that the vehicle then stalled. The contact inspected the vehicle and observed a liquid pouring out from the engine compartment onto the ground. The vehicle was not able to restart. The vehicle was towed to an independent mechanic where it was diagnosed that the engine needed to be replaced. The vehicle was repaired. The manufacturer was notified of the failure. The failure mileage was 92,380.

Driving up a hill, new knocking noise, car lost engine power, steered the car to the curb and turned engine off. Got car towed to mechanic, ultimately diagnosed as connecting rod bearing failure at cylinder 1. No noted leaks nor other issues at engine nor transmission, this appeared to be defect of the connect rod itself.

I purchased a used 2016 Acura Mdx and shortly afterward began experiencing a rhythmic metallic knocking noise under load, particularly at low rpms (e. G. , accelerating in low gears or when the engine is bogged). The noise is not present at idle or during coasting, and it closely matches the symptoms described in recall 21v-215, which affects certain 2016–2018 Acura/Honda models for premature connecting rod bearing wear. However, my vehicle’s VIN is not included in the existing recall. I purchased a used 2016 Acura Mdx and shortly afterward began experiencing a rhythmic metallic knocking noise under load, particularly at low rpms (e. G. , accelerating in low gears or when the engine is bogged). The noise is not present at idle or during coasting, and it closely matches the symptoms described in recall 21v-215, which affects certain 2016–2018 Acura/Honda models for premature connecting rod bearing wear. However, my vehicle’s VIN is not included in the existing recall. This vehicle has received on-time oil changes using high-quality synthetic oil, and I have taken care to immediately investigate any new or unusual noises. The knock has persisted across multiple oil changes and several thousand miles without worsening, but recently I noticed metallic sparkles in the used oil—potential signs of rod bearing wear. There has been no check engine light, but based on the symptom pattern, operating conditions, and consistency with the defect description in recall 21v-215, I believe this vehicle may be experiencing the same issue and is simply outside the current recall range. I am submitting this report in support of the ongoing recall query (rq) into whether Honda failed to include all affected vins. This appears to be the same failure mode as those already recalled, and it presents a serious long-term risk to engine safety and reliability.