08.07.2015 Views

Composite Training Unit Exercises and Joint Task ... - Govsupport.us

Composite Training Unit Exercises and Joint Task ... - Govsupport.us

Composite Training Unit Exercises and Joint Task ... - Govsupport.us

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

COMPTUEX/JTFEX EA/OEA Final Chapter 66.3 OTHER PAST,PRESENT, AND REASONABLY FORESEEABLE FUTURE ACTIVITIES6.3.1 Commercial FishingNOAA estimates that approximately 6,000 marine mammals die annually as a result of by catch fromU.S. fisheries (Waring et al., 2002). In addition, commercial fisheries may accidentally entangle <strong>and</strong>drown or injure cetaceans by lost <strong>and</strong> discarded fishing gear (e.g., Northridge <strong>and</strong> Hofman, 1999).National Marine Fisheries Service (NMFS) 2007 proposed List of Fisheries (LOF) categorizes fisheriesby their level of impact on marine mammals. The LOF was proposed in the Federal Register onDecember 4, 2006, <strong>and</strong> is an MMPA-required annual list consisting of a two-tiered, stock-specificapproach that addresses the total impact of all fisheries on each marine mammal stock, <strong>and</strong> the impact ofindividual fisheries on each stock. The approach is based on consideration of the rate, in numbers ofanimals per year, of incidental mortalities <strong>and</strong> serio<strong>us</strong> injuries of marine mammals due to commercialfishing operations relative to potential biological removal (PBR) level for each marine mammal stock.The Federal Register provides the list of marine mammals that are subject to incidental mortality <strong>and</strong>serio<strong>us</strong> injury as a result of fisheries interactions in the Pacific Ocean.The impact of the proposed actions is not expected to cumulatively increase the serio<strong>us</strong> injury or mortalityof Pacific stocks impacted by fisheries interactions as proposed in the 2007 LOF.6.3.2 Vessel TrafficShip strikes, or ship collisions with whales are a recognized source of whale mortality worldwide. Of the11 species known to be hit by ships, the most frequently reported is the fin whale (Laist et al., 2001). Onthe east coast of North America, ship strikes remain a significant threat to some whale populations. InNorth Atlantic right whales, for example, ship strikes are believed to be a significant factor limiting therecovery of this species (Knowlton & Kra<strong>us</strong>, 2001).A review of recent reports on ship strikes provides some insight regarding the types of whales, locations<strong>and</strong> vessels involved, but also reveals significant gaps in the data. The Large Whale Ship Strike Databaseprovides a summary of the 292 worldwide confirmed or possible whale/ship collisions from 1975 through2002 (Jenson <strong>and</strong> Silber, 2003). The report notes that the database represents a minimum number ofcollisions, beca<strong>us</strong>e the vast majority probably goes undetected or unreported.All types of ships can hit whales, <strong>and</strong> much of the time the animal is either seen too late, not observeduntil the collision occurs, or not detected. The ability of a ship to avoid a collision <strong>and</strong> to detect acollision depends on a variety of factors, including environmental conditions, ship design, size, <strong>and</strong>manning.Note that smaller ships, such as Navy destroyers <strong>and</strong> Coast Guard cutters, have a number of advantagesfor avoiding ship strike as compared to most merchant vessels.The Navy <strong>and</strong> Coast Guard ships have their bridges positioned forward, offering goodvisibility ahead of the bow.Crew size is much larger than merchant ships, <strong>and</strong> there are dedicated lookouts posted duringeach watch.These vessels are generally twin screw <strong>and</strong> much more maneuverable than single screwcommercial craft.February 2007 6-2

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

Saved successfully!

Ooh no, something went wrong!