Reducing bycatch
Title V — Sustaining fisheries through healthy ecosystems and improved management
Read this section in the full bill →
This section appears in one version only, so there is nothing to compare yet.
(a) Minimizing bycatch (1) National standards for fishery conservation and management Section 301(a)(9) (16 U.S.C. 1851(a)(9)) is amended to read as follows: (9) Conservation and management measures shall— (A) minimize bycatch; and (B) to the extent bycatch cannot be avoided, minimize the mortality of such bycatch.. (2) Contents of fishery management plans Section 303 (16 U.S.C. 1853) is amended— (A) in subsection (a)— (i) in paragraph (5), by inserting quantification of bycatch, after hauls,; and (ii) in paragraph (11), by striking to the extent practicable and; and (B) in subsection (b)— (i) in paragraph (12), by striking and at the end; and (ii) by inserting after paragraph (12) the following: (13) consider full retention requirements for species with high catch mortality rates, provided that an annual catch limit and accountability measures are in place for the species and constrain catch in the fishery; and. (3) Action by the Secretary Section 304 (16 U.S.C. 1854) is amended— (A) by redesignating the second subsection (i) as subsection (j); and (B) by adding at the end the following: (k) Standardized bycatch reporting program (1) Establishment Not later than 3 years after the date of the enactment of the Sustaining America’s Fisheries for the Future Act of 2025, the Secretary shall establish a national standardized reporting program (referred to in this subsection as the program)— (A) to assess the amount and type of bycatch occurring in each fishery and across fisheries; (B) to determine the contribution of bycatch to the total fishing-related mortality of each fishery; and (C) to evaluate the effects of bycatch on relevant fisheries and the ecosystem. (2) Methodology and standards The Secretary shall, in carrying out the program— (A) identify appropriate methodologies and standards to collect and produce statistically accurate and precise information regarding bycatch; and (B) require consistent data reporting, collection, and assessment for each fishery managed under a fishery management plan. (3) Multiple jurisdictions If a species is caught in areas under the jurisdiction of more than 1 Council or fishery management plan, the Secretary shall require consistent reporting mechanisms across each such jurisdiction to ensure that data with respect to such species can be aggregated and compared. (4) Coordination with States The Secretary shall coordinate with State fishery managers to carry out paragraph (3).. (b) Bycatch reduction engineering program Section 316 (16 U.S.C. 1865) is amended— (1) in subsection (a)— (A) by inserting (in this section referred to as the program) after bycatch reduction program; and (B) by striking paragraphs (3) and (4) and inserting the following: (3) provide information, outreach, technical assistance, and training to Councils, tribes, and fishery participants that will encourage adoption and use of technologies and methods developed under the program; and (4) provide for routine consultation with the Councils to maximize opportunities to incorporate results of the program in Council actions and provide incentives for adoption of technologies and methods developed under the program in fishery management plans, actions, and other measures developed by the Councils or the Secretary.; and (2) in subsection (d)— (A) by striking transmit an annual report and inserting, not less frequently than once every 3 years, transmit a report; (B) in paragraph (2), by striking and at the end; (C) in paragraph (3), by striking the period at the end and inserting; and; and (D) by adding at the end the following: (4) includes a description of each bycatch reduction technology and method developed, tested, or supported by the program, and a summary of how each such technology and method have been implemented into fishery management, or an explanation for why each such technology and method has not been implemented..