Skip to content
Legislation Monitor

Working near other plant, including other cranes and concrete placement booms

Code version as at 1 Jul 2018 From Tower crane code of practice 2017, no changes tracked yet
Medium severity
QLD Tower Crane Code of Practice 2017 > Planning and Design
The obligation
Tower crane siting and planning must address the risk of collision with other plant, including other cranes and concrete placement booms.
A tower crane colliding with other plant may cause injury from dropped loads, crane collapse or failed crane components such as boom sections. Collision risk may exist where a concrete placement boom works within the tower crane's operating radius, or where tower cranes on adjacent sites operate in the same air space. …
What
Tower crane siting and planning must address the risk of collision with other plant, including other cranes and concrete placement booms.
Source
worksafe.qld.gov.au

Full analysis

Free account

What this means for you

Free account

Read the full analysis, tailored to your industry

  • Impact summary tailored to your industry
  • Full plain-English analysis of what changed
  • Email alerts & digests when this law changes
  • Compliance self-assessment tools
Official sources
Frequently asked questions

Which WHS law does this come from?

Working near other plant, including other cranes and concrete placement booms is a WHS requirement set out in Tower crane code of practice 2017 (QLD). It is made under Work Health and Safety Act 2011 (QLD). The relevant provision is Tower Crane Code of Practice 2017 > Planning and Design.

What does this WHS obligation require?

Working near other plant, including other cranes and concrete placement booms is a WHS obligation under Tower crane code of practice 2017 (QLD). In short, Tower crane siting and planning must address the risk of collision with other plant, including other cranes and concrete placement booms.

What changed recently?

Working near other plant, including other cranes and concrete placement booms was last updated on 19 October 2026.

About this Topic

Updates trackedMonitoring
Monitoring detail
First seenOct 2026