Jump to content
View in the app

A better way to browse. Learn more.

Thorpe Park Mania Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

comment_39904

Exactly the point everyone's missing - it got halfway up the damn hill before it e-stopped. It shouldn't have! If you suspect something's wrong, let the last train finish and then investigate it.

So what you're saying is, you would risk people Health and well-being, just so you didn't have to bother to evacuate a lift hill? Well at least now if I know you to ever be working for a theme park and operating a ride I was about to go on, I would definately not ride. It's people safety your saying thorpe should have risked, which is not an option for any operator.
  • Replies 2.3k
  • Views 378.5k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Coaster dude, take off those employee glasses for a second, look beyond all the corporate rubbish they fill your heads with during training and inductions and start to look at the bigger picture. One

  • Oblivion, one of the rides at Towers that forces you into a shop AND arcade in order to re-ride...  

  • They couldn't even be bothered to put this one back together,     It's a bloody outrage I tell ya.

Posted Images

comment_39917

Right enough of this Theme Park Bloke.In my opinion the operator did the right thing. I am a operator and I wouldn't stop it on the lift hill unless there was a problem. A call from engineers to Colossus could have happened over the radio to e-stop the ride. Anything could of happened.Enough of this now.

comment_39918

Enough of what? I have not started anything.People can't see here that it wasn't safe to let it get up the lift hill before letting them off. Because I certainly wouldn't let that happen. People here are turning around what I am saying. If they can't see that letting it get up the lift hill wasn't safe before hitting the emergency stop button, then that's not my fault. Surely before the despatch the ride operator must have realised something was wrong, because then the team would've realised and not let anyone load, thus evacuating the queueline. It's a bit different if it left the station and that point they realised something was wrong.It is clear it left the station and headed for the lift hill, they then hit the emergency stop button. Therefore a ride operator and other employees are responsible.

His point is that they should have let the train go all the way round instead of E-stopping it on the lift hill.

No, no, no, no, no! And this is where people are wrong. Cripes at this rate I'm gonna have to spell it out sentance for sentance, for actually what happened, and what should have happened. I'm sorry Mark, but you've seen it just like everyone else has here - completely wrong.
comment_39933

Right lets just make this obvious.Theme Park Bloke. We now understand you mean the train should not have left the station in the first place and then stopped on the lift hill.You have to understand everyone else are saying that maybe the ride operator was not told there was a problem until the train had already made it half way up the lift hill.I'm sure the moment the ride operator heard "Stop the ride!" he/she smashed their palm straight onto the E-stop button.

comment_39938

Ditto Tommy.

If they can't see that letting it get up the lift hill wasn't safe before hitting the emergency stop button

Erm, it obviously was safe because nobody was injured? Also from YOUR original post, you'd notice that the problem was on the first drop, not the lift hill? Explain why it wasnt safe to let it go up the Lift Hill?
  • 3 months later...
comment_47949

Well I had a walk on the park itself today. Saw was testing after it's break down, so it should be open tomorrow. Dont hold me to that though. Samurai was looking good when I saw it, no problems there, although I am probably wrong. Queues were horrendous though, much more busier than I/anyone probably anticipated. I would say it's an average start to the season, but then again, when is any day of the season perfect? :D

comment_47951

Not a very good opening day ride wise but it is the first day of main season and most of the rides on the list have been shut since November so expect some problems. Hopfully things get better soon and hopfully Saw will be fine tomorrow.

I was there today, most rides I wanted to go on worked fine. X closed about 3 and was still closed when we left. Safety checks were being carried out on Rumba, but apart from that was a good day for operations.
comment_47954

I was there today, most rides I wanted to go on worked fine. X closed about 3 and was still closed when we left. Safety checks were being carried out on Rumba, but apart from that was a good day for operations.

Hopefully Rumba is open soon. I have missed Rumba Rapids over the close season a nice relaxing ride I think. :D
comment_47955

Well I had a walk on the park itself today. Saw was testing after it's break down, so it should be open tomorrow. Dont hold me to that though. Samurai was looking good when I saw it, no problems there, although I am probably wrong. Queues were horrendous though, much more busier than I/anyone probably anticipated. I would say it's an average start to the season, but then again, when is any day of the season perfect? :D

tpkabz, was it really testing? at what time?, really great if it was! What were queues like?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Recently Browsing 0

  • No registered users viewing this page.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.