NJ Transit Focuses On Two Options for Future Of Princeton ‘Dinky’ Rail Corridor

Rendering of potential Princeton Dinky light rail / busway at proposed new Roszel Road Station under ‘Alternative 1’

A spokeswoman from NJ Transit announced on Thursday night that the agency has narrowed the field of potential options in its ‘Princeton Transitway’ study. The study aims to identify ways to improve transit along the Princeton ‘Dinky’ rail corridor. Whereas four potential options were being considered previously (see full story at walkableprinceton.com), NJ Transit is now focusing on ‘Alternative 1’ and ‘Alternative 4’.

‘Alternative 1’ would involve replacing the existing train with a modern, electric, light rail service that would run every 15 – 30 mins. In addition, this alternative would have ‘bus rapid transit’ running over the light rail tracks to allow extension of transit service from the Dinky corridor through the central business district of Princeton and on to the Princeton Shopping Center. This bus rapid transit service would run at 10 – 15 min intervals, so that together there would be either train or bus service running along the corridor between Princeton and Princeton Junction every 6 – 10 mins. Alternative 1 would also include new rail stations at Canal Pointe Blvd and near Roszel Road, potentially providing ‘park-and-ride’ facilities for businesses in Princeton, and a new dedicated path for cyclists and pedestrians connecting Princeton and West Windsor. ‘Alternative 4’, which also remains under consideration, is essentially a ‘no-build’ alternative, which would aim to continue service with the existing aging trains.

The original four alternatives identified as part of the Princeton Transitway study in 2021.

Alternatives 2 and 3 have been set aside from further consideration. Alternative 2 would have involved a busway running in its own right-of-way, separate from a light rail line. This alternative would have required substantial acquisition of land, which made it substantially more expensive. Alternative 3 was a Bus Rapid Transit-only option, with no rail service. NJ Transit noted that Princeton residents are strongly committed to retaining rail service, so this option was considered inadequate.

Of the remaining options, ridership along the corridor would be expected to increase to around 2,175 daily passenger trips with Alternative 1, and potentially shrink to around 750 daily passenger trips with Alternative 4. Alternative 1 would be more costly, however, with an estimated capital cost of $101 million, versus a cost of just $15 million to try to salvage some more life out of the existing trains with Alternative 4. NJ Transit proposes to “continue to analyze and develop the selected Alternatives” over the next few months, before more refined alternatives will be shared with the public.

More information about the Princeton Transitway study can be found at the NJ Transit website at this link.

This entry was posted in Alternative Transportation, Biking, planning, Princeton, Transit and tagged , , , , , , . Bookmark the permalink.

3 Responses to NJ Transit Focuses On Two Options for Future Of Princeton ‘Dinky’ Rail Corridor

  1. Bill James says:

    JPods will be builing 10X lower cost solar-powered mobility networks in Macon, GA.

    https://wgxa.tv/news/local/its-a-bird-its-a-plane-its-a-new-way-to-travel-in-macon

  2. Nathanael says:

    J.F.C. Extend it into downtown as a tram. Why does NJT go out of their way to reject this.

  3. Bogos Binted says:

    I don’t understand why they need to do this. The Dinky Corridor is fine. If they wanna upgrade stuff, Update Rolling Stock, or use the funds to electrify the entire NJT Network. Heck, why don’t they just Add new corridors. Upgrading Commuter rail to light rail and “BRT” is literally a scam.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s