Because neither would be the rides fault? If it turns out to be operator error.Because Goliath wasn’t modified (as far as we know) outside of manufacturer specifications. How do the two correlate in any way?
Because neither would be the rides fault? If it turns out to be operator error.Because Goliath wasn’t modified (as far as we know) outside of manufacturer specifications. How do the two correlate in any way?
I dont see it that way but okOperator error and deliberate improper modification of a ride aren’t even remotely similar. There was a shared end result, sure, but blame falls on a different party in each scenario and different actions need to be taken.
Somebody is definitely going to prison over this
So this is similar to Apollo? Doesn’t Apollo have a screen that turns green when the seat is secure? How would a ride op miss something like that?
Apollo/nitro/raging bull do not use themHaven't been to SFOG in a good long while, but are seatbelts not in use? I know Carowinds has them on Fury and Thunder Striker. Fury has particular interesting ops in that you are instructed to buckle the belt and let a ride op push down the lap bar for you. Is it just legacy CF parks that use seatbelts as a fail-safe? Can't remember off the dome if KD and BGW use them.
Raging Bull is my home Hyper. I’ve never felt unsafe on it in my life.Apollo/nitro/raging bull do not use them
That’s a shame. But it’s 100% correctWant to quickly bookend the photo debate and then retrack the thread.
@RollyCoaster did not break any forum rules by posting the photo and did attempt to hide it behind a spoiler tag to prevent anyone from seeing it inadvertently. That's what I would have told him to do if he had asked me.
That being said, because some people apparently saw the image anyway due to some issue with the the spoiler tag functionality (maybe disabled/blocked JavaScript on the client side or similar) I edited @RollyCoaster's post to remove the photo itself and replaced it with a link to a Facebook post with the photo.
If you believe the content violates Facebook's rules, go report it there. If you think our policy should be different (we will likely need to formalize something anyway in the wake of this), message your favorite Advisory Panel member with your thoughts.
Now, back to the actual news.
I don't know why you'd think that. Cedar Point was knowingly using non-manufacturer-compliant parts on Top Thrill and they basically made off without any punishment.
The Orlando drop tower operator knowingly modified the restraints out of manufacturer spec and next to no punishment resulted there.
Our current laws massively shield parks from most liability even when wrongdoing is crystal clear. There will be a civil suit, but I think it's highly unlikely that anything further will result unfortunately.
The posts online from eye witnesses thus far seem to suggest that the restraint physically failed mid-ride. MAYBE the restraint wasn't ratcheted all the way (meaning it was likely operator error when checking the restraint)? Even then though, as far as I understand, there are multiple ratchets between minimum verify and wide open and it should have slipped into one of those lesser ratchets.
Right now it sorta seems more likely to me that the restraint ratchet mechanism itself broke somehow. I think people are right to suspect some really shotty maintenance, but hopefully we'll get a real, robust investigation with actual answers eventually.
Haven't been to SFOG in a good long while, but are seatbelts not in use? I know Carowinds has them on Fury and Thunder Striker. Fury has particular interesting ops in that you are instructed to buckle the belt and let a ride op push down the lap bar for you. Is it just legacy CF parks that use seatbelts as a fail-safe? Can't remember off the dome if KD and BGW use them.
This is horrific, and the tragedy is paramount. But the details we do have are also so inexplicable - based on the existence of the photo (FWIW I think @Zachary’s shift to a link was the right compromise here) and the eyewitness reports, this happened at the very end of the ride. Trying to understand why a restraint failure would happen there and not earlier is extremely hard to wrap one’s head around.
I assume this is for Goliath? Speaking from experience this not true for every B&M.if the sensor doesn't register the minimum verification in the station the PLC wouldn't allow a dispatch.
This, combined with the fact that the rider is on the larger side, wouldn't surprise me if the restraint was barely locked in place and it just gave out in that final stretch.Not an expert or anything, but I imagine if it was some sort of metal fatigue failure or similar, the ejector pops at the end of the ride would likely be some of the most demanding on the restraint mechanism.
I imagine this is unrelated. I know queue times and general posted six flags wait times are taken with a grain of salt, but Titan seems to still be open at over texas (or was until quite literally 3 minutes ago lmao, though I gotta imagine if it was related they would have shut it down sooner. So it's probably over texas being over texas). Unless there's some variance in the two's trains/restraints that would constitute only closing one in response to an accident on a B&MI was at magic mountain when it happened. After hearing that BM hypers were getting closed I popped over to Goliath, and was both surprised and not surprised to see it chained off
I assume this is for Goliath? Speaking from experience this not true for every B&M.
If this were the case it would be very bad for B&M hypers, and a lot of other older rides restraint systems in general that could have similar failures.Not an expert or anything, but I imagine if it was some sort of metal fatigue failure or similar, the ejector pops at the end of the ride would likely be some of the most demanding on the restraint mechanism.
We use essential cookies to make this site work, and optional cookies to enhance your experience.