Jump to content

SUBWAY - Random Thoughts Topic


Recommended Posts


  • Replies 30.7k
  • Created
  • Last Reply
34 minutes ago, brakethrow said:

Finally that viaduct project is complete. No more (M) trains delaying (J) 's coming into the junction.

You'll still have to deal with that one (M) train crossing in front of the (J) train you're on coming into Myrtle Avenue–Broadway on the Manhattan-bound track. Don't celebrate too soon.

Link to comment
Share on other sites

5 hours ago, EphraimB said:

Interesting. There was someone that pissed me off on the train back to Far Rockaway today and I had to wait until the next stop, Broad Channel, to switch to the next car. If only the (A) would be all 60-footers then I wouldn't have to wait 3 minutes to switch cars.

Sucks for you. 

Link to comment
Share on other sites

26 minutes ago, AlgorithmOfTruth said:

You'll still have to deal with that one (M) train crossing in front of the (J) train you're on coming into Myrtle Avenue–Broadway on the Manhattan-bound track. Don't celebrate too soon.

Now the (J) has more R42’s... I swear those cars are like roaches on that line. Very hard on the eyes. 

Link to comment
Share on other sites

7 hours ago, VIP said:

Now the (J) has more R42’s... I swear those cars are like roaches on that line. Very hard on the eyes. 

Roaches..:D...I really hate them things...But in my opinion they should just moved those from ENY to pitkin already....Put those on the (A) for the remainder of their service lives

Link to comment
Share on other sites

33 minutes ago, biGC323232 said:

Roaches..:D...I really hate them things...But in my opinion they should just moved those from ENY to pitkin already....Put those on the (A) for the remainder of their service lives

Agreed, give those savages some more 60ft cars. They’ll be thankful. 

Link to comment
Share on other sites

9 hours ago, VIP said:

Now the (J) has more R42’s... I swear those cars are like roaches on that line. Very hard on the eyes. 

I disagree, I think there is something charming about them, they keep running even after all the beating they have taken over the years, they are very stoic. Same with the r32s.

Link to comment
Share on other sites

12 hours ago, VIP said:

Now the (J) has more R42’s... I swear those cars are like roaches on that line. Very hard on the eyes. 

 

4 hours ago, biGC323232 said:

Roaches..:D...I really hate them things...But in my opinion they should just moved those from ENY to pitkin already....Put those on the (A) for the remainder of their service lives

Well if you had the newer cars from the (C) they would be very hard on your nose.  Those cars stink like hell. I don't think a mop has touched those cars in God knows when.

Link to comment
Share on other sites

2 hours ago, Via Garibaldi 8 said:

 

Well if you had the newer cars from the (C) they would be very hard on your nose.  Those cars stink like hell. I don't think a mop has touched those cars in God knows when.

207 must really only like the museum trains as the R160s on the (C) are already disgusting and worn. I rode one from 81st to 42nd a few days ago and every time it braked it would screech as loud, if not louder, than a R32. ENY's 32s and 42s are bad but a lot of times not as bad as the 207th street cars...

Link to comment
Share on other sites

3 hours ago, R68OnBroadway said:

207 must really only like the museum trains as the R160s on the (C) are already disgusting and worn. I rode one from 81st to 42nd a few days ago and every time it braked it would screech as loud, if not louder, than a R32. ENY's 32s and 42s are bad but a lot of times not as bad as the 207th street cars...

East New York has the BEST performing R32’s. 207 Street’s maintenance is starting to deplete.  Especially when it comes to washing their cars. 

Link to comment
Share on other sites

1 hour ago, trainfan22 said:

I'm at West 4th right now, I'm waiting for the (A) and an 68A pulls in!!! I'm like oh yeah I'm gonna ride an 68A (A) train home... then the damn thing gets taken out of service due to door trouble smh.

1 set of R68as on the (A) this unlucky ducky gets it.. i feel bad for you but worse for the (B) train riders such as myself

 

 

Edited by KK 6 Ave Local
why not xd
Link to comment
Share on other sites

23 hours ago, boweryboy said:

