PREVIOUS | NEXT
VOYAGE PLAN
Further to the requirements, it is recommended that every fishing vessel operator
should keep a voyage plan. While this is not a Regulation, it is a safety precaution and
one method of protecting the boat. The voyage plan can be kept in an ordinary school
notebook and left at home, or with anyone who can contact Search and Rescue. In the case
of an emergency, it is of great help to Search and Rescue and can save a great deal of
valuable time.
Operators should keep a strict radio watch at all time; often a vessel can't be reached
simply because nobody is listening. Finally, the Canadian Coast Guard does not monitor CB
frequencies.
A typical voyage plan is included for your information. It is important to note that it
is in two parts; one part should go inside the front cover of your notebook, the second
part will change with every voyage so that a different page should be kept for each one.
VOYAGE PLAN FOR FISHING VESSELS ^
(A voyage plan can be kept in a school notebook.)
PART 1
(This part contains permanent details and could be placed on the inside front cover).
Telephone number of nearest RCC
or SAREC
|
|
Vessel Name
|
No. of Lifeboats
|
(if applicable)
|
|
Fishing No.
|
No. of Liferafts
|
(if applicable) and size
|
|
Length
|
|
Type
|
No. of Approved
|
Pyrotechnics
|
|
|
|
Colour of Hull
|
|
Deck
|
|
Cabin
|
|
|
Radio equipment
|
|
frequencies fitted
|
Radar Reflector Yes/No
|
VHF
|
(for smaller vessels of other than
metal construction)
|
MF
|
|
MF/HF
|
|
CB
|
|
Lifeboat
|
|
Others
|
PART 2 ^
(This part changes with every voyage and should be kept in the same school notebook
using a different page for each trip).
Departure date & time
|
|
Vessel endurance in hours and days
|
|
Intended fishing areas
|
|
Estimated date and time of return
|
|
Number of persons on board
|
|
Times of regular radio calls with person holding the voyage plan
|
|
Other information
|
|
Probable port of refuge
|
|
Time at which the Search and Rescue organization should be notified if the
scheduled regular radio call is not received
|
|
PREVIOUS | NEXT
|