Filovent yacht charter agency
Welcome to the help centre

Does the insurance always cover damage caused (while underway or at an anchorage)?

Updated on: 26/05/2025
As the boat’s renter,you are your own insurer up to the amount of the security deposit you provide. For damages resulting in costs exceeding the security deposit, the comprehensive insurance on the rented boat (the rental company’s insurance) covers the costs, provided that the skipper has always exercised due care. In fact, after a major incident, the insurance company systematically sends an adjuster to assess the situation. However, if it is determined that you did not operate the boat with due care and showed obvious negligence, the insurance company will refuse to pay, and the charter company will hold you liable for the repairs.

For example: when at anchor, you must always keep an eye on the boat if you decide to go ashore. And if there is the slightest risk (strong winds or winds that may pick up, or if the anchorage is not secure), you must remain on board to monitor the situation (at least you, the skipper). Furthermore, if the weather forecast suggests that the location you have chosen is unsafe for anchoring, it is your responsibility to find a better shelter (anchorage or port). This is a constraint, but it must be viewed as the skipper’s responsibility toward their vessel.

Similarly, if it turns out that you set sail on a day when the forecast wind was particularly strong (wind force 7 or higher, i.e., a Special Weather Bulletin (BMS)), the insurance will likely not cover you, and the rental company will hold you liable in the event of damage. Similarly, one of your crew members could sue you in the event of bodily injury. Caution is therefore advised.

Can't find an answer to your question?
Pierre
With Pierre your cruise expert

Log in to receive your personalized cruise

Invalid email
Forgotten your password? Invalid password, it must be at least 8 characters long. Invalid e-mail address or password We are experiencing a technical problem, please try again later