Department of Commerce National Oceanic and Atmospheric Administration

Monday, December 15, 2008

Part III

15 CFR Part 902 50 CFR Parts 679 and 680 Pacific Halibut Fisheries; Bering Sea and Aleutian Islands King and Tanner Crab Fisheries; Groundfish Fisheries of the Exclusive Economic Zone Off Alaska; Individual Fishing Quota Program; Western Alaska Community Development Quota Program; Recordkeeping and Reporting; Permits; Rule

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00001 Fmt 4717 Sfmt 4717 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76136 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

DEPARTMENT OF COMMERCE mail to [email protected], containing nine comments on the or fax to 202–395–7285. original proposed rule. Responses to all National Oceanic and Atmospheric FOR FURTHER INFORMATION CONTACT: nine comments were provided in the Administration Patsy A. Bearden, 907–586–7008. supplemental proposed rule. NMFS SUPPLEMENTARY INFORMATION: NMFS agreed with five of these comments and 15 CFR Part 902 manages the U.S. groundfish fisheries of made the suggested changes in the the exclusive economic zone (EEZ) off supplemental proposed rule. The 50 CFR Parts 679 and 680 Alaska under the Fishery Management supplemental proposed rule’s comment period ended October 24, 2008. NMFS [Docket No. 080302360–7686–03] Plan for Groundfish of the Gulf of Alaska and the Fishery Management received one comment by email which is summarized under ‘‘Response to RIN 0648–AT91 Plan for Groundfish of the Bering Sea and Aleutian Islands Management Area. Comments.’’ Pacific Halibut Fisheries; Bering Sea With Federal oversight, the State of In summary, this final rule: and Aleutian Islands King and Tanner Alaska (State) manages the commercial • Institutes the Interagency Electronic Crab Fisheries; Groundfish Fisheries king crab and Tanner crab fisheries Reporting System (IERS) and its data of the Exclusive Economic Zone Off under the Fishery Management Plan for entry component, eLandings. eLandings Alaska; Individual Fishing Quota Bering Sea/Aleutian Islands King and replaces the current Shoreside Processor Program; Western Alaska Community Tanner Crabs and the commercial Electronic Logbook Report (SPELR) for Development Quota Program; scallop fishery under the Fishery entering groundfish catch information Recordkeeping and Reporting; Permits Management Plan for the Scallop and Crab Rationalization Program (CR) Fishery off Alaska. The fishery crab information. The use of eLandings AGENCY: National Marine Fisheries management plans were prepared by the removes and replaces the use of the Service (NMFS), National Oceanic and North Pacific Fishery Management shoreside processor daily cumulative Atmospheric Administration (NOAA), Council and approved by the Secretary production logbook (DCPL), weekly Commerce. of Commerce under authority of the production reports, daily production ACTION: Final rule. Magnuson–Stevens Fishery reports, and aggregated mothership fish Conservation and Management Act, 16 tickets. The operators of catcher/ SUMMARY: NMFS issues a final rule that U.S.C. 1801 et seq. The FMPs are processor vessels and motherships will implements new recordkeeping and implemented by regulations at 50 CFR be required to use a combination of reporting requirements; a new electronic parts 679 and 680. General provisions eLandings and the appropriate DCPL to groundfish catch reporting system, the governing fishing by U.S. vessels in record fishery information; Interagency Electronic Reporting accordance with the FMPs appear at • System, and its data entry component, Allows for the future use of subpart H of 50 CFR part 600. eLandings; the integration of eLandings electronic logbooks (ELBs) by operators Management of the Pacific halibut with existing logbook requirements and of catcher vessels, catcher/processors, fisheries in and off Alaska is governed future electronic logbooks; a variety of and motherships to replace the daily by an international agreement, the fisheries permits provisions and fishing logbook (DFL) and the DCPL ‘‘Convention Between the United States revisions to regulations governing the when used with eLandings. Equipment of America and Canada for the Bering Sea and Aleutian Islands and operational requirements in Preservation of the Halibut Fishery of Management Area Crab Rationalization conjunction with the new ELBs are the Northern Pacific Ocean and Bering Program, including fee calculations; a updated to provide the process and Sea,’’ which was signed at Ottawa, revision to a Sitka Pinnacles Marine criteria by which a private-sector vendor Canada, on March 2, 1953, and was Reserve closure provision; and a could submit ELB software programs for amended by the ‘‘Protocol Amending revision to a groundfish observer approval by NMFS Alaska Region; the Convention,’’ signed at Washington, provision regarding at–sea vessel-to- • Reorganizes IFQ crab landing report D.C., March 29, 1979. The Convention is vessel transfers. This action is intended regulations by removing them from 50 implemented in the United States by the to promote the goals and objectives of CFR part 680 and incorporating them Northern Pacific Halibut Act of 1982 the Magnuson–Stevens Fishery into eLandings regulations at 50 CFR (Halibut Act). Conservation and Management Act part 679, so that all regulations (Magnuson–Stevens Act) and other Background and Need for Action pertaining to eLandings will be found in applicable law. one set of regulations; Refer to the proposed rule preambles • DATES: Effective January 14, 2009. for further description and detail. The Adds a requirement for Registered ADDRESSES: Copies of the Categorical background and need for this action Crab Receivers to submit an annual Crab Exclusion (CE), Regulatory Impact were described in detail in the preamble Rationalization Program Registered Crab Review (RIR), and Final Regulatory to the original proposed rule published Receiver Ex–vessel Volume and Value Flexibility Analysis (FRFA) prepared for in the Federal Register on June 29, 2007 Report; this action may be obtained from the (72 FR 35748) and in a supplemental • Revises regulations that pertain to NMFS Alaska Region, P.O. Box 21668, proposed rule published on September permits in the fisheries off Alaska. Most Juneau, AK 99802, or by calling the 24, 2008 (73 FR 55368) and are not of the changes are technical or Alaska Region, NMFS, at 907–586–7228, repeated here. The supplemental administrative in nature, e.g., or from the NMFS Alaska Region proposed rule explains the clarification of existing regulations on website at http:// reorganization of materials within the how to amend or surrender a permit, alaskafisheries.noaa.gov. current recordkeeping and reporting and do not change existing Written comments regarding the (R&R) regulatory text to integrate requirements; burden-hour estimates or other aspects electronic and non–electronic • Clarifies vessel restrictions in the of the collection–of–information requirements. The original proposed Sitka Pinnacles Marine Reserve and requirements contained in this final rule rule’s comment period ended July 30, how those restrictions apply to halibut may be submitted to NMFS and by e– 2007. NMFS received two emails and sablefish IFQ permit holders;

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00002 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76137

• Revises requirements regarding at– for ‘‘checked–in’’ in the two places they purchases instead of as payment and sea transfer of an observer to enhance appear in § 679.5(e)(9)(ii) and (e)(10)(iv). value information. Finally, paragraph safety; and This final rule corrects a mistaken (m)(4) is revised in the final rule to • Technical revisions to regulations to cross reference in § 679.40(h)(3)(i), correct a website address that has been correct cross–references and other which are regulations describing changed since publication of the regulatory text. Miscellaneous revisions sablefish and halibut offload proposed rules. also include removal of outdated text obligations. The supplemental proposed and codifying existing reporting rule incorrectly cited to Classification practices for catch weighing and vessel § 679.5(e)(8)(i)(K), which describes the The Administrator, Alaska Region, monitoring system requirements. obligation to record discard or NMFS determined that this final rule is disposition information, which is Response to Comments necessary for the conservation and unrelated to offloads. The final rule management of the groundfish fisheries, Comment 1: The data entry time correctly references and that it is consistent with the limits for trawl and longline catcher/ § 679.50(e)(7)(i)(E)(6), which describes Magnuson–Stevens Act and other processors, the provision that requires entry of delivery information. applicable laws. submission ‘‘by noon each day to record Other revisions are made by this final the previous day’s discard and rule to ensure that electronic data Regulations governing the U.S. disposition information,’’ is submittal procedures are accurately and fisheries for Pacific halibut are unworkable. An example of how this completely described. These revisions developed by the International Pacific reporting deadline is a problem is when are as follows: Halibut Commission (IPHC), the Pacific a tow or set is retrieved just before eLandings relies on computers. The Fishery Management Council, the North midnight. An observer cannot start supplemental proposed rule, under Pacific Fishery Management Council monitoring and sampling a tow until it § 679.5(e), specified procedures for (Council), and the Secretary of is being processed, and in some cases an submitting information if a user’s Commerce. Section 5 of the Northern observer’s work shift may end in the computer fails. The final rule clarifies Pacific Halibut Act of 1982, 16 U.S.C. morning. This means that the vessel that if a hardware, software, or Internet 773c (Halibut Act) allows the Regional crew may not know about discard and failure occurs, these procedures should Council having authority for a particular bycatch estimates until the afternoon of be used. When a user is reporting on geographical area to develop regulations the day after the previous day’s tow has groundfish other than sablefish, the user governing the allocation and catch of been retrieved. We request the time must report the information as ‘‘non– halibut in U.S. Convention waters as limit for when data is entered in IFQ groundfish’’ in paragraph long as those regulations do not conflict eLandings or the DCPL be changed from 679.5(e)(1)(ii). with IPHC regulations. The final rule is ‘‘by noon each day to record the The final rule also removes a sentence consistent with the Council’s authority previous day’s discard and disposition in paragraph 679.5(e)(1)(ii) that stated to allocate, monitor, and manage halibut information’’ to ‘‘by midnight each day ‘‘A User who for any reason is unable catches among fishery participants in to record the previous day’s discard and to properly submit a landing report or the waters in and off Alaska. disposition information.’’ production report through eLandings This final rule has been determined to Response: NMFS agrees with this must record the information in the be not significant for the purposes of comment. NMFS understands the DCPL until network connections are Executive Order 12866. impracticability of submitting restored.’’ This sentence is NMFS is not aware of any other information prematurely and that time inappropriate because NMFS has Federal rules that would duplicate, limits must correspond with fishing determined it is unnecessary to specify overlap, or conflict with this action. operations. Therefore, NMFS revises by regulation where a user records regulations at § 679.5(c)(3) and (c)(4) for temporary information. The final rule Final Regulatory Flexibility Analysis trawl, longline, or pot catcher/ also adds ‘‘other NMFS–approved (FRFA) processors to change the time limit for software’’ to paragraphs 679.5(e)(1)(i) data entry in eLandings or the DCPL and (e)(1)(ii) because in the future, A Final Regulatory Flexibility from ‘‘by noon each day to record the NMFS may approve additional software Analysis (FRFA) was prepared for this previous day’s discard and disposition programs that will work as well as the rule as required by section 604 of the information’’ to ‘‘by midnight each day eLandings system. Regulatory Flexibility Act (RFA). The to record the previous day’s discard and The final rule, in Table 2b to part 679, FRFA incorporates the IRFA and a disposition information.’’ corrects the mis–spelled Latin term for summary of the analyses completed to red king crab and removes the check support the action; no comments were Changes from the Supplemental marks for three crab species that received on the IRFA. Copies of the Proposed Rule incorrectly indicated that the crab FRFA prepared for this final rule are Since publication of the proposed species are Crab Rationalization (CR) available from NMFS (see ADDRESSES). rules, NMFS published a final rule on crab. The complete list of CR crab may A summary of the FRFA follows. September 16, 2008 (73 FR 53390) that be viewed at Table 1 to part 680. Reason and Justification for the Rule revised the definition for an active The final rule reorganizes certain period for catcher/processors, requirements for the Registered Crab The FRFA describes in detail the motherships, shoreside processors, and Receiver (RCR) Ex–vessel Volume and objectives and legal basis for the rule, SFPs and eliminated the check–in/ Value Report at § 680.5(m). Since the and characterizes the small and non– check–out report submittal requirement report must be filed electronically, the small regulated entities that participate for motherships and catcher/processors final rule deletes the requirement for a in the fishery. A description of the that have onboard an operating vessel paper report. The final rule reorganizes action, the reasons why it is being monitoring system. To ensure regulatory paragraphs (m)(iii)(B) and (C) to include considered, and a statement of the consistency and accuracy with the retro payments, e.g., payments for crab objectives and legal basis for this action September 16, 2008, final rule, NMFS is made subsequent to the original are contained earlier in the preamble substituting the words ‘‘when active’’ payment, as part of the value of crab and are not repeated here.

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00003 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76138 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

Number of Small Entities to Which the outside of Alaska, or in non–fishing Electronic Logbooks (ELBs) Final Rule Would Apply activities. Finally, estimates do not take NMFS will provide the process and For purposes of a FRFA, the Small into account potential affiliations among criteria by which a private-sector Business Administration (SBA) has entities. software vendor could obtain approval established that a business involved in Cooperative membership and joint for ELB software in the Alaska Region fish harvesting is a small business if it venture affiliations are common among groundfish fisheries. is independently owned and operated, Alaskan fishing firms. In the absence of NMFS will provide an option for not dominant in its field of operation detailed information on ownership and operators of trawl catcher vessels and (including its affiliates), and if it has affiliations, and on revenue from fishing catcher/processors, longline or pot combined annual gross receipts not in or other activities outside of Alaska, catcher vessels and catcher/processors, excess of $4.0 million for all its NMFS has chosen to make estimates and motherships operating in the GOA affiliated operations worldwide. A that are conservative, to avoid and the BSAI in the EEZ off the coast seafood processor is a small business if undercounting the number of small of Alaska to substitute an ELB for the it is independently owned and operated, entities. DFL or DCPL that is currently required. not dominant in its field of operation, The FRFA evaluates the following This action will allow ELBs for and employs 500 or fewer persons on a regulatory amendments: voluntary use by fishery participants to full–time, part–time, temporary, or other 1. Provide an option for operators of replace the DFL for trawl gear catcher basis, at all its affiliated operations trawl catcher vessels and catcher/ vessels and longline or pot gear catcher worldwide. processors, longline or pot catcher vessels. ELBs will also be allowed for Because the SBA does not have a size vessels and catcher/processors, and use by fishery participants to replace the criterion for businesses that are motherships operating in the GOA and DCPL used by trawl gear catcher/ involved in both the harvesting and the BSAI in the EEZ off the coast of processors, longline or pot gear catcher/ processing of seafood products, NMFS Alaska to substitute an ELB for the DFL processors, and motherships to has in the past applied and continues to or DCPL that is currently required. voluntarily fulfill daily catch apply SBA’s fish harvesting criterion for 2. Provide the process and criteria by recordkeeping and reporting these businesses because catcher/ which a private software vendor could requirements. processors are first and foremost fish get ELB software approved for use in the The participants associated with this harvesting businesses. Therefore, a Alaska Region groundfish fisheries. aspect of the action include an business involved in both the harvesting 3. Implement regulations for the estimated 771 small catcher vessels, 11 and processing of seafood products is a eLandings data entry component of small catcher/processors, and no small small business if it meets the $4.0 IERS to be used for reporting motherships. The catcher vessel and million criterion for fish harvesting commercial fishery landings and catcher/processor estimates may be operations. NMFS currently is production data and allow fishery high, because they do not take account reviewing its small entity size participants to use the Internet to enter of affiliations among entities. classification for all catcher/processors data only once for subsequent NMFS considered two alternatives for in the United States. However, until distribution to the Alaska Department of implementation of the ELBs: the no– new guidance is adopted, NMFS will Fish and Game (ADF&G), the action (or status quo) and action continue to use the annual receipts International Pacific Halibut alternatives. The action alternative standard for catcher/processors. NMFS Commission (IPHC), and NMFS, as allows participants to voluntarily use an plans to issue new guidance in the near appropriate. ELB instead of a DFL or DCPL, but does future. 4. Reorganize regulations for logbooks not require firms to incur additional The FRFA contains a description and to provide complete information for costs, because all processors estimate of the number of small entities each logbook in its own section in order participating in Federal fisheries have to which the rule would apply. As to make the regulations more accessible access to a computer. The no–action required by the RFA, NMFS has and easier to use. alternative was considered, but rejected, estimated the numbers of small entities 5. Provide uniform language and because it did not meet the action that may be directly regulated by this revise permit–related regulations objective of creating a better regulatory action. Counts of small catcher vessel governing fishing activities in fisheries environment for the introduction and and catcher/processor entities are based off the coast of Alaska. The minor use of ELB software for compliance with on 2006 revenue estimates from the revisions improve enforcement of the NMFS’ reporting requirements. Alaska Fisheries Science Center. Counts regulations at 50 CFR part 679, by NMFS interacted with the fishing of shoreside processors and stationary revising text, where necessary, such that industry on the use of ELBs during a floating processors (SFPs) are based on the regulations are specific, especially pilot project described in the RIR/IRFA 2006 information on plants and plant regarding permits and permit–related wherein a trawl gear ELB created by a ownership from the NMFS Alaska issues. private vendor was used by catcher Region. Counts of other more 6. Revise 50 CFR part 680 by vessels. An early version of this analysis specialized categories of small entities removing IFQ crab landing report included a provision requiring that are explained when they occur below. regulations for incorporation into the fishing operations using the ELB In general, the estimates of small entity description of IERS at § 679.5 IERS and software file a report with NMFS within numbers described in the following by adding a requirement for a CR 24 hours of delivering their product. paragraphs are believed to be high for Registered Crab Receiver Ex–vessel This provision was eliminated from the several reasons. Each vessel or Volume and Value Report. alternatives following industry processing plant is treated as a separate 7. Revise a groundfish observer consultations during the preparation of entity; however, this does not consider provision regarding at–sea vessel-to- the IRFA. The provision was expected that a firm may own multiple vessels or vessel transfers. to impose an undue burden on plants. Moreover, revenue estimates do 8. Make miscellaneous revisions to operations that were using the software not take into account the revenues that fishing regulations at 50 CFR parts 679 voluntarily and perhaps slow its an entity may have earned in waters and 680. adoption rate. An examination of

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00004 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76139

existing response rates indicated that The preferred alternative requires Permits about 32 percent of these reports have processors to use IERS and eLandings to NMFS is unifying the language and been received by NMFS within 24 hours report data from Federal fisheries, but revising permit–related regulations of the landing, and about 73 percent only imposes small additional costs. governing fishing activities in fisheries have been received within 48 hours of IERS is a joint project of ADF&G, IPHC, off the coast of Alaska. These minor the landing. The action alternative and NMFS. If NMFS adopted an revisions will improve enforcement of relaxes a constraint on the public, and alternative system, confusion would the regulations at 50 CFR part 679 by may reduce data entry costs relative to result for the fishing industry and clarifying and simplifying text, the DFL and DCPL. industry costs would be increased. especially regarding permit–related Interagency Electronic Reporting System Additional alternatives in this instance issues. NMFS estimates that 771 small (IERS) would compromise our ability to meet catcher vessels, 11 small catcher/ the objectives of the action. Because the processors, 80 small shoreside With this final rule, NMFS costs of this action are minor, it is implements regulations for the processors, five SFPs, and six small difficult to identify additional CDQ groups are directly regulated by eLandings data entry component of alternatives with significant cost IERS to be used for reporting this action. savings. commercial fishery landings and Six CDQ groups, representing 65 production data and allow fishery Regulatory text reorganization Western Alaska communities, currently participants to use the Internet to enter participate in the CDQ Program. Each is data only once for subsequent NMFS reorganizes and revises organized as a not–for–profit entity, and distribution to the ADF&G, the IPHC, § 679.5(a) and (c), such that each of the none is dominant in its field. and NMFS, as appropriate. six groundfish logbooks is described Consequently, each is a small entity NMFS estimates that this action will clearly and completely in a separate under the RFA. Several CDQ groups directly regulate 11 small catcher/ section of regulatory text. This action own, in whole or in part, and operate processors, 80 small shoreside also makes the regulations easier for the vessels participating in the CDQ processors, five small SFPs, no small public to use. Regulations for processor fisheries. Because CDQ groups must motherships, and 184 small Registered forms also are revised and reorganized obtain permits for their vessels, the six Buyers. Under this action, these entities in this rule. Prior to this final rule, these CDQ groups also will be directly will be required to report electronically regulations were arranged into tables by regulated by this rule. using the IERS software. data element relating to multiple NMFS considered two alternatives for The Registered Buyer estimates were logbooks and forms. The reader had to the permit–related revisions: the status prepared as follows. There are 206 IFQ consult several places in the regulations quo and action alternatives. The status– Registered Buyers expected to use IERS to find complete requirements for any quo alternative would maintain the to record their halibut IFQ and halibut given logbook or form. This action inconsistency of regulatory language CDQ deliveries under provisions of this consolidates all of the requirements for regarding permit–related issues, for action. An examination of the names of each form and logbook into individual example, by maintaining the term the Registered Buyers suggests that at sections in § 679.5. ‘‘federally regulated’’ and by not least 22 are large entities under the replacing it with the specific permit that The small entities directly regulated Small Business Administration (SBA) relates to the paragraph. This would by this action include 80 shoreside criteria (i.e., processors subject to the maintain the inconsistency in processors, five SFPs, 11 catcher/ 500 employee SBA criterion). The determination of which permit processors, no motherships, and 771 remaining Registered Buyers appear to authorizes which activity. Under the catcher vessels. be small shoreside firms or fishing action alternative, NMFS ‘‘tightens up’’ operations. Thus, 184 Registered Buyers NMFS considered two alternatives for the regulations as they relate to permits, are estimated to be small for RFA the reorganization of regulations: the for example, regulatory text is made purposes. This is likely to be an status quo and action alternatives. specific as to whether a permit is issued overestimate of the number of small Under the status quo alternative, the to a person or to a vessel. Under the entities among the Registered Buyers regulations at § 679.5 would remain action scenario, NMFS clarifies directly regulated by adoption of the without reorganization. The regulations ambiguities in the permit–related IERS. at § 679.5 would remain arranged in regulatory text and improves NMFS considered two alternatives for tables by data element relating to enforcement of the regulations at 50 the IERS and eLandings: the status quo multiple logbooks and forms causing the CFR part 679. and action alternatives. The status quo reader to consult several places in the alternative, if retained, would not have regulations to find complete eLandings Landing Report required firms to begin using IERS for requirements for any given logbook or NMFS revises regulations at 50 CFR Federal reporting purposes. However, form. Under the regulatory scenario of part 680 by removing IFQ crab landing since State regulations will require firms the status quo alternative, participants report regulations for incorporation into to begin reporting in–state deliveries of would likely face increased R&R the § 679.5(e) eLandings regulations. harvests with the IERS system, retention regulatory uncertainty and a loss of The eLandings landing report originally of the status quo alternative would be of efficiency. Under the action alternative, was created for CR crab, but will be no advantage to small entities. Indeed, NMFS will reorganize and revise used for reporting groundfish, IFQ these small entities could be in the regulations at § 679.5 such that each of halibut, CDQ halibut, and IFQ sablefish position of having to conform to two the six groundfish logbooks is described as well. separate reporting standards. Moreover, in regulatory text separately, NMFS considered two alternatives for a significant proportion of the harvest completely, and clearly. Under the the eLandings regulatory revisions: the from Federal waters is delivered to regulatory scenario of the action status quo and action alternatives. onshore or inshore processors, who alternative, participants would enjoy Under the status quo scenario, the would be using the IERS to input these increased R&R regulatory certainty and regulations for use of eLandings for the records. increased efficiency. CR fisheries would remain at § 680.5

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00005 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76140 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

and the regulations for use of eLandings cost recovery fees will be used to one observer to meet observer coverage for other fisheries would be in support management of the CR Program. requirements on these vessels. This § 679.5(e). This would duplicate two An additional effect will be the removal revision would require an observer to be sets of regulations and introduce of a requirement for an RCR who transferred only at the dock, resulting in confusion. receives a landing of CR crab harvested increased costs for the company, Under the action alternative, NMFS under the IFQ, the CDQ, or Adak because vessels would have to return to removes regulatory text from § 680.5(b), community allocation programs to the dock to pick up or drop off an (c), and (d) that describe the use of submit for each landing the price per observer. This alternative was rejected eLandings for CR crab and integrates pound. Instead, each RCR will be for further analysis because the that text into regulations at § 679.5(e). required to submit a CR RCR Ex–vessel improvement in observer safety This change allows all related Volume and Value Report near the end appeared to come at a disproportionate information for the eLandings landing of the crab fishing year. In addition, the cost to fishing operations. report to be found in one section for requirement to report through Miscellaneous Revisions to Fishing groundfish, CR crab, IFQ halibut, IFQ eLandings the price paid for crab when Regulations at 50 CFR parts 679 and sablefish, and CDQ halibut. landed will become optional. 680 CR Registered Crab Receiver Ex–vessel Groundfish Observer Provision NMFS amends regulations in Parts Volume and Value Report Regarding At–sea Vessel-to-vessel 679 and 680 to improve clarity and NMFS is adding a new form, the CR Transfers efficiency. The small entities directly Registered Crab Receiver (RCR) Ex– The Fisheries Monitoring and regulated by this final rule include 80 vessel Volume and Value Report, to be Analysis Division (FMA) monitors shoreside processors, 5 SFPs, 11 submitted by participants near the end groundfish fishing activities in the EEZ catcher/processors, no motherships, and of the crab fishing year. This report is off Alaska and conducts research 771 catcher vessels. similar to a report required by associated with sampling commercial NMFS considered two alternatives for regulations implementing the NMFS fishery catches, estimation of catch and the miscellaneous regulatory revisions: Alaska Region IFQ Program for Pacific bycatch mortality, and analysis of the status quo and action alternatives. halibut and sablefish. The regulations fishery–dependent data. As part of the Under the status quo alternative the for the form will be described at FMA’s North Pacific Observer Program, regulatory text would not be changed. § 680.5(m). The small entities directly approximately 400 fishery observers Under the action alternative, NMFS regulated by this action are spend up to 90 consecutive days each amends regulations in Part 679 and Part approximately 30 RCRs required to year at sea or at processing plants 680, by adding and revising definitions, submit an annual CR RCR Ex–vessel collecting data for management of the revising text to clarify a Sitka Pinnacles Volume and Value Report. Alaskan groundfish fisheries. On Marine Reserve closure provision, NMFS considered two alternatives for occasion crab fisherman must transfer adding or correcting cross references, the addition of this form: the status quo an observer at sea from one vessel to removing obsolete text, adding new text, and action alternatives. Under the status another. codifying certain existing practices, and quo scenario, the requirement to report The small entities directly regulated revising figures and tables to Part 679. through eLandings the price paid for by this action include no motherships, These changes will facilitate crab during landing would remain 11 catcher/processors, and 771 catcher management of the fisheries and mandatory. This would mean that the vessels. enforcement efforts and promote crab price would be inaccurate, because NMFS considered three alternatives compliance with the regulations. the price at the time of landing does not for the observer at–sea transfer The preferred action alternative will include post–delivery or end–of–season revisions: the status quo and two action have no known adverse impacts on adjustments. An inaccurate report of alternatives. Under the status quo small entities. The status quo alternative crab value would then be used to assess alternative, the regulatory text would was rejected because it did not meet the fees for participants in the CR crab not be changed. The no–action action objective of creating a better fisheries, required by the Magnuson– alternative was rejected because it did regulatory environment. Stevens Fishery Conservation and not meet the action objective of creating The regulations in this final rule Management Act (Section 304(d)(2)(B)). a safe transfer environment for a appear to impose no adverse economic Inaccurate fees could result in groundfish observer. impacts on directly regulated small insufficient funds to manage the CR Under the preferred action alternative, entities. Therefore no steps were needed Program. NMFS revises a groundfish observer to minimize the effects of this regulatory The action alternative adds the new provision regarding at–sea vessel-to- action on small entities. form to collect crab price information vessel transfers by removing ‘‘via small In the various items considered in this from CR RCRs. The form collects boat or raft’’ from the regulations at analysis, the preferred alternative was information used to assess fees on an § 679.50(g)(1)(ix)(A). This revision will chosen rather than selecting the status annual basis, which is a statutory improve safety for observers undergoing quo alternative. The preferred requirement. NMFS considered but a transfer at sea because the regulatory alternative in every case supported the rejected alternatives (options) of more text now states that all at–sea transfers primary objective of this action which is frequent or less frequent collection of of an observer be conducted during to improve the methods and procedures the price information. NMFS Restricted daylight hours, under safe conditions, of recordkeeping and reporting for the Access Management Program (RAM) and with the agreement of the observers fishery programs of NMFS Alaska will collect the price information to involved. Region through expansion of electronic establish a ‘‘standard’’ ex–vessel price Under the second action alternative, reporting methods and by simplifying for CR crab. The standard price will be NMFS will prohibit the transfer of an regulations. used to estimate the cost recovery fees observer at sea. Most of the at–sea Use of electronic recordkeeping will due from processors and harvesters; the transfers are done by companies that allow the public to more easily record participants may not participate in the own two or more vessels with less than daily information and retrieve daily CR fisheries if fees are not paid. The 100 percent observer coverage and use information and will increase the

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00006 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76141

