Potamogeton crispus
Potamogeton crispus
(curly-leaf pondweed)

8 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
254801 CTHartfordGrannis Lake2004 01100004 Quinnipiacestablished
234986 CTHartfordHamlin Pond, Plainville2001 01100004 Quinnipiacestablished
254795 CTMiddlesexBlack Pond, near Meriden2004 01100004 Quinnipiacestablished
234984 CTNew HavenHanover Pond, Meriden town2001 01100004 Quinnipiacestablished
254817 CTNew HavenLake Saltonstall2004 01100004 Quinnipiacestablished
254818 CTNew HavenLake Saltonstall2004 01100004 Quinnipiacestablished
254811 CTNew HavenNorth Farms Reservoir, Wallingford2004 01100004 Quinnipiacestablished
254813 CTNew HavenQuonnipaug Lake, Guilford town2004 01100004 Quinnipiacestablished

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.


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 [4/20/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.