Why a Hoist Brake Is Not a Parking Device

Why this matters

A hoist brake is a friction device sized to stop a moving rated load and hold it for the duration of a lift, with an operator at the controls and eyes on it. It is not a restraint designed to be left loaded, unattended and unmonitored, and there is no second device behind it. The moment the crew walks away, the entire support of that load is one friction pack, whose condition nobody is watching, over a zone nobody is holding. Everything else in rigging has redundancy somewhere: two legs, a design factor, a hitch you can inspect. A parked load on a brake has none of it.

The weekend job

A shop pulled a rooftop air handler for a curb replacement. The unit came up on a chain hoist rigged to a temporary beam, the curb work ran long, and the general contractor's inspector was not going to be back until Monday. Landing the unit meant re-rigging it across the roof to a spot that could carry it, which the foreman priced at about an hour and a half of crew time. Leaving it hanging cost nothing anybody could see. It hung from Friday afternoon.

Monday it was still there, which is what people take as proof the decision was fine. What it actually proves is that nothing happened to arrive at the failure, which is a different claim. Look at what was carrying the load over those sixty-odd hours.

One friction pack, no backup. A hand chain hoist's load brake is typically a Weston-type friction pack: the load itself presses the discs together, so the harder it pulls, the harder it holds. This is a genuinely clever arrangement and it is exactly why crews trust it enough to walk away. The trap is in the same mechanism. The pack is held by load pressure through a threaded connection to the hand chain wheel, which means any rotation of the hand chain in the lowering direction backs the pressure off. A chain that snags on a passing cart, a curious hand, a strap that flogs in wind against the hand chain: all of them are inputs to the one thing that is holding it.

A friction surface that is not being inspected. Oil migrating onto a disc, water sitting in a housing over two nights, a pawl spring that was already tired: none of these announce themselves and all of them are inspected on a pre-use check, which by definition happened before the load was hung and will not happen again until somebody comes back to it.

Nobody in the zone, which means nobody holding the zone. For sixty hours the exclusion zone was a memory. The roofing sub had roof access on Saturday.

A rigging component in sustained tension over a temperature cycle. The beam clamp, the sling and the hoist body all sat at load through two overnight swings. That is not automatically a failure, but it is a condition the pre-use inspection did not evaluate, because the pre-use inspection evaluates a lift, not a storage arrangement.

The unit came down Monday without incident, and the foreman took away that it worked. The right lesson is the one the arithmetic gives.

The trade that was actually made

Run it in hours, because that is the unit both sides of this decision are really denominated in.

• Cost of landing it properly: about 1.5 hours of crew time to re-rig, crib and set down.
• Cost of leaving it hung, done correctly: an attended suspended load with the zone maintained. Roughly 60 hours of roof exposure across the weekend, and a maintained exclusion zone plus an attendant for every one of them, because that is what "hold suspended" requires.
• Cost of leaving it hung, done the way it was done: 1.5 hours saved and 60 hours of unattended exposure accepted, with the zone unheld and the site accessible to another trade.

Stated that way, nobody chooses it. The reason it gets chosen anyway is that the 60 hours are invisible on Friday afternoon and the 1.5 hours are on the schedule. The ratio is 40 to 1 against, before you count the re-inspection that the rigging now needs before it moves again.

What the standards actually say about walking away

The duty is written as an operator duty rather than as a brake specification, which is a clue about how the drafters saw it.

For construction crane work, 29 CFR 1926.1417 under Subpart CC covers operation and requires that the operator not leave the controls while a load is suspended. In general industry, 29 CFR 1910.179 covers overhead and gantry cranes and carries the equivalent duty for the operator with a load on the hook. Name your Part, because a field-service shop can be under either depending on the job, and a reader who meets both siblings needs to know which one is theirs.

Note what the rule is not. It is not a permission structure with a time limit, and there is no provision that says a load may be left if the brake is good. The rule assumes an attended load and stops there. Where a hold genuinely has to persist, the standards' answer is to change the support, not to extend the assumption.

