Morone chrysops
Morone chrysops
(White Bass)
Fishes
Native Transplant

8 results for Morone chrysops (White Bass)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1403042 AZ Big Sandy drainage1981 15030201 Big Sandylocally established
1403045 OH Upper Ohio-Shade drainage1981 05030202 Upper Ohio-Shadelocally established
39953 OHMeigsOhio River in vicinity of dams between Meigs County and Clermont County1969 05030202 Upper Ohio-Shadecollected
39952 OHMeigsOhio River in vicinity of dams of Meigs County1981 05030202 Upper Ohio-Shadecollected
269379 WV Little Kanawha drainage1986 05030203 Little Kanawhaestablished
46726 WV Little Kanawha drainage1993 05030203 Little Kanawhaestablished
1403026 WV Little Kanawha drainage1995 05030203 Little Kanawhalocally established
46730 WV Ohio River, main channel1993 05030201 Little Muskingum-Middle Islandestablished

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 [4/19/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.