Jump to content

SUBWAY - Random Thoughts Topic


Recommended Posts

5 hours ago, R32 3838 said:

 

The R44 retirement played a role in the cuts. The (V) line fleet (R46s and the 26 R32s) went directly to the (A) when they did the cuts which in turn was planned to wipe out the remaining R44s that were running on the (A) but the R32s HVAC units started crapping out on the (C) so they kept a handful of R44s by running them on the (C) and having the R32s run on the (A) until September when they finally retired the R44 fleet for good.  Budget was primarily the reason but also the lack of subway cars. Merging the   <M> with the (V) help lessen the blow of the car shortage. Plus the (W) would have been reduced anyway due to 2nd ave construction, Around that time 63rd st where they used to lay up midday trains was not in use so they had lay up trains between times sq and 49th st. This is why the (Q) went to Astoria as well besides replacing the (W).

 

Cutting service is not going to be an option when you have most of NYC already angry about them wanting to go forward with congestion pricing. This would be political suicide if they allow cuts. They are going to have to really think outside the box to keep the budget balanced. The worse case scenario would to merge a line similar to the (M)  or replace a portion of a route like example (E) train running to Euclid ave to replace the (C) in brooklyn (I doubt this would happen, Just an example) Or Have the (5) only serve flatbush Rush Hours only like before or just completely cut it in brooklyn all together (I also doubt that would happen since it's un realistic but these are examples)

 

They really can't cut much like for example, The (W). Politics will get involved now since there would be no replacement like in 2010 (I still think Astoria doesn't need 2 services, 1 is good enough with increased service) But in reality everything will be a shitshow if they even try to cut subway service. Buses on the otherhand.......

 

 

1. The (W) being cut due to 2 Av construction is not correct. Had the budget been on track, they would have just ran those midday layup trains back to Brooklyn in service like they do now.

2. The only thing I think that could be “cut” is the (W) (since when does the MTA give a f**k about Astoria these days), maybe the Rockaway Park (A) trains, the non-rush hour (5) from Brooklyn, and the (B) to/from Bedford Park Blvd, although the (B) cut wouldn’t save any money, similar to the (Z) cut since then the remaining service would have to be boosted and local to cover service. 

Link to comment
Share on other sites


  • Replies 30.8k
  • Created
  • Last Reply

Not sure if this is old news or new but, lately, when using the (J) train to get to/from Jamaica Center and Broadway Junction while getting the (A)(C) from there, the R160s on the (J) hasn't been coupled using the 8313-8376 portion from the (L) mated with 8377-8652 or 9943-9974 that's shared. It happened before CBTC started on Queens Blvd but I wonder with the 4-car R160s past 8377 and 9900s having/getting CBTC from the (M) prevented it for confusion. That being, CBTC on the (L) mated with CBTC from the (M) as one train for the (J) 

Edited by Calvin
Link to comment
Share on other sites

9 hours ago, R32 3838 said:

 

The R44 retirement played a role in the cuts. The (V) line fleet (R46s and the 26 R32s) went directly to the (A) when they did the cuts which in turn was planned to wipe out the remaining R44s that were running on the (A) but the R32s HVAC units started crapping out on the (C) so they kept a handful of R44s by running them on the (C) and having the R32s run on the (A) until September when they finally retired the R44 fleet for good.  Budget was primarily the reason but also the lack of subway cars. Merging the   <M> with the (V) help lessen the blow of the car shortage. Plus the (W) would have been reduced anyway due to 2nd ave construction, Around that time 63rd st where they used to lay up midday trains was not in use so they had lay up trains between times sq and 49th st. This is why the (Q) went to Astoria as well besides replacing the (W).

 

Cutting service is not going to be an option when you have most of NYC already angry about them wanting to go forward with congestion pricing. This would be political suicide if they allow cuts. They are going to have to really think outside the box to keep the budget balanced. The worse case scenario would to merge a line similar to the (M)  or replace a portion of a route like example (E) train running to Euclid ave to replace the (C) in brooklyn (I doubt this would happen, Just an example) Or Have the (5) only serve flatbush Rush Hours only like before or just completely cut it in brooklyn all together (I also doubt that would happen since it's un realistic but these are examples)

 

They really can't cut much like for example, The (W). Politics will get involved now since there would be no replacement like in 2010 (I still think Astoria doesn't need 2 services, 1 is good enough with increased service) But in reality everything will be a shitshow if they even try to cut subway service. Buses on the otherhand.......

 

 

I'm not sure what your not getting. If the (MTA) has no money, they have to do cuts, public input or not. But rest assured that they will go after the lines preforming the worst, which are the ones I mentioned, as well as giving station hour cuts to least used stations.

