Specimen Information

Dorosoma petenense
Dorosoma petenense
(Threadfin Shad)
Native Transplant

Specimen ID1403510
Common NameThreadfin Shad
LocalityMiddle Ohio-Laughery (HUC8) non-specific
Mapping AccuracyCentroid
Centroid TypeHUC8
HUC8 NameMiddle Ohio-Laughery
HUC8 Number05090203
Collection Year1986
Year AccuracyPublication Year
Potential Pathwaystocked for sport
Reference 1
Ref. Number:82
Author:Burr, B.M., and M.L. Warren, Jr.
Title:A distributional atlas of Kentucky fishes. Scientific and Technical Series No. 4.
Publisher:Kentucky State Nature Preserves Commission
Pages:398 pp
CommentsBefore 1945, the threadfin shad was found only in rivers and streams flowing into the Gulf of Mexico, from Florida to Mexico (Forbes and Richardson, 1920; Smith, 1979). Later, its range expanded northward (Trautman, 1981). In 1948, thread - fin shad were discovered in impoundments of the Tennessee River (Tennessee Valley Authority, 1954), and in 1957 the first Illinois specimens were collected from tributaries of the Ohio River (Minckley and Krumholz, 1960). An alternative opinion is that the threadfin shad was originally found as far south as Belize and was distributed northward into Gulf States as well as states bordering the lower Mississippi and Ohio Rivers, including Illinois and Missouri (Page and Burr, 1991).[Irons et al. 2009]
Record TypeLiterature


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 [11/28/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.