Pylodictis olivaris
Pylodictis olivaris
(Flathead Catfish)
Native Transplant

9 results for Pylodictis olivaris (Flathead Catfish)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1632591 ARCrawford[No locality description provided]2018 11110104 Robert S. Kerr Reservoirestablished
1545040 DENew CastleBrandywine River [in Wilmington] (tidal)2018 02040205 Brandywine-Christinaestablished
1616568 NCWake[No locality description provided]2018 03020201 Upper Neuseestablished
1634194 OHLucasNorth side Maumee Bay2018 04260000 Lake Erieestablished
1466093 SCCharlestonDawho River2018 03050206 Edisto Riverestablished
1466213 SCColletonEdisto River2018 03050206 Edisto Riverestablished
1466025 SCDorchesterAshley River2018 03050201 Cooperestablished
1467932 SDHutchinsonJames River at Olivet2018 10160011 Lower Jamesestablished
1523948 TXGarzaAlan Henry Reservoir2018 12050004 Double Mountain Fork Brazosestablished

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

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.