November 21, 2024
Maxi Trimaran Banque Populaire V Daggerboard Repair (Photo courtesy Banque Populaire)
Maxi Trimaran Banque Populaire V Daggerboard Repair (Photo courtesy Banque Populaire)

After running into an ‘unidentified floating object’ overnight from Wednesday to Thursday, Pascal Bidegorry and his men had to head North for a while, in order to reach better sea and wind conditions to lift the daggerboard out of its case and evaluate the extent of the damage. The operation, which took about three hours, showed that the impact tore 2m20 of the submerged part and confirmed the disappearance of the crashbox. Brought back on deck, the daggerboard currently takes full attention from the Maxi Banque Populaire V crew, which is doing everything possible with the means available on board to get back to normal racing on this Jules Verne Trophy.
Pascal Bidegorry came back on the operation on the phone this morning: “At night, we arrived in an area allowing us to lift the daggerboard without too much difficulty. The handling took us nearly three hours during which we lied off. Emmanuel Le Borgne took the “benefit” of it to dive under the Maxi Banque Populaire V to assess possible damage onto the rudder blades and hull bottoms. There is nothing serious on those matters. Once the dagg on the deck, we found out that there is a missing piece of roughly 2m20. The shock was so intense that it broke the structural bar of the dagg. We are currently trying to cut out the end of it, which is reduced to shreds. However the mission is not that simple at all with the few tools we have. We are using a hacksaw and a drill. Once cut, we will study the possibility to stratify it.  Our objective is to shut the lower part of it to make it waterproof. Otherwise, it would continue to delaminate with speed.”

A lot of work is expected for the next 24 hours, during which the Maxi Banque Populaire V will have to sail at a reduced pace.

“We are sailing under Solent with 6 knots of wind, and what is sure is that all this does not help us gaining time! We hope we will able to lift the gennaker fast enough but for now we need it to steady the dagg. We will do everything to succeed in this approach. We will move forward, hour by hour, trying to relaunch this Maxi Banque Populaire V history in this Jules Verne Trophy. We will make the appropriate decision once we have tried everything to resume on our progress around the world with normal navigation and safety conditions. But for now, we carry on and facing the events, I tell myself that I am very fortunate to sail with a highly united crew who do not hesitate to roll up its sleeves in adversity! “.

So these are difficult times that lie ahead for Pascal Bidégorry and his men who nevertheless keep their full determination to continue this wonderful story. Activity looks intense at sea, but in this thirteenth day of racing, the Maxi Banque Populaire V still leads by 195 miles on the timetable. The race against time continues.

The record in figures
Record to beat
To become holder of the Jules Verne record, the Maxi Banque Populaire V has to be back no later than the 11th March 2011 at 7 pm 55 minutes 37 seconds (Paris time).

Reference time
Groupama 3 (Franck Cammas): 48d 7h 44min 52s

Lead / Delay at 3:00pm
 156.1 miles ahead of the reference time

Maxi Banque Populaire V’s crew list
Off Watch :
Pascal Bidégorry : skipper
Juan Vila : navigator

Watch n°1
Yvan Ravussin : Watch leader, in charge of video and composite
Brian Thompson : Helmsman / Trimmer
Thierry Chabagny : Helmsman / Trimmer
Pierre-Yves Moreau : Bowman, in charge of fittings and composite

Watch n°2
Fred Le Peutrec : Watch leader
Emmanuel Le Borgne : Helmsman / Trimmer, in charge of medics
Erwan Tabarly : Helmsman / Trimmer, in charge of electonics
Ronan Lucas : Bowman, in charge of security

Watch n°3
Jérémie Beyou  : Watch leader
Kevin Escoffier: Helmsman / Trimmer, in charge of video
Xavier Revil  : Helmsman / Trimmer, in charge of food
Florent Chastel : Bowman, in charge of medics and rigging

Marcel van Triest : Shore weather routeur

error: Content is protected !!