accuracy of information collected and for catcher/processor longline and pot List of Subjects in 15 CFR part 902 summarized. In addition, this initiation gear DCPL or ELB; 30 minutes for of electronic recordkeeping is the first catcher/processor trawl gear DCPL or Reporting and recordkeeping step to interface with onboard ELB; 23 minutes for buying station requirements. electronics to collect certain information report; 7 minutes for check–in/check– List of Subjects in 50 CFR parts 679 and directly (for example location and out report, mothership or catcher/ 680 direction information from a global processor; 8 minutes for check–in/ positioning system). Electronic check–out report, shoreside processor. Alaska, Fisheries, Reporting and recordkeeping also creates a wide range The weekly production report, recordkeeping requirements. of potential reports to allow the operator estimated at 17 minutes; shoreside Dated: December 2, 2008. to analyze his or her fishing activity. processor DCPL, estimated at 31 Samuel D. Rauch III, eLandings or other NMFS–approved minutes; and mothership consolidated Deputy Assistant Administrator for software allows processors and others to ADF&G fish tickets, estimated at 35 Regulatory Programs, National Marine provide commercial harvest and minutes, are removed with this final Fisheries Service. production information of groundfish, rule. ■ halibut, and crab to NMFS, IPHC, and For the reasons set out in the OMB Control Number 0648–0272 ADF&G. Using eLandings removes preamble, NMFS amends 15 CFR reporting duplications, and once chapter IX and 50 CFR chapter VI as Public reporting burden for IFQ follows: implementation is complete, eLandings landing reports is estimated to average makes recordkeeping and reporting 18 minutes per response. TITLE 15—COMMERCE AND FOREIGN simpler. Additional benefits of the TRADE eLandings system include: OMB Control Number 0648–0334 • CHAPTER IX—NATIONAL OCEANIC AND Immediate verification of permits Public reporting burden is estimated ATMOSPHERIC ADMINISTRATION, and vessel identification; DEPARTMENT OF COMMERCE • to average per response: one hour for Timely catch reports for groundfish and crab LLP transfer management agency use; application and one hour for scallop PART 902—NOAA INFORMATION • Options for processors to import or LLP transfer application. COLLECTION REQUIREMENTS UNDER export catch and production THE PAPERWORK REDUCTION ACT: information; and OMB Control Number 0648–0515 OMB CONTROL NUMBERS • Significant reduction in data entry by management agencies and Public reporting burden is estimated ■ 1. The authority citation for part 902 processors. to average per response: 15 minutes for continues to read as follows: IERS application processor registration; Small Entity Compliance Guide 35 minutes for eLandings landing Authority: 44 U.S.C. 3501 et seq. The preamble to this final rule and report; 35 minutes for manual landing ■ 2. In § 902.1, in the table in paragraph particularly the summary of the FRFA report; and 15 minutes for catcher/ (b), under the entry ‘‘50 CFR’’: serve as the small entity compliance processor or mothership eLandings A. Remove entries for ‘‘679.5(b), (c), guide. This action does not require any production report. (d), (g), (h), (i), (j), (k) and (m)’’; additional compliance from small OMB Control Number 0648–0570 ‘‘679.5(e), (f), and (o)’’; ‘‘679.5(l)(1), entities that is not described in this final (l)(2), (l)(3), and (l)(5)’’; ‘‘679.5(l)(3)(i), rule. Copies of this final rule are Public reporting burden is estimated (l)(4)’’; ‘‘679.24(e)’’; ‘‘679.28(b) and (d)’’; available from NMFS (see ADDRESSES) to average per response: 20 minutes for ‘‘679.28(f)’’; ‘‘679.32(c)’’; ‘‘679.61(c) and and at the NMFS website at http:// crab catcher/processor offload report, 40 (f)’’; ‘‘679.61(d) and (e)’’; ‘‘679.62(b)(3) alaskafisheries.noaa.gov. hours for eligible crab community and (c)’’; ‘‘679.63(a)(2)’’; ‘‘680.5’’; organization annual report; and 1 hour ‘‘680.23(e), (f), (g), and (h)’’; ‘‘680.44(a), Paperwork Reduction Act Collections for CR Registered Crab Receiver Ex– (b), (c), (d), (e)’’; and ‘‘680.44(f)’’. of Information vessel Volume and Value Report. B. Add entries in alphanumeric order This final rule contains collection–of– These estimates include the time for for ‘‘679.5(b), (h), and (k)’’; ‘‘679.5(c)’’; information requirements that are reviewing instructions, searching ‘‘679.5(d)’’; ‘‘679.5(e) and (f)’’; subject to review and approval by the existing data sources, gathering and ‘‘679.5(g)’’; ‘‘679.5(l)(1) through (l)(5)’’; Office of Management and Budget maintaining the data needed, and ‘‘679.5(o)’’; ‘‘679.27(j)(5)’’; ‘‘679.28(a)’’; (OMB) under the Paperwork Reduction completing and reviewing the collection ‘‘679.28(b), (c), (d), and (e)’’; Act (PRA) and which have been of information. ‘‘679.28(h)’’; ‘‘679.32(c) and (e)’’; approved by OMB. The collections are Send comments regarding this burden ‘‘679.61(c), (d), (e), and (f)’’; ‘‘679.62’’; listed below by OMB control number. estimate, or any other aspect of this data ‘‘679.63’’; ‘‘680.5(a) and (h) through (l)’’; OMB Control Number 0648–0206 collection, including suggestions for ‘‘680.5(b)’’; ‘‘680.5(e) and (f)’’; ‘‘680.5(g)’’; ‘‘680.5(m)’’; ‘‘680.23(e), (f), Public reporting burden is estimated reducing the burden, to NMFS (see and (g)’’; and ‘‘680.44’’. to average per response: 21 minutes for ADDRESSES) and by e–mail to Federal fisheries permit and 21 minutes [email protected], or fax to C. Revise entries for ‘‘679.5(r)’’; for Federal processor permit. 202–395–7285. ‘‘679.5(s)’’; ‘‘679.32(d)’’; ‘‘679.32(f)’’; Notwithstanding any other provision and ‘‘679.43’’. OMB Control Number 0648–0213 of the law, no person is required to The additions and revisions read as Public reporting burden is estimated respond to, nor shall any person be follows: to average per response: 28 minutes for subject to a penalty for failure to comply catcher vessel longline and pot gear DFL with, a collection of information subject § 902.1 OMB control numbers assigned or ELB; 18 minutes for catcher vessel to the requirements of the PRA, unless pursuant to the Paperwork Reduction Act. trawl DFL or ELB; 31 minutes for that collection of information displays a * * * * * mothership DCPL or ELB; 41 minutes currently valid OMB control number. (b) * * *

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00007 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76142 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

Active/inactive periods means for CFR part or section Current OMB control CFR part or section Current OMB control where the informa- number (all numbers where the informa- number (all numbers longline or pot gear catcher vessel, see tion collection re- begin with 0648-) tion collection re- begin with 0648-) § 679.5(c)(3)(iv)(A)(1); for longline or quirement is located quirement is located pot gear catcher/processor, see * * * * * * * 679.62 -0393 § 679.5(c)(3)(iv)(B)(1); for trawl gear catcher vessel, see 50 CFR 679.63 -0213 and -0330 § 679.5(c)(4)(iv)(A)(1); for trawl gear catcher/processor, see * * * * * * * * * * * * * * § 679.5(c)(4)(iv)(B)(1); for shoreside processor or SFP, see § 679.5(c)(5)(ii); 680.5(a) and (h) -0213 679.5(b), (h), and -0213 for mothership, see § 679.5(c)(6)(iv). (k) through (l) * * * * * 679.5(c) -0213, -0272, -0330, 680.5(b) -0515 Associated processor means: -0513, and -0515 680.5(e) and (f) -0570 (1) Relationship with a buying station. A mothership or catcher/processor 679.5(d) -0213, -0272, and -0513 680.5(g) -0514 issued an FFP, or a shoreside processor or SFP issued an FPP, with a contractual 679.5(e) and (f) -0213, -0272, -0330, * * * * * * * relationship with a buying station to -0401, -0513, and conduct groundfish buying station -0515 680.5(m) -0514 activities for that processor. (2) Relationship with a custom 679.5(g) -0213, -0272, and * * * * * * * -0330 processor. A mothership or catcher/ 680.23(e), (f), and -0330 processor issued an FFP or a shoreside 679.5(l)(1) through -0272 (g) processor or SFP issued an FPP, with a (l)(5) contractual relationship with a custom * * * * * * * processor to process groundfish on its * * * * * * * 680.44 -0514 behalf. 679.5(o) -0401 At–sea operation means, for purposes * * * * * * * of eLandings, a catcher/processor or * * * * * * * mothership that is receiving and/or TITLE 50—WILDLIFE AND FISHERIES processing fish in State waters and/or in 679.5(r) -0213, -0445, and CHAPTER VI—FISHERY CONSERVATION waters of the EEZ off the coast of -0545 AND MANAGEMENT, NATIONAL OCEANIC Alaska. AND ATMOSPHERIC ADMINISTRATION, * * * * * 679.5(s) -0213, -0445, and DEPARTMENT OF COMMERCE -0565 eLandings means the Internet data PART 679—FISHERIES OF THE entry system or desktop client * * * * * * * EXCLUSIVE ECONOMIC ZONE OFF components of the Interagency ALASKA Electronic Reporting System (IERS) for 679.27(j)(5) -0213, -0330, and reporting commercial fishery landings -0565 ■ 3. The authority citation for part 679 and production from waters off Alaska. 679.28(a) -0213 and -0330 is revised to read as follows: * * * * * Authority: 16 U.S.C. 773 et seq.; 1801 et Gear deployment (or to set gear) (see 679.28(b), (c), (d), -0330 seq.; 3631 et seq.; Pub. L. 108–447. § 679.5(c)(3)(vi)(B) for longline and pot and (e) gear; see § 679.5(c)(4)(vi)(B) for trawl ■ 4. In § 679.2: gear). * * * * * * * A. Add in alphabetical order Gear retrieval (or to haul gear) (see definitions for ‘‘At–sea operation’’, 679.28(h) -0213 and -0515 § 679.5(c)(3)(vi)(C) for longline and pot ‘‘eLandings’’, ‘‘Interagency electronic gear; see § 679.5(c)(4)(vi)(C) for trawl reporting system (IERS)’’, ‘‘Maximum * * * * * * * gear). retainable amount (MRA)’’, ‘‘Non–IFQ 679.32(c) and (e) -0213 and -0269 groundfish’’, ‘‘Non–individual entity’’, * * * * * ‘‘Permit’’, ‘‘Shoreside processor Haul means the retrieval of trawl gear 679.32(d) -0213, -0269 and electronic logbook report (SPELR)’’, which results in catching fish or which -0330 ‘‘Single geographic location’’, ‘‘User’’, does not result in catching fish; a test of ‘‘User identification (UserID)’’, and trawl gear; or when non–functional gear 679.32(f) -0213, -0269, and is pulled in, even if no fish are -0272 ‘‘Week–ending date’’. B. Revise the definitions of ‘‘Active/ harvested. All hauls of any type need to * * * * * * * inactive periods’’, ‘‘Associated be recorded and numbered throughout processor’’, ‘‘Gear deployment (or to set the year, whether or not fish are caught. 679.43 -0272, -0318, -0334, gear)’’, ‘‘Gear retrieval (or to haul gear)’’, * * * * * -0398, -0401, -0545, ‘‘Haul’’, ‘‘Prohibited species catch -0565, and -0569 Interagency electronic reporting (PSC)’’, and ‘‘Tender vessel’’. system (IERS) means an interagency * * * * * * * The additions and revisions read as electronic reporting system that allows follows: fishery participants to use the Internet 679.61(c), (d), (e), -0401 or desktop client software named and (f) § 679.2 Definitions. eLandings to enter landings and * * * * * production data for appropriate

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00008 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76143

distribution to the ADF&G, IPHC, and Single geographic location (see and to provide for data security, a NMFS Alaska Region (see § 679.5(e)). § 679.4(l)(5)(iii)). separate UserID is issued to each * * * * * * * * * * individual. Maximum retainable amount (MRA) Tender vessel (see also the definition * * * * * (see § 679.20(e)). of ‘‘buying station’’ under this section) Week–ending date means the last day means a vessel that is used to transport * * * * * of the weekly reporting period which unprocessed fish or shellfish received ends on Saturday at 2400 hours, A.l.t., Non–IFQ groundfish means from another vessel to an associated groundfish, other than IFQ sablefish. except during the last week of each processor. calendar year, when it ends at 2400 Non–individual entity means a person * * * * * hours, A.l.t., December 31. who is not an individual or ‘‘natural’’ User means, for purposes of IERS and * * * * * person; it includes corporations, eLandings, an individual representative ■ partnerships, estates, trusts, joint of a Registered Buyer; a Registered Crab 5. In § 679.4: ventures, joint tenancy, and any other Receiver; a mothership or catcher/ A. Paragraph (a)(4) is removed and type of ‘‘person’’ other than a natural processor that is required to have a reserved. person. Federal Fisheries Permit (FFP) under B. Paragraphs (a)(1)(i)(A), (a)(1)(iv)(A), * * * * * § 679.4; a shoreside processor or SFP (a)(1)(iv)(B), (a)(3)(i), (a)(3)(iii), (b) Permit means documentation granting and mothership that receives groundfish heading, (b)(3), (b)(4), (b)(5) heading, permission to fish and includes from vessels issued an FFP under (b)(5)(iv), (e)(2), (e)(3), (f) heading, (f)(2), ‘‘license’’ as a type of permit. § 679.4; any shoreside processor or SFP (f)(3), (f)(4), (g)(1), (k) heading, and * * * * * that is required to have a Federal (l)(1)(iv) are revised. C. Paragraphs (a)(1)(vii)(C), (a)(1)(xiv), Prohibited species catch (PSC) means processor permit under § 679.4; and his (a)(9), (b)(5)(vi)(C), (d)(1)(iii), (d)(2)(iv), any of the species listed in Table 2b to or her designee(s). User identification (UserID), for (d)(3)(v), (k)(6)(x), (l)(1)(ii)(C), and this part. purposes of IERS and eLandings, means (l)(5)(ii) are added. * * * * * the string of letters and/or numbers that The revisions and additions read as Shoreside processor electronic identifies the individual and gives him follows: logbook report (SPELR) (discontinued, or her authorization to view and submit see definition of ‘‘eLandings’’ under this reports for specific operations or to § 679.4 Permits. section). otherwise use eLandings. To facilitate (a) * * * * * * * * the management of Users and privileges (1) * * *

Permit is in effect from issue date through the If program permit or card type is: end of . . . For more information, see . . .

(i) * * *

(A) Registered buyer Until expiration date shown on permit Paragraph (d)(3)(ii) of this section

* * * * * * *

(iv) * * *

(A) Federal fisheries Until expiration date shown on permit Paragraph (b) of this section

(B) Federal processor Until expiration date shown on permit Paragraph (f) of this section

* * * * * * *

(vii) * * *

* * * * * * *

(xiv) Crab Rationalization Program permits see § 680.4 of this chapter § 680.4 of this chapter

(A) Crab Quota Share permit Indefinite § 680.4(b) of this chapter

(B) Crab Processor Quota Share permit Indefinite § 680.4(c) of this chapter

(D) Crab Individual Processor Quota (IPQ) Specified fishing year § 680.4(e) of this chapter permit

(E) Crab IFQ hired master permit Specified fishing year § 680.4(g) of this chapter

(F) Registered Crab receiver permit Specified fishing year § 680.4(i) of this chapter

(G) Federal crab vessel permit Specified fishing year § 680.4(k) of this chapter

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00009 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76144 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

Permit is in effect from issue date through the If program permit or card type is: end of . . . For more information, see . . .

(H) Crab harvesting cooperative IFQ per- Specified fishing year § 680.21(b) of this chapter mit

