A parliamentary question regarding potential contamination at the Waterbank project site in East Perth, inquiring about past activities, expected contamination, and advice received regarding fish health in adjacent waters. The Minister confirms contamination concerns and landfill history, but states no specific advice was received regarding fish.

AnsweredQoN 8692Legislative Assembly
Asked
19 September 2012
Portfolio
Planning

QuestionView source ↗

In relation to the design guidelines for the Waterbank project at East Perth on the Swan River, I ask:
(a) could the Minister verify that the guidelines state that past activities may have led to contamination of the site, and that although there has been significant remediation of the site as part of the creation of Waterbank, the site will need to be further investigated and managed;
(b) if so, what are the past activities and what contamination may be expected; and
(c) further to the contamination of fish using the similarly excavated and contaminated site at Claisebrook Cove, what advice has the Minister or his agencies received or requested regarding fish in waters contained and adjoining the Waterbank project?

AnswerView source ↗

Answered
23 October 2012
Responded by
Minister for Planning
Response time
34 days
(a) Yes
(b) The Waterbank site was used as a land fill site from the early 1950s to the late 1960s. Contamination in the site is consistent with other riverbank sites in Perth.
(c) Nil. The Metropolitan Redevelopment Authority liaises with the Department of Environment and Conservation (DEC) and Swan River Trust (SRT) in regard to river health when required and is subject to DEC and SRT approval processes.
Notice: This document is created or edited using unregistered or evaluation copy of rtLib valid for testing or development purposes only. To use it for productive or any other purposes please register it. You may purchase the license on
http://www.rtlib.com

Explore WA Government Data

Search the full archive in the free dashboard, or query programmatically via API.

Explore more