Tower Crane Anti-Collision in the UAE — Cabinet Decision 37/2023, Load Monitoring & Smart-Crane Compliance

Stand at the corner of a Dubai megaproject — Burj Azizi, a Palm Jebel Ali cluster, Wynn Al Marjan, a Hudayriyat plot — and look up. The jib-tips overhead aren’t operating in isolation. Each crane sits inside a swept zone overlapping two, three, sometimes four neighbours. The operator in every cab sees one slew arc clearly; the others sit behind counter-jib weights or simply outside peripheral vision.

That’s the problem anti-collision was built to solve, and it’s quietly become the single biggest 2026 change to UAE tower-crane compliance. UAE Cabinet Decision 37/2023 nudged the country toward real-time load monitoring, digital compliance records and smart-crane integration, on top of the existing DM-PH&SD-P4-TG21 baseline. The practical implementation is what contractors have to specify, install, commission and document.

A note up front: Cabinet decisions and DM circulars get amended, and exact wording matters when you’re building a permit submission. Treat this post as practitioner guidance, not legal interpretation — confirm the current text against the issuing authority before drafting your documentation pack.

What anti-collision actually means on a tower-crane site

In UAE practice “anti-collision” covers four distinct risks:

Slew-arc overlap between cranes. Two or more cranes share airspace and the jibs are long enough that one crane’s full slew sweeps through another crane’s mast or counter-jib. On a Downtown Dubai cluster this is the default geometry.

Jib-tip vs counter-jib overlap. The most common collision geometry. Crane A’s hook swings over Crane B’s counter-jib while Crane B is slewing the other way — and the counter-jib weight is the heaviest moving mass on the site. A strike there is a structural event, not a near-miss.

Cab strike. A jib swings into another crane’s cab, with the operator in it. Lower probability than counter-jib strike, but the consequence is fatal.

Zone violations inside a single crane’s slew arc. No-fly zones over schools, occupied adjacent buildings, live roads, overhead power lines, lay-down areas the lift plan put off-limits. Single-crane geometry, but the same operator-awareness failure mode.

The human-error problem behind all four is the same: an operator concentrating on a hook load can’t simultaneously track every other moving element in the airspace. Banksmen, radio coordination and lift plans all help — anti-collision is the backstop when the system that’s supposed to catch the error doesn’t, because the radio was busy, the banksman didn’t see, or the operator was 11 hours into a shift.

The regulatory backdrop in the UAE

DM-PH&SD-P4-TG21 — Guidelines for Examination and Certification of Cranes, Hoists, Lifts and Other Lifting Appliances — is the Dubai Municipality baseline. It cross-references BS 7121-5, BS EN 14439 and LOLER as the technical anchor, and expects mechanical limits and zone restriction in place wherever the lift plan requires them.

UAE Cabinet Decision 37/2023 added federal direction on lifting-equipment safety, smart-crane technology and digital compliance records. The practical translation as currently interpreted on UAE sites: real-time load-moment monitoring, electronic operator logbooks, remote diagnostics and centrally-coordinated anti-collision on multi-crane sites are becoming the expected standard rather than a high-end optional. Confirm against the latest issued text before quoting specific clauses.

Trakhees runs a structurally similar regime to DM for PCFC and Nakheel-managed territory. JAFZA and DAFZA apply inside the free zones and focus the smart-crane conversation more narrowly because most of their sites are single-crane warehouse builds rather than multi-crane high-rise. Abu Dhabi operates the OSHAD framework alongside ADM and DMT; OSHAD’s code is more prescriptive on competency assurance and risk assessment, and Abu Dhabi megaprojects on Yas, Saadiyat and Hudayriyat increasingly require anti-collision spec’d into the project safety management plan from day one. The dedicated permits across DM, Trakhees, JAFZA and DAFZA guide walks through the authority-by-authority pack content.

The three layers of an anti-collision system

Anti-collision isn’t one system — it’s three layers stacked, each addressing a different failure mode.

1. Mechanical limits

Passive, OEM-fitted on every modern crane shipped to the UAE. Slew limit, hoist height limit (upper and lower hook travel), trolley travel limit (jib root and jib tip). These work whether the smart-crane software is on or off, and if they fail TPI the crane doesn’t lift. What they don’t do: define dynamic forbidden zones inside the slew arc, or coordinate with another crane.

2. Zone-restriction software

A software layer in the crane’s own controller that defines forbidden zones inside the slew arc. Typical UAE applications:

