26.03.2013 Views

Habitat use and population dynamics of the Azure-Winged Magpie ...

Habitat use and population dynamics of the Azure-Winged Magpie ...

Habitat use and population dynamics of the Azure-Winged Magpie ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

3.3.5 Pair-bond retentions<br />

Due to <strong>the</strong> short period <strong>of</strong> data collection (four years) <strong>and</strong> high number <strong>of</strong> pairings involving<br />

unidentified mates (Table 3.11), I did not attempt to analyse pair-bond retention. However, I did<br />

collect <strong>the</strong> following observations on pair-bonds.<br />

Out <strong>of</strong> <strong>the</strong> 29 pairs (that had at least one b<strong>and</strong>ed individual) known to have bred between 2007<br />

<strong>and</strong> 2010, 22 pairs had at least one pair member that attempted breeding in more than one season<br />

(Table 3.11). Of <strong>the</strong>se 22 pairs with recurring breeders, we can only tell for certain that two pairs<br />

(7785309/7542752 <strong>and</strong>7785310/7785029) stayed toge<strong>the</strong>r for two breeding seasons (2008 <strong>and</strong><br />

2009). Females from both <strong>of</strong> <strong>the</strong>se pairs were successful in breeding <strong>and</strong> raising chicks in 2008,<br />

but only 7785310 was successful in 2009. Nei<strong>the</strong>r female was seen in 2010.<br />

Female 7785308 had a different mate for each <strong>of</strong> <strong>the</strong> 2007, 2008 <strong>and</strong> 2010 breeding seasons<br />

(Table 3.11). The mate from 2007 was present in 2008, indicating a mate replacement that wasn’t<br />

due to <strong>the</strong> death <strong>of</strong> <strong>the</strong> male. This mate swap occurred despite <strong>the</strong> fact that 7785308 bred<br />

successfully in 2007 (but not in 2008). Nei<strong>the</strong>r mate from 2007 nor 2008 was seen in 2010 (Table<br />

3.11).<br />

Female 7719502 changed mates in 2008, but beca<strong>use</strong> her mate in both 2008 <strong>and</strong> 2009 was<br />

unb<strong>and</strong>ed, a mate change can nei<strong>the</strong>r be confirmed nor ruled out. Her 2007 mate was present in<br />

2008 but he paired with ano<strong>the</strong>r female (Table 3.11). 7719502 bred successfully in 2007 <strong>and</strong><br />

2008, but died in 2009 whilst incubating.<br />

7785303 <strong>and</strong> 7785028 both changed mates in 2009 (Table 3.11). They bred successfully in 2008.<br />

As 7785029 was only b<strong>and</strong>ed in 2008, we are unable to tell if he was <strong>the</strong> unb<strong>and</strong>ed male <strong>of</strong> 2007<br />

<strong>and</strong> mate <strong>of</strong> 7785310 that year.<br />

Out <strong>of</strong> <strong>the</strong> six identified females that we knew had bred successfully for more than one season<br />

between 2007 <strong>and</strong> 2010, only two were known to maintain <strong>the</strong>ir mates from <strong>the</strong> previous year<br />

(Table 3.12). There were two cases <strong>of</strong> ‘divorce’ between 2007 <strong>and</strong> 2008 (both 7719502 <strong>and</strong><br />

7785308 had new mates). Additionally, between 2008 <strong>and</strong> 2009 or 2010 two females (7785028<br />

<strong>and</strong> 7785308) obtained new mates –<strong>the</strong>ir previous mates were not sighted. There was one<br />

unknown case beca<strong>use</strong> <strong>the</strong> female (7719502) had an unknown mate in both 2009 <strong>and</strong> 2008; <strong>and</strong><br />

one case (7785303) <strong>of</strong> ei<strong>the</strong>r ‘divorce’ or ‘widowed’ occurred between 2008 <strong>and</strong> 2009 beca<strong>use</strong><br />

<strong>the</strong> 2008 mate was unb<strong>and</strong>ed <strong>and</strong> so I was unable to tell if it was present in 2009 (Table 3.11).<br />

53

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

Saved successfully!

Ooh no, something went wrong!