Specimen Information

Crangonyx pseudogracilis
Crangonyx pseudogracilis
(northern river crangonyctid)
Crustaceans-Amphipods
Native Transplant

Specimen ID242999
GroupCrustaceans-Amphipods
GenusCrangonyx
Speciespseudogracilis
Common Namenorthern river crangonyctid
StateWA
CountyCowlitz
LocalityKalama River, Kalama River Boat Launch
Mapping AccuracyAccurate
HUC8 NameLower Columbia-Clatskanie
HUC8 Number17080003
HUC10 NameKalama River-Frontal Columbia River
HUC10 Number1708000303
HUC12 NameLittle Kalama River-Kalama River
HUC12 Number170800030305
Map
+
Collection Day18
Collection Month4
Collection Year2002
Year AccuracyActual
Potential Pathwayshipping ballast water
Statusestablished
Reference 1
Ref. Number:17275
Author:Sytsma, M.D., J.R. Cordell, J.W. Chapman, and R.C. Draheim.
Date:2004
Title:Lower Columbia River Aquatic Nonindigenous Species Survey 2001-2004. Final Technical Report.
Publisher:United States Coast Guard and the United States Fish and Wildlife Service.
Volume:2004
Issue:October
Pages:78 pp
Reference 2
Ref. Number:16728
Author:Sytsma, M.D., J.R. Cordell, J.W. Chapman, and R.C. Draheim.
Date:2004
Title:Lower Columbia River Aquatic Nonindigenous Species Survey 2001-2004. Final Technical Report: Appendices.
Publisher:United States Coast Guard and the United States Fish and Wildlife Service.
Volume:2004
Issue:October
Pages:164 pp
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 [4/26/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.