* * * * * modified under § 600.735 or § 600.740 accordance with paragraph (a)(9) of this (3) * * * of this chapter. section. An IFQ hired master permit (i) A person may obtain an (ii) Surrendered permit. An FFP may be reissued to the permit holder of application for a new permit or for permit may be voluntarily surrendered record in the same fishing year in which renewal or revision of an existing permit in accordance with paragraph (a)(9) of it was surrendered. Contact NMFS/RAM for any of the permits under this section this section. An FFP may be reissued to for more information by telephone, and must submit forms to NMFS as the permit holder of record in the same locally at 907–586–7202 (Option #2) or instructed in application instructions. fishing year in which it was toll–free at 800–304–4846 (Option #2). With appropriate software, all permit surrendered. Contact NMFS/RAM by (3) * * * applications may be completed online telephone, locally at 907–586–7202 (v) A Registered Buyer permit may be and printed from the Alaska Region (Option #2) or toll–free at 800–304–4846 voluntarily surrendered in accordance website at http:// (Option #2). with paragraph (a)(9) of this section. A alaskafisheries.noaa.gov. (iii) Amended permit. An owner or Registered Buyer permit may be operator, who applied for and received reissued to the permit holder of record * * * * * an FFP, must notify NMFS of any in the same fishing year in which it was (iii) The operator, manager, Registered change in the permit information by surrendered. Contact NMFS/RAM for Buyer, or Registered Crab Receiver must submitting an FFP application found at more information by telephone, locally obtain a separate permit for each the NMFS website at http:// at 907–586–7202 (Option #2) or toll–free applicant, facility, or vessel, as alaskafisheries.noaa.gov as instructed at 800–304–4846 (Option #2). appropriate to each Federal permit in on the application form. Upon receipt * * * * * this section (§ 679.4) and retain a copy and approval of a permit amendment, (e) * * * of each permit application, whether the the Program Administrator, RAM, will (2) Halibut CDQ permit. The CDQ application is requesting an initial issue an amended FFP. group must obtain a halibut CDQ permit permit or renewing or revising an (5) Contents of an FFP application. issued by the Regional Administrator. existing permit. *** The vessel operator must have a copy of * * * * * * * * * * the halibut CDQ permit on any fishing (9) Permit surrender. The Regional (iv) Area and gear information. vessel operated by, or for, a CDQ group Administrator will recognize the Indicate the type of vessel operation. If that will have halibut CDQ onboard and voluntary surrender of a permit issued catcher/processor or catcher vessel, must make the permit available for in this section, § 679.4, if a permit may indicate only the gear types used for inspection by an authorized officer. The be surrendered and it is submitted by groundfish fishing. If the vessel is a halibut CDQ permit is non–transferable the person named on the permit, owner catcher/processor under 125 ft (18.3 m) and is issued annually until revoked, of record, or agent. Submit the original LOA that is intended to process GOA suspended, surrendered, or modified. A permit to Program Administrator, RAM inshore pollock or GOA inshore Pacific halibut CDQ permit may be voluntarily Program, P.O. Box 21668, Juneau, AK cod, mark the box for a GOA inshore surrendered in accordance with 99802, by certified mail or other method processing endorsement. paragraph (a)(9) of this section. The that provides written evidence that * * * * * halibut CDQ permit will not be reissued NMFS Alaska Region received it. The (vi) * * * in the same fishing year in which it was receiving date of signature by NMFS (C) Selections for species surrendered, but a new annual halibut staff is the date the permit was endorsements will remain valid until an CDQ permit may be issued in a surrendered. FFP is amended to remove those subsequent fishing year to the CDQ (b) Federal fisheries permit (FFP) endorsements or the permit with these group entitled to a CDQ halibut endorsements is surrendered or allocation. Contact NMFS/RAM for * * * * * revoked. more information by telephone, locally (3) Vessel operations categories. An * * * * * at 907–586–7202 (Option #2) or toll–free FFP authorizes a vessel owner to deploy (d) * * * at 800–304–4846 (Option #2). a vessel to conduct operations in the (1) * * * (3) An individual must have onboard GOA or BSAI under the following (iii) An IFQ permit may be voluntarily the vessel a legible copy of his or her categories: Catcher vessel, catcher/ surrendered in accordance with halibut CDQ hired master permit issued processor, mothership, tender vessel, or paragraph (a)(9) of this section. An by the Regional Administrator while support vessel. A vessel may not be annual IFQ permit will not be reissued harvesting and landing any CDQ operated in a category other than as in the same fishing year in which it was halibut. Each halibut CDQ hired master specified on the FFP, except that a surrendered, but a new annual IFQ permit will identify a CDQ permit catcher vessel, catcher/processor, permit may be issued to the quota share number and the individual authorized mothership, or tender vessel may be holder of record in a subsequent fishing by the CDQ group to land halibut for operated as a support vessel. year. Contact NMFS/RAM for more debit against the CDQ group’s halibut (4) Duration—(i) Length of permit information locally at 907–586–7202 CDQ. A halibut CDQ hired master effectiveness. An FFP is in effect from (Option #2) or toll–free at 800–304–4846 permit may be voluntarily surrendered the effective date through the expiration (Option #2). in accordance with paragraph (a)(9) of date, unless it is revoked, suspended, (2) * * * this section. A halibut CDQ hired master surrendered in accordance with (iv) An IFQ hired master permit may permit may be reissued to the permit paragraph (a)(9) of this section, or be voluntarily surrendered in holder of record in the same fishing year

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00010 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76145

in which it was surrendered. Contact the Regional Administrator will issue a may be voluntarily surrendered in NMFS/RAM for more information by Federal processor permit required by accordance with paragraph (a)(9) of this telephone, locally at 907–586–7202 this paragraph (f). section. A surrendered groundfish or (Option #2) or toll–free at 800–304–4846 (4) Duration—(i) Length of crab LLP license will cease to exist and (Option #2). effectiveness. An FPP is in effect from will not be subsequently reissued. * * * * * the effective date through the date of Contact NMFS/RAM for more (f) Federal processor permit (FPP) permit expiration, unless it is revoked, information by telephone, locally at * * * * * suspended, surrendered in accordance 907–586–7202 (Option #2) or toll–free at (2) Contents of an FPP application. To with paragraph (a)(9) of this section, or 800–304–4846 (Option #2). obtain an FPP, the owner must complete modified under § 600.735 or § 600.740 * * * * * an FPP application and provide the of this chapter. (l) * * * following information (see paragraphs (ii) Surrendered permit. An FPP may (1) * * * (f)(2)(i) through (v) of this section for be voluntarily surrendered in (ii) * * * each SFP and shoreside processor plant accordance with paragraph (a)(9) of this (C) Surrender of AFA permits. Except to be permitted): section. An FPP may be reissued to the for AFA inshore processor permits, AFA (i) New or amended permit. Indicate permit holder of record in the same permits may not be surrendered. whether application is for a new or fishing year in which it was * * * * * amended FPP; and if an amended surrendered. Contact NMFS/RAM for (iv) Amended permits. AFA vessel permit, provide the current FPP more information by telephone, locally and processor permits may not be used number. Indicate whether application is at 907–586–7202 (Option #2) or toll–free on or transferred to any vessel or for a shoreside processor or an SFP. at 800–304–4846 (Option #2). processor that is not listed on the (ii) Owner information. Indicate the (iii) Amended permit. An owner or permit. However, AFA permits may be name(s), permanent business mailing operator, who applied for and received amended by NMFS to reflect any change address, business telephone number, an FPP, must notify NMFS of any in the ownership of the vessel or business fax number, and business change in the permit information by processor after submittal of this email address of all owners, and if submitting an FPP application found at information to NMFS in a written letter. the NMFS website at http:// applicable, the name of any person or * * * * * alaskafisheries.noaa.gov. The owner or company (other than the owner) who (5) * * * operator must submit the application as manages the operations of the shoreside (ii) Surrender of permit. An AFA instructed on the application form. processor or SFP. inshore processor permit may be Upon receipt and approval of a permit (iii) SFP information. Indicate the voluntarily surrendered in accordance amendment, the Program Administrator, vessel name; whether this is a vessel of with paragraph (a)(9) of this section. RAM, will issue an amended FPP. the United States; USCG documentation The AFA inshore processor permit will number; ADF&G vessel registration * * * * * not be reissued in the same fishing year number; ADF&G processor code; the (g) * * * in which it was surrendered, but may be vessel’s LOA (ft); registered length (ft); (1) General requirements. (i) In reapplied for and if approved, reissued gross tonnage; net tonnage; shaft addition to the permit and licensing to the permit holder of record in a horsepower; homeport (city and state); requirements prescribed in this part, subsequent fishing year. Contact NMFS/ and whether choosing to receive a GOA each vessel within the EEZ off Alaska RAM for more information by inshore processing endorsement. A that is catching and retaining scallops, telephone, locally at 907–586–7202 GOA inshore processing endorsement is must have an original scallop LLP (Option #2) or toll–free at 800–304–4846 required in order to process GOA license onboard at all times it is (Option #2). catching and retaining scallops. This inshore pollock and GOA inshore * * * * * Pacific cod. scallop LLP license, issued by NMFS, authorizes the person named on the ■ 6. In § 679.5: (iv) Shoreside processor information. ■ A. Paragraphs (j) and (m) are removed Indicate the shoreside processor’s name; license to catch and retain scallops in compliance with State of Alaska and reserved. permanent business mailing address; ■ regulations and only with a vessel that B. Paragraphs (a) through (f), (g)(1) physical location of plant at which the introductory text, (h), (i), (l)(1)(iv), and shoreside processor is operating (street, does not exceed the maximum LOA specified on the license and the gear (l)(2) are revised. city, state, zip code); whether the The revisions read as follows: shoreside processor is replacing a designation specified on the license. previous processor at this facility (YES (ii) A scallop LLP license may be § 679.5 Recordkeeping and reporting or NO, and if YES, name of previous voluntarily surrendered in accordance (R&R). processor); whether multiple processing with paragraph (a)(9) of this section. A (a) General R&R requirements. R&R businesses are using this plant; whether surrendered scallop LLP license will requirements include, but are not the owner named in paragraph (f)(2)(ii) cease to exist and will not be limited to, paper and electronic of this section owns this plant; ADF&G subsequently reissued. Contact NMFS/ documentation, logbooks, forms, processor code; business telephone RAM for more information by reports, receipts, computer printouts, number; business fax number; and telephone, locally at 907–586–7202 and requests for inspection described in business e–mail address. (Option #2) or toll–free at 800–304–4846 this section and in § 679.28. (v) Signature. The owner or agent of (Option #2). (1) Groundfish logbooks and forms. (i) the owner of the shoreside processor or * * * * * The Regional Administrator will SFP must sign and date the application. (k) Licenses for license limitation prescribe and provide groundfish If the owner is a company, the agent of (LLP) groundfish or crab species logbooks required under this section. the owner must sign and date the * * * * * All groundfish forms required under application. (6) * * * this section are available from the (3) Issuance. Upon receipt of a (x) Surrender of groundfish or crab Alaska Region website at http:// properly completed permit application, LLP. A groundfish or crab LLP license alaskafisheries.noaa.gov or may be

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00011 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76146 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

requested by calling the Sustainable (ii) Current editions. The operator (iii) Management program defined. A Fisheries Division at 907–586–7228 or must use the current edition of the ‘‘management program’’ is a unique faxing 907–586–7465. The forms may be logbooks and current format of the fishery program with a specific completed online, printed, and mailed forms. Upon approval from the Regional management strategy and/or allocation. or faxed to NMFS at the address or fax Administrator NMFS–approved Harvest that occurred under the number shown on the form. The forms electronic versions of the forms may be management programs listed in the also may be completed online, saved as used. Upon written notification and following table must be recorded a file, and submitted to NMFS as an approval by the Regional Administrator, separately in the logbooks, forms, and attachment to an e–mail to the e–mail logbooks from the previous year may be eLandings. address shown on the form. used.

If harvest made under . . . program Record the . . . For more information, see . . .

(A) Western Alaska Community Develop- CDQ group number subpart C of this part ment Quota (CDQ)

(B) Exempted Fishery Exempted fishery permit number § 679.6

(D) Aleutian Islands Pollock (AIP) n/a subpart F of this part

(E) Open access (OA) [for recording in eLandings only] paragraph (e) of this section

(2) Responsibility. (i) The operator of non–groundfish (see Table 2d to this periods that are outside an open crab a catcher vessel, catcher/processor, part): season for use as crab bait onboard their mothership, or buying station receiving (i) Harvest information; vessel. groundfish from a catcher vessel and (ii) Receipt information from catcher (C) No groundfish species listed by delivering to a mothership (hereafter vessels and buying stations, including NMFS as ‘‘prohibited’’ in a management referred to as the operator) and the fish received from vessels not required or regulatory area may be taken in that manager of a shoreside processor, SFP, to have an FFP; and fish received under area for use as bait. or buying station receiving groundfish contract for handling or processing for (5) Inspection and retention of from a catcher vessel and delivering to another processor; records—(i) Inspection of records. The a shoreside processor or SFP (hereafter (iii) Discard or disposition operator or manager must make referred to as the manager) are each information, including fish reported but available for inspection the R&R responsible for complying with the not delivered to the operator or documentation in this section and in applicable R&R requirements in this manager, e.g., fish used onboard a § 679.28 upon the request of an section and in § 679.28. vessel, when receiving catch from a authorized officer. (ii) The owner of a vessel, shoreside catcher vessel or buying station; and (ii) Retention of records. The operator processor, SFP, or buying station is (iv) Transfer information, including or manager must retain the R&R responsible for compliance and must fish transferred out of the facility or off documentation described in this section ensure that the operator, manager, or the vessel. and in § 679.28: (4) Exemptions—(i) Catcher vessels representative (see paragraph (b) of this (A) On site. Retain these records on section) complies with the applicable less than 60 ft (18.3 m) LOA. Except for the vessel activity report described at site at the shoreside processor or SFP, R&R requirements in this section and in or onboard the vessel until the end of § 679.28. paragraph (k) of this section, the owner or operator of a catcher vessel less than the fishing year during which the (iii) The IFQ permit holder, IFQ hired 60 ft (18.3 m) LOA is not required to records were made and for as long master permit holder, or Registered comply with the R&R requirements of thereafter as fish or fish products Buyer must comply with the R&R this section. recorded in the R&R documentation are requirements provided at paragraphs (e), (ii) Catcher vessels that take retained. (g), (k), and (l) of this section. groundfish in crab pot gear for use as (B) For 3 years. Retain these records (iv) The CDQ permit holder, CDQ crab bait on that vessel. (A) Owners or for 3 years after the end of the fishing hired master permit holder, or operators of catcher vessels who, when year during which the records were Registered Buyer must comply with the crab is open anywhere or in the same made. R&R requirements provided at area as an open crab season, take (6) Maintenance of records. The paragraphs (e), (g), (k), and (l)(1) through groundfish in crab pot gear for use as operator or manager must maintain all (6) of this section. crab bait onboard their same vessels, records described in this section and in (3) Fish to be recorded and reported. and the bait is neither transferred nor § 679.28 in English and in a legible, The operator or manager must record sold, are not required to comply with timely, and accurate manner, based on and report the following information R&R requirements of this section. Alaska local time (A.l.t.); if handwritten, (see paragraphs (a)(3)(i) through (iv) of (B) This exemption does not apply to in indelible ink; if computer–generated, this section) for all groundfish (see fishermen who: as a legible printed paper copy. Table 2a to this part), prohibited species (1) Catch groundfish for bait during an (7) Custom processing. The manager (see Table 2b to this part) and forage fish open crab season and sell that of a shoreside processor or SFP or the (see Table 2c to this part). The operator groundfish or transfer it to another operator of a mothership must record or manager may record and report the vessel, or products that result from custom following information (see paragraphs (2) Participate in a directed fishery for processing for another person in (a)(3)(i) through (iv) of this section) for groundfish using any gear type during eLandings consistently throughout a

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00012 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76147

fishing year using one of the following manager of responsibility for (iv) Two logbooks of different two methods: compliance under paragraphs (a)(1) operation. If a vessel functions both as (i) Combined records. Record through (6) of this section. a mothership and as a catcher/processor landings, discards or dispositions, and (c) Logbooks—(1) Requirements—(i) in the same fishing year, the operator(s) products of custom–processed Use of two or more vessel logbooks of must maintain two logbooks, a separate groundfish routinely in eLandings using same gear type. If using more than one logbook for each operation type, each processor name, FFP or FPP number, logbook of the same gear type in a separately paginated. and ADF&G processor code; or fishing year onboard a vessel, the (ii) Separate records. Record landings, operator must ensure that the page (v) Alteration of logbook information. discards or dispositions, and products numbers follow the consecutive order of (A) Except as described in paragraph of custom–processed groundfish in the previous logbook. (c)(1)(v)(B) of this section, no person eLandings identified by the name, FPP (ii) Use of two or more vessel logbooks may alter or change any entry or record number or FFP number, and ADF&G of different gear types. If two or more in a logbook. processor code of the associated different gear types are used onboard a (B) An inaccurate or incorrect entry or business entity. vessel in a fishing year, the operator(s) record must be corrected by lining out (b) Representative. The operator of a of this vessel must use the same number the original and inserting the correction, catcher vessel, mothership, catcher/ of separate vessel logbooks for the provided that the original entry or processor, or buying station delivering different gear types, each separately record remains legible. All corrections to a mothership or manager of a paginated. must be made in ink. shoreside processor, SFP, or buying (iii) Two vessel logbooks for pair station delivering to a shoreside trawl. If two vessels are dragging a trawl (vi) Logsheet distribution and processor or SFP may identify one between them (pair trawl), the operator submittal. (A) No person except an contact person to complete the logbook of each vessel must maintain a separate authorized officer may remove any and forms and to respond to inquiries logbook to record the amount of the original white logsheet of any logbook. from NMFS. Designation of a catch retained and fish discarded by (B) The operator must distribute and representative under this paragraph (b) that vessel. Each of the two logbooks submit logsheets as indicated in the does not relieve the owner, operator, or must be separately paginated. following table:

Logsheet Distribution and Submittal Logsheet found in these logbooks If logsheet Submit to ... Time limit color is ... CV lgl CV trw CP lgl CP trw MS

(1) White X X X X X Must retain, permanently bound in logbook

(2) Goldenrod X X X X X Observer After signature of operator and prior to departure of observer from the vessel.

(3) Yellow X X X X X Must submit quarterly to: On the following sched- NOAA Fisheries Office ule: for Law Enforcement 1st quarter by May 1 of Alaska Region Logbook that fishing year Program 2nd quarter by August 1 P.O. Box 21767 of that fishing year Juneau, AK 99802 1767 3rd quarter by Novem- Telephone: 907–586– ber 1 of that fishing year 7225 4th quarter by February 1 of the following fishing year

(4) Blue X X Mothership, shoreside Within 2 hours after processor, SFP, or buy- completion of catch de- ing station that receives livery the harvest

(5) Green X X Optional, but may be re- If required, after the ves- quired by IPHC (see §§ sel’s catch is off-loaded 300.60 through 300.65 of this chapter) Note: CP = catcher/processor; CV = catcher vessel; lgl = longline; trw = trawl; MS = mothership.

(2) Recording active and inactive time was active or inactive during the time Paragraph Fishing Category periods in the DFL or DCPL—(i) Account period. for each day of the fishing year. The (A) An active period by fishing (c)(3)(iv)(A)(1) Catcher vessel, longline or pot gear operator must account for each day of category is defined in the following the fishing year, January 1 through paragraphs under this section: (c)(3)(iv)(B)(1) Catcher/processor, December 31, in the DFL or DCPL and longline or pot gear indicate whether the vessel or processor

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00013 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76148 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

Paragraph Fishing Category failure. If inactive due to surrender of a section, the operator of a catcher vessel FFP or FPP, write ‘‘surrender of permit’’ 60 ft (18.3 m) or greater LOA, using (c)(4)(iv)(A)(1) Catcher vessel, trawl as the reason for inactivity. fixed gear (NMFS), setline (IPHC), or pot gear (F) Record the date (mm/dd) of the gear to harvest IFQ sablefish, IFQ last day when inactive under ‘‘End halibut, or CDQ halibut from the GOA (c)(4)(iv)(B)(1) Catcher/processor, trawl gear date.’’ or BSAI, must maintain a longline and (iv) Inactive two or more quarters. If pot gear DFL. (c)(5)(ii) Shoreside processor or the inactive time period extends across (2) Except as described in paragraph SFP two or more successive quarters, the (f)(1)(ii) of this section, the operator of operator must complete a logsheet for a catcher/processor that is using (c)(6)(iv) Mothership each inactive quarter. The first logsheet longline or pot gear to harvest IFQ must indicate the first and last day of sablefish, IFQ halibut, or CDQ halibut (B) An inactive period is defined as a the first inactive quarter. Successive from the GOA or BSAI must use a time period other than active. logsheets must indicate the first and last combination of catcher/processor (ii) Record January 1 on page 1. The day of its respective inactive quarter. longline and pot gear DCPL and operator must record the first day of the (3) Longline and pot gear catcher eLandings to record and report daily fishing year, January 1, on page one of vessel DFL and catcher/processor processor identification information, the DFL or DCPL regardless of whether DCPL—(i) Responsibility—(A) catch–by–set halibut and sablefish the vessel or processor was active or Groundfish fisheries. (1) Except as landings data, and halibut, sablefish, inactive. The operator must record time described in paragraph (f)(1)(i) of this and prohibited species discard or periods consecutively. (iii) Required information for inactive section, the operator of a catcher vessel disposition data. periods. If inactive, the operator must 60 ft (18.3 m) or greater LOA, that is (C) CR crab fisheries. (1) The operator record the following information (see required to have an FFP under of a catcher vessel 60 ft (18.3 m) or paragraphs (c)(2)(iii)(A) through (F) of § 679.4(b) and that is using longline or greater LOA, using pot gear to harvest this section) on one logsheet in the DFL pot gear to harvest groundfish must CR crab from the BSAI must maintain a or DCPL: maintain a longline and pot gear DFL. longline and pot gear DFL. (A) If a catcher vessel, vessel name, (2) Except as described in paragraph (2) The operator of a catcher/ ADF&G vessel registration number, FFP (f)(1)(ii) of this section, the operator of processor that is using pot gear to number or Federal crab vessel permit a catcher/processor that is required to harvest CR crab from the BSAI must use number, operator printed name, have an FFP under § 679.4(b) and that a combination of catcher/processor operator signature, and page number. is using longline or pot gear to harvest longline and pot gear DCPL and (B) If a mothership or catcher/ groundfish must use a combination of eLandings to record and report daily processor, record vessel name, ADF&G catcher/processor longline and pot gear processor identification information, CR processor code, FFP number, operator DCPL and eLandings to record and crab landings data, and CR crab and printed name, operator signature, and report daily processor identification prohibited species discard or page number. information, catch–by–set information, disposition data. (C) Mark ‘‘inactive.’’ groundfish production data, and (ii) Data entry time limits—(A) (D) Record the date (mm/dd) of the groundfish and prohibited species Catcher vessel. The operator of a catcher first day when inactive under ‘‘Start discard or disposition data. vessel using longline or pot gear must date.’’ (B) IFQ halibut, CDQ halibut, and IFQ record in the DFL the information from (E) Write brief explanation why sablefish fisheries. (1) Except as the following table for each set within inactive, e.g., bad weather or equipment described in paragraph (f)(1)(i) of this the specified time limit:

DATA ENTRY TIME LIMITS, CATCHER VESSEL LONGLINE OR POT GEAR Required information Time limit for recording

(1) Set number, time and date gear set, time and date gear hauled, be- Within 2 hours after completion of gear retrieval ginning and end positions, CDQ group number, halibut CDQ permit number, halibut IFQ permit number, sablefish IFQ permit number, crab IFQ permit number, FFP number and/or Federal crab vessel permit number (if applicable), number of pots set, and estimated total hail weight for each set

(2) Discard and disposition information By noon each day to record the previous day’s discard and disposition information

(3) Submit the blue DFL to mothership, shoreside processor, SFP, or Within 2 hours after completion of catch delivery buying station receiving catch

(4) All other required information Within 2 hours after the vessel’s catch is off-loaded, notwithstanding other time limits

(5) Operator sign the completed logsheets Within 2 hours after completion of catch delivery

(6) Submit goldenrod logsheet to the observer After signature of operator and prior to departure of observer from the vessel.

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00014 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76149

(B) Catcher/processor. The operator of pot gear must record in the DCPL or following table for each set within the a catcher/processor using longline or eLandings the information from the specified time limit:

DATA ENTRY TIME LIMITS, CATCHER/PROCESSOR LONGLINE OR POT GEAR Record In Required information Time limit for recording DCPL eLandings

(1) Set number, time and date gear set, time and X X Within 2 hours after completion of gear retrieval date gear hauled, beginning and end positions, CDQ group number, halibut CDQ permit number, halibut IFQ permit number, sablefish IFQ permit number, crab IFQ permit number, FFP number and/or Federal crab vessel permit number (if applicable), number of pots set, and estimated total hail weight for each set

(2) Discard and disposition information X By midnight each day to record the previous day’s discard and disposition information

(3) Product information X By noon each day to record the previous day’s production information

(4) All other required information X X By noon of the day following completion of production

(5) Operator sign the completed logsheets X X By noon of the day following the week-ending date of the weekly reporting period

(6) Submit goldenrod logsheet to the observer X After signature of operator and prior to departure of observer from the vessel

(iii) Required information, if inactive. listed in paragraphs (c)(3)(v) and (vi) of (D) Other permit numbers (if See paragraph (c)(2) of this section. this section and must record in applicable). IFQ permit number of the (iv) Required information, if active— eLandings the information listed in operator, if any, and each permit (A) Catcher vessel, longline or pot gear. paragraphs (c)(3)(v), (vii), (viii), and (x) number of any IFQ permit on which (1) A catcher vessel using longline or of this section. anyone aboard is authorized to fish; pot gear is active when gear remains on (3) Retain and record discard groundfish CDQ group number; and the grounds in a reporting area (except quantities over the MRA. When a halibut CDQ permit number. reporting areas 300, 400, 550, or 690), catcher/processor is fishing in an IFQ (E) Reporting area—(1) Groundfish. regardless of the vessel location. fishery and the fishery for Pacific cod or Record the Federal reporting area code (2) If the catcher vessel identified in rockfish is closed to directed fishing but (see Figures 1 and 3 to this part) where paragraph (c)(3)(i)(A)(1) of this section not in PSC status in that reporting area gear retrieval was completed, regardless is active, the operator must record in the as described in § 679.20, the operator of where the majority of the set took DFL, for one or more days on each must retain and record up to and place. Use a separate logsheet for each logsheet, the information listed in including the MRA for Pacific cod or reporting area. paragraphs (c)(3)(v), (vi), (viii), (ix), and rockfish as defined in Table 10 or 11 to (2) IFQ halibut and CDQ halibut. (x) of this section. this part. Quantities over this amount Record the IPHC regulatory area (see (3) Retain and record discard must be discarded and recorded as Figure 15 to this part) where gear quantities over the MRA. When a discard in eLandings. retrieval was completed, regardless of catcher vessel is fishing in an IFQ (v) Identification information—(A) where the majority of the set took place. fishery and the fishery for Pacific cod or Page number. Number the pages in each (3) CR crab. Leave this field blank. rockfish is closed to directed fishing but logbook consecutively, beginning on the (F) Crew size. If a catcher vessel, not in PSC status in that reporting area first page of the DFL or DCPL with page record the number of crew members as described in § 679.20, the operator 1 for January 1 and continuing for the (including operator), excluding certified must retain and record up to and remainder of the fishing year. observer(s), on the last day of a trip. If including the maximum retainable (B) Printed name and signature of a catcher/processor, record the number amount (MRA) for Pacific cod or operator. The operator’s name must be of crew members (including operator), rockfish as defined in Table 10 or 11 to printed in the DFL or DCPL. The excluding certified observer(s), on the this part. Quantities over this amount operator must sign each completed last day of the weekly reporting period. must be discarded and recorded as logsheet of the DFL or DCPL as (G) Gear type. Use a separate logsheet discard in the logbook. verification of acceptance of the for each gear type. From the following (B) Catcher/processor, longline or pot responsibility required in paragraph table, indicate the gear type used to gear. (1) A catcher/processor using (a)(2) of this section harvest the fish and appropriate ‘‘gear longline or pot gear is active when (C) Vessel identification. Name of ID.’’ In addition, if using hook–and–line processing or when all or part of the vessel as displayed in official gear, enter the alphabetical letter that longline or pot gear is in the water. documentation; FFP number or Federal coincides with the gear description. If (2) If the catcher/processor identified crab vessel permit number of the vessel; gear information is the same on in paragraph (c)(3)(i)(A)(2) of this and ADF&G vessel registration number subsequent logsheets, mark the box section is active, the operator must if a catcher vessel or ADF&G processor instead of re–entering the gear type record in the DCPL the information code if a catcher/processor. information on the next logsheet.

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00015 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76150 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

If gear format, A.l.t.), and the begin position nearest 0.001 mt. Use one line to record type is ... Then ... (latitude and longitude to the nearest information for each IR/IU species, minute; indicate E or W for longitude) including species code and amount of (1) Other If gear is other than those list- when the jig or troll gear enters the catch. If more than one IR/IU species are gear ed within this table, indicate water. to be recorded, the operator must use a ‘‘Other’’ and describe (3) Pot gear begin position. Record separate line for each species. (2) Pot Enter the number of pots lost date (mm/dd), time (in military format, (J) IFQ halibut and CDQ halibut. gear (optional, but may be required A.l.t.), and the begin position (latitude Estimated total net weight of IFQ by IPHC regulations (see §§ and longitude to the nearest minute; halibut and CDQ halibut to the nearest 300.60 through 300.65 of this indicate E or W for longitude) when the pound. chapter)) and number of pots pot gear enters the water. (K) IFQ sablefish. Number and set (C) Gear retrieval (or to haul gear)— estimated total round weight of IFQ (1) Hook–and–line gear end position. sablefish to the nearest pound. Indicate (3) Hook- Indicate: Date (mm/dd), time (in military format, whether IFQ sablefish product is and-line (i) Whether gear is fixed hook gear (conventional or tub), autoline, A.l.t.), and end position coordinates (in Western cut, Eastern cut, or round or snap (optional, but may be latitude and longitude to the nearest weight. required by IPHC regulations minute; indicate E or W for longitude), (L) CR crab. If in a CR crab fishery, (see §§ 300.60 through 300.65 where the last hook–and–line gear of a record the number and scale weight of of this chapter)) set leaves the water, regardless of where raw CR crab to the nearest pound. the majority of the set took place. (vii) Product information, catcher/ (ii) Length of skate to the near- (2) Jig or troll gear end position. Date processor. The operator of a catcher/ est foot (optional, but may be (mm/dd), time (in military format, processor using longline or pot gear required by IPHC regulations A.l.t.), and end position coordinates (in must record groundfish product (see §§ 300.60 through 300.65 information for all retained groundfish of this chapter)), number of latitude and longitude to the nearest skates lost (optional, but may minute; indicate E or W for longitude) in eLandings (see paragraph (e)(10) of be required by IPHC regula- where the jig or troll gear leaves the this section). tions (see §§ 300.60 through water. (viii) Discard or disposition 300.65 of this chapter)), and (3) Pot gear end position. Date (mm/ information, catcher vessel. The number of skates set dd), time (in military format, A.l.t.), and operator must record in a DFL the end position coordinates (in latitude discard or disposition information that (iii) Number of hooks per skate and longitude to the nearest minute; occurred prior to and during delivery to (optional, but may be required indicate E or W for longitude) where the a buying station, mothership, shoreside by IPHC regulations (see §§ processor, or SFP. Discard or 300.60 through 300.65 of this last pot of a set is retrieved, regardless chapter)), size of hooks, and of where the majority of the set took disposition information must include hook spacing in feet place. the daily weight of groundfish, daily (D) Begin and end buoy or bag weight of herring PSC, and daily (iv) Seabird avoidance gear numbers. (optional, but may be required number of PSC animals. If no discard or code(s) (see § 679.24(e) and by IPHC regulations (see §§ 300.60 disposition occurred for a given day, the Table 19 to this part) through 300.65 of this chapter)). operator must write ‘‘no discards or (E) Begin and end gear depths. disposition.’’ (H) Management program. Indicate Recorded to the nearest fathom (A) Enter discard or disposition whether harvest occurred under a (optional, but may be required by IPHC information by species codes and management program (see paragraph regulations (see §§ 300.60 through product codes as follows: (a)(1)(iii) of this section). Use a separate 300.65 of this chapter)). (1) Date (mm/dd) of discard or logsheet for each management program. (F) Species codes. The operator must disposition (day that discard or If harvest is not under one of the listed record and report required information disposition occurred). management programs, leave blank. for all groundfish (see Table 2a to this (2) For whole fish discard or (I) Observer information. Record the part), prohibited species (see Table 2b to disposition of groundfish or Pacific number of observers aboard, the name of this part), and forage fish (see Table 2c herring PSC, daily estimated total the observer(s), and the observer cruise to this part). The operator may record weight, balance forward weight from the number(s). and report information for non– previous day, and cumulative total (vi) Catch–by–set information. The groundfish (see Table 2d to this part). weight since last delivery for each operator must record the following (G) Target species code. Enter the species; indicate whether weight is information (see paragraphs (c)(3)(vi)(A) species code of the intended species to estimated to the nearest pound or through (L) of this section) for each set be harvested. Enter only one target nearest 0.001 mt. (see § 679.2) in the DFL or DCPL. If no species code. (3) For whole fish discard or catch occurred for a given day, write (H) Estimated total hail weight. Enter disposition of each prohibited species ‘‘no catch.’’ the estimated hail weight, which is an (Pacific salmon, steelhead trout, Pacific (A) Set number. Sequentially by year. estimate of the total weight of the entire halibut, king crabs, and Tanner crabs) (B) Gear deployment (or to set gear)— catch without regard to species. Indicate record the daily estimated total number, (1) Hook–and–line gear begin position. whether weight is estimated to the balance forward from the previous day, Record date (mm/dd), time (in military nearest pound or to the nearest 0.001 and cumulative total number since the format, A.l.t.), and the begin position (in mt. last delivery. latitude and longitude to the nearest (I) IR/IU species (see § 679.27). If a (4) Summarize the weekly cumulative minute; indicate E or W for longitude) catcher/processor, enter species code of discard and disposition totals of when the first hook–and–line gear of a IR/IU species and estimated total round groundfish weights and number of PSC set enters the water. weight for each IR/IU species, if animals separately by reporting area, (2) Jig or troll gear begin position. applicable; indicate whether weight is management program, and gear type. Record date (mm/dd), time (in military estimated to the nearest pound or the Determine the weekly cumulative total

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00016 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76151

by adding daily totals and the balance to a buying station, mothership, logsheets per day. Upon notification by carried forward from the day before. shoreside processor, or SFP: the Regional Administrator, a DFL from (B) The operator must record ‘‘0’’ or (A) Date (mm/dd) that delivery of the previous year may be used. harvest was completed. zero balance forward and start a new (B) Except as described in paragraph (B) ADF&G fish ticket issued to (f)(1)(iv) of this section, the operator of logsheet after the offload or transfer of operator by the recipient, Registered all fish or fish product onboard and a catcher/processor that is required to Buyer, or RCR receiving the delivery. have an FFP under § 679.4(b) and that prior to the beginning of each fishing (C) Name of recipient, Registered is using trawl gear to harvest groundfish trip. Nothing shall be carried forward Buyer, or RCR. from the previous fishing trip. (D) For the unloading port, enter the is required to use a combination of name of the port or port code (see catcher/processor trawl gear DCPL and (ix) Discard or disposition eLandings to record and report daily information, catcher/processor. The Tables 14a and 14b to this part) of delivery location. processor identification information, operator of a catcher/processor using catch–by–haul landings information, longline or pot gear must record all (4) Trawl gear catcher vessel DFL and catcher/processor DCPL—(i) groundfish production data, and discard or disposition information in Responsibility. (A) Except as described groundfish and prohibited species eLandings (see paragraph (e)(10) of this in paragraph (f)(1)(iii) of this section, discard or disposition data. section). the operator of a catcher vessel 60 ft (ii) Data entry time limits—(A) (x) Catcher vessel delivery (18.3 m) or greater LOA, that is required Catcher vessel. The operator of a catcher information. The operator of a catcher to have an FFP under § 679.4(b), and vessel using trawl gear must record in vessel must enter the following that is using trawl gear to harvest the DFL the information in the information (see paragraphs (c)(3)(x)(A) groundfish must maintain a trawl gear following table for each haul within the through (D) of this section) for delivery DFL, must complete one or more specified time limit:

DATA ENTRY TIME LIMITS, CATCHER VESSEL TRAWL GEAR Required information Time limit for recording

(1) Haul number, time and date gear set, time and date gear hauled, Within 2 hours after completion of gear retrieval beginning and end positions, CDQ group number (if applicable), and total estimated hail weight for each haul

(2) Discard and disposition information By noon each day to record the previous day’s discard and disposition information

(3) Submit blue DFL to mothership, shoreside processor, SFP, or buy- Within 2 hours after completion of catch delivery ing station receiving the catch

(4) Record all other required information Within 2 hours after the vessel’s catch is off-loaded, notwithstanding other time limits

(5) Operator sign the completed logsheets Within 2 hours after completion of catch delivery

(6) Submit the goldenrod logsheet to the observer After signature of operator and prior to departure of observer from the vessel.

(B) Catcher/processor. The operator of must record in the DCPL or eLandings for each haul within the specified time a catcher/processor using trawl gear the information in the following table limit:

DATA ENTRY TIME LIMITS, CATCHER/PROCESSOR TRAWL GEAR Record In Required information Time limit for recording DCPL eLandings

(1) Haul number, time and date gear set, time X X Except for Rockfish Pilot Program, within 2 hours after comple- and date gear hauled, begin and end positions of tion of gear retrieval. gear, CDQ group number (if applicable), and total For Rockfish Pilot Program, actual scale weight from the flow estimated hail weight for each haul, or if required scale may be recorded within 24 hours after completion of to use a NMFS approved scale, the scale weight gear retrieval. for each haul

(2) Discard and disposition information X By midnight each day to record the previous day’s discard and disposition information

(3) Record product information X By noon each day to record the previous day’s production information

(4) Record all other required information X X By noon of the day following completion of production to record all other required information

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00017 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76152 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

DATA ENTRY TIME LIMITS, CATCHER/PROCESSOR TRAWL GEAR Record In Required information Time limit for recording DCPL eLandings

(5) Operator sign the completed logsheets X X By noon of the day following the week-ending date of the weekly reporting period

(6) Submit the goldenrod logsheet to the observer X After signature of operator and prior to departure of observer from the vessel.

(iii) Required information, if inactive. (E) Federal reporting area. Record the E or W for longitude) where the trawl See paragraph (c)(2) of this section. Federal reporting area code where gear net enters the water. (iv) Required information, if active— retrieval was completed, regardless of (C) Gear retrieval (or to haul gear). (A) Catcher vessel. (1) A catcher vessel where the majority of the set took place. Record the following information (see using trawl gear is active when all or Use a separate logsheet for each paragraphs (c)(4)(vi)(C)(1) and (2) of this part of the trawl net is in the water. reporting area. section) for trawl gear retrieval: (2) If the catcher vessel identified in (F) COBLZ or RKCSA. If gear retrieval (1) The date (mm/dd) and time (in paragraph (c)(4)(i)(A) of this section is occurred in the COBLZ (see Figure 13 to military format, A.l.t.) when retrieval of active, the operator must record for one this part) or RKCSA (see Figure 11 to trawl gear cable begins. day per logsheet in the DFL, the this part) area within a reporting area, (2) The position (in latitude and information described in paragraphs use two separate logsheets, the first to longitude to the nearest minute; indicate (c)(4)(v), (vi), (viii), and (x) of this record the information from the E or W for longitude) where retrieval of section. reporting area that includes COBLZ or trawl gear cable begins. (B) Catcher/processor. (1) A catcher/ RKCSA, and the second to record the (D) Average sea depth and average processor using trawl gear is active information from the reporting area that gear depth. Average sea depth and when processing groundfish or when all does not include COBLZ or RKCSA. average gear depth; indicate whether or part of the trawl net is in the water. (G) Crew size. If a catcher vessel, average is reported to the nearest meter record the number of crew members or fathom. (2) If the catcher/processor identified (E) Species codes. The operator must (including operator), excluding certified in paragraph (c)(4)(i)(B) of this section is record and report the required observer(s), on the last day of a trip. If active, the operator must record for one information for all groundfish (see Table a catcher/processor, record the number day per logsheet in the DCPL, the 2a to this part), prohibited species (see of crew members (including operator), information described in paragraphs Table 2b to this part), and forage fish excluding certified observer(s), on the (c)(4)(v) and (vi) of this section and (see Table 2c to this part). The operator last day of the weekly reporting period. record in eLandings the information may also record and report the required (H) Gear type. Use a separate logsheet described in paragraphs (c)(4)(v), (vii), information for non–groundfish (see for each gear type. Indicate whether and (ix) of this section. Table 2d to this part). (v) Identification information. If pelagic trawl or non–pelagic trawl gear (F) Target species code. Enter the active, the operator must record the was used to harvest the fish. species code of the species to be following information (see paragraphs (I) Management program. Indicate harvested. Enter only one target species (c)(4)(v)(A) through (J) of this section): whether harvest occurred under one of code. (A) Date. Enter date of each day (mm/ the management programs (see (G) IR/IU species (see § 679.27). If a dd/yyyy). This date is also the date of paragraph (a)(1)(iii) of this section). Use catcher/processor, enter species code of gear deployment. a separate logsheet for each management IR/IU species and estimated total round (B) Page number. Number the pages in program. If harvest is not under one of weight for each IR/IU species, if each logbook consecutively, beginning the listed management programs, leave applicable; indicate whether estimated on the first page of the DFL or DCPL blank. weight is to the nearest pound or the with page 1 for January 1 and (J) Observer information. Record the nearest 0.001 mt. Use one line to record continuing for the remainder of the number of observers aboard, the name of information for each IR/IU species, fishing year. the observer(s), and the observer cruise including species code and amount of (C) Printed name and signature of number(s). catch. If more than one IR/IU species are operator. The operator’s name must be (vi) Catch–by–haul information. The to be recorded, the operator must use a printed in the DFL or DCPL. The operator must record the following separate line for each species. operator must sign each completed information (see paragraphs (c)(4)(vi)(A) (H) Total estimated hail weight. (1) If logsheet of the DFL or DCPL as through (H) of this section) for each haul a catcher vessel or catcher/processor verification of acceptance of the (see § 679.2). If no catch occurred for a using trawl gear and not using NMFS– responsibility required in paragraph given day, write ‘‘no catch.’’ approved scales, the operator must (a)(2) of this section. The operator’s (A) Haul number. Number hauls record the hail weight of each haul; total signature is due by noon of the day sequentially by year. hail weight is an estimate of the total following the week–ending date of the (B) Gear deployment (or to set gear). weight of the entire catch without weekly reporting period. Record the following information (see regard to species. Indicate whether (D) Vessel identification. Name of paragraphs (c)(4)(vi)(B)(1) and (2) of this estimated weight is to the nearest pound vessel as displayed in official section) for trawl gear deployment: or to the nearest 0.001 mt. documentation; FFP number of the (1) The time (in military format, A.l.t.) (2) If a catcher/processor using trawl vessel; ADF&G vessel registration when the trawl net enters the water, and gear is required to use a NMFS– number if a catcher vessel; and ADF&G (2) The position (latitude and approved scale, the operator must processor code if a catcher/processor. longitude to the nearest minute; indicate record the scale weight of each haul

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00018 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76153

without regard to species. Indicate number since last delivery of PSC (5) Shoreside processor DCPL. The whether weight is to the nearest pound animals (Pacific salmon, steelhead trout, shoreside processor DCPL has been or to the nearest 0.001 mt. Pacific halibut, king crabs, and Tanner replaced by eLandings and is no longer (vii) Product information, catcher/ crabs). available. (See paragraph (e) of this processor. The operator of a catcher/ (D) Discard and disposition section.) processor using trawl gear must record cumulative total. Summarize (i) Required information, if inactive. all product information for all retained cumulative discard and disposition See paragraph (c)(2) of this section. groundfish in eLandings (see paragraph totals of groundfish and PSC animals (e)(10) of this section). separately by reporting area, if harvest (ii) Required information, if active. A (viii) Discard or disposition occurred in the COBLZ or RKCSA, shoreside processor or SFP is active information, catcher vessel. The management program, and gear type. when receiving or processing operator must record in a DFL (see (E) Discard zero balance forward. groundfish. paragraphs (c)(4)(viii)(A) through (E) of After the offload or transfer of all fish or (6) Mothership DCPL—(i) this section) the discard or disposition fish product onboard and prior to the Responsibility. Except as described in that occurred prior to and during beginning of each fishing trip, the paragraph (f)(1)(v) of this section, the delivery to a buying station, mothership, operator must record the balance operator of a mothership that is required shoreside processor, or SFP. If no forward from the previous day as ‘‘zero’’ to have an FFP under § 679.4(b) and that discards or disposition occurred on a and start a new logsheet. At the receives or processes any groundfish given day, write ‘‘no discards or beginning of each fishing trip, nothing from the GOA or BSAI from vessels disposition.’’ shall be carried forward from the issued an FFP under § 679.4(b) is (A) Species code and product code. previous fishing trip. required to use a combination of Record the species code and product (ix) Discard or disposition mothership DCPL and eLandings to code for all discards and disposition of information, catcher/processor. The record and report daily processor groundfish and PSC Pacific herring, operator of a catcher/processor using identification information, delivery Pacific salmon, steelhead trout, Pacific trawl gear must record discard or information, groundfish production halibut, king crabs, and Tanner crabs. disposition information in eLandings data, and groundfish and prohibited (B) Discard and disposition weight. (see paragraph (e)(10) of this section). Record the daily estimated total round species discard or disposition data. The (x) Catcher vessel delivery operator must enter into the DCPL any weight of groundfish or Pacific herring information. The operator must enter PSC discards and disposition, balance information for groundfish received the following delivery information (see from catcher vessel, groundfish received forward weight from the previous day, paragraphs (c)(4)(x)(A) through (C) of and cumulative total weight since last from processors for reprocessing or this section) for groundfish delivered to rehandling, and groundfish received delivery, calculated by adding the daily a buying station, mothership, shoreside totals and balance carried forward from from an associated buying station processor, or SFP: documented on a BSR. the day before; indicate whether (A) Date (mm/dd) that delivery of estimated weight is to the nearest pound harvest was completed, (ii) Data entry time limits. The or nearest 0.001 mt. (B) ADF&G fish ticket number issued operator of a mothership must record in (C) PSC discard numbers. Record the to operator by the recipient receiving the DCPL or eLandings the information daily number of PSC discards and the delivery, and in the following table for each disposition, balance forward from the (C) Name and ADF&G processor code groundfish delivery within the specified previous day, and cumulative total of recipient. time limit:

DATA ENTRY TIME LIMITS, MOTHERSHIP Record In Required information Time limit for recording DCPL eLandings

(A) All catcher vessel or buying station delivery X X Within 2 hours after completion of receipt of each groundfish information delivery

(B) Product information X By noon each day to record the previous day’s production

(D) All other required information X X By noon of the day following completion of production

(E) Operator sign the completed logsheets X X By noon of the day following the week-ending date of the weekly reporting period

(F) Submit the goldenrod logsheet to the ob- X After signed by the operator and prior to departure of observer server from the mothership.

(iii) Required information, if inactive. section is active, the operator must information described in paragraphs See paragraph (c)(2) of this section. record for one day per logsheet in the (c)(6)(v), (vii), and (viii) of this section. (iv) Required information, if active. A DCPL, the information described in (v) Identification information. If mothership is active when receiving or paragraphs (c)(6)(v) and (vi) of this active, the operator must record the processing groundfish. If the mothership section and record in eLandings the following information (see paragraphs identified in paragraph (c)(6)(i) of this

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00019 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76154 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

(c)(6)(v)(A) through (J) of this section) in (B) Non–submittal of discard report. ticket number that the mothership the DCPL: Indicate whether the blue logsheet was issued to each catcher vessel. If (A) Page number. Number the pages received from the catcher vessel at the receiving unprocessed groundfish from in each logbook consecutively, time of catch delivery. If the delivery an associated buying station, record the beginning with page 1 for January 1 and was from a buying station, leave this ADF&G fish ticket numbers issued by continuing throughout the logbook for column blank. If the blue logsheet is not the buying station on behalf of the the remainder of the fishing year. received from the catcher vessel, enter mothership to the catcher vessel. (B) Printed name and signature of ‘‘NO’’ and one of the response codes in (vii) Product information. The operator. The operator’s name must be the following table to describe the operator of a mothership must record all printed in the DCPL. The operator must reason for non–submittal. groundfish product information in sign each completed DCPL logsheet as eLandings (see paragraph (e)(10) of this verification of acceptance of the NON-SUBMITTAL OF DIS- CODE section), including products made from responsibility required in paragraph CARD REPORT unprocessed groundfish deliveries (a)(2) of this section. received from a buying station or a (1) The catcher vessel does ‘‘P’’ catcher vessel; groundfish received from (C) Vessel information. Name of not have an FFP mothership as displayed in official another processor or other source; and documentation, FFP number, and (2) The catcher vessel is ‘‘P’’ groundfish received for custom ADF&G processor code. under 60 ft (18.3 m) LOA and processing (see paragraph (a)(7) of this (D) Date. Enter date (mm/dd/yyyy) of does not have an FFP section) by the mothership for another each operating day. processor or business entity. (3) The catcher vessel is ‘‘L’’ (E) Crew size. Record the number of (viii) Discard or disposition under 60 ft (18.3 m) LOA and information. The operator of a crew members (including operator), has an FFP excluding certified observer(s), on the mothership must record discard and last day of the weekly reporting period. (4) The catcher vessel deliv- ‘‘U’’ disposition information in eLandings (F) Gear type. Indicate the gear type ered an unsorted codend (see paragraph (e)(10) of this section). of harvester. If gear type is other than The discard or disposition information those listed, circle ‘‘Other’’ and (5) Another reason; describe ‘‘O’’ must include: circumstances describe. Use a separate logsheet for (A) Discards and disposition that each gear type. occurred onboard after receipt of (C) Vessel identification. Name and groundfish from a catcher vessel or (G) Federal reporting areas. Record ADF&G vessel registration number of buying station; Federal reporting area code (see Figures the catcher vessel or buying station (if (B) Discards and disposition that 1 and 3 to this part) where harvest was applicable) delivering the groundfish. occurred prior to, during, and after completed. Use a separate logsheet for (D) Receipt time. Record time (in processing of groundfish; each reporting area. military format, A.l.t.) when receipt of (C) Discards and disposition that were (H) COBLZ or RKCSA. If groundfish groundfish delivery was completed. reported on a blue DFL received from a was harvested with trawl gear in the (E) Beginning position of receipt. catcher vessel delivering groundfish; COBLZ or RKCSA, use two separate Record the position coordinates (in (D) Discards and disposition that are logsheets to record the information: one latitude and longitude to the nearest recorded on a blue DFL received from logsheet for the reporting area that minute; indicate E or W for longitude) a catcher vessel even though no includes COBLZ or RKCSA, and a where receipt of the groundfish delivery groundfish are delivered; and second logsheet to record the began. (E) Discards and disposition reported information from the reporting area that (F) Estimated total groundfish hail on a BSR received from a buying station does not include COBLZ or RKCSA. weight. Enter the estimated total hail delivering groundfish, if different from (I) Observer information. Record the weight of the combined species of each the blue DFL logsheets submitted by number of observers aboard, the name(s) delivery from a catcher vessel or buying catcher vessels to the buying station. of the observer(s), and the observer station. Total estimated hail weight is an (d) Buying Station Report (BSR)—(1) cruise number(s). estimate of the total weight of the entire Responsibility—(i) Separate BSR. In (J) Management program. Indicate catch without regard to species. Indicate addition to the information required at whether harvest occurred under one of whether the estimated weight is to the paragraphs (a)(5) and (6) of this section, the management programs (see nearest pound or to the nearest 0.001 the operator or manager of a buying paragraph (a)(1)(iii) of this section). Use mt. If a catcher vessel reported discards station that receives or delivers a separate logsheet for each management on a blue DFL but did not deliver groundfish harvested from the GOA or program. If harvest is not under one of groundfish, enter ‘‘0’’ in this column. BSAI in association with a shoreside the listed management programs, leave (G) IR/IU species (see § 679.27). Enter processor or SFP as defined in blank. the species code of IR/IU species and paragraph (c)(5) of this section or a (vi) Delivery information. The the estimated total round weight for mothership as defined in paragraph operator must record delivery each IR/IU species, if applicable; (c)(6) of this section, must complete and information (see paragraphs (c)(6)(vi)(A) indicate whether estimated weight is to retain a separate BSR for each delivery through (H) of this section) when the nearest pound or the nearest 0.001 of unprocessed groundfish or donated unprocessed groundfish deliveries are mt. Use one line to record information prohibited species received from a received by the mothership from a for each IR/IU species, including species catcher vessel on behalf of an associated buying station or a catcher vessel. If no code and amount of catch. If more than processor. deliveries are received for a given day, one IR/IU species are to be recorded, the (ii) BSR attachments. The operator or write ‘‘no deliveries.’’ operator must use a separate line for manager must ensure that the following (A) Type of delivery. Enter ‘‘CV’’ or each species. (see paragraphs (d)(1)(ii)(A) through (C) ‘‘BS’’ to indicate if delivery was from a (H) ADF&G fish ticket numbers. If of this section) accompanies each catcher vessel or buying station, receiving unprocessed groundfish from groundfish delivery from the landing respectively. a catcher vessel, record the ADF&G fish site to the associated processor:

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00020 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76155

(A) A complete and accurate BSR that (v) Gear type. Indicate gear type of (E) Estimated total groundfish hail describes the delivery; harvester. weight. Enter the estimated total (B) Any blue DFL logsheets or (vi) Federal reporting area. Indicate groundfish hail weight or actual scale equivalent printed ELB discard reports Federal reporting area (see Figures 1 and weight of delivery. Estimated total hail received from a catcher vessel; and 3 to this part) from which groundfish weight is an estimate of the total weight (C) Copies of all ADF&G fish tickets were harvested. of the entire catch without regard to issued to the catcher vessel on behalf of (vii) Crab protection areas. If species. Indicate whether to the nearest the associated processor. harvester gear type was trawl and gear pound or to the nearest 0.001 mt. (iii) The operator of a catcher vessel, retrieval occurred in the COBLZ or (x) Discard and disposition by prior arrangement with an associated RKCSA (see Figures 11 and 13 to this information—(A) Discard. The operator processor, may function as a buying part), use two separate BSRs to record or manager of a buying station must station for his own catch as follows: the information: one BSR for the record in a BSR, discard or disposition (A) By shipping his groundfish catch reporting area that includes COBLZ or information that: with a copy of the BSR directly to that RKCSA, and a second BSR to record the (1) Occurred on and was reported by processor via truck or airline in the information from the reporting area that a catcher vessel on a blue logsheet; event that the processor is not located does not include COBLZ or RKCSA. (2) Occurred on the buying station where the harvest is offloaded; or prior to delivery to an associated (viii) Associated processor. Enter the (B) By driving a truck that contains processor; and his catch and a copy of the BSR to the name, ADF&G processor code, FFP (3) Was recorded on a blue logsheet processor. number or FPP number of the associated submitted to the buying station by a (2) Data entry time limits. The processor, date (mm/dd/yyyy) and time catcher vessel when no groundfish were operator or manager of a buying station (A.l.t., military format) delivery was delivered by the catcher vessel (for must record in the BSR all required completed. example, disposition code 95 describes information and sign the BSR within 2 (ix) Catcher vessel delivery fish or fish products eaten onboard or hours of completion of delivery from a information—(A) Catcher vessel taken off the vessel for personal use). catcher vessel. identification. Name and ADF&G vessel (B) No discards. If no discards or (3) Required information, if inactive. registration number of catcher vessel disposition for a delivery, write ‘‘no The operator or manager of a buying making the delivery. discards.’’ station is not required to record (B) Non–submittal of discard report. (C) Discard or disposition weight. information if inactive. Indicate whether the blue logsheet was Total discard or disposition weight of (4) Required information, if active. A received from the catcher vessel at the groundfish and herring PSC by species buying station is active when receiving, time of catch delivery. If the blue code and product code (indicate discarding, or delivering groundfish for logsheet is not received from the catcher whether to nearest pound or to the an associated processor. The operator or vessel, enter ‘‘NO’’ and one of the nearest 0.001 mt). manager of a buying station must record following response codes to describe the (D) PSC discard or disposition the following information (see reason for non–submittal. numbers. Total PSC discard or paragraphs (d)(4)(i) through (x) of this disposition number of animals by section) on a BSR for each delivery: NON-SUBMITTAL OF DIS- CODE species code and product code. (i) Original/revised report. If a BSR is CARD REPORT (e) Interagency Electronic Reporting the first submitted to the Regional (1) The catcher vessel does ‘‘P’’ System (IERS) and eLandings—(1) Administrator for a given date, gear not have an FFP Responsibility—(i) Hardware, software, type, and reporting area, indicate and Internet connectivity. A User must ‘‘ORIGINAL REPORT.’’ If a report is a (2) The catcher vessel is ‘‘P’’ obtain at his or her own expense correction to a previously submitted under 60 ft (18.3 m) LOA and hardware, software, and Internet BSR for a given date, gear type, and does not have an FFP connectivity to support Internet reporting area, indicate ‘‘REVISED submissions of commercial fishery REPORT.’’ (3) The catcher vessel is ‘‘L’’ landings for which participants report to under 60 ft (18.3 m) LOA and (ii) Identification of buying station. has an FFP NMFS: landings data, production data, Enter name and ADF&G vessel and discard or disposition data. The registration number if a vessel; or name, (4) The catcher vessel deliv- ‘‘U’’ User must enter this information via the license number, and state of license ered an unsorted codend Internet by logging on to the eLandings issuance if a vehicle. The name should system at http://elandings.alaska.gov or be recorded as it is displayed in official (5) Another reason; describe ‘‘O’’ other NMFS–approved software or by documentation. circumstances using the desktop client software. (iii) Operator or manager name and (ii) Reporting of non–IFQ groundfish. signature. The operator or manager must (C) ADF&G fish ticket number. Enter If the User is unable to submit sign the completed BSR prior to ADF&G fish ticket number issued to commercial fishery landings of non–IFQ delivery of harvest to a mothership, catcher vessel. groundfish due to hardware, software, shoreside processor, or SFP. This (D) Species codes and scale weight. In or Internet failure for a period longer signature is verification by the operator addition to recording the estimated total than the required reporting time, contact or manager of acceptance of the delivery weight or actual scale weight of NMFS Inseason Management at 907– responsibility required in paragraphs a catcher vessel delivery, if the operator 586–7228 for instructions. When the (d)(1) and (2) of this section. or manager of the buying station sorted hardware, software, or Internet is (iv) Management program. Indicate the delivery prior to delivery to an restored, the User must enter this same whether harvest occurred under a associated processor, he or she may information into eLandings or other management program (see paragraph enter specific species code and scale NMFS–approved software. (a)(1)(iii) of this section). If harvest is weights of individual species to the (iii) Reporting of IFQ crab, IFQ not under one of the listed management BSR; indicate whether to the nearest halibut, and IFQ sablefish. If the User is programs, leave blank. pound or to the nearest 0.001 mt. unable to submit commercial fishery

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00021 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76156 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

landings of IFQ crab, IFQ halibut, CDQ (3) Information required for eLandings applicable FFP number, FPP number, halibut, or IFQ sablefish due to processor registration form. The User Registered Buyer permit number, and hardware, software, or Internet failure must enter the following information Registered Crab Receiver permit for a period longer than the required (see paragraphs (e)(3)(i) through (ix) of number. reporting time, or a change must be this section) to obtain operation (ix) UserID registration for primary made to information already submitted, registration and UserID registration: User. Each operation requires a primary the User must complete an IFQ manual (i) Operation type. Select the User. Enter the following information landing report. Manual landing operation type from the dropdown list for the primary User for the new instructions must be obtained from OLE, according to the following table: operation: create and enter a UserID, Juneau, AK, at 800–304–4846 (Select initial password, company name, User Option 1). For this Federal Enter one of these name (name of the person who will use eLandings operation the UserID), city and state where the (A) The User must complete all category: types: questions on the manual report, even if operation is located, business telephone only one item has changed. The (A) Shoreside (1) Plant/receiver number, business fax number, business following additional information is processor or SFP e–mail address, security question, and required: whether the report is original security answer. or revised, name, telephone number, (2) Custom processing (4) Information entered automatically and fax number of individual for eLandings landing report. eLandings (B) Mothership At-sea submitting the manual landing report. autofills the following fields from (B) The User must fax the IFQ manual processor registration records (see (C) Catcher/proc- At-sea paragraph (e)(2) of this section): UserID, landing report to 907–586–7313. essor (C) The User must retain the paper processor company name, business copies of IFQ manual landing reports as (D) Buying station (1) Tender telephone number, e–mail address, port indicated at paragraph (a)(5) of this of landing, ADF&G processor code, and (2) Buying station section and make them available upon Federal permit number. The User must request of NMFS observers and review the autofilled cells to ensure that (ii) Operation name. Enter a name authorized officers as indicated at they are accurate for the landing that is that will refer to the specific operation. paragraph (a)(6) of this section. taking place. eLandings assigns a unique For example, if the plant is in Kodiak (2) eLandings processor registration. landing report number and an ADF&G and the company is East Pacific electronic fish ticket number upon (i) Before a User can use the eLandings Seafoods, the operation name might system to report landings, production, completion of data entry. read ‘‘East Pacific Seafoods–Kodiak.’’ (5) Shoreside processor or SFP discard or disposition data, he or she (iii) ADF&G processor code. Enter landings report. The manager of a must request authorization to use the ADF&G processor code. shoreside processor or SFP that receives system, reserve a unique UserID, and (iv) Federal permit number. Enter all groundfish from a catcher vessel issued obtain a password by using the Internet the federal permits associated with the an FFP under § 679.4 and that is to complete the eLandings processor operation. required to have an FPP under § 679.4(f) registration at https:// (A) Groundfish shoreside processor or must use eLandings or other NMFS– elandings.alaska.gov/elandings/ SFP. If a groundfish shoreside processor approved software to submit a daily Register. or SFP, enter the FPP number. landings report during the fishing year (ii) Upon registration acceptance, the (B) Groundfish catcher/processor or to report processor identification User must print, sign, and mail the User mothership. If a groundfish catcher/ information and the following Agreement Form to NMFS/RAM processor or mothership, enter the FFP information under paragraphs (e)(5)(i) eLandings Registration, P.O. Box 21668, number. through (iii) of this section: Juneau, AK 99802–1668; or fax a signed (C) Registered Buyer. If a Registered (i) Information entered for each form to 907–586–7354, Attn: eLandings Buyer, enter the Registered Buyer groundfish delivery to a shoreside Registration; or deliver the signed form permit number. processor and SFP. The User for a by courier to NMFS/RAM eLandings (D) Registered Crab Receiver. If a shoreside processor or SFP must enter Registration, 709 West Ninth Street, Registered Crab Receiver, enter the the following information (see Suite 713, Juneau, AK 99801. Registered Crab Receiver permit paragraphs (e)(5)(i)(A) through (C) of Confirmation will be e–mailed to number. this section) for each groundfish indicate that the User is registered, (v) Port code. Enter the home port delivery (other than IFQ sablefish) authorized to use eLandings, and that code (see Tables 14a, 14b, and 14c to provided by the operator of a catcher the UserID and User’s account are this part) for the operation. vessel, the operator or manager of an enabled. (vi) ADF&G vessel registration associated buying station, and from (iii) The User’s signature on the number. If a mothership, catcher/ processors for reprocessing or registration form means that the User processor, or tender operation, the rehandling product into eLandings or agrees to the following terms (see operator must enter the ADF&G vessel other NMFS–approved software: paragraphs (e)(2)(iii)(A) through (C) of identification number of the vessel. (A) Delivery information. (1) Number this section): (vii) Vehicle license number. If a of observers onboard. (A) To use eLandings access buying station operation that is a (2) For crew size, enter the number of privileges only for submitting legitimate vehicle, enter vehicle license number licensed crew aboard the vessel, fishery landing reports; and the state of license issuance. including the operator. (B) To safeguard the UserID and (viii) Physical operation. If a buying (3) Management program name and password to prevent their use by station or custom processor, enter the identifying number, if any, in which unauthorized persons; and following information to identify the harvest occurred (see paragraph (C) To ensure that the User is associated processor where the (a)(1)(iii) of this section). authorized to submit landing reports for processing will take place: operation (4) ADF&G groundfish statistical area the processor permit number(s) listed. type, ADF&G processor code, and of harvest.

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00022 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76157

(5) For date of landing, enter date (1) Discard or disposition of fish: that (6) If the delivery is received from a (mm/dd/yyyy) that the delivery was occurred on and was reported by a tender, enter the ADF&G vessel completed. catcher vessel; that occurred on and was registration number of the tender. (6) Indicate (YES or NO) whether reported by a buying station; and that (7) If delivery received from a catcher delivery is from a buying station. occurred prior to, during, and/or after vessel, enter the ADF&G vessel (7) If the delivery is received from a production of groundfish at the registration number of the vessel. buying station other than a tender, shoreside processor or SFP. Discards (8) Indicate whether the blue logsheet indicate the name of the buying station. and dispositions also must be recorded was received from the catcher vessel at If the delivery is received from a buying when no groundfish are delivered but the time of catch delivery. If the blue station that is a tender, enter the ADF&G the blue DFL is submitted by a catcher logsheet was not received from the vessel registration number. vessel containing records of discards or catcher vessel, enter ‘‘NO’’ and select a (8) If delivery is received from a disposition. code from the following table to explain catcher vessel, indicate the ADF&G (2) If groundfish or PSC herring, enter the reason provided by the catcher vessel registration number of the vessel. species code, delivery condition code, vessel for not supplying this copy. (9) Indicate whether the blue logsheet disposition code, and weight (to the was received from the catcher vessel at nearest pound), and NON-SUBMITTAL OF DIS- CODE the time of catch delivery. If the blue (3) If PSC halibut, salmon, or crab, CARD REPORT logsheet is not received from the catcher enter species code, delivery condition vessel, enter ‘‘NO’’ and select the (i) The catcher vessel does ‘‘P’’ code, disposition code, and count (in not have an FFP applicable code from the following table numbers of animals). to explain the reason provided by the (ii) Submittal time limit. The User for (ii) The catcher vessel is ‘‘P’’ catcher vessel for not supplying this a shoreside processor or SFP must enter under 60 ft (18.3 m) LOA and copy: information described at paragraph does not have an FFP (e)(5)(i) of this section into eLandings or NON-SUBMITTAL OF DIS- (iii) The catcher vessel is ‘‘L’’ CARD REPORT CODE other NMFS–approved software for each groundfish delivery from a specific under 60 ft (18.3 m) LOA and has an FFP (i) The catcher vessel does ‘‘P’’ vessel by noon of the day following not have an FFP completion of the delivery. (iv) The catcher vessel deliv- ‘‘U’’ (iii) Compliance. By using eLandings, ered an unsorted codend (ii) The catcher vessel is ‘‘P’’ the User for the shoreside processor or under 60 ft (18.3 m) LOA and SFP and the catcher vessel operator or (v) Another reason; describe ‘‘O’’ does not have an FFP buying station operator or manager circumstances providing information to the User for (iii) The catcher vessel is ‘‘L’’ (9) Gear type of harvester. under 60 ft (18.3 m) LOA and the shoreside processor or SFP accept has an FFP the responsibility of and acknowledge (10) Total estimated round weight by compliance with § 679.7(a)(10). species (pounds). (iv) The catcher vessel deliv- ‘‘U’’ (6) Mothership landings report. The (11) ADF&G fish ticket number ered an unsorted codend operator of a mothership that is issued provided to catcher vessel (eLandings an FFP under § 679.4(b) and that assigns an ADF&G fish ticket number to (v) Another reason; describe ‘‘O’’ the landing report). circumstances receives groundfish from catcher vessels required to have an FFP under § 679.4 (B) Discard or disposition is required to use eLandings or other information. (1) The User must record (10) Gear type of harvester. discard or disposition information that (11) Total estimated hail weight (to NMFS–approved software to submit a occurred on and was reported by a the nearest pound). daily landings report during the fishing catcher vessel; that occurred on and was (12) ADF&G fish ticket number year to report processor identification provided to catcher vessel (eLandings information and the following reported by a buying station; and that assigns an ADF&G fish ticket number to information under paragraphs (e)(6)(i) occurred prior to, during, and after the landing report). through (iii) of this section): production of groundfish at the (B) Landings information. The User (i) Information entered for each mothership. Discards and dispositions for a shoreside processor or SFP must groundfish delivery to a mothership. also must be recorded when no record the following landings The User for a mothership must enter groundfish are delivered but the blue information (see paragraphs the following information (see DFL is submitted by a catcher vessel (e)(5)(i)(B)(1) and (2) of this section) for paragraphs (e)(6)(i)(A)(1) through (11) of containing records of discards or all retained species from groundfish this section) provided by the operator of disposition. deliveries: a catcher vessel, operator or manager of (2) If groundfish or PSC herring, enter (1) Date of landing (mm/dd/yyyy). an associated buying station, or species code, delivery condition code, (2) Landed scale weight (to the nearest information received from processors disposition code, and weight (to the pound) by species code and delivery for reprocessing or rehandling product. nearest pound), and condition code. Obtain actual weights (A) Delivery information. (1) Number (3) If PSC halibut, salmon, or crab, for each groundfish species received of observers onboard. enter species code, delivery condition and retained by: (2) Crew size (including operator). code, disposition code, and count (in (i) Sorting according to species codes (3) Management program name and numbers of animals). and direct weighing of that species, or identifying number, if any, in which (ii) Submittal time limit. The User for (ii) Weighing the entire delivery and harvest occurred (see paragraph a mothership must enter information then sorting and weighing the (a)(1)(iii) of this section). described at paragraph (e)(6)(i) of this groundfish species individually to (4) ADF&G groundfish statistical area section into eLandings or other NMFS– determine their weights. of harvest. approved software for each groundfish (C) Discard or disposition (5) Date (mm/dd/yyyy) that delivery delivery from a specific vessel by noon information. The User must record: was completed. of the day following the delivery day.

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00023 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76158 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

(iii) Compliance. By using eLandings, halibut sold and retained (where or transfer of the fish from the landing the User for the mothership and the retained includes fish intended for site. catcher vessel operator or buying station personal use, fish weighed and reloaded (C) Landing completion. The User for operator providing information to the for delivery to another processor, and the Registered Buyer must submit a User for the mothership accept the fish landed but rejected at the dock by completed IFQ landing report, as responsibility of and acknowledge the Registered Buyer); species codes; described in this paragraph (e)(7), compliance with § 679.7(a)(10). delivery condition code; and disposition within six hours after all IFQ halibut, (7) Registered Buyer landings report. code for each ADF&G statistical area of CDQ halibut, and IFQ sablefish are A person who is issued a Registered harvest. offloaded from a specific vessel and Buyer permit under § 679.4(d)(3) and (7) Accurate weight of IFQ sablefish prior to shipment or transfer of said fish who receives IFQ halibut or IFQ processed product obtained before the from the landing site. sablefish from an IFQ permit holder or offload may be substituted for the initial (iv) IFQ manual landing report. See who receives CDQ halibut from a CDQ accurate scale weight provided in paragraph (e)(1)(iii) of this section. permit holder at any time during the paragraph (e)(7)(i)(E)(6) of this section, (8) Registered Crab Receiver (RCR) fishing year is required to use eLandings at time of offload, if the vessel operator IFQ crab landings report. (i) A person or other NMFS–approved software to is a Registered Buyer reporting an IFQ who is issued an RCR permit under submit landings reports with the sablefish landing. § 680.4(i) of this chapter and who following information from paragraphs (8) Indicate whether initial accurate receives IFQ crab from a crab IFQ (e)(7)(i) and (ii) of this section): scale weight is given with or without ice permit holder or crab IFQ hired master (i) Information entered for each IFQ and slime. Fish which have been is required to use eLandings to submit halibut, CDQ halibut, and IFQ sablefish washed prior to weighing or which have a landings report to report every landing delivery. The User for a Registered been offloaded from refrigerated salt of IFQ crab and incidental groundfish. Buyer must enter the following water are not eligible for a 2–percent (ii) An RCR using a catcher/processor information (see paragraphs (e)(7)(i)(A) deduction for ice and slime and must be is required to submit a crab landings through (E) of this section) for each IFQ reported as fish weights without ice and report using eLandings in a format halibut, CDQ halibut, and IFQ sablefish slime. The 2–percent deduction is made approved by NMFS. NMFS will provide delivery into eLandings or other NMFS– by NMFS, not the submitter. format specifications upon request. approved software: (9) Indicate whether IFQ halibut is Interested parties may contact NMFS (A) User identification. UserID and incidental catch concurrent with legal Alaska Region, Sustainable Fisheries password of person assigned for that landing of salmon or concurrent with Division, Catch Accounting/Data system. legal landing of lingcod harvested using Quality, P.O. Box 21668, Juneau, AK (B) Landing date. Date (mm/dd/yyyy) dinglebar gear. 99802–1668, telephone 907–586–7228. of the landing. (ii) Signatures for IFQ halibut, CDQ (iii) Information entered for each IFQ (C) Landing location. Location (port halibut, or IFQ sablefish deliveries. (A) crab delivery. The User for the RCR code) of the landing (See Tables 14a, The User for the Registered Buyer must must enter the following information 14b, and 14c to this part). print the completed groundfish landing (see paragraphs (e)(8)(iii)(A) through (C) (D) Permit numbers. Permit number of report (ADF&G electronic groundfish of this section) into eLandings or other the IFQ permit holder, and any IFQ ticket) and the groundfish IFQ landing NMFS–approved software for each IFQ hired master permit holder, or CDQ receipt. The User must review the crab delivery: hired master permit holder harvesting autofilled data entry cells to ensure that (A) Permit numbers. RCR permit the fish and permit number of they are accurate for the landing that is number, IFQ permit number, and IPQ Registered Buyer receiving the IFQ taking place. permit number, as appropriate. halibut, IFQ sablefish, or CDQ halibut. (B) Operation type. (1) If a shoreside (B) The User for the Registered Buyer, (E) Delivery information. As reported processor or SFP, enter type of plus the IFQ permit holder or the IFQ by the IFQ permit holder, IFQ hired processing operation and port code from hired master permit holder or CDQ master permit holder, or CDQ hired Table 14a or 14b to this part. hired master permit holder, must master permit holder including the (2) If a catcher/processor, enter acknowledge the accuracy of the printed information in paragraphs (e)(7)(i)(E)(1) operation type from Table 14c to this IFQ halibut, CDQ halibut, or IFQ through (9) of this section): part. (1) Harvesting vessel’s ADF&G vessel sablefish landing receipt, and if (C) Delivery information. As reported registration number. necessary, IFQ manual landing report, by IFQ permit holder. (2) Gear code of gear used to harvest by entering printed name, signature, and (1) ADF&G vessel registration number IFQ halibut, IFQ sablefish, or CDQ date. of the delivering vessel. halibut. (iii) Time limits—(A) Landing hours. (2) Date (mm/dd/yyyy) fishing began. (3) ADF&G fish ticket number(s) for A landing of IFQ halibut, CDQ halibut, (3) Date (mm/dd/yyyy) of the IFQ crab the landing (after the initial eLandings or IFQ sablefish may commence only landing. report is submitted, eLandings assigns between 0600 hours, A.l.t., and 1800 (4) ADF&G fish ticket number an ADF&G fish ticket number to the hours, A.l.t., unless permission to land (automatically supplied). landing report). at a different time is granted in advance (5) ADF&G statistical area of harvest (4) ADF&G statistical area of harvest. by a clearing officer. (All ADF&G statistical areas are (5) If ADF&G statistical area is (B) Landing receipt signatures. The translated to the NMFS reporting area bisected by a line dividing two IFQ User for the Registered Buyer and the and the IPHC reporting area by regulatory areas, provide the IFQ IFQ permit holder, IFQ hired master eLandings.). regulatory area of harvest. permit holder, or CDQ hired master (6) Species code of catch from Table (6) Except as provided in paragraph permit holder must sign the groundfish 2 to part 680. (e)(7)(i)(E)(7) of this section, initial IFQ landing receipt within six hours (7) Delivery–condition codes of catch accurate scale weight(s) (to the nearest after all IFQ halibut, CDQ halibut, and from Table 3a to this part. pound) made at the time of offloading IFQ sablefish are offloaded from a (8) Number of crab retained and sold for IFQ halibut, IFQ sablefish, or CDQ harvesting vessel and prior to shipment condition code, product type, size/

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00024 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76159

