Planned Subway Service Changes

[RR503]

Why? To confuse riders and give foamers train porn? 

Look, I agree the lack of QP access is an issue. Messing up the rest of the system is not the solution. Their service pattern isn’t optimal, and in a world with infinite extra cars, I’d bring the  to Roosevelt, but, well, we are in a car shortage, regardless of the cars the  will not use that week. So I think that aside from maybe making the  local, there’s little that should be changed. 

Again, change for the sake of it is a fetish. It has to have a purpose to be beneficial. 

[Lawrence St]

It is beneficial. Wanna know why?

 

1. The can not handle the QBL local on its own, something else needs to be there in place of service, which is why I said to extend the to 71st Avenue.

2. With the being out, people can take the to Jamaca Center instead of having to transfer to a 6th Avenue station.

[R68OnBroadway]

7 minutes ago, Lawrence St said:

It is beneficial. Wanna know why?

 

1. The can not handle the QBL local on its own, something else needs to be there in place of service, which is why I said to extend the to 71st Avenue.

2. With the being out, people can take the to Jamaca Center instead of having to transfer to a 6th Avenue station.

Most people head to Midtown, so the  would be near-useless. 

Making a transfer at Roosevelt Av isn't difficult.

[Daniel The Cool]

On 12/17/2017 at 9:25 PM, BM5 via Woodhaven said:

Didn't they used to send 's via Broadway on weekends before (and stopped doing it)? 

IIRC, there were weekends where the would run to Whitehall until a certain time, and then via 6 Avenue all other times.

It was only overnight weekends where the Train went via Broadway. They never did a daytime G.O with that.

[Lance]

Many of you are aware of my stance on the MTA's communication practices, or lack thereof, so it should come as a surprise that I'm actually praising them for once. As the approach the upcoming 53rd Street tunnel closure, I have been pleasantly surprised to see a blitz of workers handing out information pamphlets on the closure. I've seen these guys around the various line stations since Monday. This along with the large poster boards found in stations, frequent in-station announcements and the information on the website go a long way to informing riders of the upcoming major service change. Now, if only they could do something similar for some of the other service changes that occur.

[Daniel The Cool]

On 12/18/2017 at 2:10 PM, MysteriousBtrain said:

Lots of interesting things happening at night this week. One of my favorites is the sharing the uptown track after after 59 St after 9:45PM. I get our system is in bad shape, but for those trying to travel overnight are going to have a great night.

And they will be sharing the same tracks (Local Tracks) after 10 PM on Friday for the weekend G.O

 

[N6 Limited]

 

On 12/18/2017 at 2:10 PM, MysteriousBtrain said:

Lots of interesting things happening at night this week. One of my favorites is the sharing the uptown track after after 59 St after 9:45PM. I get our system is in bad shape, but for those trying to travel overnight are going to have a great night.

 

22 hours ago, Daniel The Cool said:

And they will be sharing the same tracks (Local Tracks) after 10 PM on Friday for the weekend G.O

 

Can they send the  and  first express on the local then send the behind them?

[Daniel The Cool]

Just now, N6 Limited said:

 

 

Can they send the  and  first express on the local then send the behind them?

That will cause heavy congestion. And whats the point of that in this case if its running local because of a G.O?

[N6 Limited]

20 minutes ago, Daniel The Cool said:

That will cause heavy congestion. And whats the point of that in this case if its running local because of a G.O?

You get more track throughput if you send an express train in front of a local. systems around the world do it all the time

[Daniel The Cool]

4 minutes ago, N6 Limited said:

You get more track throughput if you send an express train in front of a local. systems around the world do it all the time

1. Stop comparing with systems around the world because its not the same as NYC. It honestly gets annoying.

2. And with your logic, you're going to caused heavy congestion because you will be holding the Trains even longer unnecessary  

3. There will be express Trains still having to local with your logic. They're not going to hold the  for over 10 or even 20 minutes so they would put the express trains in front.

Edited December 21, 2017 by Daniel The Cool

[N6 Limited]

6 minutes ago, Daniel The Cool said:

1. Stop comparing with systems around the world because its not the same as NYC.

2. And with your logic, you're going to caused heavy congestion because you will be holding the Trains even longer unnecessary  

3. There will be express Trains still having to local with your logic. They're not going to hold the  for over 10 minutes so they would put the express trains in front.

Those trains would be to 125th st in 10 mins, it wouldn't even make sense if they did that. Just send some express to limit delays. 

I know on Queens Blvd if they sent some  and  trains first they wouldn't to sit behind terminating trains. Instead two trains wizzing through express and one train terminating. now you have 3 trains in a hold, followed by more.

Edited December 21, 2017 by N6 Limited

[Daniel The Cool]

5 minutes ago, N6 Limited said:

Those trains would be to 125th st in 10 mins, it wouldn't even make sense if they did that. Just send some express to limit delays. 

I know on Queens Blvd if they sent some  and  trains first they wouldn't to sit behind terminating trains

Dude the both the  and Trains still run 10 minute headways and it takes 12 minutes on the local from 59th Street to 125th Street. And were you really comparing Queens Blvd? It's not the same. And you keep forgetting there's going to be flaggers out there so those and Trains would get to 125th Street Late which is really pointless to still run trains express on the local.

Edited December 21, 2017 by Daniel The Cool

[R42N]

Speaking of GO’s that the MTA used to do, who remember’s the to Ocean Parkway with through service at Stilwell from 2005 or 2006? It came from Sea Beach to Ocean on the  platforms, and came from Ocean to Sea Beach/4th Ave on the platform. 

The  was suspended all weekend during that G.O.

Edited December 21, 2017 by R42N

[Bill from Maspeth]

