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

7 results for Potamogeton crispus (curly-leaf pondweed)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
232492 COJeffersoncommon in inlet to Evergreen Lake, Evergreen1952 10190002 Upper South Platteestablished
232491 COJeffersonEvergreen Lake1952 10190002 Upper South Platteestablished
1760204 PABedford[No locality description provided]1952 02050303 Raystown 
232992 PABedfordAlum Bank, fish hatchery, 1.5 mi SE1952 02050303 Raystownestablished
232557 PABedfordpond at fish hatchery, 2.5 me s e of Alum Bank1952 02050303 Raystownestablished
1658171 PAChester3 mi S of Downingtown, below bridge PA [322]1952 02040205 Brandywine-Christinaunknown
229482 RI Rhode Island1952 01090000 Massachusetts-Rhode Island Coastalestablished

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