12.07.2015 Views

Fraser River Sockeye Fisheries and Fisheries Management - Cohen ...

Fraser River Sockeye Fisheries and Fisheries Management - Cohen ...

Fraser River Sockeye Fisheries and Fisheries Management - Cohen ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

lower <strong>Fraser</strong> <strong>River</strong>. Power Point Presentation. <strong>Fisheries</strong> <strong>and</strong> Oceans Canada. 22 pp.), Anon(2008) (Anon. 2008. Interim fishery monitoring <strong>and</strong> catch reporting st<strong>and</strong>ards for commercialsalmon fisheries. Unpublished internal DFO report for discussion purposes. 24 p.), <strong>and</strong> Lightly<strong>and</strong> Masson (2009) (Lightly, D., <strong>and</strong> C. Masson. 2009 (in prep.). First Nation FSC CatchMonitoring <strong>and</strong> Reporting: Preliminary Considerations, St<strong>and</strong>ards <strong>and</strong> Recommendations. Draftreport prepared for the Can. Dept. of <strong>Fisheries</strong> & Oceans. Sept. 2009. 31 p.). Surely, LGL Ltd.can ask DFO to provide copies of recent documents <strong>and</strong> discussion papers (as that of Ionson2009) to help determine with more certainty if FN catches (<strong>and</strong> even commercial ones) arepotentially biased (precision levels is usually of secondary concern).LGL Response: Two of our formal requests to DFO were for documents that describe thecurrent (2005-2009) <strong>and</strong> historical (1980-2004) methods used to estimate First Nation <strong>and</strong>commercial catch of <strong>Fraser</strong> sockeye (See Appendix B – DFO Request #3b <strong>and</strong> #6). Thereferences related to catch monitoring in our report include all the reports provided byDFO.Page 36: In earlier sections, the authors note that US catches of <strong>Fraser</strong> <strong>River</strong> bound sockeye in2009 were relatively low (Table 1). Apparently, only scale samples <strong>and</strong> used in SE Alaska todetermine stock contribution estimates, while Washington uses DNA <strong>and</strong> scale sample. Theauthors seem to take for granted the US opinion that their figures are ‘highly accurate’ despitethe near total lack of dock side validation, yet categorize the accuracy of <strong>Fraser</strong> <strong>River</strong> catchestimates as good, <strong>and</strong> highly reliable. Seems like a farfetched conclusion. In light of whathappened in 2009, it could be hypothesized that US <strong>and</strong> north coast catches of <strong>Fraser</strong> <strong>River</strong>sockeye were seriously underestimated because of some anomaly. No evidence is reported tosupport or refute this hypothesis, but it should be investigated more thoroughly.LGL Response: In more than 20 years of conducting run reconstruction analyses forAlaskan <strong>and</strong> Northern B.C. fisheries, no one has previously suggested that “U.S. <strong>and</strong> northcoast catches of <strong>Fraser</strong> <strong>River</strong> sockeye were seriously underestimated”. Catches of <strong>Fraser</strong><strong>River</strong> sockeye in Alaskan <strong>and</strong> Northern B.C. fisheries have varied substantially from yearto year. However, this variability appears to be consistent with the timing <strong>and</strong> location offisheries <strong>and</strong> environmental characteristics of the years. The catches of <strong>Fraser</strong> sockeye inAlaska <strong>and</strong> Northern B.C. fisheries have been assessed using scale pattern analyses that areannually reviewed <strong>and</strong> approved by the PSC. The average annual catch of <strong>Fraser</strong> sockeyein Alaska <strong>and</strong> Northern B.C. fisheries was 120,000 from 1982-2008 (range 0-453,000). Thehighest catches occur in El Nino years when water temperatures are warmer in the Gulf ofAlaska <strong>and</strong> <strong>Fraser</strong> sockeye migrate through southern southeast Alaska fisheries.M-17

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

Saved successfully!

Ooh no, something went wrong!