Astoria needs to suck it up. Most of the outerlying terminals through the system are only serviced by one line. You don't hear us complaining when the (9) got cut.

Edited by Lawrence St
Link to comment
Share on other sites

1 hour ago, Lawrence St said:

I'm not sure what your not getting. If the (MTA) has no money, they have to do cuts, public input or not. But rest assured that they will go after the lines preforming the worst, which are the ones I mentioned, as well as giving station hour cuts to least used stations.

Astoria needs to suck it up. Most of the outerlying terminals through the system are only serviced by one line. You don't hear us complaining when the (9) got cut.

They tend to go after the buses first before they hit the subway. The bus redesigns are nothing but glorified cuts and merged routes. There is some good to the redesigns and improvements but overall it's cuts. If it comes to the point if they have to cut  with the subway, It is what it is but it won't sit well with people and would be political suicide on the governors part. That's all i'm saying. This isn't 2010 anymore, A lot has changed since then and (MTA) has been caving in to bullshit like the strollers on the buses and etc. With the addition of trying to add congestion pricing in fall 2023.

 

The only thing they'll likely do first is reduce service all week instead of Monday and Friday before they think about major cuts. They are already changing things up piece by piece (example The Reduction of service during midday on select routes Monday and Friday.)

Link to comment
Share on other sites

13 hours ago, Mtatransit said:

Well to be fair, you have a expected budget shortfall, you have to do two things to balance the budget, either increase the revenue, such as a government bailout. The congestion pricing goes to MTA's capital projects, not operations, that fare increase or reduce expense. 

Reducing expense without increasing the productivity of the workers (both managements and unions) means service reductions is probably the only option. It doesn't look like the MTA is looking very hard to save money anyways

 

But when there is service reductions, something has to go, hard decisions will have to be made

Not saying the (B) isn't needed or the weakest link in Brooklyn, but if there is a budget hole, the weakest link is the first one to go. 

 

The 2010 cuts was also because of budget shortfalls not R44 retirement

We should be exhausting every other possible way to either raise enough revenue to properly fund Transit operations or cut excess staffing in the (MTA)‘s very extensive ranks of management before we turn to cutting bus and subway services. You can’t run a military with too many generals and not enough soldiers. A public transit agency is no different in that regard. And like you said, the (MTA) aren’t looking very hard to save money anyway, so all this talk of cutting services is moot…for now.

And how far ahead did the (MTA) come out anyway after cutting the Bay Pkwy <M> and the (W) and the (G) to Court Sq in 2010?

Edited by T to Dyre Avenue
Link to comment
Share on other sites

On 12/30/2022 at 4:14 AM, Wallyhorse said:

And the only way I would do that is if the <R> was moved to Nassau (with the (W) becoming full-time) to help it in Brooklyn. 

The (J) can terminate at Broad with or without another Nassau St service running through to South Brooklyn. It did so for decades. It doesn’t need to be cut back at all.

Link to comment
Share on other sites

2 hours ago, T to Dyre Avenue said:

We should be exhausting every other possible way to either raise enough revenue to properly fund Transit operations or cut excess staffing in the (MTA)‘s very extensive ranks of management before we turn to cutting bus and subway services. You can’t run a military with too many generals and not enough soldiers. A public transit agency is no different in that regard. And like you said, the (MTA) aren’t looking very hard to save money anyway, so all this talk of cutting services is moot…for now.

And how far ahead did the (MTA) come out anyway after cutting the Bay Pkwy <M> and the (W) and the (G) to Court Sq in 2010?

 

Cutting the <M> from bay parkway kinda made sense by merging it with the (V). The only downfall is 4th ave lost a 2nd local train. Plus they had no other choice as the R44s needed to be retired and the portion that remained before the cuts were not replaced by the R160s as all of them were already delivered. By merging the <M> with the (V), It freed up about 15 trains of R46s from the (V) to kill off the remaining R44s.

The (W) we all knew was coming back, It was mainly temporary due to 2nd ave construction in the 63rd st tunnels that the (Q) used for midday lay ups.

The (G) being Cut to Court Sq was mainly due to Queens Blvd CBTC work but The (G) should return to Forest Hills during late nights and Weekends. During the week it can stay at Court Sq. Having only the (R) as an option sucks on weekends.

The Cuts really effected the buses more since they really went ham on the buses in all the boroughs.

 

Link to comment
Share on other sites

Just now, JustTheSIR said:

For the Rockaway Park shuttle why don’t they make it a triangle, Broad Channel to Rockaway Park, Rockaway Park to Far Rockaway, Far Rockaway to Broad Channel, and vice versa, while cutting the Rockaway A trains to Broad Channel 

