7-express

Has anyone noticed that the MTA app seems to be missing multiple Q routes this morning, rendering it impossible to track buses?  Other boroughs seem to be working though.

A few more updates on the express bus funding here: https://www.amny.com/transit/mta-express-bus-service-congestion-pricing/

3 hours ago, IAlam said:

 

I’m hoping the CP express routes are protected in the wake of congestion pricing, especially since they’re trying to cut service with the redesign.

If I was a betting person, I would say they're going to put the Queens express redesign on ice until congestion pricing ridership patterns are established in the fall to see what actually needs tweaking.

Not that it matters since CP is essentially running the service cut schedule anyways with the amount of missing runs due to a lack of drivers.

On 4/27/2024 at 8:31 AM, mikecintel said:

I see about your grandfather.  Oh wow they are still giving out Metro cards to seniors still....unreal.  But they tell people to switch to OMNY cards.  Not all people have smart phones and smart watches like elders.  They probably have basic phones like flip phones.  Guess we will wait.  Now we have to wait for another month for the meeting about OMNY ugh.  I wish this can be done with about OMNY and be switched already.

I saw EasyPay was also not an option for all new senior MetroCard applicants now that the EasyPay program is sunsetting.  They'll just get a reduced fare MetroCard and have to refill at a machine.  The MTA really is in a weird grey zone keeping the MetroCard limping around but not ramping up OMNY offerings.

Board meeting materials call out added express bus service along the BM2, BM5, SIM1C, SIM4C, SIM23 and SIM24 ahead of congestion pricing kicking in.  This is in addition to the X63 and X64 that was announced earlier.

Does anyone have any details on the $12M improvement in local and express bus service that was approved as part of the state budget this past weekend?  I couldn't find much on the specific improvements that are coming.

1 hour ago, Robert Spire said:

I wonder if they'll leave the express alone like they did with the Bronx? 

They'll probably at the very least try to push through with the service frequency cuts they were swinging for.  Though arguably things may change when congestion pricing takes effect and more commuters pivot to other options, including express buses.

I guess the reduced fare Xpress Pay will remain until they figure out how to get those special OMNY cards out the door?

49 minutes ago, QM1to6Ave said:

I 100% believe the BOs do it to keep people off of their buses so they can have empty runs. I think since covid, they got spoiled woth empty buses and never wa t to go back to full runs

It doesn't make sense to me though.  Folding up a row or two of wheelchair seats won't significantly reduce demand or occupancy.  Other than annoy the couple people who can't sit there anymore.

On 3/20/2024 at 1:06 AM, QM1to6Ave said:

THank god I've been able to avoid having to take the bus too many times per week because of some job modifications. It's been a while since I encountered a real a-hole B/O, but today's guy on the QM1 takes the cake. He blocked off 4 sets of seats (i.e., both sides of the two front rows) with his personal belongings and tying all the seatbelts together like a spider web, plus he flipped up all of the wheelchair seats. The bus ended up getting fairly crowded, so a lady flips down one wheelchair seat. The B/O starts yelling at her "I put that seat up for a reason! You can't put down the seat" Meanwhile, she got on at the last pick-up stop so there is clearly no wheelchair passenger. The lady apologizes and moves to a different seat. If it was me, I would have yelled "what is the reason? Go ahead and call command and tell them your reason for blocking seats and causing an ADA violation. Let's see what they say, jacka**"

I was too tired to take pictures and report the B/O like I used to do, because nothing ever happens anyway to get these guys in trouble.

I am noticing on the newer buses I get on, at least one wheelchair seat is flipped up or pulled forward for no real reason.  I don't get why a B/O would do this...other than decrease overall capacity of the bus?

The front seat being blocked offer never ended on CP buses but they'll generally let a regular move it and sit up there, at least on the ones I've been on.

Don't get me started about service reliability/service delivery.  It's been atrocious over the last couple of months with missing runs and proven by the MTA's own stats.

17 minutes ago, mikecintel said:

Yes right yesterday I made an excel sheet and to see what the Q61 times are and it is 15-20 minutes rush but that is not good it needs like every 10 minutes during rush hours.  IF no rush hours it should be 15-20 minutes.  Anyway, I am going to put my input on March 26, 2024 when the popup even is coming to Flushing.  I hope a lot of people in this forum will give a lot of feedback then.

