Section 36.01.210. Rail fixed guideway public transportation system—Safety program plan and security and emergency preparedness plan.

(1) Each county functioning under chapter 36.56 RCW that owns or operates a rail fixed guideway public transportation system as defined in RCW 81.104.015 shall submit a system safety program plan and a system security and emergency preparedness plan for that guideway to the state department of transportation by September 1, 1999, or at least one hundred eighty calendar days before beginning operations or instituting significant revisions to its plans. These plans must describe the county's procedures for (a) reporting and investigating any reportable incident, accident, or security breach and identifying and resolving hazards or security vulnerabilities discovered during planning, design, construction, testing, or operations, (b) developing and submitting corrective action plans and annual safety and security audit reports, (c) facilitating on-site safety and security reviews by the state department of transportation and the federal transit administration, and (d) addressing passenger and employee safety and security. The plans must, at a minimum, conform to the standards adopted by the state department of transportation as set forth in the most current version of the Washington state rail safety oversight program standard manual as it exists on March 25, 2016, or such subsequent date as may be provided by the department by rule, consistent with the purposes of this section. If required by the department, the county shall revise its plans to incorporate the department's review comments within sixty days after their receipt, and resubmit its revised plans for review.

(2) Each county functioning under chapter 36.56 RCW shall implement and comply with its system safety program plan and system security and emergency preparedness plan. The county shall perform internal safety and security audits to evaluate its compliance with the plans, and submit its audit schedule to the department of transportation pursuant to the requirements in the most current version of the Washington state rail safety oversight program standard manual as it exists on March 25, 2016, or such subsequent date as may be provided by the department by rule, consistent with the purposes of this section. The county shall prepare an annual report for its internal safety and security audits undertaken in the prior year and submit it to the department no later than February 15th. The department shall establish the requirements for the annual report. The contents of the annual report must include, at a minimum, the dates the audits were conducted, the scope of the audit activity, the audit findings and recommendations, the status of any corrective actions taken as a result of the audit activity, and the results of each audit in terms of the adequacy and effectiveness of the plans.

(3) Each county shall notify the department of transportation, pursuant to the most current version of the Washington state rail safety oversight program standard manual as it exists on March 25, 2016, or such subsequent date as may be provided by the department by rule, consistent with the purposes of this section, any reportable incident, accident, security breach, hazard, or security vulnerability. The department may adopt rules further defining any reportable incident, accident, security breach, hazard, or security vulnerability. The county shall investigate any reportable incident, accident, security breach, hazard, or security vulnerability and provide a written investigation report to the department as described in the most current version of the Washington state rail safety oversight program standard manual as it exists on March 25, 2016, or such subsequent date as may be provided by the department by rule, consistent with the purposes of this section.

(4) The system security and emergency preparedness plan required in subsection (1) of this section is exempt from public disclosure under chapter 42.56 RCW. However, the system safety program plan as described in this section is not subject to this exemption.

[ 2016 c 33 § 4; 2007 c 422 § 3; 2005 c 274 § 268; 1999 c 202 § 3.]

NOTES:

Effective date—2016 c 33: See note following RCW 81.104.115.

Part headings not law—Effective date—2005 c 274: See RCW 42.56.901 and 42.56.902.

Effective date—1999 c 202: See note following RCW 35.21.228.

2016 c 33 § 4; 2007 c 422 § 3; 2005 c 274 § 268; 1999 c 202 § 3.