Then you’re making the Far Rock Mott Ave passengers have a longer trip since they have to sit thru the journey to Rockaway Park and back. Also, they would probably have to fumigate the Rockaway A train at Broad Channel and that’ll be its own headache. Considering the A’s poor frequencies and bad scheduling, it’ll be quite a terrible game of unblock me if there is more than 1 (A) train coming in. 

Link to comment
Share on other sites

On 12/31/2022 at 9:58 AM, Calvin said:

Not sure if this is old news or new but, lately, when using the (J) train to get to/from Jamaica Center and Broadway Junction while getting the (A)(C) from there, the R160s on the (J) hasn't been coupled using the 8313-8376 portion from the (L) mated with 8377-8652 or 9943-9974 that's shared. It happened before CBTC started on Queens Blvd but I wonder with the 4-car R160s past 8377 and 9900s having/getting CBTC from the (M) prevented it for confusion. That being, CBTC on the (L) mated with CBTC from the (M) as one train for the (J) 

The R160A cars 8313-8376 can only run in series with themselves for Canarsie CBTC and aren’t compatible with Queens Blvd CBTC. 8377-8652/9943-9974 can run as they please. Technically, 8313-8376 can run with the R143s 8101-8312 as a single consist (successfully tested on the (J) a few months back). The (J) can use whichever R143s, R160s, and R179s it wants, but the (L) can only use cars 8101-8376, while the (M) can only use 8377-8652/9943-9974, which is why the R160s are grouped as such.

Edited by darkstar8983
Link to comment
Share on other sites

1 hour ago, JustTheSIR said:

For the Rockaway Park shuttle why don’t they make it a triangle, Broad Channel to Rockaway Park, Rockaway Park to Far Rockaway, Far Rockaway to Broad Channel, and vice versa, while cutting the Rockaway A trains to Broad Channel 

Before 1993, the late night (H) ran almost exactly like this, except it started and ended at Euclid Ave. Service ran very infrequently, even by late night standards.

Link to comment
Share on other sites

6 hours ago, danielhg121 said:

Then you’re making the Far Rock Mott Ave passengers have a longer trip since they have to sit thru the journey to Rockaway Park and back. Also, they would probably have to fumigate the Rockaway A train at Broad Channel and that’ll be its own headache. Considering the A’s poor frequencies and bad scheduling, it’ll be quite a terrible game of unblock me if there is more than 1 (A) train coming in. 

Doesn’t “vice-versa” mean the other way around or something? 

also wtf is up with A frequencies? It only interlines with the D?

 

Link to comment
Share on other sites

I don't see an issue with the merge at 59th between (A)(B)(C) and (D) trains since those are switches that trains can go about 25mph over. The Hoyt merge kinda sucks but that can be modified if they built a high speed switch.  Canal St is the only issue as it causes delays to all 3 (A)(C) and (E) lines which could be corrected.

 

A good chunk of you guys lack common sense and think everything has to be de interlined when its completely normal for routes to merge. There are certain things that do need to be corrected but not everything should de interlined just for the sake of it. Railroads have routes that merge but it works because trains do not go 10mph over switches that you can go 20-30mph on. All of these changes you guys are proposing costs money that we all know they don't have. And if were up to me, The only 2 junctions that would be corrected would be dekalb with a new 4 track underwater tunnel connecting Broadway and 6th ave lines and the rogers junction which was going to be corrected and was in the planning stages before the pandemic hit. 

 

Broadway can get corrected

8th ave can be corrected

These 2 wouldn't hurt because its very simple and much cheaper esp Broadway. Just have the (R)  and (W) serve Queens while the (N) / (Q) serves 2nd ave. This eliminates the merging point at 34th st and keeps the express trains on their own tracks.

 

 

Edited by R32 3838
Link to comment
Share on other sites

10 hours ago, JustTheSIR said:

Doesn’t “vice-versa” mean the other way around or something? 

also wtf is up with A frequencies? It only interlines with the D?

 

The (A)‘s main problem is the Rockaways (particularly the south channel bridge which opens for marine traffic all times except rush hours on a whim - 6:20AM to 8:20AM and 4:20PM to 6:20PM). And if you check the schedule for the weekday (A) west of Rockaway Blvd (207 St to Rockaway Blvd) it is not as even as you think.

Link to comment
Share on other sites

9 hours ago, darkstar8983 said:

The (A)‘s main problem is the Rockaways (particularly the south channel bridge which opens for marine traffic all times except rush hours on a whim - 6:20AM to 8:20AM and 4:20PM to 6:20PM). And if you check the schedule for the weekday (A) west of Rockaway Blvd (207 St to Rockaway Blvd) it is not as even as you think.

