NAS - Nonindigenous Aquatic Species
Burr, B.M. 1980. A distributional checklist of the fishes of Kentucky. Brimleyana 3:53-84.
Reference Number: 955 Type: Journal Article Author: Burr, B.M. Date (year): 1980 Article Title:A distributional checklist of the fishes of Kentucky. Journal Name: Brimleyana Volume: 3 Issue: Pages: 53-84 URL: Keywords: Kentucky fishes
Ctenopharyngodon idella KY - Mississippi River, main channel, lower
Dorosoma petenense KY - Ohio River, main channel from Louisville to its mouth KY - Cumberland River, lower, main channel KY - Lower Green drainage KY - state non-specific
Esox lucius KY - state non-specific
Gambusia affinis KY - Licking River KY - Cumberland River, upper, above falls KY - Kentucky River, upper, and Red River
Lepomis auritus KY - Little River KY - Cumberland River, upper KY - Kentucky River
Lepomis microlophus KY - Cumberland River, upper
Lota lota KY - Licking River, near Milltown
Micropterus coosae KY - Martins Fork and tributaries
Morone saxatilis KY - Ohio River, lower KY - Tennessee River, lower, main channel KY - Mississippi River, main channel, lower
Oncorhynchus mykiss KY - state non-specific KY - Cumberland River (R.M. 460.9) at Lake Cumberland
Perca flavescens KY - Ohio River, main channel KY - Cumberland River, lower, main channel
Salmo trutta KY - Indian Creek KY - Big Double Creek KY - Trammel Fork
Salvelinus fontinalis KY - Shillalah Creek and Martins Fork
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/20/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.
