NAS - Nonindigenous Aquatic Species
Miller, R.R. 1952. Bait fishes of the lower Colorado River, from Lake Mead, Nevada, to Yuma, Arizona, with a key for identification. California Fish and Game 38:7-42.
Reference Number: 114
Type: Journal Article
Author: Miller, R.R.
Date (year): 1952
Article Title:Bait fishes of the lower Colorado River, from Lake Mead, Nevada, to Yuma, Arizona, with a key for identification.
Journal Name: California Fish and Game
Keywords: Arizona, Nevada, Colorado River, fishes, bait
Astyanax mexicanus AZ - lower Colorado River
Catostomus commersonii CO - Colorado River near Hot Sulphur Springs CO - Dry Creek, 3 miles west of Olathe
Cottus bairdii AZ - Lake Havasu first point south of Needles Boat Landing AZ - Lake Havasu CA - Lake Havasu first point south of Needles Boat Landing
Cyprinus carpio NV - Pahranagat Lakes (Upper and Lower Lake)
Gila atraria UT - Strawberry Reservoir UT - Fish Lake
Lepidomeda albivallis CO - state non-specific
Lepidomeda copei UT - Strawberry Reservoir
Lepomis macrochirus AZ - Salt River at Tempe
Notemigonus crysoleucas AZ - Coconino National Forest in some lakes AZ - Upper Lake Mary CA - isolated pond near Blythe NV - Colorado River NV - Lake Tahoe NV - Amargosa River north of Beatty
Pantosteus platyrhynchus NV - Lake Mead
Rhinichthys osculus UT - near Huntington
Richardsonius balteatus hydrophlox UT - Sheep Creek WY - Colorado River drainage in Wyoming (Green River drainage)
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. . Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [9/26/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.