grade, and sold pounds; and optionally, information and all groundfish (iii) Contents. eLandings autofills the price per pound. production data. The User must retain a following fields when creating a (9) Scale weight of deadloss (to the copy of each production report per production report for a catcher/ nearest pound) and scale weight of crab paragraphs (a)(5) and (6) of this section. processor or mothership: FFP number, retained for personal use (to the nearest (i) Contents. eLandings autofills the company name, ADF&G processor code, pound). Deadloss and personal use crab following fields when creating a User name, email address, and that an IPQ holder did not purchase are production report for a shoreside telephone number. The User must not debited from the IPQ holder’s processor or SFP: FPP number, review the autofilled cells to ensure that account. company name, ADF&G processor code, they are accurate for the current report. (iv) Information entered for IFQ crab User name, email address, and In addition, the User for the catcher/ custom processing landings. In addition telephone number. The User must processor or mothership must enter the to the information required in paragraph review the autofilled cells to ensure that information in paragraphs (e)(10)(iii)(A) (e)(8)(iii) of this section, if custom they are accurate for the current report. through (N) of this section): processing IFQ crab, the User for the In addition, the User for the shoreside (A) Date. Reporting date (mm/dd/ RCR must enter the ADF&G processor processor or SFP must enter the yyyy). code of the person for which the IFQ following information (see paragraphs (B) Designation. From Table 14c to crab was custom processed. (e)(9)(i)(A) through (F) of this section): this part, enter whether the processor is (v) Signatures for IFQ crab deliveries. (A) Date. Reporting date (mm/dd/ a catcher/processor = FCP or a (A) The User for the RCR must print the yyyy). mothership = FLD. completed crab landing report (ADF&G (B) Observers. Number of observers (C) Crew size. Including operator. electronic crab ticket) and the crab IFQ onsite. (D) Management program. Enter landing receipt. The User must review (C) Area of harvest. Whether management program and identifying the autofilled data entry cells to ensure harvested in GOA or BSAI. number, if any, in which harvest that they are accurate for the landing (D) Product description. Species code, occurred (see paragraph (a)(1)(iii) of this that is taking place. product type, and product code of section). (B) The User for the Registered Crab product. (E) Gear type of harvester. Enter the Receiver (RCR), plus the IFQ permit (E) Product weight. Enter actual scale gear type used by the harvester. (F) Federal Reporting Area of harvest. holder or IFQ hired master permit weight of product to the nearest pound. holder, must acknowledge the accuracy Enter the Federal Reporting Area where (F) No production/no deliveries of the printed IFQ crab landing receipt, harvest was made. (inactive). If there was no production or and, if necessary, IFQ manual landing (G) COBLZ or RKCSA. Indicate deliveries for the day, mark the ‘‘No report, by entering printed name, whether fishing occurred in COBLZ or Production’’ and/or ‘‘No Deliveries’’ signature, and date. RKCSA (if applicable). boxes. (vi) Time limits. (A) Except as (H) Product description. Species code, indicated in paragraph (e)(8)(vi)(B) of (ii) Submittal time limits. When active product type, and product code of this section, the User for the RCR is pursuant to paragraph (c)(5)(ii) of this product. required to submit a crab landing report section, the User for a shoreside (I) Product weight. Enter product described at this paragraph (e)(8) to processor or SFP must submit a weight in metric tons to the nearest NMFS within six hours after all crab is production report by noon each day to 0.001 mt. offloaded from the vessel. record the previous day’s production (J) No production (inactive). If there (B) For IFQ crab harvested on a information. If a shoreside processor or was no production for the day, mark the catcher/processor, the User for the RCR SFP using eLandings is not taking ‘‘No Production’’ box. is required to submit an IFQ crab deliveries over a weekend, the User or (K) Discard description. The operator landing report to NMFS by Tuesday manager may transmit the eLandings must record the discard or disposition noon after the end of each weekly production report to NMFS on the that occurred prior to, during, and after reporting period in which IFQ crab was following Monday. production of groundfish by species harvested. (10) Catcher/processor or mothership code and disposition code of discards (C) The User for the RCR and the IFQ information entered for production and disposition. permit holder or IFQ hired master report—(i) Catcher/processor. The (L) Discard weight. Daily weight of permit holder must enter printed name operator of a catcher/processor that is groundfish and the daily weight of and sign the crab IFQ landing receipt issued an FFP under § 679.4 and that herring PSC to the nearest 0.001 mt. within six hours after all crab is harvests groundfish is required to use (M) PSC numbers. Daily number of offloaded from the harvesting vessel. eLandings or other NMFS–approved PSC animals (Pacific salmon, steelhead (vii) Landing document retention. The software to submit a production report trout, Pacific halibut, king crabs, and User must retain each landing report to record and report daily processor Tanner crabs) by species codes and and landing receipt per paragraph (a)(5) identification information, groundfish product codes. of this section. production data, and groundfish and (N) ADF&G statistical area. Must be (viii) IFQ manual landing report for prohibited species discard or reported beginning January 1, 2009. crab. See paragraph (e)(1)(iii) of this disposition data. (iv) Submittal time limits. When a section. (ii) Mothership. The operator of a mothership is active pursuant to (9) Shoreside processor or SFP mothership that is issued an FFP under paragraph (c)(6)(iv) of this section, a information entered for production § 679.4 and that receives groundfish is catcher/processor longline or pot gear is report. The manager of a shoreside required to use eLandings or other active pursuant to paragraph processor or SFP that is required to have NMFS–approved software to submit a (c)(3)(iv)(B) of this section, or a catcher/ an FPP under § 679.4(f) must use production report to record and report processor trawl gear is active pursuant eLandings or other NMFS–approved daily processor identification to paragraph (c)(4)(iv)(B) of this section, software during the fishing year to information, groundfish production the User for a mothership or catcher/ submit a production report to report data, and groundfish and prohibited processor must submit a production daily processor identification species discard or disposition data. report by noon each day to record the

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00025 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76160 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

