Reference List

This list includes references used to derive specimen records as well as those with scientific name Pantosteus platyrhynchus listed in key words.

Results also available in (click to export table to spreadsheet)

REFTypeCut-and-Paste Reference
121 Book La Rivers, I. 1962. Fishes and fisheries of Nevada. Nevada State Print Office, Carson City, NV.
114 Journal Article 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.
13709 Book Moyle, P.B. 2002. Inland fishes of California. Second edition. University of California Press, Berkeley, CA.
1385 Conference Proceedings Rinne, J.N. 1995. The effects of introduced fishes on native fishes: Arizona, Southwestern United States. Page 149–159 in Philipp, D.P., J.M. Epifano, J.E. Marsden, J.E. Claassen, and R.J. Wolotina, Jr, eds. Protection of aquatic diversity. Proceedings of the World Fisheries Congress, Theme 3. Oxford & IBH Publishing Company. New Delhi, India.
127 Book Sigler, W.F., and R.R. Miller. 1963. Fishes of Utah. Utah Department of Fish and Game, Salt Lake City, UT.
29139 Journal Article Taba, S.S., J.R. Murphy, and H.H. Frost. 1965. Notes on the fishes of the Colorado River, near Moab, Utah. Proceedings of the Utah Academy of Science 42(2):280–283. http://www.nativefishlab.net/library/textpdf/13441.pdf.


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. [2026]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [4/8/2026].

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.