Agreed it should be 10 minute headways for the Q61/62 between 7-9AM and 4-7PM if they want people to actually use the route.  Otherwise, it's a service decrease to current Q15/Q34 riders.

Some tidbits I found in the data for NE Queens folks:

• QM20 PM peak service only begins at 1530...seems odd for them not to start peak service at at 1500
• QM2/20 AM peak service reduced to a max frequency of 10 mins instead of the 6-8min frequency from 7-8AM
• QM2 weekend service still says via Mitchell Gardens in the route destination sign but is not shown on the Remix map
• Q61 service is only 15-20 minute service during the rush but 30 mins most of the time.
• Q62 has equally crappy 15-20 minute peak headways during the rush instead of 10 now.

They also released the metadata for the trip planner so you can see what scheduled bus runs have been cut.

It appears the MTA updated their Flushing Line Improvements page earlier this month but it doesn't seem to give any more details into the timeline of what to expect.  Looks like pretty crappy project management to me...par for the course with Transit.

https://new.mta.info/project/flushing-line

29 minutes ago, AZthefoamer said:

Sounds like an R211T is debuting on the C today (probably 4040).

Hochul is on it: https://abc7ny.com/congestion-pricing-mta-new-subway-train/14377371/

30 minutes ago, Brillant93 said:

Is it safe to assume they'll roll this out by summer?

Articles pointed to after the holidays at the end of the year for implementation.

3 hours ago, Theli11 said:

Kinda sucks how they're not thinking in advance on this option. The bellmouth will leave them with a lot more options for the future like an expansion to the Bronx which I do think the SAS should have if they can get around to it 50-100 years.

It is unfortunate.  It's going to be like the 10th Ave station on the 7 train where they cut out even the provision for it so now any attempt to create it will score poorly on capital investment score sheets since it'll require a tremendous amount of work and interruption.

FWIW, I contacted OMNY about a tapping issue but also asked them when it would be possible to view my trip history again.  The rep didn't know and it seemed like it might be a while until that functionality comes back.

So is it true that service will remain in its curtailed state till 2025 or 2026?  I saw that posted on Reddit recently and that would be a tremendous change if it were true compared to what they sold the public last year.

1 hour ago, CenSin said:

Source?

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

Not present in slide 5 diagram, called out in slide 19.

Notably, the bellmouth provision for a future expansion to the Bronx has been eliminated with this revision.

4 hours ago, zacster said:

My guess is that will be standard procedure from now on.  But I'd have been wrong since I assumed that after Roosevelt Ave that would have already been standard procedure.  Not much has changed since then except the train sets got longer, from 2 cars to 4 or 5 cars, only to make matters worse.

I totally forgot about the Roosevelt Ave accident.  I read about it years back but didn't remember it until now.  Reading the details, it sounds extremely familiar.  Looks like they were using flashlight signaling back then between the forward flagger and the operator in the middle of the set, which was not effective on curve.  Portable radios probably weren't very common back then.  I imagine radio signalling was the upgrade to flashlights but now that has proven to be defeatable by dead zones so pulling a rescue train in front seems like the likely next move to prevent this issue in the future.  Of course that'll be a challenge for operations since they have to take another train out of service and wrong rail it to pull the dead train back home.

27 minutes ago, Arrow III said:

It also seemed like he pointed his finger at his supervisor operating from the middle of the train for not stopping and nearly getting him killed.

It certainly did seem that way if you take that line only.  But reading in between the lines with what he also said during the interview, it's appears the needle is pointing on a radio communication failure.  Like they hit a dead spot at the worst possible time.

ABC7 has posted an interview with the train operator in front of the disabled 1 train who was acting as a flagger.  Seemed to point the finger at a radio communication technical error: https://abc7ny.com/subway-collision-derailment-train-operator-new-york-city/14310375/

19 hours ago, Lex said:

Unless you're talking about the lights being off for an extended period of time (you may see this elsewhere, such as WPR), I'd expect that to be a quirk of things like hitting third rail gaps.

It was for an extended time from the Main Street portal to Hunters Point Ave.