Jump to content

SUBWAY - Random Thoughts Topic


Recommended Posts


  • Replies 30.7k
  • Created
  • Last Reply
3 minutes ago, Calvin said:

Was the weekend (F) headways recently changed? Before, it used to be 8-10 minutes for each train arrival but ended up being a 15 min wait. 

(E)(F) and (R) weekend headways were officially changed to 12 minute headways to accommodate CBTC installation in Queens.

Your (F) train was technically within compliance of wait assessment guidelines even though it was a really long wait.

Link to comment
Share on other sites

Well if anyone wanted to know, it lives.

 

48065124786_f92a1ccf9e_c.jpg

R68 Subway car 2876 Rollsign Interior by Missabassie, on Flickr

48065124901_6eaed723b5_c.jpg

R68 Subway car 2876 Rollsign Exterior by Missabassie, on Flickr

48065227487_8d9f99772e_c.jpg

NYC Subway R68 Leaving 125th Street Station 1 by Missabassie, on Flickr

 

This was 207 st bound aprox. 22:00 Friday night.

Edited by Missabassie
Link to comment
Share on other sites

8 hours ago, paulrivera said:

I love how the (B) train stopped running all 10 miles of its route at 7pm because of a 300 foot long work train that got stuck on one track at a station with three other tracks.

I was shocked that they didn't at least have the southbound (B) Trains end at Kings Highway. 

 

The last southbound (B) that left 145th Street when they started suspending service did end at 2nd Avenue and went back Uptown in service however. 

Link to comment
Share on other sites

8 hours ago, Missabassie said:

Well if anyone wanted to know, it lives.

 

48065124786_f92a1ccf9e_c.jpg

R68 Subway car 2876 Rollsign Interior by Missabassie, on Flickr

48065124901_6eaed723b5_c.jpg

R68 Subway car 2876 Rollsign Exterior by Missabassie, on Flickr

48065227487_8d9f99772e_c.jpg

NYC Subway R68 Leaving 125th Street Station 1 by Missabassie, on Flickr

 

This was 207 st bound aprox. 22:00 Friday night.

Yeh. 2822 R68 was rolling into Nostrand Avenue (A) station at 21:00 last night heading to 207. 

Link to comment
Share on other sites

9 hours ago, paulrivera said:

(E)(F) and (R) weekend headways were officially changed to 12 minute headways to accommodate CBTC installation in Queens.

Your (F) train was technically within compliance of wait assessment guidelines even though it was a really long wait.

Why don’t they just send the (R) to Astoria and have only the (E)(F) to maintain somewhat decent frequencies?

Link to comment
Share on other sites

You could also turn using the pocket at Queens Plaza. They did that for a bunch of GOs maybe 2 years ago. 

(E), I’d imagine, would be local. Otherwise you’re fully cutting local riders off from 53/60, rather than forcing a transfer. 

Link to comment
Share on other sites

4 minutes ago, Lawrence St said:

Why don't some (N) trains go up 2nd Av during the Astoria closure? I imagine having a one track terminal causes delays along the whole line.

The (M) will be at 2nd Av with the (Q) nonstop weekends till 2020. 3 lines in one terminal is a problem.

Link to comment
Share on other sites

20 minutes ago, Lawrence St said:

Why don't some (N) trains go up 2nd Av during the Astoria closure? I imagine having a one track terminal causes delays along the whole line.

It's possible to operate single track terminals at as much as 15-16tph. If there are delays at 6tph, the fix is fixing operations.

Edited by RR503
Link to comment
Share on other sites

21 minutes ago, Lex said:

At 6 tph? Why bother with branching at all?

The (N) is actually *5* tph due to supplement.

Also, NYCT generally avoids having more than 15tph on any one track on Saturdays and Sundays.

Hell, they’d do *3* tph if they felt they could get away with it (hey (4)(5) and (L) riders, how y’all doin?)

Link to comment
Share on other sites

3 minutes ago, Daniel The Cool said:

Except that had to do with a G.O having both (E) and (F) Trains ending at 71st Avenue.

Yes, but the cause of (R) trains turning at Queens Plaza is pretty irrelevant to the question of whether or not you _can_ turn/they have turned (R) trains at Queens Plaza. 

Edited by RR503
Link to comment
Share on other sites

4 hours ago, paulrivera said:

The (N) is actually *5* tph due to supplement.

Also, NYCT generally avoids having more than 15tph on any one track on Saturdays and Sundays.

Hell, they’d do *3* tph if they felt they could get away with it (hey (4)(5) and (L) riders, how y’all doin?)

Hey, don't blame the MTA for that one. The whole thing surrounding that is executive meddling.

As for the (4) and (5), they definitely need to do better (5 tph should be the absolute minimum during the day).

Link to comment
Share on other sites

5 hours ago, paulrivera said:

The (N) is actually *5* tph due to supplement.

Also, NYCT generally avoids having more than 15tph on any one track on Saturdays and Sundays.

Hell, they’d do *3* tph if they felt they could get away with it (hey (4)(5) and (L) riders, how y’all doin?)

I mean with the delays in Manhattan from all the people trying to squeeze on too few trains, you practically do have 3 tph...

