20.01.2015 Views

Kogelberg IMP - 2nd SH meeting Report.pdf - Anchor Environmental

Kogelberg IMP - 2nd SH meeting Report.pdf - Anchor Environmental

Kogelberg IMP - 2nd SH meeting Report.pdf - Anchor Environmental

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

BC – you can also provide feedback on the draft KC<strong>IMP</strong> in writing. Please look at the plan and raise<br />

any comments or concerns by January next year.<br />

Strategies:<br />

BC – the strategies are a proposal of how to put the objectives into practice. The diagram of<br />

objectives and strategies indicates that all the objectives are interlinked and essentially underpin<br />

one another.<br />

Zonation:<br />

BC ‐ this is likely to be the most contentious section. A proposal that was supported in the focus<br />

group <strong>meeting</strong>s was the proclamation of one large zoned Marine Protected Area (MPA) similar to<br />

that of the Table Mountain MPA which has no take zones and controlled areas in which a blanket<br />

exemption has been granted.<br />

A similar initiative is proposed for the <strong>Kogelberg</strong> however it will be designed to benefit local<br />

communities through exemptions for the exploitation of inshore resources, like kelp, abalone and<br />

rock lobster, in controlled zones by local small‐scale fishers only. It is proposed that a general<br />

exemption be passed for all recreational fishers to fish in the controlled zones so as not to impact on<br />

the tourism industry in the area. Exemptions will also be granted for the exploitation of offshore and<br />

migratory resources by large scale commercial rights holders where applicable.<br />

All exemptions will be granted within 80% of the coastline of the MPA, the remaining 20%<br />

will be a no take sanctuary area. This no take area is necessary so to ensure that the inshore<br />

resources (which are to be utilized exclusively by local small scale fishers and recreational fishers)<br />

can be sustained from within the MPA. We need to identify 20% of the coastline to be declared no<br />

take. The zones still need to be identified and negotiated. What we need from this <strong>meeting</strong> is in<br />

principle support for the idea before we invest effort in determining where the no take zone/zones<br />

will be located. The Bot Estuary Management Plan (EMP) has been integrated into this draft plan,<br />

but we acknowledge that the Bot EMP is still not finalized. We hope that it gets carried forward and<br />

incorporated in this KC<strong>IMP</strong>. It is important to understand that the one large zoned MPA is at this<br />

point only a proposal and that if you support it in principle we can take it forward and present it to<br />

Marine and Coastal Management.<br />

Comment 5 – The Betty’s Bay MPA is the only section of the <strong>Kogelberg</strong> coast that is safe for angling<br />

from the shore. Rooiels has a dangerous coastline. Angling must be allowed in Betty’s Bay MPA as it<br />

attracts visitors and is the only area where geelbek can be caught. Anglers are not the only culprits<br />

on the coast. Visitors scramble over rocks and allow dogs on beaches. If you close a section of coast<br />

to angling you must close it to all users.<br />

Response BC – We are not here to discuss where the no take zones will be located. This will<br />

be taken up in negotiations next year once we have in principle support from you for a large zoned<br />

MPA with 20% of the coast no take. The negotiation process will be a long process to be initiated<br />

next year. One issue brought up in a focus group <strong>meeting</strong> regarding the closure of the Betty’s Bay<br />

MPA was that of equity. Currently small scale fishers are not permitted to fish here while<br />

recreational fishers can from the shore.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!