• Slew arc cut to avoid swinging over an occupied adjacent building
• No-fly zone above a school playground or live road crossing the site corner
• Electrical exclusion around an overhead line near the slewing platform
• Height limit zoned by trolley position (lower hook only allowed at certain radii)
• Lay-down area exclusions when the lift plan declares an off-limits zone

When the operator approaches a forbidden boundary the controller slows slewing and trolley motion, then stops at the boundary. This is single-crane scope only — it doesn’t know another crane exists.

3. Multi-crane anti-collision

A sensor + radio + controller stack that lets every crane on a site know where every other crane is, and brakes the relevant motion before envelopes intersect. Each crane carries:

• Slew position sensor — typically an absolute encoder on the slewing ring
• Trolley position sensor — on the trolley winch or trolley track
• Hoist position sensor — on the hoist drum
• Radio module — broadcasting position to the central controller (2.4 GHz or sub-GHz industrial bands, configured to avoid site-comms interference)
• Intervention wiring — into the slew and trolley contactors so the controller can brake motion when an intersection is computed

Scenarios protected — jib-tip vs cab, counter-jib vs jib, hook vs jib, hook vs counter-jib weight — each have their own geometric calculation. Well-specified systems compute the envelope dynamically, factoring in load swing and slewing inertia, not static geometry.

Smart-crane / IoT compliance

The smart-crane layer sits above anti-collision and is what the 2023 Cabinet direction points at most explicitly. Components contractors are specifying on UAE megaprojects in 2026:

• Load-moment indicator (LMI) — real-time monitor of the load-moment ratio against the load chart, with audible warning at 90% SWL and intervention at 100%. Smart-crane adds logging and dashboard export to the standard LMI.
• Real-time load logging — every lift, weight, radius, time-stamped with operator ID, stored on the crane and synced to a server. The artefact that proves the lift plan was followed and the load chart respected.
• Remote diagnostics — fault codes, motor temperatures, brake-pad wear estimates and controller event logs pulled to a dashboard the contractor and service provider both watch. Detects degradation before failure.
• Electronic operator logbook — replaces the paper logbook with a touchscreen the operator signs into at shift start, with the pre-shift checklist captured digitally and the timestamped lift history attached.
• Anemometer integration — wind speed feeds the dashboard and triggers stop-lift alerts when the threshold is crossed. See our wind speed and shamal management guide for the UAE-specific thresholds.

On UAE megaprojects — Burj Azizi-adjacent towers, Palm Jebel Ali clusters, Wynn Al Marjan podium work — this is the expected stack. On smaller villa and mid-rise jobs, LMI and electronic logbooks land first because they’re cheaper to commission per crane.

Anti-collision OEMs and aftermarket suppliers in MENA

The market in 2026 has consolidated around a handful of suppliers active across UAE, Saudi and Qatar. Indicative pros and cons:

Default decision tree: uniform fleet → OEM-native; mixed fleet → brand-agnostic third-party (RobWay, AGS, Smie). The split is roughly 60/40 toward third-party on UAE megaprojects because brand mixing is the norm.

For the brand-by-brand procurement view see the Yongmao / Potain / Zoomlion / XCMG comparison. For load-chart specifics the LMI enforces see the UAE load-charts and lifting-capacity guide.

Retrofit reality on older cranes

A large share of the UAE active fleet predates factory-fitted multi-crane anti-collision — pre-2018 Yongmao STT-series, Potain MD-series, Zoomlion T7020 generation, older Liebherr units. Retrofit is the standard answer. The sequence on a typical UAE crane:

1. Site survey. Crane model, year, controller generation, electrical layout, mast and jib geometry, planned climb cycles. Some controllers accept sensor data directly; others need a protocol gateway.
2. Sensor specification and procurement. Slew encoder, trolley sensor, hoist sensor, radio module, controller unit. Lead time 4–8 weeks to Dubai depot for most third-party kits.
3. Cable run. Shielded signal cabling down the mast inside the existing festoon, protected against the high RF noise of a UAE construction site.
4. Mechanical mounting. Encoder on the slewing ring, brackets on the trolley track, antenna on the cab or counter-jib. Typically 2–3 working days out of service per crane.
5. Controller wiring. Intervention outputs from the anti-collision controller into the slew and trolley contactors. Slower on older relay-based controls.
6. Commissioning. Each sensor calibrated against actual geometry, no-fly zones programmed, intervention tested across every motion in both directions.
7. Hand-over documentation. Commissioning report, calibration certificate, functional test log, software configuration export, operator training records.

