Jump to content

Abba

Veteran Member
  • Posts

    2,535
  • Joined

  • Last visited

Posts posted by Abba

  1. Today I heard the on scanner the train operator of N train announce the incident at 20av. I can’t day exactly what I heard but I will say say he sounded very upset 😢 .Also I happenend to be going to 86st on R line when the Jay St incident occurred . At Atlantic Platform was packed ! I was first thinking why not run some trains local but it’s very hard to do that since they have to stop at DeKalb and merge with the (B) and (Q) . One (N) went local 2 (D) ‘s cane went express . I took one and for heaven sake why do we have to wait 3 min to get into 36th st .Why dosnet the train operator announce himself by like 25th and then they will just give the lineup. I don’t understand. Especially with countdown clocks don’t the tower operators know what train is coming ?

  2. 20 hours ago, Daniel The Cool said:

    It depends on the issue whether they can divert all trains to run local or run express and that Saturday night incident, they couldn't send anything through because the switch issue blocked off both tracks (Southbound). And if this happened during the weekday Rush Hours or Middays, I can tell you it would've been much worse.

    But I think they would have worked quicker to fix it but that’s just me . I think  this issue might have been caused by trackwork and it’s possible today’s  Burnside Ave issues were also caused by trackwork.

  3. 31 minutes ago, BM5 via Woodhaven said:

    Service Change  Posted: 08/05/2018 12:07AM 
     

    There is no (A) and (D) train service in both directions between 59 St-Columbus Circle and 125 St because of switch problems at 72 St.

    For service between 59 St-Columbus Circle and 125 St, passengers can take M10 or (1) train service stopping at nearby (A)(D) stations. 

    I have a question ? If this happend during rush would service still Be out? Something tells me no! Anyone agree? 

×
×
  • Create New...

Important Information

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