Specimen Information

Pylodictis olivaris
Pylodictis olivaris
(Flathead Catfish)
Fishes
Native Transplant

Specimen ID293273
GroupFishes
GenusPylodictis
Speciesolivaris
Common NameFlathead Catfish
StateNC
CountyCumberland
LocalityCape Fear River, 0.5 miles [N] US 301, [ca. 1.6 air miles E center Fayetteville], [see remarks]
Mapping AccuracyAccurate
HUC8 NameUpper Cape Fear
HUC8 Number03030004
HUC10 NameCross Creek-Cape Fear River
HUC10 Number0303000407
HUC12 NameCity of Fayetteville-Cape Fear River
HUC12 Number030300040706
Map
+
Collection Day4
Collection Month10
Collection Year1976
Year AccuracyActual
Potential Pathwaystocked for sport
Statusestablished
Reference 1
Ref. Number:25185
Author:Anonymous
Date:2012
Title:Museum collection records of Pylodictis olivaris in U.S. derived from a search on FishNET on 7 Dec 2012.
Publisher:Anonymous
Reference 2
Ref. Number:20908
Author:North Carolina Museum of Natural Sciences.
Date:2011
Title:North Carolina Museum of Natural Sciences - Ichthyology Collection Database.
Publisher:North Carolina Museum of Natural History.
Reference 3
Ref. Number:1491
Author:Guier, C.R., L.E. Nichols, R.T. Rachels.
Date:1981
Title:Biological investigation of flathead catfish in the Cape Fear River.
Journal:Proc. Annual Conference S.E. Assoc. Fish & Wildl. Agencies
Volume:35
Pages:607-621
CommentsDifferent size classes present.
Record TypeSpecimen
DisposalNorth Carolina Museum of Natural Sciences
Museum Cat NumberNCSM 48157
Freshwater/MarineFreshwater
Number Collected5
Number Preserved1


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/16/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.