Single-crane retrofit: 3–5 days end-to-end. Multi-crane site (4–6 cranes): 2–3 weeks with parallel teams. The longest variable is commissioning, not installation.

Implementation steps for a multi-crane site

Beyond the per-crane retrofit, the multi-crane scope adds site-level engineering:

1. Airspace survey. Number of cranes, base coordinates, mast heights at each programme stage, jib lengths, slew arcs, planned climbs. Computed envelope intersections per phase. This is the artefact the supplier needs before quoting.
2. Specify blocked vs warned scenarios. Not every intersection needs full intervention — some warrant audible warning, some need full slew braking. The lift plan drives the call.
3. Vendor selection. OEM-native vs third-party (above), against the airspace survey.
4. Installation and commissioning. Per-crane retrofit plus site-level radio coordination, central controller positioning, intervention boundary testing across every crane pair.
5. Operator training. Supplier-led top-up on site, 1–2 days per operator. The counterintuitive content matters — what happens when the system intervenes mid-lift, how to clear an alarm correctly, how to recognise drift symptoms. See the operator licensing baseline.
6. Maintenance cadence. Monthly functional test per crane. Annual full recalibration in parallel with TPI. Re-calibration after every climb cycle, since sensor positions shift relative to the slewing reference. See the TPI third-party inspection guide for how anti-collision fits the annual inspection.

What goes wrong — common implementation failures

Five patterns we see most often on UAE sites:

• Sensor drift after climb. Every climb cycle moves the crane’s reference geometry — the slew encoder doesn’t know the mast got taller. Without re-calibration the controller computes against obsolete geometry, generating false alarms (operators mute the system) or worse, missed alarms. Fix: bake recalibration into the climb method statement.
• Calibration loss from controller power cycles. Some older systems lose calibration on hard power-off — lightning, slew-cabinet breakdown. Fix: back up the calibration file off-crane and confirm the restore procedure before commissioning sign-off.
• Radio interference from site comms. The 2.4 GHz band on a UAE megaproject is congested — site Wi-Fi, walkie-talkies, telemetry. Anti-collision links on that band drop intermittently. Fix: spectrum survey before commissioning, sub-GHz configuration if 2.4 GHz is saturated.
• Operators disabling warnings. Repeated false alarms train operators to mute. Once mute is normalised, real alarms get ignored too. Fix: calibration discipline plus a controller audit trail with every mute logged against operator ID.
• Service-mode parking. Intervention is disabled for maintenance, the technician leaves without re-enabling production mode, the next shift lifts blind. Fix: pre-shift checklist includes service-mode status; the electronic logbook flags non-production at sign-in.

Documentation pack — what UAE inspectors look for

The “smart-crane file” UAE reviewers expect on a multi-crane site:

1. Commissioning report per crane — installed sensors, intervention points, tested boundaries, supplier sign-off
2. Calibration certificate per crane, dated, tied to the commissioning report — re-issued after every climb
3. Software version and configuration file with a change log if site geometry was updated
4. Functional test logs — every intervention scenario tested, pass/fail, date of last monthly check
5. Operator competency record — top-up assessment on the anti-collision UI, per operator
6. Change-management log — new tower inside the swept zone, climb, jib reconfigure
7. Electronic logbook export — lifts, alarms, overrides and operator IDs over the inspection period

DM reviewers and Trakhees-CED desks ask for the file in roughly that order. The TPI body running annual inspection cross-checks calibration and functional test logs against the commissioning baseline.

Getting started — HOE for anti-collision on multi-crane UAE projects

HOE coordinates anti-collision specification, vendor selection, retrofit and operator competency for multi-crane UAE projects across the full supplier matrix — RobWay, AGS, Smie and OEM-native systems on Yongmao, Potain, Zoomlion, Sany and XCMG. On supply-and-erect scope we run the site survey, specify against the airspace geometry, manage the retrofit, commission the file, train operators and bundle the documentation pack.

• Sales / new project enquiries: +971 50 144 4810 or the contact form
• 24/7 breakdown and maintenance on existing systems: +971 4 880 3079
• Email: inquiry1@hoe.ae

Send the site geometry — number of cranes planned, mast heights, jib lengths, plot boundaries — and we come back inside 48 hours with the anti-collision spec, vendor shortlist and an indicative cost stack. For the wider compliance picture see the services hub and the 2026 operations compliance guide that this anti-collision view fits into. The FAQ below covers the eight questions contractors ask most often when scoping an anti-collision system for a UAE site.