Jump to content

Lance

Veteran Member
  • Posts

    3,197
  • Joined

  • Last visited

  • Days Won

    35

Posts posted by Lance

  1. If I explicitly meant the "A line" as you see it I would have explicitly typed "the (A) ".

     

    And if the R32's were retired the damn R44's would have stayed. They would have ultimately been forced to pick the lesser of two evils, and by that I mean car classes.

     

    The MTA may do a lot of stupid shit, but they usually manage to come through with having an actual fleet to provide service. Cutting the (C) outright would have been the biggest f**k up of 2010 and even I could never even fathom that.

    You're right. Even if by some stroke of extremely bad luck and the 32s were retired before the 44 issues cropped up, they would not cut an important secondary line like the C. The merger of the M and V may not have happened and a few lines would've seen reductions in service. Of course, the 179 order would've been rushed up a bit and whatever 44s that were in good enough condition to be in service would remain active.

  2. The problem with a question like that is there are so many variables to deal with. Where will these lines run? Specifically, where are the termini? That plays an important part as to how often trains can run (which is another question), especially when the terminus of one line is a through-station for another. Also to be included is when these lines would operate. Would they run all day or just for one part of the day? You really can't answer the question of how many lines can be run without dealing with or eliminating some of these factors.

  3. Reminder: The goal of FASTRACK is to shut down a specific part of a line while affecting as few other lines as possible. It's also to spend as little money on providing alternate methods of transit as possible. Your (M) (or (J))to 168 St does the opposite of that. Your idea calls for the extension of the (M) to damn near its full length, but along Central Park West instead of Queens Blvd or extending the (J) well beyond its full length route and for what benefit? You claim it's to provide good service for (A) line riders east of Broadway-East New York, but if either of your ideas were implemented, riders would still have to transfer between the (A) and (J) at the Junction (and would have to transfer again if your (M) plan specifically was enacted). On the subject of the (J) option, what would serve the stations south of Delancey-Essex Sts? You can't shaft one part of the system at the "benefit" of another. Once again, it looks like you're trying to serve a very niche market by rearranging the subway when the easiest option is the one the MTA put forward, which is to run shuttle buses through the affected area.

  4. Looking at the month ahead (weekend-wise), here are the major disruptions that are planned for January:

     

    (4) - no service between 149 St and Woodlawn (1/4, 1/11)

    - shuttle buses run from 149 St to 161 St, Woodlawn to Bedford Park Blvd (D)

     

    (5) - no service between E 180 St and 149 St-Grand Concourse (1/18)

    - shuttle service runs every half-hour along Dyre Avenue branch

     

    (A) - no direct service between Howard Beach and the Rockaways (1/4)

     

    (D) - shuttle buses replace trains between 205 St and Bedord Park Blvd (1/18)

     

    (G) - alternate Queens-bound trains turn at Bedford-Nostrand Avs (1/11, 1/18)

     

    (J) - no service between Essex St and Chambers St (1/11)

     

    (R) - service extended from 71 Av to 179 St (1/18)

     

    A few more things of note include the (F) running via 53rd Street (Queen-bound) almost every weekend, the (A) and (C) via Rutgers and (F) via Cranberry (both Brooklyn-bound) for a weekend each and one-direction express only service along parts of the Queens Boulevard Line.

  5. Well the ultimate solution to this entire thread, not to boast is simple. The MTA in the 60's and 70's should have carried out their promise to replace the 3rd Ave El with the (T) to the Bronx with a new subway as stated in their presentations. That would have solved everything.

    Yes, the "ultimate solution". As if it's so feasible. Not to be mean or anything, but from the way you name-check the T-line, some would assume you're getting a paycheck every time you do so.

  6. Not for nothing, but your post is a bit contradictory. If the C had a lot of hot cars when it ran the A1s last summer, what would sending more over there do? Besides, wasn't last summer's swap a two-fold solution of upgrading the 160s out of East New York and giving the 32s some much-needed fresh air for the compressors? Unless the former is still going on next summer, wouldn't it make more sense to return to the 32/46 swap?

  7. A better question would be "which sets don't use the "Manhattan-bound" announcement in Manhattan?" If I'm not mistaken, it's a glitch in the software that leads to this happening on the trains. I don't think it's really limited to any particular sets, unlike when someone catches a train with older transfer announcement files or old strip maps.

  8. Like I said, service to and from Jamaica Center seems to be unaffected, based on how this service advisory is worded. If it was affected, the advisory would read something like "Trains run every [X] minutes between [briarwood] Van Wyck Blvd and Jamaica Center." Instead, it reads as such: "Additional service operates between World Trade Center and [briarwood] Van Wyck Blvd." There will be additional service on the E-line for those two weekends, not less. It's just that those added trains will run to 179 St instead of Jamaica Center.

  9. Late nights and weekends it will run to/from Essex St. Now if it will still run OPTO on weekends is another question...

    It'll remain OPTO unless it's extended past Essex St. Also, the M will run to Essex St during the daytime and evening hours on weekends. Service will continue to terminate at Myrtle Av during the overnight hours.

  10. It dosent say massive.Just says ongoing signal problems.Give a little explanation and some updates as to when service will be restored.its been going on for about 18 hours now.

    Ny1 says its a broken fiber cable.They say they are hoping service will be restored.They are giving better explanations as to when service will be restored.

    http://www.ny1.com/content/news/transit/199878/l-train-issues-cause-morning-commute-headaches

    Since I can't watch the video without a TWC account (stupid if you ask me, but whatever), I'm going to have to take your word that some other information was mentioned in the aforementioned video because the article itself just paraphrases the MTA service alert.

  11. Here's an interesting service change (starts the weekend of 12/14):

     

    E.png Additional service operates between World Trade Center and Van Wyck Blvd 

    Weekends, 9 AM to 7 PM, Sat, until Dec 21 
                      11 AM to 6 PM, Sun, until Dec 22 

    Alternate E.png trains run to/from the 179 St F.png Station.
     
    I wonder if service will be cut on the F-line for some reason that would require the E to be doubled like this.
  12. Wait a minute... One minute you complain about the (MTA) not maximizing on services they provide, and then the next you complain about them trying to market their services to get more people to use it.  Which is it?  They're marketing their SBS service because they want to increase usage on their bus network. I don't see anything so terrible about that.

    I'm just questioning why these glorified limited bus routes have to be announced while the rest of the bus network gets left to the wayside. The other local/limited bus routes don't get a mention. And I never said it was terrible that they're mentioned.

×
×
  • Create New...

Important Information

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