previous day’s production information. (ii) Catcher/processor longline and of the appropriate DFL or DCPL If a vessel is required to have 100 pot gear ELB. The operator of a catcher/ onboard. In the event that electronic percent observer coverage or more, the processor using longline or pot gear may transmission is not made or confirmed User may transmit a production report use a combination of a NMFS–approved for the ELB, the operator must enter for Friday, Saturday, and Sunday no catcher/processor longline or pot gear information into the paper DFL or DCPL later than noon on the following ELB and eLandings to record and report in accordance with the regulations at Monday. groundfish information. The operator paragraphs (c)(1) through (c)(4) of this (11) Printing of landing reports, may use a NMFS–approved catcher/ section. The operator must transfer any landing receipts, and production processor longline and pot gear ELB to information recorded in a DFL or DCPL reports. (i) The User daily must retain a record daily processor identification to the ELB when transmission resumes printed paper copy onsite or onboard of: information and catch–by–set function. (A) Each landing report (ADF&G information. In eLandings, the operator (iii) Enter all required information electronic groundfish tickets or must record daily processor into the ELB—(A) Inactive. The operator electronic crab tickets). identification, groundfish production must enter all required information, if (B) Each production report. data, and groundfish and prohibited inactive (see paragraph (c)(2) of this (C) If IFQ halibut, IFQ sablefish, or species discard or disposition data. section). CDQ halibut, each groundfish IFQ (iii) Catcher vessel trawl gear ELB. (B) Active. The operator must enter all landing receipt. The operator of a catcher vessel using required information, if active (see (D) If IFQ crab, each crab IFQ landing trawl gear may use a NMFS–approved paragraph (c)(3), (c)(4), or (c)(6) of this receipt. catcher vessel trawl gear ELB in lieu of section, as appropriate). (ii) In addition to paragraph (e)(11)(i) using the NMFS–prescribed catcher (1) Record the haul number or set of this section, the mothership operator vessel trawl gear DFL required at number, time and date gear set, time or User must print an additional copy of paragraph (c)(4) of this section. and date gear hauled, begin and end each landing report and provide it to the (iv) Catcher/processor trawl gear ELB. position, CDQ group number (if operator of the catcher vessel delivering The operator of a catcher/processor applicable), and hail weight for each groundfish to the mothership by 1200 using trawl gear may use a combination haul or set within 2 hours after hours, A.l.t., on Tuesday following the of a NMFS–approved catcher/processor completion of gear retrieval. end of applicable weekly reporting trawl gear ELB and eLandings to record (2) Daily complete ELB data entry and period. and report groundfish information. In printing of copies as indicated in (12) Retention and inspection of the ELB, the operator would record paragraph (f)(3)(i) of this section. landing reports, landing receipts, and daily processor identification (iv) Regularly backup ELB data. The production reports. The User must information and catch–by–haul retain a printed copy of each IFQ information. In eLandings, the operator operator must regularly backup ELB landing report (ADF&G electronic must record daily processor data to ensure that data are not lost in groundfish ticket or electronic crab identification, groundfish production the event of hardware or software ticket), crab IFQ landing receipt, data, and groundfish and prohibited problems. groundfish IFQ landing receipt, and species discard or disposition data. (v) Correct errors in ELB data. If after production report as indicated at (v) Mothership ELB. The operator of a an ELB discard report and ELB logsheet paragraphs (a)(5) and (6) of this section. mothership may use a combination of a are printed, an error is found in the The User must make available the NMFS–approved mothership ELB and data, the operator must make any printed copies upon request of NMFS eLandings to record and report necessary changes to the data, print a observers and authorized officers as groundfish information. The operator new copy of the ELB discard report and indicated at paragraph (a)(5) of this may use a NMFS–approved mothership ELB logsheet, and export the revised file section. ELB to record daily processor to NMFS. The operator must retain both (f) Electronic logbooks (ELBs). The identification information and catcher the original and revised ELB reports. operator may use a combination of a vessel and buying station groundfish (3) Printed copies. Upon completion NMFS–approved ELB (instead of a DFL delivery information. In eLandings, the of ELB data entry each day, the operator or DCPL) and eLandings to record and operator must record daily processor must print the following information report groundfish information. To identification, groundfish production (see paragraphs (f)(3)(i) and (ii) of this satisfy ELB use requirements, the data, and groundfish and prohibited section) in the NMFS–specified format: operator after data entry must routinely species discard or disposition data. (i) ELB logsheet. (A) Print a copy of an create the following three products: an (vi) If using a NMFS–approved ELB, ELB logsheet when a vessel is active, by ELB logsheet, an ELB discard report, the operator is not required to quarterly noon each day to record the previous and an ELB data export. submit logsheets to OLE. day’s ELB information. (1) Responsibility. The operator must (2) Requirements for using an ELB— (B) Print one ELB logsheet to describe notify the Regional Administrator by fax (i) Use a NMFS–approved ELB. The a continuous period of inactivity, when at 907–586–7465 to ensure that NMFS operator must use only a NMFS– a vessel is inactive. knows that the operator is using a approved ELB. The Regional (C) Print a copy of the ELB logsheet NMFS–approved ELB instead of a DFL Administrator maintains a list of for the observer’s use if an observer is or DCPL, prior to participating in any approved ELBs on the Alaska Region present, by noon each day to record the Federal fishery. NMFS website at http:// previous day’s ELB information. (i) Catcher vessel longline and pot alaskafisheries.noaa.gov (see also (ii) ELB discard report. (A) Print a gear ELB. The operator of a catcher § 679.28(h) for approval of vendor copy of an ELB discard report upon vessel using longline and pot gear may software). completion of each fishing trip or each use a NMFS–approved catcher vessel (ii) Keep a current copy of DFL or offload of fish. longline or pot gear ELB in lieu of using DCPL onboard. To ensure proper (B) If an observer is present, print a the NMFS–prescribed catcher vessel recording of the vessel’s fishing activity copy of the ELB discard report for the longline or pot gear DFL required at in the event of problems with the ELB, observer’s use upon completion of each paragraph (c)(3) of this section. the operator must keep a current copy fishing trip or each offload of fish.

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00026 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76161

