Pylodictis olivaris
Pylodictis olivaris
(Flathead Catfish)
Native Transplant

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

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1468036 IAWoodburyMissouri River [at River mile 717]1974 10230001 Blackbird-Soldierestablished
1468037 IAWoodburyMissouri River [at River mile 717]1982 10230001 Blackbird-Soldierestablished
1468057 IAWoodburyMissouri River [at River mile 717]1982 10230001 Blackbird-Soldierestablished
1467152 IAWoodburyMissouri River [between Sioux City and Plattsmouth]1967 10230001 Blackbird-Soldierestablished
1467167 IAWoodburyMissouri River [between South Sioux City and Dakota City], Dakota County, Nebraska1990 10230001 Blackbird-Soldierestablished
1467150 IAWoodburyMissouri River [in Nebraska portion]1944 10230001 Blackbird-Soldierestablished

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. [2024]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [6/14/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.