Why are all the ATBs switching their vessel type to wing in ground?
Not true I work on atb’s and we have it listed as a tanker since we transport oil and are larger then a lot of the us flagged tankers. I haven’t seen any atb’s that use wig as their identifier.
The Coast Guard issued new AIS Encoding Guidelines a few weeks ago. They were supposed to take affect April 1st. Vessel types were one of the things that was going to change. A lot of the sub types under type 20 (WIG) were unused. OSVs were going to be type 25. One of the problems is that all types under 20 (sub-types 20-29) still show up as WIG. I emailed them to ask if I should just keep our code for Cargo, since that seemed the closest to OSV. They told me to still choose the 25 sub-type. The destination/voyage codes were changing too.
But it looks like all of that has just been rescinded, so we will have to wait and see.
We are using the WIG designation. Not cargo, although cargo makes more sense, see the link above.
We (Reinauer) are using the WIG designation for our ATB fleet. Not cargo, although cargo makes more sense, see the link above.
Sorry about the link, I’ll have to add the attachment later.
I think all the AIS units will need a software upgrade which may be why the USCG rescinded the letter, they forgot to tell the manufacturers so they will not be ready for April. SO… I think it is being pushed back for that reason. In others they forgot that part of making a rule is letting EVERYONE know, not just the ship driver (tug, boat, whatever, if I forgot someone I am sorry). It is called attention to detail and realizing who ALL your customers are.
The attachment should show now. If it’s activation is delayed I don’t know. I saw that Location codes were being delayed, not identity codes.
[QUOTE=captbbrucato;64989]The attachment should show now. If it’s activation is delayed I don’t know. I saw that Location codes were being delayed, not identity codes.
Your copy of the document does show.
It was originally posted here:
linked to from this page
with the label: “AIS encoding guide & LOCODES”
When you go there now you get:
AIS DESTINATION CODES
Under Construction - USLOCODES (GUID) are in transition and subject to change; their use is not effective until April 1st, 2012.
Not to hijack your thread and/or induce a headache:
A problem with the document/concept as it evolved was a conflict between the USCG HQ instructions for coding “Destinations” and existing local (also USCG) practices for coding destinations.
An example is here:
It is going to be interesting to see how it gets resolved.
Will convenient local exceptions be recognized?
(Take Excedrin now}