It was hysterical watching so many passengers this morning at Kosciuszko not get on the (J), expecting an (M) to come next. Read the damn signs! Hipsters...I wanted to get out and shake everyone.

They must have thought the 30th was the last day of service there and didn't care for the signs. Turns out it was gonna end on the 29th (ended up being the 27th)

Link to comment
Share on other sites

39 minutes ago, KK 6 Ave Local said:

1 set of R68as on the (A) this unlucky ducky gets it.. i feel bad for you but worse for the (B) train riders such as myself

 

 

I love the 68A's, I have fond memories of them when they was dominant fleet on the (Q) in the mid 2000s, got me to school reliably a countless number of times.

 

 

With that being said, the (A) right behind it was an 32, which is just as cool to me, but I didn't ride it cause it was packed like sardines (I took the (M) home instead) its funny as once the train pulled in a whole lot of sighs and grunts due to that fact that the train was crushloaded BEFORE the doors opened at West 4th. When I saw it was an 32 I couldn't but to laugh, younger train breaks down and now all these riders gonna squeeze in a 50 plus year old train to get home😀

 

 

 

Link to comment
Share on other sites

4 minutes ago, Calvin said:

Was there a difference on the (M) with train traffic to/from Metropolitan Av compared to Broadway Junction on the (J) ?

There was. At Broadway Junction, trains had only one track to turn, which delayed (M)s waiting to get in and Queens bound (J) service. 

Link to comment
Share on other sites

I have serious misgivings about this " plan " to re-work service on the Brooklyn IRT proposed by some members of the forum. All Seventh Avenue (2) and (3) service to Flatbush-Brooklyn College ? All Lexington Avenue (4) and (5) trains to Utica/ New Lots ? What, exactly is this supposed to accomplish if I may ask ? Has anyone who proposed this " plan " actually used this segment of the IRT before because it ignores the real world usage patterns completely. I'm basing my opinion on almost sixty years of riding the New Lots and Nostrand Avenue lines. I'll throw in 30 years of NYCT work experience, too. Starting when the first SMEE equipment appeared on the (2) Dyre to New Lots line. Back when the (5) ran to Utica during rush hours and the (4) supplemented the (3) service to the 'Bush during the rush. When there was no Lex service south of Atlantic middays. Back when I made the 3:45 (5) put in from Atlantic or the 3:54 (5) put in from Franklin. Over the years things improved and we got (4) Lex service from Utica , meaning the Brooklyn IRT had express service besides the rush . Passengers from ENY, Brownsville, and eastern Crown Heights got a service improvement while Nostrand Avenue riders were left in the cold. They were subjected to the madhouse crowding at Franklin Avenue where n/b (3)  and later, (2) riders had to transfer to Lexington Avenue (4) trains in addition to the ever present transfers by the New Lots and Utica people who had to endure the up and down move there to reach the Flatbush trains heading in the opposite direction. Don't overlook the fact that before any Lex service was provided mid day the Nevins Street station was the transfer point. All the newer service pattern did was move the transfer point, and crowding, to Franklin Avenue. Finally a service plan came out that every rider I encountered and my family and friends liked. The extension of the mid day (5) from Bowling Green to Flatbush-Brooklyn College. Finally everyone on both branches had a choice, Seventh or Lexington service. The holy grail if you will. Now I see that some forum members want to remove that option. I thought I read somewhere that this proposal would speed up service because the (5) wouldn't have to traverse the switches it now utilizes to get from President St to the n/b express track. That is something probably thought of by someone who glanced at a track map and never saw the interlocking plant even from a RFW. That interlocking is timed and always has been, whether your lineup is the local or express track heading into Franklin Avenue. T-I-M-E-D, heading n/b. Guess what ? Heading s/b toward Utica, Nostrand or President Street the interlocking is timed. If I'm operating a n/b Lexington train stopping at Kingston and Nostrand Avenues and I'm heading for the express track into Franklin Avenue I'm subject to the same timers as before and the n/b train at President St is going to have the same wait as it does today. Before someone suggests, or maybe I missed it, if that n/b train leaving Nostrand doesn't cross over before Franklin Avenue once that train leaves Atlantic on the local track, you guessed it, timers in effect to bring the train over to the n/b Lex tracks. Maybe there are other parts to the proposal that I've overlooked but operation-wise these are the limitations that I see offhand. BTW, if the Lexington line is the most utilized and desired by the ridership increased speed or capacity on the Seventh Avenue side is an exercise in futility if it doesn't improve their commute. Take this (2) or (3) from Flatbush to Times Square and transfer for the shuttle, (7) , or (Q) , for example, sounds like something only a railfan would tell someone. Just my thoughts. No hard feelings if you don't agree with me. This is a discussion thread after all. Carry on.

