My 2002 3.0 AWD has lost all gears on 4 occasions recently in the last 2 months. The first 2 times were whilst kicking down on a left hand bend, the very same bend but a month apart. The 3rd time on very sharp left hand turn, and lastly just on a straight road. On each occasion after 15 minutes of moving the selector from D to R to P etc the gears would reappear and the car world work fine for a week or so.
When the problem occurs and I try moving the selector through the gears I can hear and feel the normal clonk from the propshaft as it engages drive or reverse but when I accelerate the engine just revs and the car doesn't move. When moving the selector back to P there is a horrible grinding that come from the gearbox. On the first 2 occasions I managed to rev the engine very high and the car would creep forward very slowly until then it suddenly found a gear and then worked as normal. The last 2 times however no amount of revving would make the car move but I could smell the transmission fluid burning.
After getting towed home this last time it started working again as normal outside my house.
The fluid was changed a year ago and the transmission has only done approx 50,000 miles over its entire lifetime.
Any ideas?

 

Make sure to read the other threads in the posts =

https://www.jaguarforums.com/forum/x...-fault-206869/

 

So I think I've sorted it, the long R/H driveshaft wasn't in the gearbox properly. When I replaced them many months the snap ring seemed too big but I hammered it home as best I could. The driveshaft was only in by about 3mm or 1/8" as the snap ring stopped it from going all the way in. Over time this had ground down the end of the splines on the driveshaft. I suspected it was the driveshaft popping out on left hand bends but had no idea how. It was just never in properly in the first place. A quick bit of remedial filing of the damaged ends of the splines and squeezing the snap ring tighter and the driveshaft went in properly this time.
Someone else on another forum had almost identical issues with a similar problem so I suspected this from the outset.