6 hours ago, N6 Limited said:

Those trains would be to 125th st in 10 mins, it wouldn't even make sense if they did that. Just send some express to limit delays. 

I know on Queens Blvd if they sent some  and  trains first they wouldn't to sit behind terminating trains. Instead two trains wizzing through express and one train terminating. now you have 3 trains in a hold, followed by more.

Dude.  You are assuming that a B or C would not have to wait for an A or D to come first.  Even if your scheme would work, with 4 services on 1 track your A and D would catch up to the leader no matter what, + you have adjacent track flagging slowing everything down more.

When you have 4 services on 1 track, the dispatcher has to keep the railroad moving.  No holding trains for another, no gaps in service leaving the station.

The answer is to end B service early.

[Abba]

Looks like SubwayTime decided to call the short turn  trains . Anyone know if these trains to the public are  or .Im curious!

[RR503]

On the  and  service change notices, it lists  (and also it says it’s running wknd schedule to Essex). On the  page, it says  to Chambers. On trains, I’ve seen both. (at lease one set of SMEEs said chambers/  on its side, but all the NTTs I saw were , and some of those even said Essex). In stations,  to Chambers. 

In essence, we either have a designation-fluid subway route, or a bunch of really drunk service planners. 

Edited December 27, 2017 by RR503

[Daniel The Cool]

2 hours ago, RR503 said:

On the  and  service change notices, it lists  (and also it says it’s running wknd schedule to Essex). On the  page, it says  to Chambers. On trains, I’ve seen both. (at lease one set of SMEEs said chambers/  on its side, but all the NTTs I saw were , and some of those even said Essex). In stations,  to Chambers. 

In essence, we either have a designation-fluid subway route, or a bunch of really drunk service planners. 

Really drunk service planners sounds about right.

[Lance]

Seriously though, this is why nobody knows what the hell is going on half the time. If all of the service change posters state that mainline train service is suspended, perhaps it would be prudent to not label the shortened line as an . Or better yet, make the actual service change reflect the real service. It would've been much easier to convey to passengers that trains were not running between Essex St and 71 Avenue.

[S78 via Hylan]

Starting off the weekends of the new year:

 242 St bound service runs express from Dyckman to 242 St: Jan 6-7

 Operates between 241 St and South Ferry (No service to Dyre Av): Jan 6-8, 13-15, 20-22

 Split service at 125 St (Woodlawn bound trains skip 138 St); Local service in Manhattan: Jan 6-8, 13-15, 20-22

 No service north of Grand Central: Jan 6-8, 13-15, 20-22 

 Flushing bound service is express from Queensboro Plaza to Willets point: Jan 6-7

 Local service in Brooklyn between Hoyt St and Broadway Junction: Jan 5-8

 Local service along CPW: Jan 12-15

 Uptown service is express in Manhattan: Jan 19-22

 No service north of 145 St: Jan 20-21

  Via 8 Av Express and Culver: Jan 5-8, 12-15

 Manhattan bound service is Express overnight in Brooklyn and skips DeKalb Av: Jan 19-22

 Local service in Queens: Jan 5-8, Manhattan bound service is local: Jan 19-22

 Queens bound trains skip 14 and 23 Sts: Jan 19-22

 Via B’way/4 Av Express and West End: Jan 5-8, 12-15

 No service south of Church Av: Jan 26-29

 No service east of Crescent St: Jan 6-7, 13-14, 20-21

 Manhattan bound service runs express from Myrtle to Marcy Avs: Jan 6-7, 13-14, 20-21, 27-28

 Split service at Broadway Junction: Jan 20 (Saturday only)

 No Mainline service: Jan 6-7, 13-14, 20-21, 27-28

 Astoria bound trains run express from Queensboro Plaza to Astoria Blvd: Jan 5-8, 12-15, 19-22, 26-29

 via Montague, both directions, Manhattan bound service is local in Brooklyn: Jan 5-8, 12-15

 Local service in Brooklyn, both directions: Jan 27-29

 Manhattan bound service via Montague: Jan 19-22

 Bay Ridge bound service runs express from Atlantic-Barclays to 59 St: Jan 5-8, 12-15

 Manhattan bound service express in Brooklyn, via Bridge, no late night service between Whitehall St and 59 St, Brooklyn: Jan 19-22

 Manhattan bound service is express in Queens: Jan 27-28

Edited December 27, 2017 by S78 via Hylan
Forgot to add some service changes.

[N6 Limited]

1 hour ago, Lance said:

Seriously though, this is why nobody knows what the hell is going on half the time. If all of the service change posters state that mainline train service is suspended, perhaps it would be prudent to not label the shortened line as an . Or better yet, make the actual service change reflect the real service. It would've been much easier to convey to passengers that trains were not running between Essex St and 71 Avenue.

If the  trains are running between Broadway Junction and Chambers St, why not just label them as  ?

[Lance]

Who knows? That's what the official service change states, but for some reason, they are running as trains.

[Eric B]

Today, they began running as (J)'s, apparently from a memo put out. The countdownclocks still say (M), though.

[Eric B]

8 hours ago, Lance said:

Who knows? That's what the official service change states, but for some reason, they are running as trains.

Today, they began running as (J)'s, apparently from a memo put out. The countdownclocks still say (M), though.

[Lance]

Correct me if I'm wrong, but doesn't that information come from RCC? I understand the need to internally distinguish between actual runs and the short runs between Chambers St and Broadway Junction, but I'd imagine there has to be a way to do so without involving the clocks that the general public sees, right?

[Eric B]

They apparently haven't updated the bluetooth device that feeds the clocks. It would take time for whatever office is responsible for that to change them, and since it's only a week, they probably won't bother for the two remaining days.