Specimen Information

Pacifastacus leniusculus
Pacifastacus leniusculus
(Signal Crayfish)
Crustaceans-Crayfish
Native Transplant

Specimen ID4754
GroupCrustaceans-Crayfish
GenusPacifastacus
Speciesleniusculus
Common NameSignal Crayfish
StateCA
CountyMonterey
LocalityMonterey County
Mapping AccuracyCentroid
Centroid TypeCounty
HUC8 NameCentral California Coastal
HUC8 Number18060000
Map
+
Collection Year1959
Year AccuracyActual
Potential Pathwaydispersed
Statusestablished
Reference 1
Ref. Number:10319
Author:Cohen, A.N., and J.T. Carlton.
Date:1995
Title:Nonindigenous Aquatic Species in a United States Estuary, A Case Study of the Biological Invasions of the San Francisco Bay and Delta.
Journal:Report for USFWS, WA DC, and Connecticut Sea Grant
Publisher:A report for the United States Fish and Wildlife Service, Washington, DC and The National Sea Grant College Program Connecticut Sea Grant.
Pages:246 pp
Reference 2
Ref. Number:9262
Author:Riegel, J.A.
Date:1959
Title:The systematics and distribution of crayfishes in California.
Journal:California Fish and Game
Volume:45
Issue:1
Pages:29-50
CommentsNative to Oregon and Washington. This crayfish may have contributed to the extinction of the native sooty crayfish, Pacifastacus nigrescens. Also it may have contributed to extirpation of Pacifastacus from half of its range. Year is publication date.
Record TypeLiterature
Freshwater/MarineFreshwater


Disclaimer:

The data represented on this site vary in accuracy, scale, completeness, extent of coverage and origin. It is the user's responsibility to use these data consistent with their intended purpose and within stated limitations. We highly recommend reviewing metadata files prior to interpreting these data.

Citation information: U.S. Geological Survey. [2024]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [11/25/2024].

Contact us if you are using data from this site for a publication to make sure the data are being used appropriately and for potential co-authorship if warranted.

For general information and questions about the database, contact Wesley Daniel. For problems and technical issues, contact Matthew Neilson.