Specimen Information

Oncorhynchus clarkii seleniris
Oncorhynchus clarkii seleniris
(Paiute cutthroat trout)
Fishes
Native Transplant

Specimen ID293652
GroupFishes
GenusOncorhynchus
Speciesclarkii
Subspeciesseleniris
Common NamePaiute cutthroat trout
StateCA
CountyMono
LocalityNorth Fork of Cottonwood Creek, Inyo National Forest.
Mapping AccuracyAccurate
HUC8 NameFish Lake-Soda Spring Valleys
HUC8 Number16060010
HUC10 NameFurnace Creek-Frontal Fish Lake Valley
HUC10 Number1606001009
HUC12 NameCottonwood Creek
HUC12 Number160600100906
Map
+
Collection Day23
Collection Month8
Collection Year1946
Year AccuracyActual
Potential Pathwaystocked for conservation
Statusestablished
Reference 1
Ref. Number:25336
Author:Vestal, E.H.
Date:1947
Title:A new transplant of the Piute trout (Salmo clarkii seleniris) from Silver King Creek, Alpine County, California.
Journal:California Fish and Game
Volume:33
Issue:2
Pages:89-95
Reference 2
Ref. Number:25329
Author:U.S. Fish and Wildlife Service (USFWS).
Date:2004
Title:Revised recovery plan for the Paiute cutthroat trout (Oncorhynchus clarkii seleniris).
Publisher:USFWS
Pages:105 pp.
Reference 3
Ref. Number:13709
Author:Moyle, P.B.
Date:2002
Title:Inland fishes of California.
Publisher:University of California Press
Pages:502 pp.
CommentsLimited to uppermost 5.5 km of stream above Tres Plumas barrier.
Record TypeLiterature
Earliest Recorddrainage
Freshwater/MarineFreshwater
Number Stocked401


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