02.11.2012 Views

Piping Plover - U.S. Fish and Wildlife Service

Piping Plover - U.S. Fish and Wildlife Service

Piping Plover - U.S. Fish and Wildlife Service

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

WM 2.2 UPDATED INFORMATION AND CURRENT SPECIES STATUS<br />

FOR THE WINTERING AND MIGRATION RANGE<br />

<strong>Piping</strong> plover subspecies are phenotypically indistinguishable, <strong>and</strong> most studies in the<br />

nonbreeding range, i.e, wintering <strong>and</strong> migration range, report results without regard to<br />

breeding origin. Although a recent analysis shows strong patterns in the wintering<br />

distribution of piping plovers from different breeding populations, partitioning is not<br />

complete <strong>and</strong> major information gaps persist (see section WM 2.2.1.3 below). Therefore,<br />

new information summarized here pertains to the species as a whole (i.e., all three<br />

breeding populations delineated in section 2.1), except where a particular breeding<br />

population is specified.<br />

WM 2.2.1 Biology <strong>and</strong> habitat<br />

A large body of information regarding the biology, habitat, <strong>and</strong> status of wintering <strong>and</strong><br />

migrating piping plovers has become available since publication of the 1985 final rule,<br />

the 1988 Northern Great Plains recovery plan, <strong>and</strong> the 1991 five-year review. Much of<br />

this information was incorporated into the 1996 revised Atlantic Coast <strong>and</strong> 2003 Great<br />

Lakes recovery plans. Here, we summarize recent information pertinent to the<br />

nonbreeding portion of the annual cycle, emphasizing studies <strong>and</strong> reports that have<br />

become available since 2003, with brief references to a few earlier studies.<br />

WM 2.2.1.1 Life history:<br />

New information confirms inter- <strong>and</strong> intra-annual fidelity of piping plovers to migration<br />

<strong>and</strong> wintering sites as described in the 1996 Atlantic Coast <strong>and</strong> 2003 Great Lakes<br />

recovery plans. Gratto-Trevor et al. (2009) reported that six of 259 b<strong>and</strong>ed piping<br />

plovers observed more than once per winter moved across boundaries of seven<br />

continental U.S. regions (subdivisions of the migration <strong>and</strong> wintering range as depicted in<br />

Figure WM1). Of 216 birds observed in different years, only eight changed regions<br />

between years, <strong>and</strong> several of these shifts were associated with late summer or early<br />

spring migration periods (Gratto-Trevor et al. 2009). Local movements are more<br />

common. In South Carolina, Maddock et al. (2009) documented many cross-inlet<br />

movements by wintering b<strong>and</strong>ed piping plovers as well as occasional movements of up to<br />

18 km by approximately 10% of the b<strong>and</strong>ed population; larger movements within South<br />

Carolina were seen during fall <strong>and</strong> spring migration. Similarly, eight b<strong>and</strong>ed piping<br />

plovers that were observed in two locations during 2006-2007 surveys in Louisiana <strong>and</strong><br />

Texas were all in close proximity to their original location, such as on the bay <strong>and</strong> ocean<br />

side of the same isl<strong>and</strong> or on adjoining isl<strong>and</strong>s (Maddock 2008).<br />

The mean home range size (95% of locations) for 49 radio-marked piping plovers in<br />

southern Texas in 1997-1998 was 12.6 km 2 , the mean core area (50% of locations) was<br />

2.9 km 2 , <strong>and</strong> the mean linear distance moved between successive locations (1.97 + 0.04<br />

days apart), averaged across seasons, was 3.3 km (Drake et al. 2001). Seven radio-tagged<br />

piping plovers used a 20.1 km 2 area (100% minimum convex polygon) at Oregon Inlet,<br />

23

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!