Specimen Information

Dorosoma petenense
Dorosoma petenense
(Threadfin Shad)
Fishes
Native Transplant

Specimen ID1403580
GroupFishes
GenusDorosoma
Speciespetenense
Common NameThreadfin Shad
StateTN
LocalityUpper Elk drainage
Mapping AccuracyCentroid
Centroid TypeHUC8
HUC8 NameUpper Elk
HUC8 Number06030003
Map
+
Collection Year1993
Year AccuracyPublication Year
Potential Pathwaystocked for sport
Statusestablished
Reference 1
Ref. Number:705
Author:Etnier, D.A., and W.C. Starnes.
Date:1993
Title:The fishes of Tennessee.
Publisher:The University of Tennessee Press
Pages:681 pp
Reference 2
Ref. Number:14971
Author:Boschung, H.T., Jr., and R.L. Mayden.
Date:2004
Title:Fishes of Alabama.
Publisher:Smithsonian Books
Pages:736 pp
Reference 3
Ref. Number:1523
Author:Laird, C.A., and L.M. Page
Date:1996
Title:Non-native fishes inhabiting the streams and lakes of Illinois.
Journal:Illinois Natural History Survey Bulletin
Volume:35
Issue:1
Pages:1-51
CommentsBoschung and Mayden 2004 say introduced to TN drainage; Mettee et al. say native to TN drainage; Etnier and Starnes 1993 say native; In 1948, thread - fin shad were first discovered in impoundments of the Tennessee River (Tennessee Valley Authority, 1954)[Irons et al. 2009]; stocked in TVA reservoirs in 1940s-1950s (Laird and Page, 1996).
Record TypeLiterature
Freshwater/MarineFreshwater


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