PDFRCW 47.56.875

State route No. 520 corridor accountDepositsUse and transfer of funds.

A special account to be known as the state route number 520 corridor account is created in the state treasury.
(1) Deposits to the account must include:
(a) All proceeds of bonds issued for the state route number 520 bridge replacement and HOV program, including any capitalized interest;
(b) Except as provided in RCW 47.56.870(4)(b)(vii), all of the tolls and other revenues received from the operation of the state route number 520 corridor as a toll facility, to be deposited at least monthly;
(c) Any interest that may be earned from the deposit or investment of those revenues;
(d) Notwithstanding RCW 47.12.063, proceeds from the sale of any surplus real property acquired for the state route number 520 bridge replacement and HOV program; and
(e) All damages, liquidated or otherwise, collected under any contract involving the state route number 520 bridge replacement and HOV program.
(2) Subject to the covenants made by the state in the bond proceedings authorizing the issuance and sale of bonds for the state route number 520 bridge replacement and HOV program, toll charges, other revenues, and interest received from the operation of the state route number 520 corridor as a toll facility may be used to:
(a) Pay any required costs allowed under RCW 47.56.820; and
(b) Repay amounts to the motor vehicle fund as required.
(3) When repaying the motor vehicle fund, the state treasurer shall transfer funds from the state route number 520 corridor account to the motor vehicle fund on or before each debt service date for bonds issued for the state route number 520 bridge replacement and HOV program in an amount sufficient to repay the motor vehicle fund for amounts transferred from that fund to the highway bond retirement fund to provide for any bond principal and interest due on that date. The state treasurer may establish subaccounts for the purpose of segregating toll charges, bond sale proceeds, and other revenues.
[ 2010 c 248 s 4; 2009 c 472 s 4.]

NOTES:

IntentEffective date2009 c 472: See notes following RCW 47.56.870.