|
|
| MTA Bus & NYCT Bus routes "On Time Performance" data for September & October 2014 (300771) | |
 |
|
| Home > BusChat | |
[ Post a New Response | Return to the Index ]
|
| (300771) | |
MTA Bus & NYCT Bus routes "On Time Performance" data for September & October 2014 |
|
|
Posted by Gold_12th on Tue Dec 9 19:02:59 2014 link: http://nathan9.github.io/nycbusperformance/#2014-10 |
|
|
| (300795) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by BrooklynBus on Wed Dec 10 14:51:17 2014, in response to MTA Bus & NYCT Bus routes "On Time Performance" data for September & October 2014, posted by Gold_12th on Tue Dec 9 19:02:59 2014. I am really surprised that so many buses are late operating between midnight and 6 AM. How could the MTA blame that on traffic? |
|
|
| (300796) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by TerrApin Station on Wed Dec 10 15:11:26 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by BrooklynBus on Wed Dec 10 14:51:17 2014. CONSTRUCTION |
|
|
| (300829) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by checkmatechamp13 on Wed Dec 10 23:51:36 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by BrooklynBus on Wed Dec 10 14:51:17 2014. Sometimes the schedules are cut really tightly at night to minimize the number of buses used. For instance, the B3 uses just one bus, with the minimum 3 minute layover at each end. If the bus driver misses a few lights too many, that could easily set him back 5 minutes. The B44 has two buses covering the whole run from WBP to Sheepshead Bay. The same for routes like the Bx10, Bx12, S51, etcAlso, you could have drivers recovering from delays earlier in the evening. Or maybe a few late pullouts from the depot in the 5-6 hour. (Also, just regular delays from the beginning of rush hour from 5-6). |
|
|
| (300832) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by New Flyer #857 on Thu Dec 11 08:54:46 2014, in response to MTA Bus & NYCT Bus routes "On Time Performance" data for September & October 2014, posted by Gold_12th on Tue Dec 9 19:02:59 2014. The number of buses running early is very disappointing. And that's solely the fault of the transit agency. |
|
|
| (300837) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by BrooklynBus on Thu Dec 11 13:17:28 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by TerrApin Station on Wed Dec 10 15:11:26 2014. What are you mumbling about? |
|
|
| (300838) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by BrooklynBus on Thu Dec 11 13:18:04 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by New Flyer #857 on Thu Dec 11 08:54:46 2014. Don't you mean the bus operator? |
|
|
| (300842) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by New Flyer #857 on Thu Dec 11 15:25:06 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by BrooklynBus on Thu Dec 11 13:18:04 2014. Well, yes, primarily. He is an employee of the agency of course. And now with the latest technology the agency can very easily track intentional violations of the schedule.I'm patient with so much regarding getting around, even missed runs! But running early is just wrong. Even the 1 minute buffer is questionable to me. I can understand that running early can be helpful in certain circumstances. For example railroads will often not mind running early when moving away from the city. I believe LIRR had a clause that it may leave 3 minutes early from outer stations when moving away from the city. That's fine, as long as they publicize that. OTOH, Metro North waits an extra minute at Grand Central before departure. That's much more passenger-friendly, though not necessary. |
|
|
| (300843) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by New Flyer #857 on Thu Dec 11 15:43:02 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by BrooklynBus on Thu Dec 11 13:17:28 2014. He does have a point. For example, when they were working on Flatbush Ave near the Belt Pkwy over the summer at night, each Q35 run was delayed a good 10 minutes getting by, making it almost impossible to be on schedule, and no detour available. |
|
|
| (300848) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by Terrapin Station on Thu Dec 11 21:27:51 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by New Flyer #857 on Thu Dec 11 15:43:02 2014. Thank you. Of course I have a point. |
|
|
| (300849) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by Terrapin Station on Thu Dec 11 21:28:24 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by BrooklynBus on Thu Dec 11 13:17:28 2014. Just what I said. Construction causes delays at night. |
|
|
| (300850) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by Spider-Pig on Fri Dec 12 09:32:45 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by BrooklynBus on Thu Dec 11 13:18:04 2014. Why would anyone say "transit agency" to mean "bus operator?" |
|
|
| (300851) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by BrooklynBus on Fri Dec 12 10:33:32 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by New Flyer #857 on Thu Dec 11 15:25:06 2014. I agree with you. |
|
|
| (300852) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by BrooklynBus on Fri Dec 12 10:34:02 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by Spider-Pig on Fri Dec 12 09:32:45 2014. He already explained and I agree with him. |
|
|
| (300854) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by sloth on Fri Dec 12 10:48:51 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by checkmatechamp13 on Wed Dec 10 23:51:36 2014. I'd guess they sometimes run late on purpose, so as not to get ahead of the schedule mid-route. |
|
|
| (300856) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by randyo on Fri Dec 12 13:14:57 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by New Flyer #857 on Thu Dec 11 15:25:06 2014. The one minute lag dated back to the old NYCRR days. The posted departure time for the passengers was one minute before the actual departure time of the train to allow “walk time” from the gate at the platform entrance to the train. As for running ahead of time, NY bound Amtrak trains coming from points south of DC often run ahead of time since once in N/E Corridor territory, they only discharge passengers but don’t pick up. Since there are no boarding passengers to wait for, trains can run contingent only on train traffic ahead. When I returned from New Orleans on the Crescent, the train arrived at Penn Sta 20 min ahead of schedule. |
|
|
| (300858) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by randyo on Fri Dec 12 13:22:44 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by BrooklynBus on Wed Dec 10 14:51:17 2014. I don’t understand that either unless they just take the word of the bus operator when asked about the reason for the delay. I once waited for a B63 bus on 5 Av/9 St which was already 15 min late on a 1 hour headway at 230 AM when a road control supt in an MTA patrol car happened along. I identified my self with my TA pass and asked him to check on the delay. He notified bus command center who contacted the bus and the operators excuse was “heavy traffic on Atlantic AV.” I find that hard to believe at around 200 AM. I have since heard that the bus operator in question was terminated but for what specific reason I never found out although, since I traveled that route abut the same time quite frequently, I noticed that same operator always ran late on that trip. |
|
|
| (300859) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by New Flyer #857 on Fri Dec 12 13:39:48 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by randyo on Fri Dec 12 13:14:57 2014. On the same vein I think many NYCT/MTAB express bus schedules have it arranged that the bus often can't keep up with the schedule while it does its pickups (such that passengers are at the stop well before the bus is), but then there is a nice buffer when making the crossing into drop-off territory so that it catches up to the schedule and may even end up early, especially if there is a liberty to detour around stops that no passenger is requesting.I think it's totally cool for services to, once past pick-up territory, run early, or even to have some spots have a "zone" (i.e. "train may leave up to x minutes early") for boarding so that passengers are aware. The most important thing is that services do not leave the station before any boarding passengers were informed they would. |
|
|
| (300860) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by New Flyer #857 on Fri Dec 12 13:46:36 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by sloth on Fri Dec 12 10:48:51 2014. They really should just follow their procedures instead of making it a big drama. You have a set of timepoints. Leave them right on the dot or maybe a minute or two late if you think you're fast. If you have to wait at a spot, just tell the passengers what you're doing.On the 1 train, especially heading northbound, there are a lot of scheduled holds, but very often the passengers are left in the dark and that's what annoys them. Just a simple announcement, "We are x minutes early and are holding in order to ensure even spacing. . ." or however you want to phrase it. Yeah every now and then someone will get upset, but that's their problem. This whole nonsense of coasting at 5 MPH or stopping at a green light is silly and I think upsets passengers more. |
|
|
| (300861) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by BrooklynBus on Fri Dec 12 13:52:14 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by sloth on Fri Dec 12 10:48:51 2014. If the run point timing were proper, they woudn't have to do that. |
|
|
| (300862) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by Petabread2 on Fri Dec 12 14:10:59 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by BrooklynBus on Fri Dec 12 13:52:14 2014. i have been on runs on the q65 that had to wait at jewel Ave for 5 mins, driver told the passengers and some of them would complain that he is making them late for work. When in reality that is their fault. You cannot make time points accurately, it's a known fact that the same run will most likely not arrive at the same point everyday because Nyc is very dynamic. It is up to the operator to maintain his time point but he can't help if his leader wants to play games and drive slow so his follower can catch up and pick up more people. |
|
|
| (300863) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by Kevin from Midwood on Fri Dec 12 15:20:50 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by New Flyer #857 on Fri Dec 12 13:46:36 2014. I rode the B12 often last year at various times of day and saw a great deal of bus bunching coupled with long gaps in service. Sometimes buses would leave the first eastbound stop at Ocean and Parkside too close together. Do bus operators have the discretion to increase or decrease layover time as conditions dictate? I'm no expert on these matters, but it seems to me that even spacing between buses should trump strict adherence to the schedule. |
|
|
| (300866) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by New Flyer #857 on Fri Dec 12 16:00:58 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by Kevin from Midwood on Fri Dec 12 15:20:50 2014. This is where a dispatcher is most helpful. For example, when there are frequent intervals a bus that is at the beginning of a run and full up with passengers should be allowed to just go since there is nobody else who can get on.Another ideal would be a system where one or more buses that have become bunched together can terminate short of the destination, empty out and transfer their passengers to one of the other buses that are continuing on, so the terminating bus can turn around and start going the other way and work to steady out the intervals. I would say that once frequencies are better than 8 to 10 minutes then, yes, even spacing should take precedence over strict adherence to the schedule. But of course at the times when its most costly to miss a bus, such as overnights, I would say that in ordinary circumstances buses should not even be 1 second early. |
|
|
| (300870) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by checkmatechamp13 on Fri Dec 12 17:03:48 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by New Flyer #857 on Fri Dec 12 16:00:58 2014. There's times when even infrequent buses bunch together. For instance, sometimes on a Saturday night, I see the S46 on BusTime. One of the buses might be running 20 minutes late leaving St. George. The layover is only 5 minutes at the West Shore Plaza, so even if the bus driver misses his whole layover, he'll still leave 15 minutes late. Meanwhile, if he was short-turned at Forest Avenue, he would save a good 15 minutes at least, meaning he'd be back on time for his return trip.Keeping in mind that ridership north of Forest is significantly higher than ridership south of it, and at that time of night, a lot of ridership is oriented around the ferry, that solution makes the most sense. A handful of people south of Forest have to wait 10 minutes for the next bus (whether it's southbound passengers who need the follower, or northbound passengers who will catch his follower coming back up), and meanwhile, people north of Forest get on-time service and are able to catch the ferry and avoid a 30 minute wait. |
|
|
| (300894) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by checkmatechamp13 on Sat Dec 13 08:24:09 2014, in response to MTA Bus & NYCT Bus routes "On Time Performance" data for September & October 2014, posted by Gold_12th on Tue Dec 9 19:02:59 2014. I just realized something: Sometimes the BusTime stop isn't exactly at the geographical location. In some cases, the stop is a little bit behind the actual stop. So if the driver is loading up at the stop, BusTime might have him down as having already departed (of course, this only explains some cases. I'm sure there's cases where the bus has actually departed already). |
|
|
| (300900) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by randyo on Sat Dec 13 16:38:30 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by checkmatechamp13 on Sat Dec 13 08:24:09 2014. I use the BusTime app quite frequently and there are time when a bus shows up about 10 blocks away and when I refresh about a minute later, the bus no longer shows up. Other times the app doesn’t show the bus at all even though the bus is approaching the stop where I am waiting. |
|
|
| (301142) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by Transitbuff on Thu Dec 18 22:39:51 2014, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by Petabread2 on Fri Dec 12 14:10:59 2014. In some cases...the LEADER takes off like a banshee! |
|
|
| (301886) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by checkmatechamp13 on Wed Jan 7 18:24:56 2015, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by New Flyer #857 on Fri Dec 12 13:46:36 2014. I'd prefer the bus come a little bit late, and just keep it moving entirely, over waiting at stops. (Though like you, I'd prefer waiting at one stop for 5 minutes over driving excessively slowly). It gives me a better chance of catching it. That definitely applies for express buses, where there's no turnover within a borough (except for the BxM1 in Inwood and BxM18 from 26th Street to Downtown of course).Of course, if it's a route with a lot of turnover, then it's a different story. (The idea with leaving late is that most of the passengers end up arriving to their destination on time, but if you leave late, that means most of the passengers on the first half of the route will end up arriving late). In that case, then it's better to wait at timepoints when necessary. I also think there's certain cases where, from a practical perspective, there's no harm in running early. For instance, if a Staten Island bus is scheduled to miss the ferry by 2 minutes, and the driver runs a few minutes early to catch the ferry, there's realistically no harm done, especially if the running early is done in the portion of the route closer to the ferry, where there's likely to be alternate routes that a passenger can take if they miss their intended bus. |
|
|
| (301909) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by BrooklynBus on Thu Jan 8 13:44:09 2015, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by checkmatechamp13 on Wed Jan 7 18:24:56 2015. Why would a bus even be scheduled to miss the ferry by two minutes? |
|
|
| (301913) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by checkmatechamp13 on Thu Jan 8 16:35:56 2015, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by BrooklynBus on Thu Jan 8 13:44:09 2015. Well, there's plenty of instances in the schedules. Reasons could be as follows:* The bus could be running every 20 minutes, and be scheduled to arrive on the :02s, :22s, and :42s. (For instance, the S52 during weekday middays) * The bus could be running every 15 minutes, and be scheduled to arrive on the :02s, :17s, :32s, and :47s. In some cases, the buses arriving on the :02s and :32s are the full-length buses, while the ones arriving on the :17s and :47s are short-turns. (For instance, the S62 in the early weekday midday, or the S78 on Saturdays). * Pure laziness in writing the schedule. For the S46 on weekday evenings, buses are scheduled to arrive at 8:41, 9:03, 9:33, 10:03, 10:33, 10:59, 11:27, and 11:56. The 9:03, 9:33, 10:03, and 10:33 buses are scheduled to make a return trip 27 minutes later. If they pushed the times back by 15-20 minutes, they could allow more people to catch that ferry. |
|
|
| (301919) | |
Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014 |
|
|
Posted by New Flyer #857 on Thu Jan 8 19:26:42 2015, in response to Re: MTA Bus & NYCT Bus routes ''On Time Performance'' data for September & October 2014, posted by checkmatechamp13 on Wed Jan 7 18:24:56 2015. Yes, I wouldn't be opposed to having a clause that allows buses to run early after a certain point, such as the last mile or after the last major intersection, or wherever, as long as the possibility of the bus running early is properly publicized (like the LIRR's up-to-3-minutes-early policy at the PM rush).One time, on the other hand, I was on a Q21 bus (when it was Elmhurst to Rockaway Park) that flew through its run (typical for that route) and was about to arrive at Rockaway Park, the last stop, a good 15 minutes early. At Beach 108th, we stopped and waited about half that time, making me miss my Q35 conneciton at Rockaway Park. And at that point, nobody is looking for that bus! |
|
|