Reply
 
Thread Tools Search this Thread
 
Old 22 June 2008, 21:28   #1
Member
 
Country: UK - Wales
Town: Southampton
Boat name: DynaMoHumm/ SRV/deja
Make: Avon8.4, 5.4 & 4.777
Length: 8m +
Engine: Cat3126 Yam 90 &70
MMSI: 42
Join Date: Dec 2003
Posts: 6,556
coding question

I was rading the MGN 280 last night, come to think of it I can think of better ways to spend a Saturday night, and I noticed a section stating that inflatables and RIBs must have the upper surface of the toobs covered in an antislip materila.

I can't think of any coded RIBs that comply with this or ami misreading the document
__________________

__________________
Here it comes again, I don't stand a chance
Soul possession, Got me in a trance
Pullin' me back to you - Deja Voodoo
Rogue Wave is offline   Reply With Quote
Old 24 June 2008, 04:40   #2
Member
 
Pete7's Avatar
 
Country: UK - England
Town: Gosport
Boat name: April Lass
Make: Moody 31
Length: 9m +
Join Date: Aug 2001
Posts: 4,850
You are mis reading the document. Old Spice had none slip tube surfaces made from Hyperlon. Even when wet they provided a great none slip surface.

However if it was a yellow Tornado with those slippery PVC tubes then you would be right to worry

When you are reading MGN 280 do look up the deffinitions of inflatable and rib. There is a difference in parts of the coding.

You read 140 pages of MGN 280 on Saturday night, hmm nightlife must be exciting in Norf Wales

Pete
__________________
.
Ribnet is best viewed on a computer of some sort
Pete7 is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off





Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -5. The time now is 08:43.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.