Specimen Information

Myriophyllum aquaticum
Myriophyllum aquaticum
(parrot feather)

Specimen ID1396569
Common Nameparrot feather
LocalityIn backwaters of Mississippi River, Pool 5; just south of Buffalo City, WI
Mapping AccuracyAccurate
HUC8 NameBuffalo-Whitewater
HUC8 Number07040003
HUC10 NameCity of Winona-Mississippi River
HUC10 Number0704000306
HUC12 NameBuffalo City-Mississippi River
HUC12 Number070400030604
Collection Day8
Collection Month8
Collection Year2012
Year AccuracyActual
Potential Pathwayunknown
Reference 1
Ref. Number:24369
Author:Center for Invasive Species and Ecosystem Health.
Title:EDDMapS: Early detection and distribution mapping system
Publisher:The University of Georgia
Commentsparrot feather found and identified on August 8, 2012, but in looking at prior photos taken on July 26, 2012 noted they were also present then. Half acre site also had water lettuce and water hyacinth present (will report them separately). On August 15, WI DNR Invasives Coordinator Scott Provost and aquatic plant expert Paul Kawinski came to the site and removed the parrotfeather by hand. They reported the plants all originated from 2 plants. Paul, Scott, and Sam Betterley made a voucher specimen from those plants and submitted it to the Robert W. freckmann Herbarium, UW - Stevens Point. ; EDDMapS report
Record TypeLiterature
DisposalRobert W. Freckmann Herbarium
Museum Cat Number Record ID:163708
Size4 Sq Feet


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/19/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.