(4) Signatures—(i) ELB logsheet. The operator of a mothership or the manager submitted by fax to 907–586–7131, or by operator daily must sign and date each of a shoreside processor or SFP will e–mail to printed ELB logsheet by noon each day forward the ELB data export to NMFS as [email protected]. to record the previous day’s ELB an email attachment within 24 hours of (2) Exceptions—(i) VMS onboard. The information. The signature of the completing receipt of the catcher operator of a catcher/processor or operator is verification of acceptance of vessel’s catch. mothership is not required to submit to the responsibility required in paragraph (8) Return receipt. (i) Upon receiving NMFS a check–in report or check–out (a)(2) of this section. an ELB data export, NMFS will generate report if the vessel is carrying onboard (ii) ELB discard report. The operator a dated return–receipt to confirm receipt a transmitting VMS that meets the daily must sign and date each printed of the ELB data. If errors exist in the requirements of § 679.28(f). ELB discard report upon completion of data transmitted to NMFS, the receipt (ii) Two adjacent reporting areas. If on each fishing trip or each offload of fish. will identify the errors. If errors are the same day a catcher/processor The signature of the operator is identified, the operator must correct the intends to fish in two adjacent reporting verification of acceptance of the errors and send a revised transmission areas (an action which would require responsibility required in paragraph to NMFS which will then confirm submittal of check–out reports and (a)(2) of this section. acceptance of the ELB data. (5) Submittal time limits. (i) The check–in reports multiple times a day (ii) The operator must retain the when crossing back and forth across a operator of a catcher vessel using an NMFS return receipt as described in ELB must upon delivery of catch submit reporting area boundary), and the two paragraph (a)(5) of this section. reporting areas have on that day and the ELB discard report to the (iii) If a return receipt from NMFS is mothership, shoreside processor, or time an identical fishing status for every not received within 24 hours, the species, the operator must: SFP. operator of the catcher vessel, the (A) Submit to NMFS a check–in (ii) The operator or manager of a operator of a catcher/processor, the report to the first area prior to entering buying station that receives groundfish operator of the mothership, or the the first reporting area, and catch from a catcher vessel using an ELB manager of the shoreside processor or must upon delivery of catch submit the SFP forwarding the ELB data export for (B) Submit to NMFS a check–in report ELB discard report to the mothership, the operator of the catcher vessel, must to the second area prior to entering the shoreside processor, or SFP, and submit contact NMFS by telephone at 907–586– second reporting area. the ELB data export directly to the 7228 or fax at 907–586–7131 for (C) Remain within 10 nautical miles Regional Administrator or through the instructions. (18.5 km) of the boundary described in mothership, shoreside processor, or (g) * * * paragraph (h)(2)(i) of this section. SFP. (1) General requirements. Except as (D) If the catcher/processor proceeds (6) Retention. The operator must keep provided in paragraphs (g)(2)(i) through in the second reporting area beyond 10 a signed copy of each ELB logsheet and (v) of this section, the operator or nautical miles (18.5 km) of the boundary each ELB discard report, filed in manager must record on a PTR those between the two areas, the operator sequence for immediate access by species that are listed in Tables 2a and must submit a check–out report from authorized personnel as described at 2c to this part when those species are the first reporting area. The operator paragraph (a)(5) of this section. must submit a check–out report from (7) ELB data export. The operator transferred out of the facility or off the the second area upon exiting that must transmit an ELB data export to vessel and may also record species reporting area. NMFS at the specified e–mail address listed in Table 2d to this part. within 24 hours of completing each * * * * * (3) Transit through reporting areas. fishing trip or offload, as described (h) Check–in/Check–out report—(1) The operator of a catcher/processor or under paragraph (f)(7)(i) or (ii) of this Requirement. Except as described in mothership is not required to submit a section in the following manner: paragraph (h)(2) of this section, the check–in or check–out report if the (i) Directly to NMFS as an email operator of a catcher/processor or vessel is transiting through a reporting attachment; or mothership and manager of a shoreside area and is not fishing or receiving fish. (ii) If a catcher vessel, send directly to processor or SFP must submit to NMFS (4) Time limits and submittal. Except NMFS as an email attachment or to a check–in report (BEGIN message) prior as indicated in paragraph (h)(2) of this NMFS through a shoreside processor, to becoming active and a check–out section, the operator or manager must SFP, or mothership who received his/ report (CEASE message) for every submit a check–in report and a check– her groundfish catch. Through a prior check–in report submitted. The check– out report according to the following agreement with the catcher vessel, the in report and check–out report must be table:

For ... If you are a ... Submit a BEGIN message Submit a CEASE message

(i) Each reporting area, except (A) C/P using trawl gear Before gear deployment. Within 24 hours after departing a area 300, 400, 550, or 690 reporting area but prior to checking in to another reporting area.

(B) C/P using longline or pot gear Before gear deployment. May be Upon completion of gear retrieval checked in to more than one area and within 24 hours after depart- simultaneously. ing each reporting area.

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00027 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76162 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

For ... If you are a ... Submit a BEGIN message Submit a CEASE message

(C) MS Before receiving groundfish, must Within 24 hours after receipt of check–in to reporting area(s) fish is complete from that report- where groundfish were harvested. ing area. May be checked in to more than If receipt of groundfish from a re- one area simultaneously. porting area is expected to stop for at least one month during the fishing year and then start up again, may submit check–out report for that reporting area.

(ii) COBLZ or RKCSA (A) C/P using trawl gear Prior to fishing. Submit one Upon completion of gear retrieval check–in for the COBLZ or for groundfish, submit a separate RKCSA and another check–in for check–out for the COBLZ or the area outside the COBLZ or RKCSA and another check–out for RKCSA. the area outside the COBLZ or RKCSA.

(B) MS Before receiving groundfish har- Upon completion of groundfish re- vested with trawl gear that were ceipt, submit a separate check– harvested in the COBLZ or out for the COBLZ or RKCSA and RKCSA, submit one check–in for another check–out for the area the COBLZ or RKCSA and an- outside the COBLZ or RKCSA. other check–in for the area outside the COBLZ or RKCSA.

(iii) Gear Type (A) C/P If in the same reporting area but Upon completion of gear retrieval using more than one gear type, for groundfish, submit a separate prior to fishing submit a separate check–out for each gear type for check–in for each gear type. which a check–in was submitted.

(B) MS If harvested in the same reporting Upon completion of receipt of area but using more than one groundfish, submit a separate gear type, prior to receiving check–out for each gear type for groundfish submit a separate which a check–in was submitted. check–in for each gear type.

(iv) CDQ (A) MS Prior to receiving groundfish CDQ, Within 24 hours after receipt of if receiving groundfish under more groundfish CDQ has ceased for than one CDQ number, use a each CDQ number. separate check–in for each CDQ number.

(B) C/P Prior to fishing, submit a separate Within 24 hours after groundfish check–in for each CDQ number. CDQ fishing for each CDQ number has ceased.

(v) Exempted or Research (A) C/P Prior to fishing, submit a separate Upon completion of receipt of Fishery check–in for each type. groundfish submit a separate check–out for each type for which a check–in was submitted.

(B) MS Prior to receiving groundfish, sub- Upon completion of receipt of mit a separate check-in for each groundfish submit a separate type. check–out for each type for which a check–in was submitted.

(vi) Aleutian Islands Pollock (A) C/P Prior to AIP fishing. Within 24 hours after completion (AIP) of gear retrieval for AIP.

(B) MS Before receiving AIP. Within 24 hours after receipt of AIP has ceased.

(vii) Processor Type C/P, MS If a catcher/processor and func- Upon completion of simultaneous tioning simultaneously as a activity as both catcher/processor mothership in the same reporting and mothership, a separate area, before functioning as either check–out, one for catcher/proc- processor type. essor and one for mothership.

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00028 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76163

For ... If you are a ... Submit a BEGIN message Submit a CEASE message

(viii) Change of fishing year (A) C/P, MS If continually active through the If a check–out report was not pre- end of one fishing year and at the viously submitted during a fishing beginning of a second fishing year for a reporting area, submit a year, submit a check–in for each check–out report for each report- reporting area to start the year on ing area on December 31. January 1.

(B) SS, SFP If continually active through the If a check–out report was not pre- end of one fishing year and at the viously submitted during a fishing beginning of a second fishing year, submit a check–out report year, submit a check–in to start on December 31. the year on January 1.

(ix) Interruption of production SS, SFP, MS n/a If receipt of groundfish is expected to stop for at least one month during the fishing year and then start up again, the manager or operator may choose to submit a check– out report.

(5) Required information. The shoreside processor or SFP must record on a check–in report and a check–out operator of a catcher/processor or the information in the following table report, as appropriate. mothership and the manager of a

Check-in Report Check-out Report Required information MS C/P SS, SFP MS C/P SS, SFP

(i) Whether an original or revised report X X X X X X

(ii) Vessel name, ADF&G processor code, FFP X X X X number

(iii) Processor name, ADF&G processor code, X X FPP number

(iv) Representative name, business telephone X X X X X X number, business fax number

(v) COMSAT number (if applicable) X X X X

(vi) Management program name (see paragraph X X X X (a)(1)(iii) of this section) and identifying number (if any). If harvest is not under one of these management programs, leave blank.

(vii) Processor type, gear type X X X X

(viii) Date (mm/dd/yyyy) and time (A.l.t., military format)

(A) When receipt of groundfish will begin X X

(B) When gear deployment will begin X

(D) When the vessel departed the reporting area X

(ix) Position coordinates

(A) Where groundfish receipt begins X

(B) Where receiving groundfish (if SFP): X

(D) Where the last receipt of groundfish was X completed

(E) Where the vessel departed the reporting area X

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00029 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76164 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

Check-in Report Check-out Report Required information MS C/P SS, SFP MS C/P SS, SFP

(x) Reporting area code

(A) Where gear deployment begins X

(B) Where groundfish harvest occurred X

(D) Where the vessel departed the reporting area X

(xi) Primary and secondary target species (A change in intended target species within the same reporting area does not require a new BEGIN message.)

(A) Expected to be received the following week X

(B) Expected to be harvested the following week X

(xii) Indicate (YES or NO) whether this is a X check-in report

(xiii) If YES, indicate

(A) If checking-in for the first time this fishing X year

(B) If checking-in to restart receipt and proc- X essing of groundfish after filing a check–out report

(xiv) Indicate (YES or NO) whether this is a X check-out report

(xv) If YES, indicate product weight of all fish or X X fish products (including non groundfish) remaining at the facility (other than public cold storage) by species code and product code. In- dicate if recorded to the nearest pound or to the nearest 0.001 mt.

(i) Weekly production report (WPR). (2) IFQ landing—(i) Remain at a single offload site all sablefish The WPR is removed from use. Instead landing site. Once the landing has onboard the vessel. of a WPR, the operator of a mothership commenced, the IFQ permit holder, the * * * * * or catcher/processor and the manager of IFQ hired master permit holder, or the ■ 7. In § 679.7, paragraph (a)(1)(iii) is a shoreside processor or SFP must CDQ hired master permit holder, and added to read as follows: submit all landings information, the harvesting vessel may not leave the production information, and discard landing site until the IFQ halibut, IFQ § 679.7 Prohibitions. and disposition information using sablefish, or CDQ halibut account is * * * * * eLandings or other NMFS–approved properly debited (see § 679.40(h)). (a) * * * software (see paragraph (e) of this (ii) No movement of IFQ halibut, CDQ (1) * * * section). halibut, or IFQ sablefish. The offloaded (iii) Conduct fishing operations from * * * * * IFQ halibut, CDQ halibut, or IFQ a vessel using other than the operation (l) * * * sablefish may not be moved from the type(s) specified on the FFP (see (1) * * * landing site until the IFQ Landing § 679.4(b)) issued for that vessel. (iv) Exemption—(A) Halibut. An IFQ Report is completed through eLandings * * * * * landing of halibut of 500 lb or less of or other NMFS–approved software and ■ 8. In § 679.22, paragraph (b)(6) that IFQ weight determined pursuant to the IFQ permit holder’s or CDQ permit was revised on June 1, 2006 (71 FR § 679.40(h) and concurrent with a legal holder’s account is properly debited (see 31107) effective July 3, 2006 through landing of salmon harvested using hand § 679.40(h)). December 31, 2010, is removed and troll gear or power troll gear is exempt (iii) Single offload site—(A) IFQ reserved, and paragraphs (b)(5)(i) and from the PNOL required by this section. halibut and CDQ halibut. The vessel (ii) are revised to read as follows: (B) Lingcod. An IFQ landing of operator who lands IFQ halibut or CDQ halibut of 500 lb or less of IFQ weight halibut must continuously and § 679.22 Closures. determined pursuant to § 679.40(h) and completely offload at a single offload * * * * * concurrent with a legal landing of site all halibut onboard the vessel. (b) * * * lingcod harvested using dinglebar gear (B) IFQ sablefish. The vessel operator (5) * * * is exempt from the PNOL required by who lands IFQ sablefish must (i) No FFP holder may fish for this section. continuously and completely offload at groundfish in the Sitka Pinnacles

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00030 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76165

Marine Reserve, and no vessel named (i) Register the vessel’s VMS unit with following standards in paragraphs on an FFP may be anchored in the Sitka an appropriate service provider; (h)(1)(iii)(A) through (H) of this section): Pinnacles Marine Reserve, as described (ii) Use VMS check–in report to (A) Has fields for the entry of all in Figure 18 to this part. contact OLE by fax at 907–586–7703 information required for a paper DFL or (ii) No person fishing under an IFQ and provide the date (mm/dd/yyyy), DCPL as described in § 679.5(c)(3) and halibut permit may fish for halibut and vessel name, USCG documentation (4), as appropriate. no person fishing under an IFQ number, FFP number or Federal crab (B) The software must automatically sablefish permit may fish for sablefish vessel permit number, name and time and date stamp each printed copy in the Sitka Pinnacles Marine Reserve; telephone number of contact person, of the ELB logsheet and ELB discard and no vessel with an IFQ permit holder and VMS transmitter ID or serial report and clearly identify the first or IFQ hired master permit holder number; and printed copy as an original. If any onboard may be anchored in the Sitka (iii) Call OLE at 907–586–7225, changes are made to the data in the ELB, Pinnacles Marine Reserve, as described Monday through Friday, between the subsequent printed copies must clearly in Figure 18 to this part. hours of 0800 hours, A.l.t., and 1630 be identified as revised. The software * * * * * hours, A.l.t., at least 72 hours before must be designed to prevent the ■ leaving port and receive confirmation operator from overriding this feature. 9. In § 679.28: (C) The software must export data as ■ A. Paragraph (b)(2)(v) is removed and that the transmissions are being received. an ASCII comma delimited text file, xml reserved. file, or other format approved by NMFS. ■ B. Paragraphs (f)(4)(iii) and (h) are (5) What must the vessel owner do when the vessel replaces a VMS (D) The software must integrate with added. the vessel’s global positioning system ■ C. Paragraphs (a), (b)(2)(iii), (b)(2)(iv), transmitter? A vessel owner who must use a VMS and who intends to replace (GPS) to allow vessel location fields to (b)(2)(vi)(A), (f)(4)(i), (f)(4)(ii), and (f)(5) be completed automatically. are revised. a transmitter, must follow the reporting and confirmation procedure for the (E) When the software is started, it The revisions and additions read as must clearly show the software version follows: replacement transmitter, as described in paragraph (f)(4) of this section. number. § 679.28 Equipment and operational (F) The software must be designed to * * * * * facilitate the transfer of an export file to requirements. (h) ELB software—(1) How do I get my (a) Applicability. This section NMFS as an email attachment. ELB software approved by NMFS?—(i) (G) The software must be designed to contains the operational requirements Specifications. NMFS will provide ensure that an operator can comply with for scales, observer sampling stations, specifications for ELB software upon the requirements for ELB use as bins for volumetric estimates, vessel request. Interested parties may contact described in § 679.5(f). monitoring system hardware, catch NMFS by mail at NMFS Alaska Region, (H) The software must include monitoring and control plan, and Sustainable Fisheries Division, Catch sufficient data validation capability to catcher vessel electronic logbook Accounting/Data Quality, P.O. Box prevent a submitter from accidentally software. The operator or manager must 21668, Juneau, AK 99802–1668; by transmitting a data file or printing an retain a copy of all records described in telephone at 907–586–7228. The four ELB logsheet that is incomplete or this section (§ 679.28) as indicated at types of ELB software are: contains clearly erroneous data. § 679.5(a)(5) and (6) and make available (A) Catcher vessel longline or pot gear (2) What if I need to make changes to the records upon request of NMFS (see § 679.5(c)(3)); NMFS–approved ELB software?—(i) observers and authorized officers as (B) Catcher/processor longline or pot NMFS–instigated changes. NMFS will indicated at § 679.5(a)(5). gear (see § 679.5(c)(3)); provide the developer with information (b) * * * (C) Catcher vessel trawl gear (see that affects the ELB software as soon as (2) * * * § 679.5(c)(4)); and it is available for distribution, e.g., (iii) Who may perform scale (D) Catcher/processor trawl gear (see changes in species codes or product inspections and approvals? Scales must § 679.5(c)(4)). codes. be inspected and approved by a NMFS– (ii) ELB submittal package. A vendor (ii) Developer–instigated changes. The staff scale inspector or an inspector or developer wishing to have an ELB developer must submit a copy of the designated by NMFS and trained by a approved by NMFS must submit: changed software along with NMFS–staff scale inspector. (A) A fully operational test copy of documentation describing the need for (iv) How does a vessel owner arrange the software; and the change to NMFS for review and for a scale inspection? The operator (B) An application for ELB–approval approval as described in paragraph must submit a request for a scale giving the following information (see (h)(1)(ii) of this section. NMFS will inspection at least 10 working days in paragraphs (h)(1)(ii)(B)(1) through (3) of review and approve the new version advance of the requested date of this section): according to the guidelines set forth in inspection by filing a request online or (1) Company, contact person, address, paragraph (h)(1)(iii) of this section. by printing and faxing the scale telephone number, and fax number for (iii) NMFS–approved ELB changes. If inspection request at http:// the company developing the software; changes to ELB software are approved alaskafisheries.noaa.gov/scales/ (2) Name and type of software; and by NMFS, the developer must: default.htm. (3) Printed name and signature of (A) Give the revised software a new * * * * * individual submitting the software for version number; (vi) * * * approval. (B) Notify all known ELB users of the (A) Make the vessel and scale (C) Copies of all manuals and software that a new version is available; available for inspection by the scale documentation for the software. and inspector. (iii) ELB approval. NMFS will (C) Ensure that the ELB users are * * * * * approve ELB software within 60 provided with a revised copy within 15 (f) * * * working days of receipt of all required days of notification. (4) * * * information if the software meets the * * * * *

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00031 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76166 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

■ 10. In § 679.40, paragraph (c)(3) is (i) Unprocessed landing. If offload of (4) Liability. Owners and operators of revised and paragraph (h) is added to unprocessed IFQ halibut, CDQ halibut, vessels exceeding these limitations are read as follows: or IFQ sablefish from a vessel, the scale jointly and severally liable with IFQ weight (to the nearest pound) of the permit holders and IFQ hired master § 679.40 Sablefish and halibut QS. halibut or sablefish product actually permit holders whose harvesting causes * * * * * measured at the time of offload, as the vessel to exceed these limitations. (c) * * * required by § 679.5(e)(7)(i)(E)(6) to be * * * * * (3) IFQ permit. The Regional included in the IFQ Landing Report. (j) * * * Administrator shall issue to each QS (ii) Processed landing. If offload of (8) A corporation, partnership, or holder, pursuant to § 679.4, an IFQ processed IFQ halibut, CDQ halibut, or other non–individual entity, except for permit specifying the maximum amount IFQ sablefish from a vessel, the scale a publicly held corporation, that of halibut and sablefish that may be weight (to the nearest pound) of the receives an allocation of QS must harvested with fixed gear in a specified halibut or sablefish processed product provide annual updates to the Regional IFQ regulatory area and vessel category. actually measured at or before the time Administrator identifying all current Such IFQ permits will be sent to each of offload. If the product scale weights shareholders, partners, or members to QS holder at the address on record for are taken before the time of offload, then the individual person level and that person prior to the start of the IFQ the species and actual product weight of affirming the entity’s continuing fishing season or to any IFQ holder(s) each box or container must be visibly existence as a corporation or following transfers or penalties (15 CFR marked on the outside of each container partnership, or other non–individual part 904). to facilitate inspection by OLE or entity. * * * * * designees. * * * * * ■ (h) Properly debited landing—(1) 11. In § 679.42, paragraphs (c), (h)(3), ■ 12. In § 679.50, paragraph (g)(1)(ix)(A) Permit holder’s account. Except as and (j)(8) are revised and paragraph is revised to read as follows: provided in paragraph (g) of this (h)(4) is added to read as follows: section, all IFQ halibut, CDQ halibut, § 679.50 Groundfish Observer Program. § 679.42 Limitations on use of QS and IFQ. and IFQ sablefish catch onboard a vessel * * * * * must be weighed and debited from the * * * * * (g) * * * IFQ permit holder’s account or CDQ (c) Requirements and deductions. Any (1) * * * halibut permit holder’s account under individual who harvests halibut or (ix) * * * which the catch was harvested. sablefish with fixed gear must have a (A) Ensure that transfers of observers (2) Properly debited account. A valid IFQ permit, and if a hired master at sea are carried out during daylight properly concluded groundfish IFQ is conducting the harvest, a valid IFQ hours, under safe conditions, and with landing receipt, crab IFQ landing hired master permit, aboard the vessel at the agreement of observers involved. all times during the fishing trip and receipt, or a manual IFQ landing report * * * * * which is signed by the Registered Buyer present during the landing. and IFQ permit holder or IFQ hired * * * * * §§ 679.1, 679.2, 679.4, 679.5, 679.20, 679.21, master permit holder or CDQ hired (h) * * * 679.22, 679.27, 679.28, 679.40, 679.41, master permit holder constitutes (3) Excess. An IFQ permit holder who 679.42, 679.50, 679.61, and 679.84 confirmation that the IFQ permit receives an approved IFQ allocation of [Amended] holder’s or CDQ permit holder’s account halibut or sablefish in excess of these ■ 13. At each of the locations shown in is properly debited. limitations may nevertheless catch and the Location column, remove the phrase (3) Source of debit. NMFS shall use retain all that IFQ with a single vessel. indicated in the ‘‘Remove’’ column and the following sources (see paragraphs However, two or more IFQ permit replace it with the phrase indicated in (h)(3)(i) and (ii) of this section) of holders may not catch and retain their the ‘‘Add’’ column for the number of information to debit a CDQ halibut, IFQ IFQs with one vessel in excess of these times indicated in the ‘‘Frequency’’ halibut, or IFQ sablefish account: limitations. column.

Location Remove Add Frequency

§ 679.1 introductory text under the Magnuson–Stevens Fishery Conserva- under the Magnuson–Stevens Fishery Conserva- 1 tion and Management Act and the Northern Pa- tion and Management Act, 16 U.S.C. 1801 et cific Halibut Act seq. (Magnuson–Stevens Act) and the Northern Pacific Halibut Act of 1982 (Halibut Act)

§ 679.1(a)(2) 5 AAC 28.110 5 AAC 28.111 1

§ 679.2 definition of food bank distributors food bank distributors 1 ‘‘Authorized distributor’’ (see § 679.26, Prohibited Species Donation Pro- gram)

§ 679.2 definition of paragraph (10)(ix) paragraph (14)(ix) 1 ‘‘Authorized fishing gear’’ paragraph (14)(iii) introductory text

§ 679.2 definition of paragraph (10)(iii) paragraph (14)(iii) 1 ‘‘Authorized fishing gear’’ paragraph (14)(iv)

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00032 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76167

Location Remove Add Frequency

§ 679.2 definition of paragraphs (10)(iii) and (iv) paragraphs (14)(iii) and (iv) 1 ‘‘Authorized fishing gear’’ paragraph (14)(v)

§ 679.2 definition of authorized to harvest authorized to harvest 1 ‘‘Basis species’’ (see Tables 10 and 11 to this part)

§ 679.2 definition of Catcher/processor means: Catcher/processor (C/P) means: 1 ‘‘Catcher/processor’’ introductory text

§ 679.2 definition of Catcher vessel means Catcher vessel (CV) means 1 ‘‘Catcher vessel’’

§ 679.2 definition of Weekly Production Report production report 1 ‘‘Legal rockfish landing for purposes of qualifying for the Rockfish Program’’ paragraph (2)(i)

§ 679.2 definition of other entity other non-individual entity 1 ‘‘Person’’

§ 679.2 definition of regulated under this part issued an FFP under § 679.4(b) 1 ‘‘Prohibited species’’

§ 679.2 definition of Stationary floating processor Stationary floating processor (SFP) 1 ‘‘Stationary floating processor’’

§ 679.2 definition of other entity other non-individual entity 1 ‘‘U.S. Citizen’’ paragraph (2)(ii)

§ 679.2 definition of § 679.5(b)(3) § 679.4(b)(3) 1 ‘‘Vessel operations category’’

§ 679.2 definition of (see § 679.5(i)) is no longer required (see § 679.5(e)(9) and (10)) 1 ‘‘Weekly production report (WPR)’’

§ 679.4(b)(5)(ii) owner; and the name owner; and if applicable, the name 1

§ 679.4(b)(5)(iii) horsepower; whether this is a vessel of the horsepower; and whether this is a vessel of the 1 United States; and whether this vessel will be United States. used as a stationary floating processor.

§ 679.4(d)(1)(i), (d)(2)(i), suspended, or modified suspended, surrendered in accordance with para- 1 (d)(3)(i), and (d)(3)(iv) graph (a)(9) of this section, or modified

§ 679.4(k) heading Licenses for license limitation groundfish or crab Licenses for license limitation program (LLP) 1 species groundfish or crab species

§ 679.4(k)(3)(ii)(A)(3) Weekly Production Reports production reports 1 and (k)(4) introductory text

§ 679.4(k)(5)(iv) Pacific time Alaska local time 1

§ 679.5(g)(1)(i) heading Groundfish. Groundfish and donated prohibited species. 1

§ 679.5(p)(2) Alaska Department of Fish & Game, Division of ADF&G Division of Commercial Fisheries 1 Commercial Fisheries

§ 679.5(r)(3) SPELR eLandings 2

§ 679.5(r)(5) heading Weekly production report (WPR). Production reports. 1

§ 679.5(r)(5) submit a WPR as described in paragraph (i) of submit a production report as described in para- 1 this section graphs (e)(9) and (10) of this section

