Specimen Information

Alosa sapidissima
Alosa sapidissima
(American Shad)
Fishes
Native Transplant

Specimen ID35568
GroupFishes
GenusAlosa
Speciessapidissima
Common NameAmerican Shad
StateMI
CountyWayne
LocalityDetroit River at Detroit
Mapping AccuracyAccurate
HUC8 NameDetroit
HUC8 Number04090004
HUC10 NameDetroit
HUC10 Number0409000405
HUC12 Name040900040000
HUC12 Number040900040503
Map
+
Collection Day24
Collection Month6
Collection Year1873
Year AccuracyActual
Potential Pathwaystocked for food
Statusfailed
Reference 1
Ref. Number:1499
Author:Baird, S.F.
Date:1878
Title:Report of the U.S. Fish Commission for 1875-1876.
Publisher:Goverment Printing Office, Washington.
Volume:4
Reference 2
Ref. Number:1776
Author:Milner, J.W.
Date:1874
Title:Report on the propagation of the shad (Alosa sapidissima) and its introduction into new waters by the U.S. Fish Commissioner in 1873.
Publisher:United States Commission of Fish and Fisheries
Pages:419-451
Reference 3
Ref. Number:24746
Author:Clark, G., A.J. Kellogg, J.J. Bagley, and G.H. Jerome.
Date:1874
Title:State of Michigan. First report of the state commissioners and superintendent, on state fisheries, for 1873-4, ending December 1st, 1874.
Publisher:W.S. George and Company, Lansing, MI
Pages:46 pp.
CommentsPut into river near the Detroit and Milwaukee Railway depot.
Record TypeLiterature
Freshwater/MarineFreshwater
Number Stocked20000


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