The Nonindigenous Occurrences section of the NAS species profiles has a new structure. The section is now dynamically updated from the NAS database to ensure that it contains the most current and accurate information. Occurrences are summarized in Table 1, alphabetically by state, with years of earliest and most recent observations, and the tally and names of drainages where the species was observed. The table contains hyperlinks to collections tables of specimens based on the states, years, and drainages selected. References to specimens that were not obtained through sighting reports and personal communications are found through the hyperlink in the Table 1 caption or through the individual specimens linked in the collections tables.

Notropis buccatus
Notropis buccatus
(Silverjaw Minnow)
Native Transplant

Copyright Info
Notropis buccatus (Cope, 1865)

Common name: Silverjaw Minnow

Synonyms and Other Names: Ericymba buccata

Taxonomy: available through www.itis.govITIS logo

Identification: Smith (1985); Page and Burr (1991); Etnier and Starnes (1993); Pflieger (1997); another name is Ericymba buccata.

Size: 9.8 cm.

Native Range: Disjunct distribution: Atlantic, lower Great Lakes, and Mississippi River drainages from New York, Pennsylvania, and Maryland to eastern Missouri; Gulf drainages from Apalachicola River, Georgia and Florida, to Mississippi River, Mississippi and Louisiana. Absent from Tennessee River drainage and Cumberland River drainage below Cumberland Falls (Lee et al. 1980 et seq.; Page and Burr 1991).

Native range data for this species provided in part by NatureServe NS logo
Hydrologic Unit Codes (HUCs) Explained
Interactive maps: Point Distribution Maps

Nonindigenous Occurrences:

Table 1. States with nonindigenous occurrences, the earliest and latest observations in each state, and the tally and names of HUCs with observations†. Names and dates are hyperlinked to their relevant specimen records. The list of references for all nonindigenous occurrences of Notropis buccatus are found here.

StateFirst ObservedLast ObservedTotal HUCs with observations†HUCs with observations†
MO199719972Upper Black; Upper St. Francis
VA197219944Lower Chesapeake; Middle New; Rapidan-Upper Rappahannock; Upper Clinch, Tennessee, Virginia

Table last updated 7/23/2024

† Populations may not be currently present.

Means of Introduction: Unknown; possible bait bucket introductions. According to Bart et al. (1994), there are two plausible explanations for this species' present distribution within the Ocmulgee River system. The original entry may have been below Lake Jackson after 1971, with subsequent dispersal to other areas (and an independent introduction into Tussahaw Creek above Lake Jackson). Or, the entry could have occurred above Lake Jackson after the late 1970s, with subsequent dispersal to areas below the lake. The Clinch River, Virginia records probably represent one or more introductions form the Big Sandy (Jenkins and Burkhead 1994).

Status: Reported from Georgia and Virginia.

Impact of Introduction: The impacts of this species are currently unknown, as no studies have been done to determine how it has affected ecosystems in the invaded range. The absence of data does not equate to lack of effects. It does, however, mean that research is required to evaluate effects before conclusions can be made.

Remarks: The absence of this species in earlier fish collections lend support to the idea that it was a recent introduction to the Ocmulgee River system of Georgia (Bart et al. 1994). In addition, Bart et al. (1994) considered it unlikely that such a distinctive species would have been overlooked by earlier investigators. This species may have entered the Susquehanna as a bait bucket release (Denoncourt et al. 1975b). Bean and Weed (1911) stated that this species was probably introduced into the upper portion of the Potomac River by the U.S. Bureau of Fisheries. According to Jenkins and Burkhead (1994), introduced status in the Potomac would indicate that this species also was introduced into the Rappahannock, for which the first record is 1962. However, Hocutt et al. (1986) listed it as native to the Rappahannock and Susquehanna drainages. In his recent work on Missouri fishes, Pflieger (1997) stated that isolated records of this species from the St. Francis drainage in Madison County and a tributary of Logan Creek in Reynolds County are fairly recent and possibly the result of bait bucket releases.

References: (click for full references)

Pflieger, W. 1997. The Fishes of Missouri. Missouri Department of Environmental Conservation, Jefferson City, MO. 372 pp.

Other Resources:
FishBase Summary

Author: Nico, L.

Revision Date: 8/5/2004

Peer Review Date: 8/5/2004

Citation Information:
Nico, L., 2024, Notropis buccatus (Cope, 1865): U.S. Geological Survey, Nonindigenous Aquatic Species Database, Gainesville, FL, https://nas.er.usgs.gov/queries/FactSheet.aspx?speciesID=588, Revision Date: 8/5/2004, Peer Review Date: 8/5/2004, Access Date: 7/23/2024

This information is preliminary or provisional and is subject to revision. It is being provided to meet the need for timely best science. The information has not received final approval by the U.S. Geological Survey (USGS) and is provided on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from the authorized or unauthorized use of the information.


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 [7/23/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.