Edit: On the bright side the Batman side of the chiller is open again! *** Edited 5/6/2006 5:58:42 AM UTC by medusa3232***
Well is it wierd that the fact that the blue side of Chiller is running makes it all better? I'm SO happy about that. :)
It is sad to see the ride have so many problems as it runs so much better and efficiant then Dragster.
Disclaimer: The preceding comment was in no way intended to carry CP Fanboy connotations :)
*** Edited 5/6/2006 2:39:57 PM UTC by Peabody*** *** Edited 5/6/2006 2:41:15 PM UTC by Peabody***
It says Kingda Ka is Temporarily Closed, so that can't be a good sign.
http://www.sixflags.com/parks/greatadventure/Rides/KingdaKa.html
Would there be sparks if the cable snapped?
...because giant magnetic brakes coming up against a giant moving train could cause a multitude of sparks, noises, and many other bad things, I imagine.
And, if I recall correctly, a similar thing happened to Red Train on TTD before it ever opened to the public in its 1st season...on either the first, or one of the first, rollbacks...causing Red Train to be out-of-service for quite a while. I think it was Red Train, anyhow.
You'd think they'd get that right the 2nd time around.
I am just speculating anything that could cause a "bang".
That is too bad about KK though and especially all the people that were hoping to ride it
If Toro *and* B:TC are up and running, I'll call it "better than a draw"...
It could be something else entirely but i dont blame it on maintanance . They were actually there when it happened. They are always at the ride.
I wonder if the Discovery/Travel channel is going to make another special for it.
:)
Great Lakes Brewery Patron...
-Mark
ANYTHING being "lodged in the launch area" should cause an immediate system shutdown from the control system. Something still ain't right with the design if you can launch a train with something (or, theoretically, someONE) in the launch area...
Whatever got messed up mechanically needs fixed, but with all the *sensors* on these rides, something shoulda CAUGHT that the launch area was "occupied".
You must be logged in to post