§ 679.5(r)(10)(i)(B)(2) as reported in a WPR as reported in a production report 1

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00033 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76168 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

Location Remove Add Frequency

§ 679.20(e) heading Maximum retainable amounts— Maximum retainable amounts (MRA)— 1

§ 679.20(g)(2)(iii) § 679.5(a)(9) § 679.5(a)(7)(v)(C) 1

§ 679.21(a)(2) motherships and shoreside processors motherships, shoreside processors, and SFPs 1

§ 679.21(e)(7)(vii) during August during the period August 1

§ 679.22(b)(1)(iii) open to any trawl other than a pelagic trawl gear open unless otherwise closed to trawling. 1 year round.

§ 679.27(j)(2) weekly production report required at § 679.5(i) production report required at § 679.5(e)(10) 1

§ 679.28(c)(3)(i) § 679.5(a)(13) § 679.5(a)(5)(ii) 1

§ 679.40(a)(2)(i)(D) other entity other non-individual entity 1

§ 679.40(a)(3)(v)(B) WPRs production reports 1

§ 679.40(a)(6)(i) corporation or partnership corporation, partnership, or other non-individual 2 entity

§ 679.41(d)(2)(ii) A corporation, partnership, or other entity. A corporation, partnership, or other non-individual 1 entity.

§ 679.42(j) heading corporations and partnerships corporations, partnerships, or other non-individual 1 entities

§ 679.42(j) corporation, partnership, or other entity corporation, partnership, association, or other 13 non-individual entity

§ 679.42(j) corporation or partnership corporation, partnership, association, or other 10 non individual entity

§ 679.50(c)(3)(i) weekly production report submitted to the Re- production report submitted to the Regional Ad- 1 gional Administrator under § 679.5(i). ministrator under § 679.5(e)(10).

§ 679.50(c)(3)(ii) weekly production report submitted to the Re- production reports submitted to the Regional Ad- 1 gional Administrator for that week by the ministrator under § 679.5(e)(10). mothership under § 679.5(i).

§ 679.61(d)(1) paragraph (c) of this section this paragraph (d) 1

§ 679.61(e)(1) paragraph (c) of this section this paragraph (e) 1

§ 679.84(b) § 679.4(m) § 679.4(n) 1

■ 14. The map in Figure 3 to part 679 is revised to read as follows: BILLING CODE 3510–22–S

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00034 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76169

* * * * * ■ 15. The heading for Figure 5 to part Figure 5 to Part 679—Kodiak Island 679 and the map are revised to read as Closure Status for Vessels Using Non- follows: pelagic Trawl Gear

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00035 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 ER15DE08.000 76170 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

* * * * * ■ 16. Figure 7 to part 679 is revised to read as follows:

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00036 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 ER15DE08.001 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76171

■ 17. Figure 12 to part 679 and its Figure 12 to Part 679—Bristol Bay heading are revised to read as follows: Trawl Closure Area

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00037 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 ER15DE08.002 76172 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

BILLING CODE 3510–22–C TABLE 1ATOPART 679—DELIVERY TABLE 1ATOPART 679—DELIVERY ■ 18. Table 1 to part 679 is removed; CONDITION AND PRODUCT CODES— CONDITION AND PRODUCT CODES— Tables 1a, 1b, and 1c to part 679 are Continued Continued added; and Tables 2a and 2b to part 679 GENERAL USE CODES GENERAL USE CODES are revised to read as follows: Description Code Description Code TABLE 1ATOPART 679—DELIVERY CONDITION AND PRODUCT CODES Bled only. Throat or isthmus 03 Butterfly, no backbone. 37 slit to allow blood to drain. Head removed, belly slit, GENERAL USE CODES viscera and most of backbone Bled fish destined for fish meal 42 removed; fillets attached. Description Code (includes offsite production). DO NOT RECORD ON PTR. Cheeks. Muscles on sides of 17 Belly flaps. Flesh in region of 19 head (ancillary only). pelvic and pectoral fins and be- Bones (if meal, report as 32) 39 hind head (ancillary only). (ancillary only).

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00038 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 ER15DE08.003 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76173

TABLE 1ATOPART 679—DELIVERY TABLE 1ATOPART 679—DELIVERY TABLE 1BTOPART 679—DISCARD CONDITION AND PRODUCT CODES— CONDITION AND PRODUCT CODES— AND DISPOSITION CODES Continued Continued GENERAL USE CODES GENERAL USE CODES Description Code Confiscation. 63 Description Code Description Code Deadloss (crab only). 79 Chins. Lower jaw (mandible), 18 Heads. Heads only, regardless 16 muscles, and flesh (ancillary where severed from body (an- only). cillary only). Halibut retained for future sale 87 (Halibut only). Fillets, deep-skin. Meat with 24 Kirimi (Steak). Head removed 11 skin, adjacent meat with silver either in front or behind the col- Overage (Specify overage type 62 lining, and ribs removed from lar bone, viscera removed, and in comment). sides of body behind head and tail removed by cuts perpen- in front of tail, resulting in thin dicular to the spine, resulting in Tagged Fish (Exempt from 64 fillets. a steak. IFQ).

Fillets, skinless/boneless. Meat 23 Mantles, octopus or squid. 36 Whole fish/bait, not sold. Used 92 with both skin and ribs re- Flesh after removal of viscera as bait on board vessel. moved, from sides of body be- and arms. hind head and in front of tail. Whole fish/bait, sold. 61 Milt (in sacs, or testes) (ancil- 34 Fillets with ribs, no skin. 22 lary only). Whole fish/discard at sea. 98 Meat with ribs with skin re- Whole groundfish and prohib- moved, from sides of body be- Minced. Ground flesh. 31 ited species discarded by hind head and in front of tail. catcher vessels, catcher/proc- Other retained product. If prod- 97 essors, motherships, or Fillets with skin and ribs. 20 uct is not listed on this table, tenders. DO NOT RECORD Meat and skin with ribs at- enter code 97 and write a de- ON PTR. tached, from sides of body be- scription and product recovery hind head and in front of tail. rate next to it in parentheses. Whole fish/discard, damaged. 93 Whole fish damaged by ob- Fillets with skin, no ribs. 21 Pectoral girdle. Collar bone 15 server’s sampling procedures. Meat and skin with ribs re- and associated bones, car- moved, from sides of body be- tilage and flesh. Whole fish/discard, decom- 89 hind head and in front of tail. posed. Decomposed or previously discarded fish. Roe. Eggs, either loose or in 14 Fish meal. Meal from whole 32 sacs, or skeins (ancillary only). fish or fish parts; includes bone Whole fish/discard, infested. 88 meal. Salted and split. Head re- 12 Flea-infested fish, parasite-in- moved, belly slit, viscera re- fested fish. Fish oil. Rendered oil from 33 moved, fillets cut from head to whole fish or fish parts. Record tail but remaining attached Whole fish/discard, onshore. 99 only oil destined for sale and near tail. Product salted. Discard after delivery and be- not oil stored or burned for fuel fore processing by shoreside processors, stationary floating onboard. Stomachs. Includes all internal 35 processors, and buying sta- organs (ancillary only). Gutted, head on. Belly slit and 04 tions and in-plant discard of whole groundfish and prohib- viscera removed. Surimi. Paste from fish flesh 30 ited species during processing. and additives. DO NOT RECORD ON PTR. Gutted, head off. Belly slit and 05 viscera removed. Whole fish or shellfish/food 01 Whole fish/donated prohibited 86 fish. Head and gutted, with roe. 06 species. Number of Pacific salmon or Wings. On skates, side fins are 13 Pacific halibut, otherwise re- Headed and gutted, Western 07 cut off next to body. quired to be discarded that is cut. donated to charity under a Head removed just in front of SHELLFISH ONLY NMFS-authorized program. the collar bone, and viscera removed. Soft shell crab 75 Whole fish/fish meal. 41 Whole fish destined for meal Headed and gutted, Eastern 08 Bitter crab 76 (includes offsite production.) cut. DO NOT RECORD ON PTR. Head removed just behind the Deadloss 79 collar bone, and viscera re- Whole fish/personal use, con- 95 moved. Sections 80 sumption. Fish or fish products eaten on board or taken off the Headed and gutted, tail re- 10 Meat 81 vessel for personal use. Not moved. sold or utilized as bait. Head removed usually in front NOTE: When using whole fish codes, record of collar bone, and viscera and round weights not product weights, even if the tail removed. whole fish is not used.

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00039 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76174 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

TABLE 1BTOPART 679—DISCARD TABLE 2ATOPART 679—SPECIES TABLE 2ATOPART 679—SPECIES AND DISPOSITION CODES—Continued CODES: FMP GROUNDFISH—Contin- CODES: FMP GROUNDFISH—Contin- ued ued Description Code Species Description Code Species Description Code Whole fish/sold, for human 60 consumption. Aurora (Sebastes aurora) 185 Tiger (S. nigrocinctus) 148 NOTE: When using whole fish codes, record round weights not product weights, even if the Black (BSAI) (S. 142 Vermilion (S. miniatus) 184 whole fish is not used. melanops) Widow (S. entomelas) 156 Blackgill (S. 177 TABLE 1CTOPART 679—PRODUCT melanostomus) Yelloweye (S. ruberrimus) 145 TYPE CODES Blue (BSAI) (S. mystinus) 167 Yellowmouth (S. reedi) 175 Description Code Bocaccio (S. paucispinis) 137 Yellowtail (S. flavidus) 155 Ancillary product. A A product, such as meal, Canary (S. pinniger) 146 Sablefish (blackcod) 710 heads, internal organs, pectoral girdles, or any other product Chilipepper (S. goodei) 178 Sculpins 160 that may be made from the same fish as the primary prod- China (S. nebulosus) 149 SHARKS uct. Copper (S. caurinus) 138 Other (if salmon, spiny 689 Primary product. P dogfish or Pacific sleeper shark A product, such as fillets, made Darkblotched (S. crameri) 159 — use specific species code) from each fish, with the highest recovery rate. Dusky (S. ciliatus) 154 Pacific sleeper 692

Reprocessed or rehandled R Greenstriped (S. 135 Salmon 690 product. elongatus) A product, such as meal, that Spiny dogfish 691 Harlequin (S. variegatus) 176 results from processing a pre- SKATES viously reported product or Northern (S. polyspinis) 136 from rehandling a previously Big 702 reported product. Pacific Ocean perch (S. 141 alutus) Longnose 701 TABLE 2ATOPART 679—SPECIES Pygmy (S. wilsoni) 179 Other (If longnose or big 700 CODES: FMP GROUNDFISH skate — use specific species Quillback (S. maliger) 147 code) Species Description Code Redbanded (S. babcocki) 153 SOLE Atka mackerel (greenling) 193 Redstripe (S. proriger) 158 Butter 126 Flatfish, miscellaneous(flatfish 120 species without separate Rosethorn (S. 150 Dover 124 codes) helvomaculatus) English 128 FLOUNDER Rougheye (S. aleutianus) 151 Flathead 122 Alaska plaice 133 Sharpchin (S. zacentrus) 166 Petrale 131 Arrowtooth and/or 121 Shortbelly (S. jordani) 181 Kamchatka Rex 125 Shortraker (S. borealis) 152 Starry 129 Rock 123 Silvergray (S. brevispinis) 157 Octopus, North Pacific 870 Sand 132 Splitnose (S. diploproa) 182 Pacific cod 110 Yellowfin 127 Stripetail (S. saxicola) 183 Pollock 270 Squid, majestic 875 Thornyhead (all 143 ROCKFISH Sebastolobus species) Turbot, Greenland 134

TABLE 2BTOPART 679—SPECIES CODES: FMP PROHIBITED SPECIES AND CR CRAB

Species Description Code CR Crab Ground- fish PSC

CRAB

VerDate Aug<31>2005 18:37 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00040 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76175

TABLE 2BTOPART 679—SPECIES CODES: FMP PROHIBITED SPECIES AND CR CRAB—Continued Box Lopholithodes mandtii 900 ✓

Dungeness Cancer magister 910 ✓

King, blue Paralithodes platypus 922 ✓ ✓

King, golden (brown) Lithodes aequispinus 923 ✓ ✓

King, red Paralithodes camtshaticus 921 ✓ ✓

King, scarlet (deepsea) Lithodes couesi 924 ✓

Korean horsehair crab Erimacrus isenbeckii 940 ✓

Multispinus crab Paralomis multispinus 951 ✓

Tanner, Bairdi Chionoecetes bairdi 931 ✓ ✓

Tanner, grooved Chionoecetes tanneri 933 ✓

Tanner, snow Chionoecetes opilio 932 ✓ ✓

Tanner, triangle Chionoecetes angulatus 934 ✓

Verrilli crab Paralomis verrilli 953 ✓

PACIFIC HALIBUT Hippoglossus stenolepis 200 ✓

PACIFIC HERRING Family Clupeidae 235 ✓

SALMON

Chinook (king) Oncorhynchus tshawytscha 410 ✓

Chum (dog) Oncorhynchus keta 450 ✓

Coho (silver) Oncorhynchus kisutch 430 ✓

Pink (humpback) Oncorhynchus gorbuscha 440 ✓

Sockeye (red) Oncorhynchus nerka 420 ✓

STEELHEAD TROUT Oncorhynchus mykiss 540 ✓

* * * * * TABLE 2DTOPART 679—SPECIES TABLE 2DTOPART 679—SPECIES ■ 19. Table 2d to part 679 is revised to CODES: NON-FMP SPECIES—Con- CODES: NON-FMP SPECIES—Con- read as follows: tinued tinued GENERAL USE TABLE 2DTOPART 679—SPECIES GENERAL USE CODES: NON-FMP SPECIES Species Description Code Species Description Code

GENERAL USE Whitespot 192 Pacific saury 220

Species Description Code Grenadier, giant 214 Pacific tomcod 250

Arctic char (anadromous) 521 Grenadier (rattail) 213 Poacher (Family Agonidae) 219

Bering flounder 116 Jellyfish (unspecified) 625 Prowfish 215 (Hippoglossoides robustus) Lamprey, Pacific 600 Ratfish 714 Dolly varden (anadromous) 531 Lingcod 130 Rockfish, black (GOA) 142 Eels or eel-like fish 210 Lumpsucker 216 Rockfish, blue (GOA) 167 Eel, wolf 217 Pacific flatnose 260 Sardine, Pacific (pilchard) 170 GREENLING Pacific hagfish 212 Sea cucumber, red 895 Kelp 194 Pacific hake 112

Rock 191 Pacific lamprey 600

VerDate Aug<31>2005 18:37 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00041 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76176 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

TABLE 2DTOPART 679—SPECIES TABLE 2DTOPART 679—SPECIES TABLE 2DTOPART 679—SPECIES CODES: NON-FMP SPECIES—Con- CODES: NON-FMP SPECIES—Con- CODES: NON-FMP SPECIES—Con- tinued tinued tinued

GENERAL USE GENERAL USE GENERAL USE Species Description Code Species Description Code Species Description Code

Shad 180 Eastern softshell 842 SHRIMP

Skilfish 715 Pacific geoduck 815 Coonstripe 964

Snailfish, general (genus 218 Pacific littleneck 840 Humpy 963 Liparis and genus Careproctus) Pacific razor 830 Northern (pink) 961 Sturgeon, general 680 Washington butter 810 Sidestripe 962 Wrymouths 211 Spot 965 SHELLFISH Coral 899 Snails 890 Abalone, northern (pinto) 860 Mussel, blue 855 Urchin, green sea 893 CLAMS Oyster, Pacific 880 Urchin, red sea 892 Arctic surf 812 Scallop, weathervane 850

Cockle 820 Scallop, pink (or calico) 851 ■ 20. Table 4 to part 679 is revised to read as follows:

TABLE 4 TO PART 679—STELLER SEA LION PROTECTION AREAS POLLOCK FISHERIES RESTRICTIONS

Column Number 1 2 3 4 5 6 7

Site Name Area or Subarea Boundaries from Boundaries to1 Pollock No-fishing Zones for Trawl Gear2,8 (nm)

Latitude Longitude Latitude Longitude

St. Lawrence I./S Punuk I. Bering Sea 63°04.00 N 168°51.00 W 20

St. Lawrence I./SW Cape Bering Sea 63°18.00 N 171°26.00 W 20

Hall I. Bering Sea 60°37.00 N 173°00.00 W 20

St. Paul I./Sea Lion Rock Bering Sea 57°06.00 N 170°17.50 W 3

St. Paul I./NE Pt. Bering Sea 57°15.00 N 170°06.50 W 3

Walrus I. (Pribilofs) Bering Sea 57°11.00 N 169°56.00 W 10

St. George I./Dalnoi Pt. Bering Sea 56°36.00 N 169°46.00 W 3

St. George I./S Rookery Bering Sea 56°33.50 N 169°40.00 W 3

Cape Newenham Bering Sea 58°39.00 N 162°10.50 W 20

Round (Walrus Islands) Bering Sea 58°36.00 N 159°58.00 W 20

Attu I./Cape Wrangell Aleutian I. 52°54.60 N 172°27.90 E 52°55.40 N 172°27.20 E 20

Agattu I./Gillon Pt. Aleutian I. 52°24.13 N 173°21.31 E 20

Attu I./Chirikof Pt. Aleutian I. 52°49.75 N 173°26.00 E 20

Agattu I./Cape Sabak Aleutian I. 52°22.50 N 173°43.30 E 52°21.80 N 173°41.40 E 20

Alaid I. Aleutian I. 52°46.50 N 173°51.50 E 52°45.00 N 173°56.50 E 20

Shemya I. Aleutian I. 52°44.00 N 174°08.70 E 20

Buldir I. Aleutian I. 52°20.25 N 175°54.03 E 52°20.38 N 175°53.85 E 20

Kiska I./Cape St. Stephen Aleutian I. 51°52.50 N 177°12.70 E 51°53.50 N 177°12.00 E 20

VerDate Aug<31>2005 18:37 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00042 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76177

TABLE 4 TO PART 679—STELLER SEA LION PROTECTION AREAS POLLOCK FISHERIES RESTRICTIONS—Continued Kiska I./Sobaka & Vega Aleutian I. 51°49.50 N 177°19.00 E 51°48.50 N 177°20.50 E 20

Kiska I./Lief Cove Aleutian I. 51°57.16 N 177°20.41 E 51°57.24 N 177°20.53 E 20

Kiska I./Sirius Pt. Aleutian I. 52°08.50 N 177°36.50 E 20

Tanadak I. (Kiska) Aleutian I. 51°56.80 N 177°46.80 E 20

Segula I. Aleutian I. 51°59.90 N 178°05.80 E 52°03.06 N 178°08.80 E 20

Ayugadak Point Aleutian I. 51°45.36 N 178°24.30 E 20

Rat I./Krysi Pt. Aleutian I. 51°49.98 N 178°12.35 E 20

Little Sitkin I. Aleutian I. 51°59.30 N 178°29.80 E 20

Amchitka I./Column Rocks Aleutian I. 51°32.32 N 178°49.28 E 20

Amchitka I./East Cape Aleutian I. 51°22.26 N 179°27.93 E 51°22.00 N 179°27.00 E 20

Amchitka I./Cape Ivakin Aleutian I. 51°24.46 N 179°24.21 E 20

Semisopochnoi/Petrel Pt. Aleutian I. 52°01.40 N 179°36.90 E 52°01.50 N 179°39.00 E 20

Semisopochnoi I./Pochnoi Pt. Aleutian I. 51°57.30 N 179°46.00 E 20

Amatignak I. Nitrof Pt. Aleutian I. 51°13.00 N 179°07.80 W 20

Unalga & Dinkum Rocks Aleutian I. 51°33.67 N 179°04.25 W 51°35.09 N 179°03.66 W 20

Ulak I./Hasgox Pt. Aleutian I. 51°18.90 N 178°58.90 W 51°18.70 N 178°59.60 W 20

Kavalga I. Aleutian I. 51°34.50 N 178°51.73 W 51°34.50 N 178°49.50 W 20

Tag I. Aleutian I. 51°33.50 N 178°34.50 W 20

Ugidak I. Aleutian I. 51°34.95 N 178°30.45 W 20

Gramp Rock Aleutian I. 51°28.87 N 178°20.58 W 20

Tanaga I./Bumpy Pt. Aleutian I. 51°55.00 N 177°58.50 W 51°55.00 N 177°57.10 W 20

Bobrof I. Aleutian I. 51°54.00 N 177°27.00 W 20

Kanaga I./Ship Rock Aleutian I. 51°46.70 N 177°20.72 W 20

Kanaga I./North Cape Aleutian I. 51°56.50 N 177°09.00 W 20

Adak I. Aleutian I. 51°35.50 N 176°57.10 W 51°37.40 N 176°59.60 W 20

Little Tanaga Strait Aleutian I. 51°49.09 N 176°13.90 W 20

Great Sitkin I. Aleutian I. 52°06.00 N 176°10.50 W 52°06.60 N 176°07.00 W 20

Anagaksik I. Aleutian I. 51°50.86 N 175°53.00 W 20

Kasatochi I. Aleutian I. 52°11.11 N 175°31.00 W 20

Atka I./North Cape Aleutian I. 52°24.20 N 174°17.80 W 20

Amlia I./Sviech. Harbor11 Aleutian I. 52°01.80 N 173°23.90 W 20

Sagigik I.11 Aleutian I. 52°00.50 N 173°09.30 W 20

Amlia I./East11 Aleutian I. 52°05.70 N 172°59.00 W 52°05.75 N 172°57.50 W 20

Tanadak I. (Amlia11) Aleutian I. 52°04.20 N 172°57.60 W 20

Agligadak I.11 Aleutian I. 52°06.09 N 172°54.23 W 20

Seguam I./Saddleridge Pt.11 Aleutian I. 52°21.05 N 172°34.40 W 52°21.02 N 172°33.60 W 20

Seguam I./Finch Pt. Aleutian I. 52°23.40 N 172°27.70 W 52°23.25 N 172°24.30 W 20

Seguam I./South Side Aleutian I. 52°21.60 N 172°19.30 W 52°15.55 N 172°31.22 W 20

VerDate Aug<31>2005 18:37 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00043 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76178 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

TABLE 4 TO PART 679—STELLER SEA LION PROTECTION AREAS POLLOCK FISHERIES RESTRICTIONS—Continued Amukta I. & Rocks Aleutian I. 52°27.25 N 171°17.90 W 20

Chagulak I. Aleutian I. 52°34.00 N 171°10.50 W 20

Yunaska I. Aleutian I. 52°41.40 N 170°36.35 W 20

Uliaga3 Bering Sea 53°04.00 N 169°47.00 W 53°05.00 N 169°46.00 W 20,10

Chuginadak Gulf of Alaska 52°46.70 N 169°41.90 W 20

Kagamil3 Bering Sea 53°02.10 N 169°41.00 W 20,10

Samalga Gulf of Alaska 52°46.00 N 169°15.00 W 20

Adugak I.3 Bering Sea 52°54.70 N 169°10.50 W 10

Umnak I./Cape Aslik3 Bering Sea 53°25.00 N 168°24.50 W BA

Ogchul I. Gulf of Alaska 52°59.71 N 168°24.24 W 20

Bogoslof I./Fire I.3 Bering Sea 53°55.69 N 168°02.05 W BA

Polivnoi Rock Gulf of Alaska 53°15.96 N 167°57.99 W 20

Emerald I. Gulf of Alaska 53°17.50 N 167°51.50 W 20

Unalaska/Cape Izigan Gulf of Alaska 53°13.64 N 167°39.37 W 20

Unalaska/Bishop Pt.9 Bering Sea 53°58.40 N 166°57.50 W 10

Akutan I./Reef-lava9 Bering Sea 54°08.10 N 166°06.19 W 54°09.10 N 166°05.50 W 10

Unalaska I./Cape Sedanka6 Gulf of Alaska 53°50.50 N 166°05.00 W 20

Old Man Rocks6 Gulf of Alaska 53°52.20 N 166°04.90 W 20

Akutan I./Cape Morgan6 Gulf of Alaska 54°03.39 N 165°59.65 W 54°03.70 N 166°03.68 W 20

Akun I./Billings Head9 Bering Sea 54°17.62 N 165°32.06 W 54°17.57 N 165°31.71 W 10

Rootok6 Gulf of Alaska 54°03.90 N 165°31.90 W 54°02.90 N 165°29.50 W 20

Tanginak I.6 Gulf of Alaska 54°12.00 N 165°19.40 W 20

Tigalda/Rocks NE6 Gulf of Alaska 54°09.60 N 164°59.00 W 54°09.12 N 164°57.18 W 20

Unimak/Cape Sarichef9 Bering Sea 54°34.30 N 164°56.80 W 10

Aiktak6 Gulf of Alaska 54°10.99 N 164°51.15 W 20

Ugamak I.6 Gulf of Alaska 54°13.50 N 164°47.50 W 54°12.80 N 164°47.50 W 20

Round (GOA)6 Gulf of Alaska 54°12.05 N 164°46.60 W 20

Sea Lion Rock (Amak)9 Bering Sea 55°27.82 N 163°12.10 W 10

Amak I. And rocks9 Bering Sea 55°24.20 N 163°09.60 W 55°26.15 N 163°08.50 W 10

Bird I. Gulf of Alaska 54°40.00 N 163°17.2 W 10

Caton I. Gulf of Alaska 54°22.70 N 162°21.30 W 3

South Rocks Gulf of Alaska 54°18.14 N 162°41.3 W 10

Clubbing Rocks (S) Gulf of Alaska 54°41.98 N 162°26.7 W 10

Clubbing Rocks (N) Gulf of Alaska 54°42.75 N 162°26.7 W 10

Pinnacle Rock Gulf of Alaska 54°46.06 N 161°45.85 W 3

Sushilnoi Rocks Gulf of Alaska 54°49.30 N 161°42.73 W 10

Olga Rocks Gulf of Alaska 55°00.45 N 161°29.81 W 54°59.09 N 161°30.89 W 10

Jude I. Gulf of Alaska 55°15.75 N 161°06.27 W 20

VerDate Aug<31>2005 18:37 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00044 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76179

TABLE 4 TO PART 679—STELLER SEA LION PROTECTION AREAS POLLOCK FISHERIES RESTRICTIONS—Continued Sea Lion Rocks (Shumagins) Gulf of Alaska 55°04.70 N 160°31.04 W 3

Nagai I./Mountain Pt. Gulf of Alaska 54°54.20 N 160°15.40 W 54°56.00 N 160°15.00 W 3

The Whaleback Gulf of Alaska 55°16.82 N 160°05.04 W 3

Chernabura I. Gulf of Alaska 54°45.18 N 159°32.99 W 54°45.87 N 159°35.74 W 20

Castle Rock Gulf of Alaska 55°16.47 N 159°29.77 W 3

