Waiting times kill coaster fun!
Why do they do that?
Lack of spare parts for the coaster trains? *** Edited 1/4/2004 2:33:48 PM UTC by superman***
SFA's Wild one had a similar problem (pre-SF)in which they could only run 1 train due to the bad skid brakes...that changed in 99 when they upgraded to pnuematic brakes & added new trains to the ride.
Even with all that work capacity still stinks...so imagine how bad it would be with only 1 train running all the time.
It's not like it really matters if Phantom only has one train unelss it's an uberbusy day, though. That thing's a people-eater even with one train and your average park guest is happy with riding it once or maybe twice... they're not into the power riding thing.
Warning: this post contains satire...
Sometimes the Rides are too short to Run two trains. Raven, Thunder Run, Tennessee Tornado, and Cannonball at Lake Winnie all run one train because if there were two , the Stacking would become a problem. Tennessee Tornado runs two sometimes, but that' rare because it's only done when the park is really busy.
And if a shuttle coaster ran two trains , it would then be very unsafe.:)`
On both of my visits to Knoebels, they only had one train running on both of the woodies, but at least they warned you on Phoenix before you got in line. Dorney Park also only had one train running on Thunderhawk, Laser, and the dearly departed Hercules in 2001. Quite possibly the worst offense I've seen was PKD on opening day last year. They only ran one train on Hypersonic XLC for a whopping total of eight people at a time. The other trains weren't even visible on the transfer table.
I can't say there are any advantages except what's already been mentioned. *** Edited 1/4/2004 9:26:54 PM UTC by Intamin Fan***
On another note, the added stress to the operators and attendents when a second train is added is really a non-issue. Your average ride crew at your average park really won't behave much differently, no matter how much people here fuss about stacking the trains. In fact, your average ride crew doesn't even know what stacking is, or that its even undesirable. Its not like the mantinence guys are sitting around thinking "Gee, we really should put a second train on Coaster X but little Attendant Timmy seems pretty stressed already."
Its not like the mantinence guys are sitting around thinking "Gee, we really should put a second train on Coaster X but little Attendant Timmy seems pretty stressed already."
Baaahahahahahahaa! Good form. Thanks for the early morning belly laugh! :) Little Timmy. LOL
I'm not too sure that stacking would be that much of an issue. With three trains (assuming, hypothetically, that the rides you mentioned had enough blocks to handle that many), it would absolutely be an issue considering the length of these coasters. However, one-train coasters like Raven and Thunder Run (I can't speak for Cannonball) have a ride time of at least a minute and a half. So, if ride crews are efficient enough, this should be plenty of time to roll Train 1 out of the station so that Train 2 wouldn't sit on the brake run for too long.
Sometimes the Rides are too short to Run two trains. Raven, Thunder Run, Tennessee Tornado, and Cannonball at Lake Winnie all run one train because if there were two , the Stacking would become a problem.
Indeed. And I don't really see why it's so undesirable among enthusiasts, anyway. It's not like I'm ever in a mad hurry to get off a coaster when it stops.
In fact, your average ride crew doesn't even know what stacking is, or that its even undesirable.
Just hypothetically....Raven runs so perfectly, and I'm sure it would run great with 2 trains, too, but if it ain't broke, I sure as hell wouldn't vote to fix it.
If a crew isn't fast enough with two train operation to prevent stacking, there's no point adding a third (see Goliath at SFMM). However, going from one-train to two-train is a huge difference. Let's assume it's a shorter ride at a 1:30 ride time. While that train is on the track, the other can spend 1:30 unloading and reloading. This means that you already have another load ready to go (or nearly) by the time the other train gets back. With one train ops, you just wasted that 1:30 doing nothing.
Why would a busy park let a two train coaster run with only one train? Easy....money. It becomes a choice of whether happier customers are worth spending more money.
As far as the stacking. I would rather stack for 15-30 seconds on a coaster running two trains than wait nearly twice as long in line for a coaster running one train. I can't think of anyone that would feel differently.
Stressful?? Let me just say this....minus Cedar Point, I don't think many parks really put that much stress on their employees to not stack. Oh, and also, I'd rather keep busy with two trains than stand around most of the day waiting on the other train to get back. The busier you are, the quicker the time passes.
Stacking is not a big deal. All coasters running more than one train will stack occassionaly even with the best crews (ie clean up, transfer, station delay, duty shifts, etc..). I believe most patrons believe a small wait is just part of normal operation. I've only complained about stacking once, but it was a 3 minute wait each and every cycle due entirely to the ineptitude of the crew.
Some coasters also likely run a single train due to weight concerns for the ride itself -- if the trains aren't nearly full, then rollbacks are more likely. Gemini (Cedar Point) will run fewer trains because of this likelihood; running only one means that everyone fills it up first.
You must be logged in to post