Flood Mapping and Standing Advice for Development and Flood Risk

1
Flood Mapping and Standing Advice for Development
and Flood Risk

• CIWEM Tyne Humber Branch Meeting - January 2005

2
Iain Andrews Strategic Planning Team Leader
Beki HoweyDevelopment Control Team Leader
3
What are we going to cover?

• Flood Mapping
• Standing Advice for Flood Risk
• Forward look

4
Flood Mapping

• Background
• Flood Zones
• Flood Map
• Future Work

5
Why is Flood MappingImportant?

• For the Environment Agency
• For other people we work with
• Association of British Insurers
• Emergency Services
• Local Authorities
• Public

6
Looking back

• Easter 1998 floods
• Call for publication of flood maps even in a
  relatively unrefined state

7
Indicative Floodplain
8
Why Change?

• Planning Policy Guidance Note 25
• Improve information on flood risk
• Flood events e.g. Autumn 2000
• Strategy for Flood Risk Management 2003-2008
• Continued provision of insurance

9
Flood Mapping Strategy -2004 Outputs

• Flood Zones
• To meet the requirements of PPG25
• June 2004, sent to Planning Authorities
• The Flood Map
• To raise awareness
• 7 October 2004, launched on Internet

10
Flood Zones

• Zone 1 - Little / No Chance
• Zone 2 - Low to Medium Chance (light blue)
• Zone 3 - High Chance (dark blue)

11
Flood Zones
12
Flood Map
13
Future Work

• Flood zones for year 2050
• climate change
• Flood Hazard Data
• depth
• direction
• velocity

14
Review

• Flood Mapping is important
• Flood Zones
• Flood Map

15
Standing Advice for Development and Flood Risk
16
Planning revisions

• Amendments to Planning law
• Standing Advice now accepted as material planning
  consideration
• Re-clarify Agencys role as statutory consultee
• Enable Agency to focus on high risk and strategic
  issues

17
Standing Advice

• Risk-based approach
• Ease of use by showing as a matrix
• LPAs able to make more informed decisions using
  supporting advice
• Encourage pre-application input

18
Why a Flood Risk Assessment

• To avoid inappropriate development - PPG25
• Scale and nature of development - PPG25
• The applicant needs to demonstrate that the
  development would not be at flood risk or
  increase flood risk to others.

19
Standing Advice matrix
20
Flood Zones

• School re-development - located in Zone 1
• House on Boundary Avenue - located in Zone 2
• Application at Holmefield Farm - located in Zone
  3

21
Standing Advice matrix
22
Grey Boxes

• Indicate lowest level of risk
• Agency does not require FRA
• LPA can ask for FRA under Para 60 of PPG25
• appropriate to scale and nature of development

23
Green Boxes

• Indicate lower level of risk
• LPAs to assess FRAs
• FRA submitted with planning application using the
  Standing Advice without direct consultation with
  the Agency

24
Red Boxes

• Indicate highest level of risk
• LPAs to consult Agency with FRA submitted by
  applicant
• Objection to planning application sent without
  FRA

25
Sensitive developments - Zone 1 2

• Particular uses which are especially vulnerable
  to flooding, or have potential to increase flood
  risk elsewhere
• Site may be located in lower risk zones, but
  potential for wider impact needs particular
  consideration

26
FRA acceptance

• Agency recommends that proposed mitigation
  measures should be covered by planning conditions
• LPA is responsible for discharging conditions

27
Future Work

• Letter of Compliance - pre-application
• Incorporation of CIRIA guidance

28
Letter of Compliance

• Encourage consultation at pre-application stage
• Risk reduced by consultation and agreement on
  surface water issues
• Agency will issue Letter of Compliance for
  applicant to submit with FRA in planning
  application
• Covers flood risk only

29
CIRIA guidance

• Flood Map - one answer to questions for Level 1
  FRA
• Standing Advice Matrix - provides some guidance
  for scope of Level 2 FRA for fluvial and tidal
  flooding

30
Review

• Flood mapping
• Standing Advice
• www.pipernetworking.com

31
Flood Mapping and Standing Advice for Development
and Flood Risk

• CIWEM Tyne Humber Branch Meeting - January 2005