Mahindra Scorpio-N Breaks Down Multiple Down in Just 2 Months!

Mahindra Scorpio-N breaks down numerous times!

Suraj Thakur had bought the Mahindra Scorpio-N two months ago, and since then the SUV has broke down numerous times as the owner reports he uses the SUVs to transport cow dung and cow feed as a form of protest.

2 Months Old Mahindra Scorpio-N Breaks Down: What Happened?

There have been several concerning ownership experiences reported with Mahindra vehicles, and one recent incident involves a Mahindra Scorpio-N that faced repeated breakdowns within just two months of ownership. The owner, Suraj Thakur, has resorted to using the SUV to transport cow dung and cow feed in the vehicle’s trunk, as a form of protest.

In a video, the owner displayed a placard on the front of the vehicle, detailing the issues he encountered since acquiring the Scorpio-N two months ago. The problems began just four days after purchase, with the clutch plates malfunctioning at a mere 475 kilometers on the odometer. At 1,785 kilometers, the Scorpio-N faced a steering rack issue, although the exact nature of the problem wasn’t specified.

As the vehicle reached 4,800 kilometers, issues with the disc brake emerged, necessitating replacement by the service center. At 5,212 kilometers, the Scorpio-N went into limp mode, which restricts its speed to 40 kmph. Limp mode is typically activated in emergencies to prevent further damage, though the precise diagnostics remain unclear. The owner also shared a video of the Scorpio-N stuck in limp mode, illustrating how the car struggled to accelerate beyond 43 kmph on an open road, even when changing gears from 3rd to 5th. Strangely, no errors were displayed on the vehicle’s instrument cluster.

In another incident earlier this year, a brand-new Mahindra XUV700, just three days old, broke down in Chennai. The owner, Richard M Nathan, encountered this distressing situation at the Luz Corner signal around 2:50 PM. Despite seeking roadside assistance, no help arrived. Nathan took possession of the car on June 2nd and had it on the road by June 5th, even before receiving the registration number. The vehicle unexpectedly came to a halt at a busy traffic signal during peak hours. Roadside assistance refused to come to the location and instead tried to resolve the issue over the phone.

Prior to that, there was an incident involving a Mahindra XUV700 catching fire without warning. According to the owner, the car burst into flames with no prior signs of overheating. Fortunately, no injuries were reported as all passengers managed to safely exit the vehicle before it was engulfed in flames. In response to a viral video of a Mahindra XUV700 catching fire, the brand issued an official statement, stating that the fire was a result of wire tampering, as determined by a comprehensive investigation conducted by Mahindra Automotive.

Like this article?

Share on Facebook
Share on Twitter

Leave a comment