<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-CA link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>Would it be possible to give a scientific name of the plant in the
list’s communications or in the official documents? Why to use only the
vernacular names? In the matter of fact, the Tennessee Purple Coneflower should
be spelled Tennessee Purple-Coneflower with a hyphen between “Purple”
and “Coneflower”. That hyphen indicates that the plant is not a
real Coneflower (the genus Rudbeckia), but it belongs to a different genus, in
this case the genus Echinacea. Why not to use “Echinacea tennesseensis
(Beadle) Small” at least once in this document?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>Adolf Ceska, Victoria, British Columbia, Canada<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>
native-plants-bounces@lists.plantconservation.org
[mailto:native-plants-bounces@lists.plantconservation.org] <b>On Behalf Of </b>Patricia_DeAngelis@fws.gov<br>
<b>Sent:</b> August-13-10 8:12 AM<br>
<b>To:</b> native-plants@lists.plantconservation.org;
mpwg@lists.plantconservation.org<br>
<b>Subject:</b> [PCA] Fw: [fws-news] Tennessee Purple Coneflower Proposed for
Delisting: Comments being accepted<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><br>
<span style='font-family:"Arial","sans-serif"'>Date: Thursday, August 12, 2010
11:54:47 AM<br>
Subject: [fws-news] Tennessee Purple Coneflower Proposed for Delisting<br>
<br>
**************************************************************<br>
<br>
<b>Tennessee Purple Coneflower Proposed for Delisting </b><br>
<br>
The U.S. Fish and Wildlife Service today proposed removing the Tennessee <br>
purple coneflower from the list of threatened and endangered species, <br>
marking the success of a decades-long cooperative conservation effort <br>
under the Endangered Species Act. The rule was published in today’s
<br>
Federal Register, and the public is invited to comment on the proposal for <br>
the next 60 days until October 12, 2010.<br>
<br>
“More than 30 years of protecting and expanding Tennessee purple <br>
coneflower colonies finally brought success to the Service and its <br>
conservation partners,” said Cindy Dohner, the Service’s Southeast <br>
Regional Director. “Thanks to the efforts of many people, adequate <br>
regulations exist to protect the plant’s populations, and these <br>
populations have stabilized to the point that the species has recovered <br>
and no longer needs the protection of the Endangered Species Act.” <br>
<br>
In addition, successful recovery efforts increased the known number and <br>
distribution of Tennessee purple coneflower populations range-wide, and <br>
provided adequate protection and management to ensure the plant’s <br>
long-term survival and recovery. <br>
<br>
When first listed in 1979, the coneflower was found only in small <br>
populations in Davidson, Rutherford, and Wilson counties, each considered <br>
a unique population. Tennessee purple coneflower was first collected in <br>
1878, in Rutherford County, by one of Tennessee’s earliest botanists, Dr.
<br>
Augustin Gattinger, and was described in 1898. The species then went <br>
unnoticed until it was rediscovered in the late 1960s in Davidson County <br>
and in the early 1970s in Wilson County. Currently, this plant exists in <br>
limestone barrens and cedar glades of the Central Basin in Davidson, <br>
Rutherford, and Wilson counties in Tennessee. <br>
<br>
In 1989, the Service published the revised recovery plan for Tennessee <br>
purple coneflower which included a criterion for recovering the species to <br>
the point that it could be considered for delisting. This criterion <br>
requires that the species exist in five secure or protected populations, <br>
consisting of at least three colonies each. There are now 19 secure <br>
colonies distributed among six populations, five of which contain three or <br>
more colonies. These 19 colonies account for approximately 83 percent of <br>
the species’ distribution. <br>
<br>
This recovery success story is the result of conservation efforts by many <br>
partners who worked more than 30 years to protect and expand the Tennessee <br>
purple coneflower colonies. The Service’s partners include the
Tennessee <br>
Department of Environment and Conservation and Tennessee Division of <br>
Forestry, The Nature Conservancy, U.S. Army Corps of Engineers, National <br>
Park Service and various private landowners. <br>
<br>
Many factors influenced the recovery, including discovering new colonies <br>
through surveys of suitable habitat; researching the life history, <br>
genetics, and ecology of the species; and establishing new colonies from <br>
seed or nursery propagated plants. <br>
<br>
The Tennessee Department of Environment and Conservation was instrumental <br>
in recovering the Tennessee purple coneflower by buying or securing sites <br>
through other means to protect the species, as well as building fences to <br>
protect colonies from outdoor recreational vehicle damage, removing <br>
competing vegetation, and using fire with prescribed burns at many sites <br>
to provide habitat conditions that help this species thrive. <br>
<br>
Tennessee purple coneflower is a member of the sunflower family in the <br>
genus Echinacea, which includes several purple coneflower species that are <br>
commercially marketed for ornamental and medicinal purposes. The <br>
Tennessee purple coneflower can be found commercially for landscaping <br>
purposes, but most often these plants are hybrids. <br>
<br>
If Tennessee purple coneflower is removed from the list of threatened and <br>
endangered species, federal agencies will no longer need to consult with <br>
the U.S. Fish and Wildlife Service to ensure any action they authorize, <br>
fund, or carry out is not likely to jeopardize the continued existence of <br>
this species. The Service will work with Tennessee Department of <br>
Environment and Conservation to implement a post-delisting monitoring plan <br>
for at least five years if the species is delisted. <br>
<br>
To ensure that the final decision resulting from this proposal should be <br>
as accurate and effective as possible, the Service is soliciting comments <br>
and information from the public, other governmental agencies, the <br>
scientific community, industry, and any other interested parties. <br>
<br>
The Service particularly seeks comments relating to the biological <br>
information about this species, relevant data pertaining to threats, <br>
especially relating to current or planned activities near Tennessee purple <br>
coneflower habitat, and the draft post-delisting monitoring plan. <br>
<br>
The proposal and a draft post-delisting monitoring plan were published in <br>
today’s Federal Register. Written comments regarding the proposed
rule <br>
and draft post-delisting monitoring plan must be received by October 12, <br>
2010. All comments will be considered before a final determination is <br>
made. Comments should be submitted by one of the following methods:<br>
<br>
· Federal eRulemaking Portal:
http://www.regulations.gov. Follow <br>
the instructions for submitting comments.<br>
<br>
· U.S. mail or hand-delivery to: Public Comments
Processing, Attn: <br>
Docket Number FWS–R4–ES–2010–0059, Division of Policy
and Directives <br>
Management; U.S. Fish and Wildlife Service; 4401 N. Fairfax Drive, Suite <br>
222; Arlington, VA 22203. <br>
<br>
The proposed rule is on the Cookeville Ecological Services Field Office <br>
website at http://www.fws.gov/cookeville/. Copies of the proposed rule <br>
and draft post-delisting monitoring plan are also available by contacting <br>
Geoff Call, Recovery Coordinator, U.S. Fish and Wildlife Service, 446 Neal <br>
Street, Cookeville, Tennessee 38501 (telephone 931/528-6481, extension <br>
213; facsimile 931/528-7075). <br>
<br>
The mission of the U.S. Fish and Wildlife Service is working with others <br>
to conserve, protect and enhance fish, wildlife, plants and their habitats <br>
for the continuing benefit of the American people. For more information, <br>
visit http://www.fws.gov or http://www.fws.gov/southeast. <br>
<br>
-FWS-<br>
<br>
***************************************************************************<br>
News releases are also available on the World Wide Web at <br>
http://news.fws.gov<br>
<br>
Questions concerning a particular news release or item of<br>
information should be directed to the person listed as the<br>
contact. General comments or observations concerning the<br>
content of the information should be directed to Malcomb Barsella </span><br>
<span style='font-family:"Arial","sans-serif"'>(malcomb_barsella@fws.gov) in
the Office of External Affairs.<br>
<br>
. ***************************************************************************</span><o:p></o:p></p>
</div>
</body>
</html>