Article 72QHT 1 Line Update: more strategic closures

1 Line Update: more strategic closures

by
Nathan Dickey
from Seattle Transit Blog on (#72QHT)
Story Image

This week Sound Transit announced another batch of work for which it will be strategically closing" sections of the 1 Linefor upgrades and complex maintenance. In summary:

Friday, January 9 to Sunday, January 11 (Now): Buses will replace trains between Capitol Hill and SODO each night from 10pm Friday to noon Saturday and 10pm Saturday to noon Sunday. This closure is for continued installation of advanced signals (ATP) in the former DSTT.

Tuesday, January 13 to Thursday, January 15: Buses will replace trains between Stadium and Mount Baker each night after about 9-10pm, with normal service resuming each morning. This work is part of ST's monthly maintenance program.

Friday, January 16 to Sunday, January 18: Buses will replace trains between Capitol Hill and SODO each night from 10pm Friday to noon Saturday and 10pm Saturday to noon Sunday for continued ATP installation.

Friday, January 23 to Monday, January 26: Buses will replace trains between Capitol Hill and SODO from 10pm on Friday through the weekend with normal service resuming on Monday morning. This longer closure is for ATP installation and testing.

Check Sound Transit's service alerts for up-to-the-minute updates. Sports fans will be enthused with a few additional updates ST included in Thursday's press release:

Seahawks playoffs

Sound Transit is working closely with the SeahawkstomonitortheNFLplayoff calendar andkeep the region moving. The 1 Line will be open to servethe Seahawks playoffs and fan activity before and after games.

Future Work

Additionalclosureswillbe necessary as crews work to open the Crosslake Connectionto extend the 2Line from the Eastside toSeattleand prepare the system for increaseddemandduring theFIFAWorldCup.

External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/seattletransitblog/rss
Feed Title Seattle Transit Blog
Feed Link https://seattletransitblog.com/
Reply 0 comments