Potamogeton crispus
Potamogeton crispus
(curly-leaf pondweed)

9 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
1526722 WAAdamsSprague Lake1994 17060108 Palouseestablished
1525516 WAAdamsSprague Lake1999 17060108 Palouseestablished
1529124 WAAdamsSprague Lake2002 17060108 Palouseestablished
1527919 WAAdamsSprague Lake2011 17060108 Palouseestablished
1468892 WAFranklin[Palouse River, N of Palouse Falls State Park]2018 17060108 Palouseestablished
1525563 WAFranklinSnake River at Lyons Ferry1997 17060108 Palouseestablished
1529180 WAFranklinSnake River near Lyons Ferry1997 17060108 Palouseestablished
243832 WAFranklinSnake River, Lake Herbert G West, at Lyons Ferry State Park.2006 17060108 Palouseestablished
1529314 WASpokaneWilliams Lake2014 17060108 Palouseestablished

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