© 2026 Zoe. All rights reserved.
Zoe is a legal information platform. Always consult the Federal Register of Legislation for authoritative text.
[2012] ACAT 53
ACT Civil and Administrative Tribunal
2012-08-13
Original judgment source is linked above.
JOHNSON AND XU & ACT PLANNING AND LAND AUTHORITY & ORS (Administrative Review) [2012] ACAT 53
Catchwords: ADMINISTRATIVE REVIEW - PLANNING AND DEVELOPMENT - development application approved out of time - deemed refusal of development application - status of development application deemed refused - objective (b) of RZ2 suburban core zone - neighbourhood characteristics - meaning of scale, form and site development - mixed character of neighbourhood - dominant character of neighbourhood - tree management plan - mains water consumption - stormwater quality and quantity - traffic generation - parking - solar access - hedge screening - direct sunlight - private open space - when or means and - adequate external clothes drying facilities
ACT Civil and Administrative Tribunal Act 2008 ss. 12 and 68
List of Regulations: ACT Civil and Administrative Tribunal (Transitional
Planning and Development (Draft Variation Number 306) Consultation Notice 2011 ( N12011-273)
Crime Prevention Through Environmental Design General Code
Waterways Water Sensitive Urban Design General Code
List of Cases: Bonansea and Commissioner for Land and Planning
Canberra Cruises and Tours v Minister of Urban Services (1999) ACTAAT 14
Drake-v-Minister for Immigration and Ethnic Affairs
Drake v Minister for Immigration and Ethnic Affairs
Glenella Estate v Mackay RC (2010) QPEC 132
Golden Paradise v Kogarah MC (1997) NSWLEC 164
Lewiac v Gold Coast C C (1996) 2 Qd R 266
Mal Nichols v Cardinia SC (2011) VCAT 2146
Mason v ACTPLA [2009] ACAT 7
Minister for Aboriginal Affairs v Peko-Wallsend Ltd
Rudder v ACTPLA [2010] ACAT 24
Super Studio-v-Waverley [2004] NSWLEC 91
CIVIL AND ADMINISTRATIVE TRIBUNAL ) NO: AT 12/6
The Tribunal orders that the decision under review be confirmed subject to the following variations:
That conditions A1 and A2 be deleted and the following conditions be substituted:
A1 The development application is approved on condition that the development be constructed in accordance with the following plans:
Streetscape Elevations A10 Revision B (Exhibit PJ4)
Demolition and Landscape TMP-01 Revision D (Exhibit PJ4)
Excavation Tree Management TMP-02 Revision D (Exhibit PJ4)
Ground Floor Plan - Tree TMP-03 Revision D (Exhibit PJ4)
Ground Floor Plan - Tree TMP-04 Revision D (Exhibit PJ4)
Driveway Profile (option 2) as MM SK03 dated 20/4/2012 & MM SK03b
7 May 2012 annexed to email to Lingam Jatheendran from Graeme
Shoobridge dated 7/5/2012 (Exhibit R3 in proceedings AT12/6)
A2(a) That plan A10 Revision B (Exhibit PJ4) "Streetscape Elevations" and any other relevant plans set out above be amended to show the changed heights of Units 1, 2 & 3.
A2(b) That any amendment to the Stormwater Management Plans (Exhibits PJ7 & PJ15) be approved by the Authority.
A2(c) That any hedge be planted not less than 300mm inside any boundary of the subject land."
Mr R Arthur of counsel. The Authority was represented by Mr S Whybrow of counsel. Ms Fisher did not appear and was not represented. 3. Mr Arthur called the following witnesses: Dr Xu, one of the applicants, and
Ms Wang, Ms Nicholson and Mr Jervis who are all parties joined. He also called four expert witnesses Mr Goodyer, a planner, Mr Graham, a traffic engineer, Dr Martens, a civil engineer and Mr Mann, an arborist. Witness statements were tendered by all of the witnesses. The remaining parties joined were not called as witnesses but their Statements of Facts and Contentions and witness statements were tendered in evidence. 4. Oral evidence on behalf of the Authority was given by Ms Jamaly, Technical Coordinator, Merit Assessment South, of the Authority, as an expert witness. Mr Jatheendran a senior traffic and civil engineer with Territory and Municipal Services Directorate, gave expert evidence. Both experts' witness statements were tendered. Ms Park who carried out the assessment of the development proposal for the Authority also gave evidence. 5. Expert evidence on behalf of the developers was given by Mr Streatfield, a planner, Mr Shoobridge, a traffic and civil engineer, and Mr Scholtens, an arborist. Mr T Milin, the architect for the proposed development, gave oral evidence about a number of aspects of the proposal and provided several revised plans during the hearing. Mr Beer, an architect who prepares three dimensional computer generated images, gave evidence in relation to Exhibit PJ16. Statements of evidence were tendered by these witnesses. The Statement of Facts and Contentions of the developers was tendered but they were not called to give evidence. 6. At the suggestion of the parties the witnesses with a common expertise gave their oral evidence together. 7. The Tribunal inspected the site of the proposed development and took note of the general character of the neighbourhood and the surrounding developments.
The Territory, the Executive, a Minister or a territory authority must not do any act, or approve the doing of an act, that is inconsistent with the territory plan.
Note 1 The Territory, or a territory authority, is prevented from doing anything inconsistent with the national capital plan.
Note 2 The Territory, the Executive, a Minister or a territory authority are also prevented from doing anything inconsistent with some draft variations of the territory plan (see s 65 and s 72).
(1) The objectives for a zone set out the policy outcomes intended to be achieved by applying the applicable development table and code to the zone.
(2) Each objective for a zone must be consistent with the statement of strategic directions.
(1) Development approval must not be given for a development proposal in the merit track unless the proposal is consistent with -
(b) if the proposed development relates to land comprised in a rural lease - any land management agreement for the land; and
(c) if the proposed development will affect a registered tree or declared site - the advice of the conservator of flora and fauna in relation to the proposal.
Note 1 An application cannot be approved if it is inconsistent with the territory plan (see s 50) or the National Capital Plan (see Australian Capital Territory (Planning and Land Management) Act 1988 (Cwlth), s 11).
(2) Also, development approval must not be given for a development proposal in the merit track if approval would be inconsistent with any advice given by an entity to which the application was referred under division 7.3.3 unless the person deciding the application is satisfied that -
(ii) any realistic alternative to the proposed development, or relevant aspects of it; and
(b) the decision is consistent with the objects of the territory plan.
(3) To remove any doubt, if a proposed development will affect a registered tree or declared site -
(a) the person deciding the development application for the proposed development must not approve the application unless the approval is consistent with the advice of the conservator of flora and fauna in relation to the proposal; and
(b) subsection (2) does not apply in relation to the conservator's advice.
In deciding a development application for a development proposal in the merit track, the decision-maker must consider the following:
(a) the objectives for the zone in which the development is proposed to take place;
(b) the suitability of the land where the development is proposed to take place for a development of the kind proposed;
(c) each representation received by the authority in relation to the application that has not been withdrawn;
(d) if an entity gave advice on the application in accordance with section 149 (Requirement to give advice in relation to development applications) - the entity's advice;
Note Advice on an application is given in accordance with section 149 if the advice is given by an entity not later than 15 working days (or shorter prescribed period) after the day the application is given to the entity. If the entity gives no response, the entity is taken to have given advice that supported the application (see s 150).
(e) if the proposed development relates to land that is public land - the plan of management for the land;
(f) the probable impact of the proposed development, including the nature, extent and significance of probable environmental impacts.
(1) The planning and land authority or, for a development application that the Minister decides to consider under division 7.3.5 (Ministerial call-in power for development applications), the Minister, must -
(b) approve a development application subject to a condition; or
Note 1 For provisions about conditions, see s 165. Also, a development application to vary a lease granted as a concessional lease by surrender and regrant of the lease as a market value lease is subject to a condition (see s 262).
Note 2 Notice of a decision under s (1) must be given under div 7.3.8.
Note 3 If a development application has been referred to an entity under division 7.3.3, the notice of the decision under this section must include information about any comment by the referral entity and whether the authority has followed the entity's advice (see s 172).
Note 4 The criteria for a decision on an application to vary a lease granted as a concessional lease are in div 9.4.2.
Note 5 An applicant and, in some cases, other people may have a right to apply for review of a decision under s (1) (see ch 13 and sch 1). However, the right to apply for legal review of a decision by the Minister is time-limited (see s 410).
(2) However, the planning and land authority or Minister must refuse a development application to which division 9.4.2 (Varying concessional leases to remove concessional status) applies if the Minister decides under section 261 that considering the application is not in the public interest.
(3) The planning and land authority or Minister must take action under subsection (1) in relation to a development application not later than the end of the prescribed time period for the application.
(4) To remove any doubt, the time for deciding a development application is not affected by -
(a) the referral of the application to the Minister by the planning and land authority under section 158; or
(b) the referral of the application back to the authority by the Minister under section 159.
(5) If the planning and land authority approves a development application that relates to a regulated tree, the authority may, under this section -
(a) if a tree management plan is already in force for the tree - approve an amendment of, or replacement for, the tree management plan; or
(b) in any other case - approve a tree management plan for the tree.
prescribed time period, for a development application, means -
(a) the period set out in part 7.2 (Assessment tracks for development applications) for deciding an application for a development proposal in the assessment track that applies to the proposal; or
(b) if the period mentioned in paragraph (a) is extended under division 7.3.7 - the period mentioned in paragraph (a) plus each extension that applies to the application under division 7.3.7.
(b) the time for deciding the application has ended; and
(c) neither the planning and land authority nor the Minister has decided the application under section 162.
(2) The planning and land authority or, if the Minister has decided to consider the application under division 7.3.5, the Minister, may approve the application, or approve the application subject to a condition, under section 162 despite the ending of the time for deciding the application.
(3) To remove any doubt, if neither the planning and land authority nor the Minister has decided an application under section 162, the authority is taken to have decided to refuse the application under the ACT Civil and Administrative Tribunal Act 2008, section 12 (When no action taken to be decision).
Note Because a decision of the ACAT on review is taken to have been a decision of the original decision-maker, the planning and land authority or Minister will not be able to approve an application if the ACAT has decided an application for review of the deemed refusal (see ACT Civil and Administrative Tribunal Act 2008, s 69).
(1) If a development application is refused under section 162 (1) (c) (Deciding development applications), the planning and land authority must give written notice of the refusal to -
(b) each person who made a representation under section 156 about the application.
(2) However, to remove any doubt, the planning and land authority need not give notice of a decision deemed under the ACT Civil and Administrative Tribunal Act 2008, section 12 (When no action taken to be decision) to have been made to refuse a development application.
(3) A notice under subsection (1) must set out the reasons for the decision.
Note If the notice is given to a person who may apply to the ACAT for review of the decision to which it relates, the notice must be a reviewable decision notice (see s 408 (2)).
2 September 2010 had ceased to exist. It had been deemed refused because the Authority had not made a decision within the time mandated under section 162 of the Act. Thus it could not be said on 3 June 2010 there was an existing DA that was protected by the "grandfathering" provisions of DV306. 3. Secondly, Mr Arthur proposed that the email of 2 June 2011 (T474) from Ida Schuurmans-Stekhover of the Authority to Tomi Milins saying " I have been instructed to refuse this development application " amounted to a refusal of the DA under the Act. 4. Thirdly, Mr Arthur said that even if the original DA had not ceased to exist the principle in Coty (England) Pty Ltd v Sydney City Council (1957) 2 LGRA 117 (Coty) and subsequent cases should be applied so that the requirements of DV306 would limit the development to five units. 5. Fourthly, he considered that a decision to approve a DA is discretionary and the factors to be taken into account are determined by the subject-matter and scope and purpose of the legislation. He relied on Minister for Aboriginal Affairs v Peko-Wallsend Ltd [1986] HCA 40; [1985-1986] 162 CLR 24 ("Peko Wallsend"). Mr Arthur said these factors included whether the DA was consistent with the Territory Plan, the circumstances at the time of the decision and whether they are different to the circumstances at the time of the deemed refusal, fairness to the developer, the interests of affected persons in stability and certainty and ensuing orderly development. 6. Fifthly, he said that the development did not comply with objective (b) of the Residential RZ2: Suburban Core Zone which required the development to address the existing neighbourhood characteristics in scale, form and site development. 7. Finally, he took issue with a number of specific rules, criteria and provisions contained in the Residential Zones- Multi Unit Housing Development Code ("the MUHD Code") and a number of general codes which he said the proposed development did not comply with.
"Deemed refusal" - status of DA after 3 June 2010
Peko Wallsend and the discretion to approve the DA
"Ensure that the development addresses the street and the existing neighbourhood characteristics in scale, form and site development".
There was no disagreement that the development addresses the street and meets that part of the objective. However there is substantial disagreement as to whether the development addresses the neighbourhood characteristics in scale, form and site development.
Height not to exceed 2 storeys - Rule 13 MUHD Code
Buildings must be within building envelope - Rule 14 MUHD Code
Plot ratio not to exceed 50% - Rule 15 MUHD Code
Crime Prevention Through Environmental Design General Code - Applied by Criterion 35 MUHD Code
Access and Mobility General Code - Applied by Criterion 36 MUHD Code
Mr T Milin produced the updated Revision D plans for the development which he said addressed all of these issues. Mr Eric Martin then confirmed that in his opinion the Revision D plans complied with the Code. In his opening submission, Mr Arthur accepted that the access and mobility aspects of the proposal were now satisfactory. When the levels of units 1-3 were adjusted during the course of the hearing in response to tree management issues, the developers provided a further statement from Mr Eric Martin confirming that the plans still complied with the Access and Mobility General Code. The applicants did not dispute this statement. Although Mr Adamson and Mr Martin provided expert opinions they were not required to give oral evidence.
This rule applies to a development that has one or more of the following characteristics:
a) requires groundwork within the tree protection zone of a protected tree
b) is likely to cause damage to or removal of any protected trees
The authority shall refer the development application to the Conservator of Flora and Fauna.
1. Under the Planning and Development Regulation 2008 a development application for a declared site under the Tree Protection Act 2005, must be referred to the Conservator of Flora and Fauna.
2. The authority will consider any advice from the Conservator of Flora and Fauna before determining the application in accordance with the Planning and Development Act 2007.
3. Protected tree and declared site are defined under the Tree Protection Act 2005.
Mr Paul Scholtens for the developers. It became evident that a revision of the tree management plan might overcome the concerns outlined in Mr Mann's original witness statement commenting on the development. Mr Milin prepared a revised tree management plan (Exhibit PJ11- TMP 01, 02, 03 and 04) which incorporated changes to the basement excavations, a revised stormwater management plan, post and beam construction in places and adjustment to the levels of units 1-3. All parties indicated that the revised tree management plan was satisfactory, including the Authority who had obtained confirmation from the Conservator.
6.7 Water Sensitive Urban Design - Mains Water Consumption
Note: Refer to the Water Ways: Water Sensitive Urban Design General Code for more information on Water Sensitive Urban Design
Evidence is provided that shows the development achieves a minimum 40% reduction in mains water consumption compared to an equivalent development constructed in 2003 using the ACTPLA on-line assessment tool or another tool as included in the Water Ways: Water Sensitive Urban Design General Code. The 40% target is met without any reliance on landscaping measures to reduce consumption.
This requirement does not apply for extensions with an increase in the combined roof area, driveway, car manoeuvring areas and car parking areas of less than 25% of the original area.
This is a mandatory requirement. There is no applicable criterion.
Stormwater Quality and Quantity - Rules/Criteria 47 and 49 MUHD Code
6.8 Water Sensitive Urban Design - Stormwater Quality and Quantity
Note: Refer to the Water Ways: Water Sensitive Urban Design General Code for more information on Water Sensitive Urban Design
All sites of size greater than 2,000m2 need to provide evidence of stormwater storage greater than or equal to the volume of 1.4kL per 100m2 of impervious area and release over a period of 1 to 3 days. 50% of the volume of rainwater tanks connected to at least the toilet and all external taps may be regarded as contributing towards this requirement.
This requirement does not apply for extensions with an increase in the combined roof area, driveway, car manoeuvring areas and car parking areas of less than 25% of the original area.
Evidence is provided that demonstrates that for all sites of size greater than 2,000m2, a reduction of 1-in-3 month stormwater peak run off flow to pre-development levels with release of captured flow over a period of 1 to 3 days can be achieved.
This requirement does not apply for extensions with an increase in the combined roof area, driveway, car manoeuvring areas and car parking areas of less than 25% of the original area.
All sites of size greater than 2,000m2 and subject to redevelopment need to ensure that the capacity of the existing pipe (minor) stormwater connection to the site is not exceeded in the 1-in-10 year storm event.
All sites of size greater than 2,000m2 and subject to redevelopment need to ensure that the capacity of the existing overland (major) stormwater system to the site is not exceeded in the 1-in-100 year storm event.
For estate and multiple block developments larger than 5000 m2, retardation of stormwater to meet the above requirements are to be met at the estate scale rather than by measures on individual blocks.
Evidence is provided by a suitably qualified person that shows that for all sites of size greater than 2,000m2 and subject to redevelopment.
stormwater peak run off flow to pre-development levels. See WaterWays General Code for more detail.
That the capacity of the downstream piped stormwater system to its outlet with an open channel is not exceeded in the 1-in-10 year storm event.
For estate and multiple block developments larger than 5000 m2, retardation of stormwater to meet the above requirements are to be met at the estate scale unless it can be demonstrated that this is less feasible than measures on individual blocks.
Dr Martens for the applicants and Mr Shoobridge for the developers. As earlier discussed stormwater management was inter-related with tree management, with revisions of both the tree management plan and the stormwater management plan submitted during the course of the hearing. 2. In relation to Rules 47 and 49, the expert witnesses were not able to resolve all the issues in detail during the course of the hearing. Dr Martens conceded that the revised stormwater plan was conceptually workable, though he also made the point this was not yet verified with model data. Mr Shoobridge stated that absolute compliance with Rules 47 and 49 should be verified at the final design stage. He indicated on his preliminary storm water management plan (Exhibit PJ7) that the arrangement set out in that plan would be expected to satisfy Rules 47 and 49 of the MUHD Code. This involved an on-site detention (OSD) tank of 17,206 litres which was not disputed. Although Dr Martens and Mr Shoobridge were in agreement that a 13,000 litre on-site stormwater retention tank was the correct size, Ms Park said that she had been told that 14,400 litres might be preferable. The Tribunal prefers the direct evidence of the experts and accepts that the volume of the OSR tank should be 13,000 litres. 3. Both Dr Martens and Mr Shoobridge said that the reduction of the stormwater gross pollutant export load set out in the Waterways Water Sensitive Urban Design General Code had not been met and suggested that this was a deficiency that should be addressed. This General Code applies the reduction targets to developments on areas of land larger than 2,000 m2 such as that proposed.
Rule 48 of the MUHD Code requires only that these reduction targets to be met for sites larger than 5,000 m2. The MUHD Code states that the general codes are subject to it, so the pollution reduction targets are therefore not applicable to the development proposal. 4. Some debate arose between Dr Martens and Mr Shoobridge as to whether a charged stormwater system or an uncharged system was preferable. Both systems are acceptable to deal with stormwater management but a charged system requires greater maintenance. Mr Milin in Exhibit PJ10 and
Mr Shoobridge in Exhibit PJ7A provided freehand diagrams showing the layout of such systems. The Tribunal does not need to make a decision on this matter as either system or a combination can allow Rules 47and 49 to be met. 5. The Authority indicated that all the relevant agencies had confirmed the revised stormwater plan was satisfactory. Based on all the evidence and the plans in Exhibits PJ7 and PJ15 the Tribunal considers that Rules 47 and 49 are met.
Parking - Rule 81 and Parking and Vehicular Access General Code
Mr Graham. 2. Mr Graham said that the security door to the basement car park ".....would require swipe cards or an intercom for a tradesman or visitors to gain access then the vehicle would need to reverse out" if the occupier was not answering. This, he said, was contrary to Clause 2.3.2 (b) of the Parking and Vehicular Access General Code which requires ingress and egress to and from the site to be made in a forward direction. 3. However that requirement is limited to vehicles "... having a regular requirement to enter the site" [Clause 2.3.2 (b)], for example, residents. In the Tribunal's view the fact that a visitor or tradesman might need to reverse out is not inconsistent with this General Code.
Private Open Space (POS) - Rule 89 Criterion 89 MUHD Code
Private Open Space (POS) - Rule 90(a) Criterion 90 MUHD Code
Private Open Space (POS) - Rule 90(c) MUHD Code
Private Open Space (POS) - Rule 90(d) and Criterion 90 MUHD Code
Adequate External Clothes Drying Facilities - Criterion 95, Rule 97 and
FULL REPORT ( ) CASE NOTE ( ) UNREPORTED DECISION ( )
(1979) 24 ALR 577
(1996) 2 Qd R 266
(2000) 1 Qd R 306