Yeah them not opening the bridge at all during the Rush Hour at all is nowhere near true. They had numerous instances where the South Channel was open for marine traffic during the Rush Hour. 

Link to comment
Share on other sites

On 12/4/2022 at 8:43 PM, Calvin said:

Today is the new pick for the MTA New York City Subway: 

 

One of the lines have adjusted changes to its timetable. 

 

The (7) Flushing line: 

PM put-ins out of Corona Yard leaving 111 St before today: 4:27 PM, 4:32 PM, 4:38 PM, 4:40 PM, 4:48 PM, 4:50 PM, 4:58 PM, 5:00 PM, 5:09 PM, 5:11 PM, 5:15 PM and 5:17 PM 

Current: 3:52 PM, 4:18 PM, 4:32 PM, 4:36 PM, 4:38 PM, 4:40 PM, 4:48 PM, 4:50 PM, 4:58 PM, 5:03 PM, 5:05 PM, 5:15 PM and 5:17 PM. 1 Extra added put-in from the CBTC Flushing line. 

Adjustments made at Flushing-Main St, Mets-Willets Point dropout was cut (9:30 AM before today leaving Hudson Yards and 5:04 PM on Friday, 12/2, 5:14 PM was moved from the 5:09 PM departure to Mets-Willets Point)

https://new.mta.info/document/9461

 

The (B) Brighton / 6 Av Express line: 

Going to Brighton Beach, additional time was added by 2-5 minutes. 

Leaving Brighton Beach, 2-3 mins early than before. 

https://new.mta.info/document/9481

 

Replying back to the thread because there are more changes that have been reflected: 

The 9:30 AM trip from 34 St-Hudon Yards on the (7) to Willets Point was swapped to 8:19 AM. 8:13 AM was the adjustment. 

 

The (4) train: 

- There are 2 added trains from the AM side to accommodate more passengers on Lexington Av. 4:58 AM and 5:29 AM from Woodlawn to Bowling Green and 5:54 AM with 6:27 AM leaving Bowling Green back to Woodlawn. (Midnight)

- 10:55 AM was the old tripper from Utica Av to Burnside Av is now leaving at 7:46 AM, Burnside Av bound. 10:06 AM from Utica Av is the last tripper to Burnside Av. The train that pulls into Mosholu Yard gets there by noon time. However, a PM group does a put-in at Mosholu Yard as there is now one that leaves Lehman College at 1:55 PM from the Yard. 10:30 AM and 10:55 AM have been changed to terminate at Woodlawn.  (AM)

- 3:47 PM from Utica Av has been changed to end at Bedford Park Blvd-Lehman College to go to Mosholu Yard. The 4:59 PM train that starts at Bedford Park Blvd has been shifted as 4:49 PM to leave at Woodlawn. 4:45 PM leaves to New Lots Av from Woodlawn, 4:43 PM. The last 4-train to leave Mosholu Yard during the PM is 4:26 PM. 

The 3 trains that end at Burnside Av from Utica Av, 6:04 PM, 7:04 PM and 7:29 PM. The 6:48 PM has been diverted to Woodlawn. (PM). 

 

Link to comment
Share on other sites

On 1/2/2023 at 4:24 PM, darkstar8983 said:

Technically, 8313-8376 can run with the R143s 8101-8312 as a single consist (successfully tested on the (J) a few months back). 

No they can not.

That was not a “successful” test.

That wasn’t even a test.

That was an accident that should NEVER have left the yard!

 

you guys all just assumed it was an intentional test.

Link to comment
Share on other sites

1 hour ago, Kamen Rider said:

No they can not.

That was not a “successful” test.

That wasn’t even a test.

That was an accident that should NEVER have left the yard!

 

you guys all just assumed it was an intentional test.

How tf does something like that happen

edit: and why doesn’t the MTA build NTTs to be interoperable like the early SMEEs

Edited by JustTheSIR
Link to comment
Share on other sites

15 hours ago, Kamen Rider said:

No they can not.

That was not a “successful” test.

That wasn’t even a test.

That was an accident that should NEVER have left the yard!

 

you guys all just assumed it was an intentional test.

Wait what?!?!?!?! How did that happen? How do people that work in car maintenance AKA people that KNOW the subtle differences between different train car types compared to Joe Public make that kind of mistake (an R143 + an R160 in a mixed consist IN SERVICE - its one thing for a non-revenue move, but this is with passengers and expected to run properly in service. 

I can only assume they reprimanded or fired the person who set that consist up.

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.