spot_img
spot_img

Video: Mississippi Ski Riders Demonstrate Yamaha FX Range & Fuel Gauge Issues

A little over two weeks ago, The Watercraft Journal published a short recap of of class action lawsuit filed by Mitchell Higgins against Yamaha Motor Company, USA. The lawsuit itself addressed three significant issues that consumers have found pertaining to all Yamaha FX WaveRunners; the Connext dashboard software resetting the trip and fuel consumption data at every restart; the inconsistent metering of the low fuel alarm; and the rider’s inability to extinguish said alarm while underway.

While our article points out several key features of the lawsuit that will likely keep it from ever gaining any traction in a serious court of law (the damages listed are “annoyance” and “inability to enjoy my watercraft”, as well as Higgins personally seeking $5 million dollars), the issues with the vehicle itself remain valid. Publishing the article spurred thousands of replies and responses and encouraged many to share their experiences with these same issues.

One such reply was Mississippi Ski Riders (MSSR) who pieced together this incredibly well-made documentation of all three of the above listed complaints in this single video (featured below). Although The Watercraft Journal strongly recommends that riders never run their PWC dry (to the point of fuel starvation) for fear of overheating the in-tank fuel pump, MSSR does properly document full range in optimal conditions and the corresponding behaviors of the Yamaha. See below:

Kevin Shaw
Kevin Shawhttps://watercraftjournal.com
Editor-in-Chief – [email protected] Kevin Shaw is a decade-long powersports and automotive journalist whose love for things that go too fast has led him to launching The Watercraft Journal. Almost always found with stained hands and dirt under his fingernails, Kevin has an eye for the technical while keeping a eye out for beautiful photography and a great story.

Related Posts

LEAVE A REPLY

Please enter your comment!
Please enter your name here
Captcha verification failed!
CAPTCHA user score failed. Please contact us!