Atkins I. Gulf of Alaska 55°03.20 N 159°17.40 W 20

Spitz I. Gulf of Alaska 55°46.60 N 158°53.90 W 3

Mitrofania Gulf of Alaska 55°50.20 N 158°41.90 W 3

Kak Gulf of Alaska 56°17.30 N 157°50.10 W 20

Lighthouse Rocks Gulf of Alaska 55°46.79 N 157°24.89 W 20

Sutwik I. Gulf of Alaska 56°31.05 N 157°20.47 W 56°32.00 N 157°21.00 W 20

Chowiet I. Gulf of Alaska 56°00.54 N 156°41.42 W 56°00.30 N 156°41.60 W 20

Nagai Rocks Gulf of Alaska 55°49.80 N 155°47.50 W 20

Chirikof I. Gulf of Alaska 55°46.50 N 155°39.50 W 55°46.44 N 155°43.46 W 20

Puale Bay12 Gulf of Alaska 57°40.60 N 155°23.10 W 3,10

Kodiak/Cape Ikolik Gulf of Alaska 57°17.20 N 154°47.50 W 3

Takli I. Gulf of Alaska 58°01.75 N 154°31.25 W 10

Cape Kuliak Gulf of Alaska 58°08.00 N 154°12.50 W 10

Cape Gull Gulf of Alaska 58°11.50 N 154°09.60 W 58°12.50 N 154°10.50 W 10

Kodiak/Cape Ugat Gulf of Alaska 57°52.41 N 153°50.97 W 10

Sitkinak/Cape Sitkinak Gulf of Alaska 56°34.30 N 153°50.96 W 10

Shakun Rock Gulf of Alaska 58°32.80 N 153°41.50 W 10

Twoheaded I. Gulf of Alaska 56°54.50 N 153°32.75 W 56°53.90 N 153°33.74 W 10

Cape Douglas (Shaw I.)12 Gulf of Alaska 59°00.00 N 153°22.50 W 20, 10

Kodiak/Cape Barnabas Gulf of Alaska 57°10.20 N 152°53.05 W 3

Kodiak/Gull Point4 Gulf of Alaska 57°21.45 N 152°36.30 W 10, 3

Latax Rocks Gulf of Alaska 58°40.10 N 152°31.30 W 10

Ushagat I./SW Gulf of Alaska 58°54.75 N 152°22.20 W 10

Ugak I.4 Gulf of Alaska 57°23.60 N 152°17.50 W 57°21.90 N 152°17.40 W 10, 3

Sea Otter I. Gulf of Alaska 58°31.15 N 152°13.30 W 10

Long I. Gulf of Alaska 57°46.82 N 152°12.90 W 10

Sud I. Gulf of Alaska 58°54.00 N 152°12.50 W 10

Kodiak/Cape Chiniak Gulf of Alaska 57°37.90 N 152°08.25 W 10

Sugarloaf I. Gulf of Alaska 58°53.25 N 152°02.40 W 20

Sea Lion Rocks (Marmot) Gulf of Alaska 58°20.53 N 151°48.83 W 10

Marmot I.5 Gulf of Alaska 58°13.65 N 151°47.75 W 58°09.90 N 151°52.06 W 15, 20

Nagahut Rocks Gulf of Alaska 59°06.00 N 151°46.30 W 10

Perl Gulf of Alaska 59°05.75 N 151°39.75 W 10

VerDate Aug<31>2005 18:37 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00045 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76180 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

TABLE 4 TO PART 679—STELLER SEA LION PROTECTION AREAS POLLOCK FISHERIES RESTRICTIONS—Continued Gore Point Gulf of Alaska 59°12.00 N 150°58.00 W 10

Outer (Pye) I. Gulf of Alaska 59°20.50 N 150°23.00 W 59°21.00 N 150°24.50 W 20

Steep Point Gulf of Alaska 59°29.05 N 150°15.40 W 10

Seal Rocks (Kenai) Gulf of Alaska 59°31.20 N 149°37.50 W 10

Chiswell Islands Gulf of Alaska 59°36.00 N 149°34.00 W 10

Rugged Island Gulf of Alaska 59°50.00 N 149°23.10 W 59°51.00 N 149°24.70 W 10

Point Elrington7, 10 Gulf of Alaska 59°56.00 N 148°15.20 W 20

Perry I.7 Gulf of Alaska 60°44.00 N 147°54.60 W

The Needle7 Gulf of Alaska 60°06.64 N 147°36.17 W

Point Eleanor7 Gulf of Alaska 60°35.00 N 147°34.00 W

Wooded I. (Fish I.) Gulf of Alaska 59°52.90 N 147°20.65 W 20

Glacier Island7 Gulf of Alaska 60°51.30 N 147°14.50 W

Seal Rocks (Cordova)10 Gulf of Alaska 60°09.78 N 146°50.30 W 20

Cape Hinchinbrook10 Gulf of Alaska 60°14.00 N 146°38.50 W 20

Middleton I. Gulf of Alaska 59°28.30 N 146°18.80 W 10

Hook Point10 Gulf of Alaska 60°20.00 N 146°15.60 W 20

Cape St. Elias Gulf of Alaska 59°47.50 N 144°36.20 W 20 1Where two sets of coordinates are given, the baseline extends in a clockwise direction from the first set of geographic coordinates along the shoreline at mean lower-low water to the second set of coordinates. Where only one set of coordinates is listed, that location is the base point. 2Closures as stated in § 679.22(a)(7)(iv), (a)(8)(ii), and (b)(2)(ii). 3This site lies within the Bogoslof area (BA). The BA consists of all waters of area 518 as described in Figure 1 of this part south of a straight line connecting 55°00′ N / 170°00′ W, and 55°00′ N / 168°11′4.75″ W. Closure to directed fishing for pollock around Uliaga and Kagamil is 20 nm for waters west of 170° W long. and 10 nm for waters east of 170° W long. 4Trawl closure between 0 nm to 10 nm is effective from January 20 through May 31. Trawl closure between 0 nm to 3 nm is effective from August 25 through November 1. 5Trawl closure between 0 nm to 15 nm is effective from January 20 through May 31. Trawl closure between 0 nm to 20 nm is effective from August 25 to November 1. 6Restriction area includes only waters of the Gulf of Alaska Area. 7Contact the Alaska Department of Fish and Game for fishery restrictions at these sites. 8No-fishing zones are the waters between 0 nm and the nm specified in column 7 of this table around each site and within the BA. 9This site is located in the Bering Sea Pollock Restriction Area, closed to pollock trawling during the A season. This area consists of all waters of the Bering Sea subarea south of a line connecting the points 55°46′30″ N lat. 163°00′00″ W long. 54°42′9″ N lat. 165°08′00″ W long. 54°26′30″ N lat. 165°40′00″ W long. 54°18′40″ N lat. 166°12′00″ W long. and 54°8′50″ N lat. 167°00′00″ W long. 10The 20 nm closure around this site is effective in federal waters outside of State of Alaska waters of Prince William Sound. 11Some or all of the restricted area is located in the Seguam Foraging area (SFA) which is closed to all gears types. The SFA is established as all waters within the area between 52° N lat. and 53° N lat. and between 173°30′ W long. and 172°30′ W long. 12The 3 nm trawl closure around Puale Bay and the 20 nm trawl closure around Cape Douglas/Shaw I. are effective January 20 through May 31. The 10 nm trawl closure around Puale Bay and the 10 nm trawl closure around Cape Douglas/Shaw I. are effective August 25 through No- vember 1.

■ 21. Table 9 is removed and reserved; and Tables 10, 11, and 12 to part 679 are revised to read as follows: BILLING CODE 3510–22–S

VerDate Aug<31>2005 18:37 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00046 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76181

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00047 Fmt 4701 Sfmt 4725 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 ER15DE08.004 76182 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00048 Fmt 4701 Sfmt 4725 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 ER15DE08.005 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76183

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00049 Fmt 4701 Sfmt 4725 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 ER15DE08.006 76184 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

BILLING CODE 3510–22–C

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00050 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 ER15DE08.007 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76185

TABLE 12 TO PART 679—STELLER SEA LION PROTECTION AREAS, 3NM NO GROUNDFISH FISHING SITES

Column Number 1 2 3 4 5 6 7

Site Name Area or Subarea Boundaries from Boundaries to1 No transit23 (nm)

Latitude Longitude Latitude Longitude

Walrus I. (Pribilofs) Bering Sea 57°11.00 N 169°56.00 W Y

Attu I./Cape Wrangell Aleutian I. 52°54.60 N 172°27.90 E 52°55.40 N 172°27.20 E Y

Agattu I./Gillon Pt. Aleutian I. 52°24.13 N 173°21.31 E Y

Agattu I./Cape Sabak Aleutian I. 52°22.50 N 173°43.30 E 52°21.80 N 173°41.40 E Y

Buldir I. Aleutian I. 52°20.25 N 175°54.03 E 52°20.38 N 175°53.85 E Y

Kiska I./Cape St. Stephen Aleutian I. 51°52.50 N 177°12.70 E 51°53.50 N 177°12.00 E Y

Kiska I./Lief Cove Aleutian I. 51°57.16 N 177°20.41 E 51°57.24 N 177°20.53 E Y

Ayugadak Point Aleutian I. 51°45.36 N 178°24.30 E Y

Amchitka I./Column Rocks Aleutian I. 51°32.32 N 178°49.28 E Y

Amchitka I./East Cape Aleutian I. 51°22.26 N 179°27.93 E 51°22.00 N 179°27.00 E Y

Semisopochnoi/Petrel Pt. Aleutian I. 52°01.40 N 179°36.90 E 52°01.50 N 179°39.00 E Y

Semisopochnoi I./Pochnoi Pt. Aleutian I. 51°57.30 N 179°46.00 E Y

Ulak I./Hasgox Pt. Aleutian I. 51°18.90 N 178°58.90 W 51°18.70 N 178°59.60 W Y

Tag I. Aleutian I. 51°33.50 N 178°34.50 W Y

Gramp Rock Aleutian I. 51°28.87 N 178°20.58 W Y

Adak I. Aleutian I. 51°35.50 N 176°57.10 W 51°37.40 N 176°59.60 W Y

Kasatochi I. Aleutian I. 52°11.11 N 175°31.00 W Y

Agligadak I. Aleutian I. 52°06.09 N 172°54.23 W Y

Seguam I./Saddleridge Pt. Aleutian I. 52°21.05 N 172°34.40 W 52°21.02 N 172°33.60 W Y

Yunaska I. Aleutian I. 52°41.40 N 170°36.35 W Y

Adugak I. Bering Sea 52°54.70 N 169°10.50 W Y

Ogchul I. Gulf of Alaska 52°59.71 N 168°24.24 W Y

Bogoslof I./Fire I. Bering Sea 53°55.69 N 168°02.05 W Y

Akutan I./Cape Morgan Gulf of Alaska 54°03.39 N 165°59.65 W 54°03.70 N 166°03.68 W Y

Akun I./Billings Head Bering Sea 54°17.62 N 165°32.06 W 54°17.57 N 165°31.71 W Y

Ugamak I. Gulf of Alaska 54°13.50 N 164°47.50 W 54°12.80 N 164°47.50 W Y

Sea Lion Rock (Amak) Bering Sea 55°27.82 N 163°12.10 W Y

Clubbing Rocks (S) Gulf of Alaska 54°41.98 N 162°26.7 W Y

Clubbing Rocks (N) Gulf of Alaska 54°42.75 N 162°26.7 W Y

Pinnacle Rock Gulf of Alaska 54°46.06 N 161°45.85 W Y

Chernabura I. Gulf of Alaska 54°45.18 N 159°32.99 W 54°45.87 N 159°35.74 W Y

Atkins I. Gulf of Alaska 55°03.20 N 159°17.40 W Y

Chowiet I. Gulf of Alaska 56°00.54 N 156°41.42 W 56°00.30 N 156°41.60 W Y

Chirikof I. Gulf of Alaska 55°46.50 N 155°39.50 W 55°46.44 N 155°43.46 W Y

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00051 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76186 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

TABLE 12 TO PART 679—STELLER SEA LION PROTECTION AREAS, 3NM NO GROUNDFISH FISHING SITES—Continued Sugarloaf I. Gulf of Alaska 58°53.25 N 152°02.40 W Y

Marmot I. Gulf of Alaska 58°13.65 N 151°47.75 W 58°09.90 N 151°52.06 W Y

Outer (Pye) I. Gulf of Alaska 59°20.50 N 150°23.00 W 59°21.00 N 150°24.50 W Y

Wooded I. (Fish I.) Gulf of Alaska 59°52.90 N 147°20.65 W

Seal Rocks (Cordova) Gulf of Alaska 60°09.78 N 146°50.30 W 1Where two sets of coordinates are given, the baseline extends in a clock-wise direction from the first set of geographic coordinates along the shoreline at mean lower-low water to the second set of coordinates. Where only one set of coordinates is listed, that location is the base point. 2See 50 CFR 223.202(a)(2)(i) for regulations regarding 3 nm no transit zones. Note: No groundfish fishing zones are the waters between 0 nm to 3 nm surrounding each site.

■ 22. Tables 14a and 14b to part 679 are TABLE 14ATOPART 679—PORT OF TABLE 14ATOPART 679—PORT OF revised to read as follows: LANDING CODES, ALASKA—Continued LANDING CODES, ALASKA—Continued

TABLE 14ATOPART 679—PORT OF ADF&G Port Name NMFS Code ADF&G Port Name NMFS Code LANDING CODES, ALASKA Code Code

ADF&G False Pass 125 FSP Moser Bay 312 MOS Port Name NMFS Code Code Fairbanks 305 FBK Naknek 149 NAK Adak 186 ADA Galena 306 GAL Nenana 313 NEN Akutan, 101 AKU Akutan Bay Glacier Bay 307 GLB Nikiski (or 150 NIK Nikishka) Alitak 103 ALI Glennallen 308 GLN Ninilchik 151 NIN Anchorage 105 ANC Gustavus 127 GUS Nome 152 NOM Angoon 106 ANG Haines 128 HNS Nunivak Is- 314 NUN Aniak 300 ANI Homer 132 HOM land

Anvik 301 ANV Hoonah 133 HNH Old Harbor 153 OLD

Atka 107 ATK Hydaburg 309 HYD Other Alas- 499 OAK ka1 Auke Bay 136 JNU Hyder 134 HDR Pelican 155 PEL Beaver Inlet 119 DUT Juneau 136 JNU Petersburg 156 PBG Bethel 302 BET Kake 137 KAK Port Alex- 158 PAL Captains Bay 119 DUT Kaltag 310 KAL ander

Chefornak 189 CHF Kasilof 138 KAS Port Arm- 315 PTA strong Chignik 113 CHG Kenai 139 KEN Port Bailey 159 PTB Cordova 115 COR Kenai River 139 KEN Port Graham 160 GRM Craig 116 CRG Ketchikan 141 KTN Port Lions 316 LIO Dillingham 117 DIL King Cove 142 KCO Port Moller 317 MOL Douglas 136 JNU King Salmon 143 KNG Port Protec- 161 PRO Dutch Har- 119 DUT Kipnuk 144 KIP tion bor/Unalaska Klawock 145 KLA Quinhagak 187 QUK Egegik 122 EGE Kodiak 146 KOD Sand Point 164 SPT Ekuk 303 EKU Kotzebue 311 KOT Savoonga 165 SAV Elfin Cove 123 ELF Larsen Bay 327 LRB Selawik 326 SWK Emmonak 304 EMM Mekoryuk 147 MEK Seldovia 166 SEL Excursion 124 XIP Inlet Metlakatla 148 MET Seward 167 SEW

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00052 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76187

TABLE 14ATOPART 679—PORT OF TABLE 14ATOPART 679—PORT OF TABLE 14ATOPART 679—PORT OF LANDING CODES, ALASKA—Continued LANDING CODES, ALASKA—Continued LANDING CODES, ALASKA—Continued

Port Name NMFS Code ADF&G ADF&G ADF&G Code Port Name NMFS Code Code Port Name NMFS Code Code

Sitka 168 SIT Tenakee 174 TEN Valdez 181 VAL Springs Skagway 169 SKG Wasilla 322 WAS Togiak 176 TOG Soldotna 318 SOL Whittier 183 WHT Toksook Bay 177 TOB St. George 170 STG Wrangell 184 WRN Tununak 178 TUN St. Mary 319 STM Yakutat 185 YAK Ugashik 320 UGA St. Paul 172 STP 1To report a landing at an Alaska location Unalakleet 321 UNA not currently assigned a location code num- Tee Harbor 136 JNU ber, use ‘‘Other Alaska’’ code ‘‘499’’ or ‘‘OAK.’’

TABLE 14BTOPART 679—PORT OF LANDING CODES: NON-ALASKA (California, Canada, Oregon, and Washington)

Port State or Country Port Name NMFS Code ADF&G Code

CALIFORNIA Eureka 500 EUR

Other California1 599 OCA

CANADA Other Canada1 899 OCN

Port Edward, B.C. 802 PRU

Prince Rupert, B.C. 802 PRU

Vancouver, B.C. 803 VAN

OREGON Astoria 600 AST

Newport 603 NPT

Other Oregon1 699 OOR

Portland 323 POR

Warrenton 604 WAR

WASHINGTON Anacortes 700 ANA

Bellingham 702 BEL

Blaine 717 BLA

Everett 704 EVT

La Conner 708 LAC

Olympia 324 OLY

Other Washington1 799 OWA

Seattle 715 SEA

Tacoma 325 TAC 1To report a landing at a location not currently assigned a location code number, use the code for ‘‘Other California’’, ‘‘Other Oregon’’, ‘‘Other Washington’’, or ‘‘Other Canada’’ at which the landing occurs.

* * * * * ■ 23. Table 15 to part 679 is revised to read as follows:

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00053 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76188 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

TABLE 15 TO PART 679—GEAR CODES, DESCRIPTIONS, AND USE (X indicates where this code is used)

Use alphabetic code to complete the following: Use numeric code to complete the following: Name of gear Electronic check- Numeric gear Alpha gear code NMFS logbooks in/ check-out code IERS eLandings ADF&G COAR

NMFS AND ADF&G GEAR CODES

Hook-and-line HAL X X 61 X X

Jig, mechanical JIG X X 26 X X

Pot POT X X 91 X X

Trawl, nonpelagic/ NPT X X 07 X X bottom

Trawl, pelagic/ PTR X X 47 X X midwater

Troll, dinglebar TROLL X X 25 X X

Troll, hand TROLL X X 05 X X

Troll, power gurdy TROLL X X 15 X X

All other gear types OTH X X

ADF&G GEAR CODES

Diving 11 X X

Dredge 22 X X

Dredge, hydro/me- 23 X X chanical

Fish ladder/race- 77 X X way

Fish wheel 08 X X

Gillnet, drift 03 X X

Gillnet, herring 34 X X

Gillnet, set 04 X X

Gillnet, sunken 41 X X

Handpicked 12 X X

Net, dip 13 X X

Net, ring 10 X X

Other/specify 99 X X

Pound 21 X X

Seine, purse 01 X X

Seine, beach 02 X X

Shovel 18 X X

Trap 90 X X

Trawl, beam 17 X X

Trawl, double otter 27 X

Trawl, pair 37 X X

Weir 14 X X

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00054 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations 76189

TABLE 15 TO PART 679—GEAR CODES, DESCRIPTIONS, AND USE—Continued (X indicates where this code is used)

FIXED GEAR

Authorized gear for All longline gear (hook-and-line, jig, troll, and handline) and, for purposes of determining initial IFQ allocation, all pot sablefish harvested gear used to make a legal landing. from any GOA reporting area

Authorized gear for All hook-and-line gear and all pot gear. sablefish harvested from any BSAI reporting area

Authorized gear for All fishing gear comprised of lines with hooks attached, including one or more stationary, buoyed, and anchored lines halibut harvested with hooks attached. from any IFQ regulatory area

PART 680—SHELLFISH FISHERIES OF (4) Catcher/processor crew (CPC) IFQ Record- THE EXCLUSIVE ECONOMIC ZONE means crab IFQ derived from QS keeping and Person re- Reference OFF ALASKA initially issued to persons who reporting responsible historically held CFEC crab permits and port ■ 24. The authority citation for part 680 signed fish tickets for qualifying * * * * * * * continue to read as follows: landings based on landings processed at Authority: 16 U.S.C. 1862. sea, to annually harvest and process CR (G) CR crab RCR § 679.5(e)(9) crab. landing re- ■ 25. In § 680.2, under the definition of * * * * * port ‘‘Crab individual fishing quota (crab IFQ)’’, paragraphs (1), (2) introductory Sideboards (see § 680.22). * * * * * * * text, (3), and (4) are revised and a * * * * * definition for ‘‘Sideboards’’ is added in (L) CR RCR RCR § 680.5(m) ■ 26. In § 680.4, paragraph (d)(3) is Ex vessel alphabetical order to read as follows: revised to read as follows: Volume and Value Report § 680.2 Definitions. § 680.4 Permits. * * * * * * * * * * * * * * * Crab individual fishing quota (crab (d) * * * (b) IFQ crab landings—(1) Landing IFQ) * * * reports. See § 679.5(e) of this chapter. (1) Catcher vessel crew (CVC) IFQ (3) On an annual basis, the Regional Administrator will issue a crab IFQ (2) Properly debited landing. All means crab IFQ derived from QS landed crab catch must be weighed, initially issued to persons who permit to a person who submits a complete annual application for a crab reported, and debited from the historically held CFEC crab permits and appropriate IFQ account under which signed fish tickets for qualifying IFQ/IPQ permit, described at paragraph (f) of this section, that is subsequently the catch was harvested, and IPQ landings based on pounds delivered account under which it was received, as raw; to annually harvest, but not approved by the Regional Administrator. appropriate (see § 679.5(e) of this process, CR crab onboard the vessel chapter). * * * * * used to harvest that crab. * * * * * (2) Catcher vessel owner (CVO) IFQ ■ 27. In § 680.5: (m) CR Registered Crab Receiver means crab IFQ derived from QS ■ A. Paragraphs (c) and (d) are removed (RCR) Ex-vessel Volume and Value initially issued to persons who held LLP and reserved. Report—(1) Applicability. An RCR that crab permits and had qualifying ■ B. Paragraphs (a)(2)(i)(G) and (b) are also operates as a shoreside processor or landings based on pounds delivered revised. stationary floating crab processor and raw; to annually harvest, but not receives and purchases landings of CR ■ C. Paragraphs (a)(2)(i)(L) and (m) are process, CR crab onboard the vessel crab must submit annually to NMFS a added. used to harvest that crab. complete CR RCR Ex-vessel Volume and * * * * * The revisions and additions read as Value Report, as described in this (3) Catcher/processor owner (CPO) follows: paragraph (m), for each reporting period IFQ means crab IFQ derived from QS § 680.5 Recordkeeping and reporting in which the RCR receives CR crab. initially issued to persons who held LLP (R&R). (2) Reporting period. The reporting crab permits and had qualifying period of the CR RCR Ex-vessel Volume landings derived from landings (a) * * * and Value Report shall extend from processed at sea, to annually harvest (2) * * * August 15 through April 30 of the and process CR crab. (i) * * * following year, inclusive.

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00055 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3 76190 Federal Register / Vol. 73, No. 241 / Monday, December 15, 2008 / Rules and Regulations

(3) Due date. A complete CR RCR Ex- (B) Ex-vessel value paid. The total by road or regularly scheduled air vessel Volume and Value Report must gross ex-vessel value paid for raw CR service and weigh that product on a be received by the Regional crab pounds before any deductions are scale approved by the state in which the Administrator not later than May 15 of made for goods and services provided to CR crab product is removed from the the reporting period in which the RCR the CR crab harvesters. The gross value vessel that harvested the CR crab; and received the CR crab. includes all value paid in any form (e.g., * * * * * (4) Information required. The RCR dollars, goods, services, bait, ice, fuel, must log in to http:// repairs, machinery replacement, etc.), ■ 29. In § 680.44, paragraph (a)(2)(i) is alaskafisheries.noaa.gov using the and any retro payments paid for crab in revised to read as follows: RCR’s password and NMFS person ID to paragraph (m)(4)(iii)(A) of this section. submit a CR RCR Ex-vessel Volume and (iv) Certification. By using the RCR § 680.44 Cost recovery. Value Report. The NMFS software NMFS ID and password and submitting (a) * * * autofills the RCR name. The User must the report, the RCR certifies that all (2) * * * review the autofilled cells to ensure that information is true, correct, and they are accurate. The RCR must enter complete to the best of his or her (i) All CR allocation holders and RCR the information in paragraphs (m)(4)(i) knowledge and belief. permit holders will be subject to a fee through (iv) of this section for a (5) Submittal. The RCR must complete liability for any CR crab debited from a complete CR RCR Ex-vessel Volume and and submit online by electronic CR allocation during a crab fishing year, Value Report for priced crab delivered submission to NMFS the CR Registered except for crab designated as personal raw: Crab Receiver Ex-vessel Volume and use or deadloss, or crab confiscated by (i) RCR identification. (A) RCR permit Value Report available at https:// NMFS or the State of Alaska. number. alaskafisheries.noaa.gov. * * * * * (B) Landing month. ■ 28. In § 680.23, paragraph (b)(4) is (C) Port (location of facility or vessel). revised to read as follows: §§ 680.7, 680.20, and 680.40 [Amended] (ii) CR crab program (e.g., IFQ, CDQ, ADAK). § 680.23 Equipment and operational ■ 30. At each of the locations shown in (iii) CR crab pounds purchased and requirements. the Location column, remove the phrase ex-vessel value. Enter for each program, * * * * * indicated in the ‘‘Remove’’ column and fishery, species, and month. (b) * * * replace it with the phrase indicated in (A) Pounds purchased. The total CR (4) Offload all CR crab product the ‘‘Add’’ column for the number of crab pounds purchased by fishery and processed onboard at a shoreside times indicated in the ‘‘Frequency’’ species for each month. location in the United States accessible column.

Location Remove Add Frequency

§ 680.7(e)(1) without a valid crab IFQ permit without a legible copy of a valid crab IFQ 1 permit

§ 680.20(g)(2)(ix) not required under this section, except as unless required under this section. 1 permitted by paragraph (j) of this section.

§ 680.40(c)(2)(vi)(A) § 679.40(k)(5)(v) § 679.4(k)(5)(v) of this chapter 1

[FR Doc. E8–29625 Filed 12–12–08; 8:45 am] BILLING CODE 3510–22–S

VerDate Aug<31>2005 17:22 Dec 12, 2008 Jkt 217001 PO 00000 Frm 00056 Fmt 4701 Sfmt 4700 E:\FR\FM\15DER3.SGM 15DER3 pwalker on PROD1PC71 with RULES3