Link to comment
Share on other sites

When recently has this been brought up? 

Anyway, I think you're misidentifying the problem here. The issue with the current Rogers set up isn't slow speeds on the (5). It's the fact that that junction restricts A division express capacity moreso than any other single factor, and does so while making any issue on any of the served lines into an issue on all A div expresses.

I don't think I need to remind you that Rogers is currently maxed out. The fact that (5)s have to make that diverging move across the (2) and (3)s path puts a very real cap on the number of trains per hour any of those lines can run (a cap which extends to the (4) by merit of merging). And may I remind you that while the Lex corridor is pretty much saturated service wise (with platform crowding mitigation, you could maybe send an extra 1 or 2 tph up there before timing restricts you), the 7th avenue expresses can take another 4-6 tph of service over the rest of their routes -- if it wasn't for Rogers.

Moving beyond capacity, though, service through that junction is currently shit. It isn't just slow speed due to timers, or limited train frequency. It's that sitting in the tunnel waiting for a lineup through the interlocking is now such a quotidian event that we now schedule some (2) and (5) trips to have six minutes between Franklin and President. And remember, this is the MTA, where we never adjust schedules.

But even this seems to not be enough. I have a friend who commutes daily from Newkirk on the (5), and at least three times a week, she'll complain of waiting for more than five minutes coming into the junction for want of a lineup through it. But even beyond that, I'll sometimes hear of how something at 72nd St led to (2)(3) service getting bunched, creating a parade of late local trains hogging lineups through Rogers, making the (4)(5) have the same problem. It'd be one thing if this was some relatively low ridership corridor, but we're talking the (4)(5) here. A gap of as little as 4 minutes on those lines can create platform crowding issues elsewhere on the corridor that so impact train service and customer experience that we sometimes have to bar entry to stations. If I could, I'd hermetically seal the (4)(5). Those trains are f**king toxic. 

Now, in terms of mitigation, changing service patterns won't be enough. The crossover configuration means that even with the suggested setup, trains would still have to cross paths for that segment of track between the express/local crossover and the Nostrand diverge. For this to work, you'd have to at the very least install a new crossover beyond the Nostrand diverge so that whichever Lex service ends up serving Nostrand and Kingston can do so without interfering with (2)(3) service. And about timers: don't regard them as absolutes. Many of those timers at Rogers should be either eliminated, raised, or converted to DGTs so their function better reflects their purpose and need. I don't think citing them as a reason for not implementing a service change is rational unless you can make the case that they all must stay, and that they will all sustain the same delay cascading/capacity restriction issues as today's interlined set up.

For more on potential junction design changes, I urge you to look at this:

http://www.vanshnookenraggen.com/_index/wp-content/uploads/2018/03/IRT-Nostrand-Junction-Report.pdf

Finally, customer preference. Yes. It's very important. I take two issues with your characterization, however. I first play don't think that Franklin will experience crowding that is in any way equivalent to that of our systems more packed stops. There simply is not the ridership to create it, especially not if trains are running with today's frequencies. Regardless, I think the larger issue many here and elsewhere have is that they only see the preferences of customers in the directly impacted area. We can't think like that. Yes, some will lose access to the precious Lex. But they'll simultaneously gain better, more frequent train service. And the literal millions who use these lines elsewhere in the city will benefit too. Their commutes on the (2)(3)(4)(5) will be less insufferable than they are today as the effects of shorter headways and fewer delays play out across the system. In short, I think their preferences should be included too. 

Link to comment
Share on other sites

8 minutes ago, RR503 said:

