Specimen Information

Faxonius rusticus
Faxonius rusticus
(Rusty Crayfish)
Crustaceans-Crayfish
Native Transplant

Specimen ID154603
GroupCrustaceans-Crayfish
GenusFaxonius
Speciesrusticus
Common NameRusty Crayfish
StateNC
CountyRutherford
LocalityBroad River, Clark Road, SR 1181 (Site_No 991027.5btw, Green River Game Land Project), ca. 10.0 air km SE Lake Lure and 13.0 air km WNW Rutherfordton
Mapping AccuracyAccurate
HUC8 NameUpper Broad
HUC8 Number03050105
HUC10 NameHeadwaters Broad River
HUC10 Number0305010503
HUC12 NameKnob Creek-Broad River
HUC12 Number030501050308
Map
+
Collection Day27
Collection Month10
Collection Year1999
Year AccuracyActual
Potential Pathwayreleased bait
Statuscollected
Reference 1
Ref. Number:13635
Author:Fullerton, A.H., and B.T. Watson
Date:2001
Title:New distributional records for two nonindigenous and one native crayfish in North Carolina.
Journal:The Journal of the Elisha Mitchell Scientific Society
Volume:117
Issue:1
Pages:66-70
CommentsRecord from NCWRC. John Alderman, Aimee Fullerton, Brian Watson, and Judith Johnson supplied information.
Record TypeSpecimen
DisposalNCSM
Museum Cat Number5261
VerifierJ. E. Cooper, A. H. Fullerton
Freshwater/MarineFreshwater
Number Collected2
Number of Females1
Specimen ImpactI Form I Male collected and 1 Female. Rare Abundance. Reproduction occurring.


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.