Specimen Information

Potamogeton crispus
Potamogeton crispus
(curly-leaf pondweed)

Specimen ID1695529
Common Namecurly-leaf pondweed
LocalityLake Beseck
Mapping AccuracyAccurate
HUC8 NameOutlet Connecticut River
HUC8 Number01080205
HUC10 NameMattabesset River
HUC10 Number0108020506
HUC12 NameCoginchaug River
HUC12 Number010802050602
Collection Day7
Collection Month8
Collection Year2021
Year AccuracyActual
Potential Pathwayhitch hiker on small watercraft
CommentsObservations reported in report: Lake Beseck 2021 Quantitative Aquatic Plant Study Prepared for the Lake Beseck Environmental Committee Town of Middlefield, CT February 12, 2022 Potamogeton crispus is an early senescing species that is present in the lake between early May and mid-June. Because P. crispus dies off early in the season, it generally does not create issues with recreational access. Furthermore, the population of P. crispus in Lake Beseck was significantly impacted by the dam repair in 2013; that repair required that the lake be drained to about 10 percent capacity. The draining of the lake resulted in the exposure of the littoral zone to winter temperatures and dewatering of the lake sediments. Freezing and drying have a significant impact the reproductive structures of all aquatic macrophytes including P. crispus. Since that time, the population of P. crispus has remained small and has not significantly affect recreational access
Record TypeNAS sighting report
VerifierLarry Marsicano, Aquatic Ecosystem Research
Number Collected1


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