The support that is designed to be parked on

The difference between a brake and a stand is what the device was designed to do with time.

A hoist brake is designed to arrest and hold during an operation. A crib stack, a set of rated stands, a shoring post or a structural set-down point is designed to carry a static load indefinitely, with no active element, no friction surface, no spring, and nothing that a stray input can release. That is the whole distinction and it is the reason the answer to "we need it up for two days" is always a change of support rather than a change of confidence in the brake.

Two rules follow, and they are the ones crews break first.

Never work under a load supported only by a hoist brake. Not to place cribbing, not to look at the curb, not for a second. Where cribbing has to go under, it goes in from outside the load's footprint using a bar or a purpose-made tool, with hands and feet out of the crush line, and it goes in progressively so the load never has a gap it can drop into. Then the hoist lowers onto the cribbing until the rigging is visibly slack, and only after the rigging is slack does anybody's body go anywhere near it. The check is the slack sling, not the sound of it landing.

A load is not parked because it is resting on something. Cribbing that is not stable, not on ground that carries the bearing pressure, or stacked taller than its own footprint safely allows is a support that fails sideways rather than downward, and sideways is worse because it launches the load rather than dropping it. The stack's geometry and the bearing pressure under it are questions for the lift plan and, where the consequence warrants it, the professional the plan routes them to.

The two questions that settle it in the field

When somebody proposes leaving a load up, the argument tends to be about the brake, and it should not be. Ask these instead.

Who is at the controls, for how long, and what are they doing when they are not looking at it? If the answer is nobody, the proposal is not "leave it on the brake," it is "leave it unattended," and those are different requests. If the answer is somebody, price their hours honestly, because an attendant for two shifts is more expensive than the re-rig almost every time.

What is holding the zone while it hangs? An unattended load needs a physical barrier that survives another trade arriving with their own key. Tape does not survive that. If you cannot hold the zone, you cannot leave the load, whatever the brake is doing.

The other places this shows up

A powered industrial truck holding a load in the air is the same mistake with a different mechanism. A truck's mast holds hydraulically, its stability depends on a load centre that does not change, and 29 CFR 1910.178 in general industry addresses truck operation including leaving a truck unattended. A raised load on forks is not a park position, and a truck is not a hoist. Land it or crib it.

A jack is not a stand. Same category, same reason, and the trade has already settled it in the shop: everybody knows a vehicle goes on stands, and the same person will leave a compressor on a bottle jack because the object is not a car.

A lever hoist held on its pawl is not parked either. The pawl is a stop, not a designed static support, and the load-holding brake behind it is the same friction arrangement discussed above.

Catching the habit before it catches you

The tell is in the language, not the equipment. Listen for "we will just leave it up," and for a plan whose next step is scheduled in days rather than in the current shift. Then look at the job board for lifts whose landing step depends on somebody else's work being finished, because that is the specific shape of job that produces a parked load: the crew who lifted it cannot land it until a different trade is done, and nobody planned for the gap.

The fix is a planning fix, not a discipline fix. On any lift where the set-down depends on work outside your control, identify the interim set-down point before the load leaves the ground, and confirm that spot will carry the load statically. That single question, asked at the tailgate, removes the Friday afternoon decision entirely, because by then there is a place to put it.

References

• 29 CFR 1926.1417 (operation), Subpart CC, cranes and derricks in construction
• 29 CFR 1910.179 (overhead and gantry cranes) and 29 CFR 1910.178 (powered industrial trucks), general industry
• The hoist manufacturer's manual for the brake's rating, its inspection intervals and its stated duty, which is the governing source for what that specific brake is designed to do
• ASME B30.16 (overhead hoists) and ASME B30.21 (lever hoists), in the edition your jurisdiction, contract or employer programme has adopted
• See related: Stopping a Lift and What Happens Next; Where the Zone Under a Suspended Load Actually Is