Pylodictis olivaris
Pylodictis olivaris
(Flathead Catfish)
Native Transplant

7 results for Pylodictis olivaris (Flathead Catfish)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1410182 SDDavisonLake Mitchell2007 10160011 Lower Jamesestablished
1410183 SDDavisonLake Mitchell2011 10160011 Lower Jamesestablished
1410184 SDDavisonLake Mitchell2012 10160011 Lower Jamesestablished
1410185 SDDavisonLake Mitchell2014 10160011 Lower Jamesestablished
1467932 SDHutchinsonJames River at Olivet2018 10160011 Lower Jamesestablished
1464611 SDHutchinsonJames River between the confluence of the Missouri River and the first major dam2000 10160011 Lower Jamesestablished
1464744 SDYanktonJames River [near railroad crossing]1975 10160011 Lower Jamesestablished

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.


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. [2023]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [12/8/2023].

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.