Disclaimer:

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.




Meda fulgida
Meda fulgida
(Spikedace)
Fishes
Native Transplant

Copyright Info
Meda fulgida Girard, 1856

Common name: Spikedace

Taxonomy: available through www.itis.govITIS logo

Identification: Minckley (1973); Sublette et al. (1990); Page and Burr (1991).

Size: 9.1 cm.

Native Range: Gila River system, Arizona and New Mexico (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 Meda fulgida are found here.

StateFirst ObservedLast ObservedTotal HUCs with observations†HUCs with observations†
AZ199019901Upper Santa Cruz

Table last updated 12/2/2024

† Populations may not be currently present.


Means of Introduction: Intentionally stocked for the purpose of restoring or preserving an imperiled species. Stock obtained from Arivaipa Creek was placed in Sonoita Creek in 1968 (U.S. Fish and Wildlife Service 1990a).

Status: The population is now extirpated (U.S. Fish and Wildlife Service 1990a).

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 Spikedace is listed as a federally threatened species (U.S. Fish and Wildlife Service 1993a). It has been extirpated throughout much of its native range apparently as a result of competition or displacement by the introduced red shiner Cyprinella lutrensis (Minckley and Deacon 1968).

Other Resources:
FishBase Summary

Author: Pam Fuller, and Leo Nico

Revision Date: 8/27/1999

Peer Review Date: 8/27/1999

Citation Information:
Pam Fuller, and Leo Nico, 2024, Meda fulgida Girard, 1856: U.S. Geological Survey, Nonindigenous Aquatic Species Database, Gainesville, FL, https://nas.er.usgs.gov/queries/FactSheet.aspx?SpeciesID=570, Revision Date: 8/27/1999, Peer Review Date: 8/27/1999, Access Date: 12/2/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.

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 [12/2/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.