Do roped hydraulic elevators need "rupture valves"? Is a rupture valve needed for a standard hydraulic elevator? What does the rupture valve do?

I write construction specifications for architects, and occasionally I have to spec hydraulic elevators. This info would help me greatly. Many thanks in advance!

-- Briana White (collectivewisdom@yahoo.com), February 11, 2000

Answers

The answers to your questions is very much a matter of opinion.

I would say that in general, "rupture valves" are not necessary. There could be specific applications where they would be advisable. If one wants maximum safety, they couldn't hurt and in certain circumstances, they would be great.

As an example, I heard of a case where a car in a parking garage went thru the block wall of an elevator hatch and sheared the feed line, causing an uncontrolled rapid descent. A rupture valve here (assuming the car didn't wipe it out as well) would have prevented the uncontrolled descent. You be the judge as to whether this is an event that should be "defensed against".

If a roped hydraulic is equipped with a conventional (governor operated) safety device, it could be argued that a "rupture valve" is redundant.

Sorry not to give you a simple answer, but in my opinion, it "ain't" a simple matter.

John Brannon

-- John Brannon (akaelevman@AOL.com), February 11, 2000.

Rupture valves are required in Seismic Zones 2 and 3. The only time we supply them is if the spec clearly ask for it or references requirments for Seismic Zone 2 or 3. I am in Maine and we are in Seismic Zone 2 - which I never would have guessed - so check with your state office to confirm which if any zone your in.

-- Kevin Kisamore (kisamore@thyssenelevator.com), March 20, 2000.

Yes, rupture valves are required on roped hydro's, however the governing within your area has total code requirements enforcements authority, any elevator within seismic II or greater will have rupture on all hydro's, along with schedule 40 pipe between hydraulic cylinders if it is holeless.

-- jim sternberg (jimsternberg@otis.com), July 29, 2003.