Most anti-collision thinking imagines two cranes on the same runway, running toward each other like trains on a single track. The danger is one-dimensional — how far apart they are along the rail — and the fix is to slow and stop them before the gap closes.
But many bays are not built that way. They have cranes running on different rails, at different heights, whose paths cross rather than share a line. A low-headroom crane working beneath a higher one. Two bridges on adjacent runways whose ends overlap. A shorter-span crane passing under the walkway of a taller one. Here the geometry is completely different — and so is the danger.
| THE KEY DIFFERENCE Cranes at different heights can occupy the same floor space and be perfectly safe — as long as their hooks respect the height between them. The hazard is not proximity. It is proximity plus a hook in the wrong place. |
That single shift — from “how close are they” to “how close are they, and where are their hooks” — turns a one-dimensional problem into a three-dimensional one. This article explains why cranes at different heights need a different kind of anti-collision, how such a system senses the danger, and what to specify for a multi-level Indian bay.
The Geometry of a Different-Height Clash
Picture two overhead cranes whose travel paths overlap in plan — seen from above, their working areas cross — but which run at different levels. The higher crane’s bridge clears the lower crane’s bridge comfortably. On paper, they never touch.
For most of the time, they do not. A crane travelling with its hook raised is compact and stays within its level. The two machines pass over and under each other in the overlap region without incident, all day long.
The clash comes from the hook, and it comes in one direction:
The higher crane reaches down. Its operator lowers a load into the overlap region while the lower crane is passing beneath — and the descending load meets the crane below, or its load, or its operator’s workspace.
In this case the two bridges never came close to each other. The collision happened in the vertical space between them, created the instant a hook was raised or lowered into the wrong place at the wrong time.
Why a Same-Runway System Cannot See This
A conventional anti-collision system for a shared runway measures one thing: the distance between two cranes along the rail. It slows and stops them before that gap closes. For trains on a track, that is exactly right.
But apply that same logic to cranes at different heights and it fails in two opposite and equally dangerous ways.
| Situation | Same-runway system sees | Reality |
| Cranes far apart along the bay | Safe | Safe |
| Cranes overlapping, both hooks high | — (not on same rail, so not watched) | Safe — they pass over/under each other |
| Cranes overlapping, high crane’s load lowered into the low crane’s path | Not watched | DANGER — the load fouls the lower crane |
Look at the second row. A same-runway system, if it watched these cranes at all, would either stop them needlessly every time their paths overlapped — even though they are safely separated in height — or, more likely, would not watch them at all because they are not on the same rail. Both outcomes are wrong. Now look at the third row The real danger — a hook lowered into the other crane’s space — involves height, and a distance-along-the-rail system has no concept of height whatsoever. It is measuring the wrong dimension.
A system that measures only horizontal distance is blind to a vertical clash — and cries wolf over a horizontal overlap that is perfectly safe.
What a Different-Height System Must Actually Sense
To protect cranes at different heights, the system has to reason in three dimensions. It needs four pieces of information.
| The system must know | How it is sensed |
| Each crane’s position along the bay | Travel encoders, position sensors, or crane-to-crane distance sensing (radar or laser) |
| Whether their paths overlap horizontally | Comparing the two cranes’ positions against the known overlap region |
| Top Crane hook’s height | Hoist position feedback — an encoder or limit sensing on the hoist |
| The safe vertical clearance | A configured threshold: how much height separation must be maintained where paths overlap |
With those four inputs, the logic becomes clear and, importantly, it becomes intelligent about when to act:
- Paths do not overlap? No restriction — the cranes are working in separate areas and need no interference.
- Paths overlap, but height separation is safe? No restriction — this is the normal, safe case, and the system must not stop the cranes for it.
- Paths overlap and height separation is being lost? Act — warn, then prevent the hoist or travel motion that is closing the vertical gap.
That middle case is what separates a good system from a crude one. The whole point is to allow safe overlap — to let the cranes share floor space freely whenever their heights keep them apart — and to intervene only in the specific combination of overlap and lost clearance that is actually dangerous. A system that simply stopped the cranes whenever their footprints crossed would make a multi-crane bay unworkable, and would quickly be switched off.
From Distance Sensing to Zone Protection
The most capable way to handle different-height cranes is to stop thinking in terms of crane-to-crane distance at all, and to think in terms of zones instead.
A zone-based system holds a map of the bay. It knows where the overlap regions are, and it can enforce rules within them — rules that depend on both position and height:
- Height restriction in the overlap zone. When a crane is inside a region where another crane’s path crosses, its maximum hook height (or minimum, for the upper crane) is limited so that clearance is preserved.
- Conditional no-go zones. A region that is forbidden to one crane only while the other is present in it — and free otherwise.
- Slow zones. Reduced speed as a crane approaches an overlap region, giving the system and the operators margin.
- Mutual awareness. Each crane’s controller knows the other’s position and height, so protection is coordinated rather than each crane guessing in isolation.
Zone protection is more flexible than raw distance sensing because it encodes the actual geometry of the bay — which parts of the floor are shared, at what heights, and under what conditions. It is the natural fit for the messy, real three-dimensional layouts that multi-crane Indian bays actually have.
Warn, Slow, Stop — and Let Them Escape
As with any good anti-collision system, the response to a developing clash should be graduated, not binary. A warning as clearance starts to erode, a slowing as it continues, and a stop of the offending motion at the limit — delivered smoothly through the drives so a suspended load is not thrown into a swing.
And the system must allow escape. This matters even more with height than with distance: if the top crane has lowered its hook too far into the overlap, the correct recovery is to raise it — so the system must block the lowering that caused the problem while freely permitting the hoisting that resolves it. Blocking both would strand the crane in the dangerous position and force someone to bypass the system to recover, which is how anti-collision systems end up disabled.
The same directional logic applies to travel: block movement that deepens the overlap while permitting movement that clears it. The operator is always left with a safe way out.
It Only Works If It Reaches the Controls
A different-height anti-collision system is only as good as its connection to the crane. If it is bolted on as a bare relay that simply cuts a motor, the operator gets an unexplained stop with no idea which motion caused it — and an unexplained stop is a bypass waiting to happen.
Integrated with the crane’s control system, the same detection can tell the operator what is happening: which crane is close, that a height limit is being approached, which motion is being restricted and why. On cranes with variable frequency drives, it can slow and stop smoothly rather than snatching. Information reaches the operator; protection is enforced on the crane. That combination is what makes the system one operators trust rather than fight.
Specifying and Compliance for a Multi-Level Bay
A few things determine whether different-height anti-collision performs in an Indian plant:
- Map the overlaps honestly. Identify every region where crane paths cross in plan, and the height relationship in each. This survey is the foundation — the system can only protect the overlaps it has been told about.
- Choose sensing suited to the environment. Position and height feedback from encoders is robust; where crane-to-crane distance sensing is used, radar is far more dependable than laser in the dust, steam and fog of an Indian plant.
- Preserve realistic clearances. Set height thresholds that keep genuine clearance including load swing and the longest loads carried — not just the static hook.
- Insist on graduated response and escape logic. Warn before stopping; always leave a safe way out.
- Integrate with the controls. So the operator is informed, not mystified.
Functioning anti-collision where cranes share space is also a compliance expectation. In India it sits within the framework of the Occupational Safety, Health and Working Conditions Code, 2020, with Indian Standards such as IS 3177:2020, the code of practice for EOT and gantry cranes, and IS 13367 for the safe use of cranes, framing the operating and inspection discipline around multi-crane operation.
At Aggra Cranes & Engineering LLP, anti-collision and zone protection are core to the crane safety devices we supply, install, integrate and configure for Indian plants. Working with established technology partners including Kymati, Elfatek, GIS and Danfoss, we survey the bay’s real three-dimensional geometry, match the sensing to its conditions, configure the height thresholds and zones to the actual overlaps, and integrate the system with the crane controls — so cranes at different heights share the bay safely without being stopped needlessly.
Conclusion
Cranes at different heights break the mental model most anti-collision is built on. They are not two trains on one track, kept apart by distance along a rail. They are machines that can share the same floor space safely all day — until a hook is raised or a load lowered into the vertical gap between them, at which point a clash appears in a dimension a distance-only system cannot even see.
Protecting them means sensing in three dimensions: where each crane is, whether their paths overlap, how high each hook sits, and whether the clearance between them is being preserved. Done as zone protection, with graduated warnings, smooth intervention and an always-available escape, it lets a multi-level bay run freely and safely at once — allowing the overlaps that are safe and preventing only the specific combination that is not.
Watch the height, not just the distance — and stop only the clash that is real.
To engineer anti-collision for cranes at different heights in your bay, talk to the team at Aggra Cranes.
Frequently Asked Questions
-
Why do cranes at different heights need a different kind of anti-collision?
Because the danger is in a different dimension. A conventional system for cranes on a shared runway measures how far apart they are along the rail and stops them before the gap closes — a one-dimensional problem. Cranes at different heights can share the same floor space safely, passing over and under each other, so distance alone does not indicate danger. The hazard appears only when a hook or load is raised or lowered into the vertical space between them. Protecting against that requires the system to know each crane’s position, whether their paths overlap, and crucially each hook’s height — information a distance-only system does not have.
-
What actually causes a collision between cranes at different heights?
The hook, not the bridges. Two cranes at different levels whose paths overlap will pass over and under each other safely as long as their hooks stay within their own levels. A clashhigher crane lowers a load down into the path of the lower crane passing beneath. In this case the bridges never came close — the collision happened in the vertical gap between them, the moment a hook went where it should not.
-
Won’t an anti-collision system constantly stop cranes that share floor space?
Not if it is designed for the geometry. The whole point of a different-height system is to allow safe overlap — to let the cranes share floor space freely whenever their heights keep them apart — and to intervene only in the specific combination of overlapping paths and lost vertical clearance that is genuinely dangerous. A crude system that stopped the cranes whenever their footprints crossed would make the bay unworkable and would soon be switched off. A properly configured zone-based system distinguishes the safe overlap (no action) from the dangerous one (warn, then stop the offending motion), so the cranes are only ever restrained when a clash is actually developing.
-
How does the system know where the hooks are?
Through hoist position feedback on each crane — typically an encoder or height sensing on the hoist that reports how far the hook has been raised or lowered. Combined with each crane’s travel position (from travel encoders or crane-to-crane distance sensing) and a configured map of where the paths overlap and what vertical clearance must be maintained, the controller can continuously work out whether the two cranes are safely separated in height within any shared region. When the clearance in an overlap zone starts to erode, the system warns and then inhibits the hoist or travel motion that is closing the gap.
-
Can a crane still recover after the system stops it?
Yes, and the system must be designed so it can. If the higher crane has lowered its hook too high into the overlap, the correct recovery is to hoist it — so the system blocks the lowering that caused the problem while freely permitting the hoisting that resolves it. The same directional logic applies to travel: movement that deepens the overlap is blocked, while movement that clears it is allowed. Blocking every motion would strand the crane in the dangerous position and force someone to bypass the safety system to recover, which is exactly how anti-collision systems end up disabled. A well-designed system always leaves the operator a safe way out.