Oncorhynchus clarkii
Oncorhynchus clarkii
(Cutthroat Trout)
Fishes
Native Transplant

7 results for Oncorhynchus clarkii (Cutthroat Trout)
Download Data

Specimen IDCommon NameStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
28734 Cutthroat TroutCA Mono Lake drainage1976 18090101 Mono Lakecollected
259719 Paiute cutthroat troutCAInyoBirchim Lake1957 18090102 Crowley Lakefailed
283330 Colorado River cutthroat troutCAInyoWilliamson Lakes1931 18090103 Owens Lakeestablished
1419155 Cutthroat TroutCAMonoFarringtons.1916 18090101 Mono Lakeestablished
259714 Paiute cutthroat troutCAMonoMcGee Creek1956 18090101 Mono Lakefailed
1419152 Cutthroat TroutCAMonoNorth FK Cottonwood Creek, White Mountains1974 18090102 Crowley Lakeestablished
1419191 Cutthroat TroutCAMonoO'Harrel Canyon1978 18090102 Crowley Lakeestablished

Data Disclaimer: Number of records does not imply species abundance. This summary represent collection records only and may not reflect the actual distribution of established populations. 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 [12/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.