When recently has this been brought up? 

Anyway, I think you're misidentifying the problem here. The issue with the current Rogers set up isn't slow speeds on the (5). It's the fact that that junction restricts A division express capacity moreso than any other single factor, and does so while making any issue on any of the served lines into an issue on all A div expresses.

I don't think I need to remind you that Rogers is currently maxed out. The fact that (5)s have to make that diverging move across the (2) and (3)s path puts a very real cap on the number of trains per hour any of those lines can run (a cap which extends to the (4) by merit of merging). And may I remind you that while the Lex corridor is pretty much saturated service wise (with platform crowding mitigation, you could maybe send an extra 1 or 2 tph up there before timing restricts you), the 7th avenue expresses can take another 4-6 tph of service over the rest of their routes -- if it wasn't for Rogers.

Moving beyond capacity, though, service through that junction is currently shit. It isn't just slow speed due to timers, or limited train frequency. It's that sitting in the tunnel waiting for a lineup through the interlocking is now such a quotidian event that we now schedule some (2) and (5) trips to have six minutes between Franklin and President. And remember, this is the MTA, where we never adjust schedules.

But even this seems to not be enough. I have a friend who commutes daily from Newkirk on the (5), and at least three times a week, she'll complain of waiting for more than five minutes coming into the junction for want of a lineup through it. But even beyond that, I'll sometimes hear of how something at 72nd St led to (2)(3) service getting bunched, creating a parade of late local trains hogging lineups through Rogers, making the (4)(5) have the same problem. It'd be one thing if this was some relatively low ridership corridor, but we're talking the (4)(5) here. A gap of as little as 4 minutes on those lines can create platform crowding issues elsewhere on the corridor that so impact train service and customer experience that we sometimes have to bar entry to stations. If I could, I'd hermetically seal the (4)(5). Those trains are f**king toxic. 

Now, in terms of mitigation, changing service patterns won't be enough. The crossover configuration means that even with the suggested setup, trains would still have to cross paths for that segment of track between the express/local crossover and the Nostrand diverge. For this to work, you'd have to at the very least install a new crossover beyond the Nostrand diverge so that whichever Lex service ends up serving Nostrand and Kingston can do so without interfering with (2)(3) service. And about timers: don't regard them as absolutes. Many of those timers at Rogers should be either eliminated, raised, or converted to DGTs so their function better reflects their purpose and need. I don't think citing them as a reason for not implementing a service change is rational unless you can make the case that they all must stay, and that they will all sustain the same delay cascading/capacity restriction issues as today's interlined set up.

For more on potential junction design changes, I urge you to look at this:

http://www.vanshnookenraggen.com/_index/wp-content/uploads/2018/03/IRT-Nostrand-Junction-Report.pdf

Finally, customer preference. Yes. It's very important. I take two issues with your characterization, however. I first play don't think that Franklin will experience crowding that is in any way equivalent to that of our systems more packed stops. There simply is not the ridership to create it, especially not if trains are running with today's frequencies. Regardless, I think the larger issue many here and elsewhere have is that they only see the preferences of customers in the directly impacted area. We can't think like that. Yes, some will lose access to the precious Lex. But they'll simultaneously gain better, more frequent train service. And the literal millions who use these lines elsewhere in the city will benefit too. Their commutes on the (2)(3)(4)(5) will be less insufferable than they are today as the effects of shorter headways and fewer delays play out across the system. In short, I think their preferences should be included too. 

The physical layout between Nostrand , President and Franklin Avenue preclude installing a  newer crossover at that location without a rebuild of the whole junction which is why it has never been attempted. I was taught that more than 30 years ago by people who knew the plant and surrounding signals, columns, and the general topography. I have physically walked the north and southbound tracks from Utica Avenue, Nostrand Junction tower, President St tower, and the s/b track 3 from Atlantic Avenue to Utica Avenue pulling cable the length of track from point to point on a work train 5 nights a week when the old tower at the junction was decommissioned and relocated to the present tower at Utica Avenue. Senior motor instructors and a Trainmaster were my teachers back then. I think I'll defer to their knowledge. Carry on.

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.