I just talked to someone at NMC and they told me to let you guys know that when you apply for your VSO be sure to send copies of all your credentials especially your STCW. Also be sure to send the required sea service.
The problem is if they don’t have your discharges in the computer they have to send for your legacy file to get your service. It may be downstairs or if it is over six months old it has been sent to archives in D.C. due to the fact that they don’t have room to store all the files. It can take several weeks to get your old file.
Never assume that they have everything they need to process the application. Always send copies.
[quote=former contract evaluator;15179]I just talked to someone at NMC and they told me to let you guys know that when you apply for your VSO be sure to send copies of all your credentials especially your STCW. Also be sure to send the required sea service.
The problem is if they don’t have your discharges in the computer they have to send for your legacy file to get your service. It may be downstairs or if it is over six months old it has been sent to archives in D.C. due to the fact that they don’t have room to store all the files. It can take several weeks to get your old file.
Never assume that they have everything they need to process the application. Always send copies.[/quote]
It is always good to remind the community of mariners to ensure that their applications are complete prior to submission. Incomplete or improperly filled out applications have got to be one of the REC’s biggest headaches. But the REC, of course, is not supposed to send anything on to the NMC until they have checked for completeness.
In this case however, I don’t recall there being any specific sea service requirements necessary to add VSO to your MMC. I’ve browsed 33 CFR Part 104.215 and there is no mention of it. Why would they need to be digging around for it at NMC?
That’s kinda funny, I had an evaluator complain that there were so many duplicate certificates, and that my file was too big due to me always sending them in to make for sure that there was NOTHING missing, however they still seem to lose one certificate or overlook the proper date and then request more copies. Continual comedy of errors.
Capt_Anon
When we first started issuing the VSO NMC came out with a checklist and one of the requirements was sea service. I think they may have changed that now but I’m not sure. Some evaluators may still be using that check list. If they are, you will get a kickback letter telling you to submit service thus more delays.
[I][quote=Capt_Anonymous;15181]…I don’t recall there being any specific sea service requirements necessary to add VSO to your MMC. I’ve browsed 33 CFR Part 104.215 and there is no mention of it. [/quote][/I]
You may be using an old copy of the CFR. 33 CFR 104.215 was changed on 5/20/2008 (LINK). The sea service requirements are in 33 CFR 104.215(d)(v)
Sea Service. Fulfill one of the following:
(A) Have approved sea service of not
less than 12 months on any vessel subject
to § 104.105 of this part, credited in
accordance with 46 CFR 10.205(e), 10.211,
and/or 10.213; or
(B) Have approved sea service of not
less than 6 months on any vessel subject
to § 104.105 of this part, credited in
accordance with 46 CFR 10.205(b), 10.211,
and/or 10.213, and have knowledge of
vessel operations.
Digging through all those cfr’s doesn’t give me a clear idea what they really want. Are they really delaying the endorsements on 1600 ton licenses to find “old” sea time?
Or is this sea time issue possibly a “90 days in the last 3 years” recency issue?
I just couldn’t imagine being held up even longer for something like this. It would be nice to know what they freaking want.
What was the point of [B]centralization?
[/B]Thanks in advance for any help.
Shippedout
Sea Service. Fulfill one of the following:
(A) Have approved sea service of not
less than 12 months on any vessel subject
to § 104.105 of this part, credited in
accordance with 46 CFR 10.205(e), 10.211,
and/or 10.213; or
(B) Have approved sea service of not
less than 6 months on any vessel subject
to § 104.105 of this part, credited in
accordance with 46 CFR 10.205(b), 10.211,
and/or 10.213, and have knowledge of
vessel operations.
Digging through all those cfr’s doesn’t give me a clear idea what they really want. Are they really delaying the endorsements on 1600 ton licenses to find “old” sea time?
Or is this sea time issue possibly a “90 days in the last 3 years” recency issue?
I just couldn’t imagine being held up even longer for something like this. It would be nice to know what they freaking want.
What was the point of [B]centralization? [/B]
Thanks in advance for any help.
Shippedout[/quote]
It looks to me like to endorse you as a VSO that want you to have 6-12 months time on a ship, not just the school.
It looks to me like to endorse you as a VSO that want you to have 6-12 months time on a ship, not just the school.
I can understand an OS or wiper needing to show seatime, but even an AB special has 180 days seatime. Why would an evaluator need to see time on most of the people applying for VSO?
Exactly. There was no mention of submitting sea time when I did the VSO refresher course. If NMC can’t figure out that it’s a given that a licensed officer holds the required sea time by default, then things are worse than I feared.
I am in the process of taking my VSO course. I recently took my Chief Mates test and havent been sailing in a few months will they use my sea time on file.
if it is over six months old it has been sent to archives in D.C. due to the fact that they don’t have room to store all the files. It can take several weeks to get your old file.
All this despite the USCG’s own words concerning the VSO
What will the estimated turn around time be for STCW certificate/VSO endorsement to be returned to the mariner assuming that the mariner presents sufficient proof of training?
If the mariner provides all the requirements necessary for the endorsement as VSO, the estimated turn around time should be relatively short. http://www.uscg.mil/NMC/faq/vso_rule_making.asp