(a) Notification of suspicious activities. An owner or operator required to have a security plan under part 104, 105, or 106 of this subchapter shall, without delay, report activities that may result in a transportation security incident to the National Response Center at the following toll free telephone: 1-800-424-8802, direct telephone 202-267-2675, or TDD 202-267-4477. Any other person or entity is also encouraged to report activities that may result in a transportation security incident to the National Response Center.
(b) Notification of breaches of security. An owner or operator required to have a security plan under parts 104, 105, or 106 of this subchapter shall, without delay, report breaches of security to the National Response Center via one of the means listed in paragraph (a) of this section.
(c) Notification of transportation security incident (TSI).
(1) Any owner or operator required to have a security plan under part 104 or 105 of this subchapter shall, without delay, report a TSI to their local COTP and immediately thereafter begin following the procedures set out in their security plan, which may include contacting the National Response Center via one of the means listed in paragraph (a) of this section.
(2) Any owner or operator required to have a security plan under part 106 of this subchapter shall, without delay, report a TSI to their cognizant District Commander and immediately thereafter begin following the procedures set out in their security plan, which may include contacting the National Response Center via one of the means listed in paragraph (a) of this section.
(d) Callers to the National Response Center should be prepared to provide as much of the following information as possible:
(1) Their own name and contact information;
(2) The name and contact information of the suspicious or responsible party;
(3) The location of the incident, as specifically as possible; and
(4) The description of the incident or activity involved.
[USCG-2003-14792, 68 FR 39278, July 1, 2003, as amended by USCG-2004-18057, 69 FR 34925, June 23, 2004; USCG-2005-21531, 70 FR 36349, June 23, 2005; USCG-2006-25150, 71 FR 39208, July 12, 2006; USCG-2008-0179, 73 FR 35009, June 19, 2008]