Specimen Information

Potamogeton crispus
Potamogeton crispus
(curly-leaf pondweed)

Specimen ID1695528
Common Namecurly-leaf pondweed
LocalityMiddleton Town, Crystal Lake
Mapping AccuracyAccurate
HUC8 NameOutlet Connecticut River
HUC8 Number01080205
HUC10 NameHigganum Creek-Connecticut River
HUC10 Number0108020507
HUC12 NameMill Creek-Connecticut River
HUC12 Number010802050702
Collection Day8
Collection Month4
Collection Year2021
Year AccuracyActual
Potential Pathwayhitch hiker on small watercraft
CommentsFrom report: Aquatic Plant Survey Report for Crystal Lake (Middletown, CT), Prepared for the Pond and Lake Connection, December 21st, 2021 Data from an herbicide pre-treatment survey. Since 2019, there has been a steady decrease in curly-leaf pondweed abundance during the pre-treatment surveys. During the April 8, 2021 survey most of the plants reached about 1/3 to 2/3 of the water column in height. The Curlyleaf pondweed plants were much lower in the water column in the 2020 and 2021 pre-treatment surveys than in the 2019 pre-treatment survey. In 2019, the plants were almost always just beneath the surface or breaking the surface of the water. It should be noted, however, that the 2019 pre-treatment survey was conducted on May 1st, much later than the March 24th, 2020 and April 8th, 2021 pre-treatment surveys.
Record TypeNAS sighting report
VerifierNortheast Aquatic Research, LLC
Number Collected68


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. [2023]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [1/28/2023].

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.