20 minute waits on the weekends are regular at this point.

Link to comment
Share on other sites

1 hour ago, Lex said:

Hey, don't blame the MTA for that one. The whole thing surrounding that is executive meddling.

As for the (4) and (5), they definitely need to do better (5 tph should be the absolute minimum during the day).

This is very much a NYCT problem. Weekend service reduction is a direct result of the agency’s lack of attention to GO productivity and of flagging rules developed largely by the agency. The agency may not have control over some of the more arcane work rules, but it absolutely can do a better job coordinating projects, properly scheduling work trains and flagging crews, etc. It also could either invest in track barriers to eliminate adjacent flagging, or review flagging rules to understand what in them is working and what is not while comparing to other systems’ practices. And of course there’s always the option of changing the predominant GO format — emphasizing less frequent full shutdowns over the endless dribble of one-direction reroutes. 

With the (4)(5), the issue is the (6) and Brooklyn. You can’t run the (6) at 5tph, nor can you run Lex-Brooklyn or Jerome that low. So you run 7.5/3/7.5, which itself is really pushing it in terms of flagging capacities. I just wish they’d run 3tph of overlay service as far as 149-GC to complement the 3 of Manhattan service. 

Edited by RR503
Link to comment
Share on other sites

1 hour ago, RR503 said:

This is very much a NYCT problem. Weekend service reduction is a direct result of the agency’s lack of attention to GO productivity and of flagging rules developed largely by the agency. The agency may not have control over some of the more arcane work rules, but it absolutely can do a better job coordinating projects, properly scheduling work trains and flagging crews, etc. It also could either invest in track barriers to eliminate adjacent flagging, or review flagging rules to understand what in them is working and what is not while comparing to other systems’ practices. And of course there’s always the option of changing the predominant GO format — emphasizing less frequent full shutdowns over the endless dribble of one-direction reroutes. 

With the (4)(5), the issue is the (6) and Brooklyn. You can’t run the (6) at 5tph, nor can you run Lex-Brooklyn or Jerome that low. So you run 7.5/3/7.5, which itself is really pushing it in terms of flagging capacities. I just wish they’d run 3tph of overlay service as far as 149-GC to complement the 3 of Manhattan service. 

The (6) has to run at 5 tph when the (5) is replacing the (2) as 241 St and Flatbush Av can't have 20 minute headways. The (4) has to run local when this happens though

 

It is either: 

(4) 7.5 / (5) 3  / (6) 7.5  

or

(4) 7.5  / (5) 5  / (6)

Link to comment
Share on other sites

12 minutes ago, GreatOne2k said:

The (6) has to run at 5 tph when the (5) is replacing the (2) as 241 St and Flatbush Av can't have 20 minute headways. The (4) has to run local when this happens though

 

It is either: 

(4) 7.5 / (5) 3  / (6) 7.5  

or

(4) 7.5  / (5) 5  / (6)

Yes, this was the pattern that was ran all through Clark. The point is again not that it’s impossible to run (5) at 5, just that the agency prefers not to given the runtime impact of (4) local and the relatively high weekend ridership on Pelham. 

Link to comment
Share on other sites

2 hours ago, RR503 said:

This is very much a NYCT problem. Weekend service reduction is a direct result of the agency’s lack of attention to GO productivity and of flagging rules developed largely by the agency. The agency may not have control over some of the more arcane work rules, but it absolutely can do a better job coordinating projects, properly scheduling work trains and flagging crews, etc. It also could either invest in track barriers to eliminate adjacent flagging, or review flagging rules to understand what in them is working and what is not while comparing to other systems’ practices. And of course there’s always the option of changing the predominant GO format — emphasizing less frequent full shutdowns over the endless dribble of one-direction reroutes. 

With the (4)(5), the issue is the (6) and Brooklyn. You can’t run the (6) at 5tph, nor can you run Lex-Brooklyn or Jerome that low. So you run 7.5/3/7.5, which itself is really pushing it in terms of flagging capacities. I just wish they’d run 3tph of overlay service as far as 149-GC to complement the 3 of Manhattan service. 

Turning (5) trains there would be a real pain, whereas turning the (4) (on the upper level) is rather straightforward. If we must decrease service in Manhattan, the best course would be to run both at 5 tph, have the (5) serve Brooklyn (Flatbush Avenue unless the Nostrand Avenue Line is closed, in which case it'll run to Utica Avenue) and run (4) short-turns between Woodlawn and 149th Street. This keeps the number of people screwed over to a minimum and avoids excessive relaying.

Link to comment
Share on other sites

1 hour ago, Lex said:

Turning (5) trains there would be a real pain, whereas turning the (4) (on the upper level) is rather straightforward. If we must decrease service in Manhattan, the best course would be to run both at 5 tph, have the (5) serve Brooklyn (Flatbush Avenue unless the Nostrand Avenue Line is closed, in which case it'll run to Utica Avenue) and run (4) short-turns between Woodlawn and 149th Street. This keeps the number of people screwed over to a minimum and avoids excessive relaying.

Running (4) shuttles in the Bronx solves nothing because just about everyone riding is going to Manhattan.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.