Lance

None of the converted sets have been in service. Not since 7211 was taken out for mechanical problems months ago.

Precisely.

As long as it takes to build a full-length Second Avenue line. All jokes aside, even if they blitzed every station, completely shutting several down concurrently to install elevators and other ADA necessities, and money was not an issue, it would likely take several years, if not at the very least a decade to make the entire subway accessible.

That's my point. When this GO was done in the past, Transit explicitly stated that Q trains would not stop at 49 St. I don't know why they stopped doing that, but they really reconsider their decision.

Yep. While it is possible, it doesn't make much sense for the Q as the Broadway Express to cut over to the local tracks at 34 St then bounce back over to the express tracks to terminate at Midtown-57 St. I don't know why Transit has gotten out of the habit of mentioning that the Q trains will also bypass 49 St when this GO is in effect.

It's a (very old) glitch in the 142 software. However, since it doesn't affect how the program runs or plays incorrect information that would easily confuse riders, it hasn't been fixed and probably won't be any time soon.

The Q is another interesting exception to the rule. I think it changed over to Helvetica with the J in the mid 1980s because the 1984 27-38 rollsigns contain the Helvetica J and diamond Q, while also retaining the older AG/Standard C and R letters.

The usual suspects are still vying for last place I see. However, the 143s are participating in that race as well unfortunately. That's a bit disconcerting to say the least.

You're better off taking the L to Union Sq for the 6. That way you don't have to deal with the buses.

You are not alone on that. Maybe it's the repetitiveness combined with the verbose nature of the announcements. @YankeesPwnMets: That's not really all that surprising, given that she's done various recordings for several different transit systems and airports around the world. Check out this piece from the New York Times for more.

But something has to be at the stations to trigger the announcements and that will likely add up, considering whatever sensors potentially used would have to be able to handle the varying conditions of the underground stations. Like I said, the wheel detector hardware isn't the best for automated announcements. It's not the worst though either. If the MTA can replace the dated software to something would truly be flexible in terms of reroutes, it would make a world of difference. (Adding WiFi connectivity would be an added bonus for easier updates.)

It's not as bad as you're making it out to be. The problem with using something other than wheel detection to cue the announcements is the same one that prevents real-time tracking without complex signal upgrades like ATS or CBTC. Above ground, there is obviously the option of GPS tracking for both situations, but below ground, that's not as possible. However, with Transit Wireless wiring the system for internet access, that has the possibility to change. The main problem with the announcements themselves is the archaic software used to trigger them. You're right when you say they have their quirks when it comes to unexpected reroutes. For all the talk of Flexible Information and Notice Display, they aren't all that flexible in a pinch. Say for instance you have a 71 Av-bound M at Bryant Park that has to be rerouted via 63rd Street. Instead of a simple option to tell the computer to reroute the announcement program through 63rd Street instead of 53rd Street, the conductor has to reload the entire option from Metropolitan via 63rd Street and then knock off all stops from Metropolitan through 42 St. All that while the conductor has to inform the passengers of the route change, opening/closing doors in a timely fashion, etc. That's why you often see the announcements/FINDs simply turned off. While this method of only allowing routing options from their terminals was acceptable in the early years of the 142s and 143s, computer technology and software has advanced greatly in the intervening years so we don't need to do these things so backwards. Of course, since we're talking about the MTA, which has this strange aversion to technology at times, the likelihood of this changing any time soon is slim.

Until the 188s become the majority fleet on the line (or we at least get some of the converted sets on the rails along with the new builds), you will likely continue to see 62s on the 7-line, including the Mets specials.

You want to know why I highly doubt these "occurrences" actually happened? If the cars were uncoupling and the doors were opening on the wrong side of the train, the train would've been immediately taken out of service. That's a serious safety issue right there. And if it was happening on several sets, you wouldn't see any 188s around until Transit was absolutely sure they resolved the issue. They don't want riders potentially falling out of trains or cars getting stuck on the rails. However, since the 188s are in service fairly regularly, it kind of disproves this rumor.

I'm glad we've still got some level-headed members here. Someone posts one thing and everything snowballs from there despite the lack of any proof. It's becoming a disturbing trend around here as of late. As for why the 188s were all sitting in Corona, think back to when the 160s first hit the L and N lines. I'm sure that back in 2007, there were in fact times when one could go without seeing a single 160 in service. It wasn't a big deal then and it still isn't today. With the exception of 7211 and company, I'm sure the trains are relatively fine.

I guess she didn't feel like playing with the computers this morning. There is an option in the 142s for the 5 from New Lots to Dyre Av, but it's only express from Utica Av to 125 St. Rather than have to add all those local stops in the TOD, she chose the easy solution to go manual through Crown Heights and then turn on the AAS and program it as a 5 local from Utica to Dyre, which is an option on those old computers.

The reason why other useful extensions, like Nostrand, Utica and many others aren't at a higher priority is because they're always behind the never-completed Second Avenue line. Dating way back, probably to the 1939 Second System plans, the plan of action has always been, build Second Avenue, then everything else. Since we can't seem to get Second Avenue done, nothing else gets done. Considering this, it's actually quite amazing we've got the 63rd Street and Archer Avenue stub lines built. Obviously, there is a good reason Second Avenue gets precedence over other projects when expansion funds materialize. One only needs to ride the Lex to see why, but it is a bit disconcerting to see that because we can't get one big line built, we also can't seem to get any of the other much smaller projects done either.

The lack of the appropriate south rollsign is a non-issue and would little to do with them not running on the M. They could sign the trains to Myrtle Av (close enough) or print out a couple dozen B/W posters that indicate the M's terminals and that would solve that problem easy-peezy lemon-squeezy.

(Bowling Green to Wakefield-241 St) on the combined line map I'm not sure about this one, but I decided to post it anyway. It's based on my earlier version with indicators for 7th Avenue and Lexington Avenue service, but it still looks too cluttered in my opinion with the transfers stacked on top of the station names.

Not to my knowledge, no. The M gets first dibs on East New York's 160s, so unless something extrordinary occurs, you won't see that lone 32 on the M.

Except the buffs obviously. Alas, it is what it is. I will be glad when they're gone though. They have been workhorses over their lives, but as of late, we have to keep accommodating them so they don't crap out while in service.

Unless you send both the J and Z via Brighton, that can't be done without throwing off the skip-stop schedule. Sending the Q via Whitehall is an option, but I don't know how well it would be received. Then there are the merging issues at DeKalb since Q trains would have to switch over to the R tracks to run via the tunnel.

They're not going to release a "new train" press statement for a temporary car assignment. You'll likely see one when significant 179 cars arrive on property.

Some goodies from the '90s: R110A 8006 NYC Transit Museum (fmr Court St (IND Fulton Street)) Gin Yee nycsubway,org R110A 8006 NYC Transit Museum (fmr Court St (IND Fulton Street)) Gin Yee nycsubway,org R110A 8007 NYC Transit Museum (fmr Court St (IND Fulton Street)) Gin Yee nycsubway,org R110A 8006 NYC Transit Museum (fmr Court St (IND Fulton Street)) Gin Yee nycsubway,org R110B 3005 NYC Transit Museum (fmr Court St (IND Fulton Street)) Gin Yee nycsubway,org R110B 3004 NYC Transit Museum (fmr Court St (IND Fulton Street)) Gin Yee nycsubway,org R110B 3006 NYC Transit Museum (fmr Court St (IND Fulton Street)) Gin Yee nycsubway,org R110B 3006 NYC Transit Museum (fmr Court St (IND Fulton Street)) Gin Yee nycsubway,org

Starting early this year. Usually they wait until at least after Memorial Day.