MSC 70/11/3
| Q |
Defects/damage/deficiencies/other
limitations |
Brief detail of defects,
deficiencies (which includes non-Y2K compliant) or
other limitations.
*Indicate "Yes" or
"No" to whether vessel is Y2K compliant. |
* Applicable on the following
dates and times:
(i) 0000 hours UTC on 26 December 1998 to 2359
hours UTC on 1 January 1999;
(ii) 0000 hours UTC on 16 August 1999 to 2359
hours UTC on 22 August 1999 (22 August 1999 is the "roll
over" date for GPS systems);
（iii) 0000 hours UTC on 3 September 1999 to 2359
hours UTC on 9 September 1999;
(iv) 0000 hours UTC on 26 December 1999 to 2359
hours UTC on 1 January 2000;
(v) 0000 hours UTC on 23 February 2000 to 2359
hours UTC on 29 February 2000
(29 February 2000 is the leap day); and
(vi) 0000 hours UTC on 25 December 2000 to 2359
hours UTC on 31 December 2000
(31 December 2000 is the 366th day in 2000)
4 The information on whether a ship is Y2K
compliant will be required during the period" one week
before to 2359 hours UTC of that particular date (1 January 1999, 22 August 1999,9 September 1999, 1 January 2000, 29
February 2000 and 31 December 2000), which could be critical
as mentioned in MSC/Circ.868. The earlier commencement of
such reporting would increase the awareness of shipmasters of
the Y2K problem as well as to assist in the running in of our
monitoring system. With this information the coastal States
would be in a better position to take any precautionary
measures as necessary to deal with situations where ships are
not Y2K compliant.
Action requested of the Committee
5 The Committee is invited to consider and
approve the inclusion of non-Y2K compliant information as
part of deficiencies and are required to report this fact
under the Mandatory Ship Reporting System in the Straits of
Malacca and Singapore (STRAITREP) adopted at its sixty-ninth
session.
I:/MSC/70/11-3.WPD
