Potamogeton crispus
Potamogeton crispus
(curly-leaf pondweed)
Plants
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

6 results for Potamogeton crispus (curly-leaf pondweed)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1891093 MIEaton[No locality description provided]2025 04050004 Upper Grand 
1562437 MIIngham[Lake Lansing] [No locality description provided]2014 04050004 Upper Grandestablished
1562030 MIIngham[No locality description provided]2014 04050004 Upper Grandestablished
1562130 MIIngham[No locality description provided]2014 04050004 Upper Grandestablished
1562409 MIIngham[No locality description provided]2014 04050004 Upper Grandestablished
1691961 MIJacksonGrass Lake2021 04050004 Upper Grandunknown

Data Disclaimer: Number of records does not imply species abundance. This summary represent collection records only and may not reflect the actual distribution of established populations. These data are preliminary or provisional and are subject to revision. They are being provided to meet the need for timely best science. The data have not received final approval by the U.S. Geological Survey (USGS) and are 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 data.

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 [1/16/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.