Procambarus clarkii
Procambarus clarkii
(Red Swamp Crayfish)
Crustaceans-Crayfish
Native Transplant

5 results for Procambarus clarkii (Red Swamp Crayfish)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
1958 Procambarus clarkii Disease/Parasites/Toxicity Observational Field Procambarus clarkii introduces novel parasites that are shown to be of high impact, in... 24593
5168 Procambarus clarkii Disease/Parasites/Toxicity Observational Field Wild populations of Procambarus clarkii are known to carry white spot syndrome, a... 37837
5170 Procambarus clarkii Disease/Parasites/Toxicity Observational Field Wild populations of Procambarus clarkii have been found hosting and transporting the... 37837
9494 Procambarus clarkii Disease/Parasites/Toxicity Anecdotal N/A The potential presence of white spot syndrome virus (WSSV) in Procambarus clarkii may... 42982
9521 Procambarus clarkii Disease/Parasites/Toxicity Anecdotal Field The exportation of Procambarus clarkii to South Carolina and the potential presence of... 42993

View all impact types for Procambarus clarkii
Data Disclaimer: These data are preliminary or provisional and are subject to revision. They are being provided to meet the need for timely best science. The data have not received final approval by the U.S. Geological Survey (USGS) and are provided on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from the authorized or unauthorized use of the data.

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/24/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.