29.10.2012 Views

Proceedings of the fifth mountain lion workshop: 27

Proceedings of the fifth mountain lion workshop: 27

Proceedings of the fifth mountain lion workshop: 27

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

80 PROCEEDINGS OF THE FIFTH MOUNTAIN LION WORKSHOP<br />

<strong>the</strong>re appears to be a correlation between <strong>the</strong> number <strong>of</strong><br />

scrapes and <strong>the</strong> number <strong>of</strong> male tracks recorded, providing<br />

support for <strong>the</strong> notion that more males have been using <strong>the</strong><br />

study area during <strong>the</strong> last two years <strong>of</strong> <strong>the</strong> track count. The<br />

increased scratching activity could indicate a higher<br />

proportion <strong>of</strong> young males vying for home areas, possibly a<br />

result <strong>of</strong> <strong>the</strong> removal <strong>of</strong> one or two established resident males<br />

from <strong>the</strong> area during <strong>the</strong> winter <strong>of</strong> 1993-1994.<br />

The value <strong>of</strong> making a second survey <strong>of</strong> <strong>the</strong> routes,<br />

based on <strong>the</strong> results listed in Table 1, is uncertain. Because<br />

care was taken only to record tracks deposited since <strong>the</strong> first<br />

survey, <strong>the</strong> accumulation period for <strong>the</strong> second survey is less<br />

than five days. It is difficult to constrain <strong>the</strong> accumulation for<br />

<strong>the</strong> first survey, but it is likely less than a week, with <strong>the</strong><br />

exception <strong>of</strong> tracks in mud which were observed to persist for<br />

several weeks. As indicated in table 1, <strong>the</strong> number <strong>of</strong> tracks<br />

recorded during <strong>the</strong> first and second run were similar. Thus,<br />

it might be more productive to survey additional routes instead<br />

<strong>of</strong> repeating <strong>the</strong> track count along <strong>the</strong> base routes. We note,<br />

however, that while <strong>the</strong> total number <strong>of</strong> tracks recorded in<br />

1994 were similar for <strong>the</strong> first and second surveys, more male<br />

tracks were recorded during <strong>the</strong> second survey.<br />

Many more years <strong>of</strong> data need to be collected on <strong>the</strong><br />

Fort Huachuca track count before our interpretation <strong>of</strong> <strong>the</strong> data<br />

can be realistically considered to be meaningful. In <strong>the</strong><br />

meantime, an important aspect <strong>of</strong> <strong>the</strong> Track Count is <strong>the</strong><br />

increasing number <strong>of</strong> volunteer participants (39 in 1995),<br />

which provides an excellent forum for <strong>the</strong> discussion <strong>of</strong> <strong>lion</strong><br />

issues, <strong>the</strong> study <strong>of</strong> local flora and fauna, and networking<br />

among <strong>the</strong> participants. The Fort Huachuca track count has<br />

also facilitated important spin<strong>of</strong>fs, including <strong>the</strong> formation <strong>of</strong><br />

Keeping Track, Inc., The Juniper Institute, and <strong>the</strong> Canelo<br />

Hills track count.<br />

CANELO HILLS TRACK COUNT<br />

Starting in August 1995, <strong>the</strong> Fort Huachuca track<br />

count was expanded to identify potential corridors between<br />

<strong>the</strong> Huachuca Mountains and <strong>the</strong> neighboring <strong>mountain</strong> ranges<br />

used by <strong>lion</strong>s and o<strong>the</strong>r large carnivores. We speculate that<br />

<strong>the</strong> Huachuca Mountains fall within <strong>the</strong> home ranges <strong>of</strong><br />

several <strong>lion</strong>s, and that <strong>the</strong>re is movement by <strong>lion</strong>s between <strong>the</strong><br />

Huachuca Mountains and neighboring ranges. Each <strong>of</strong> <strong>the</strong><br />

four closest <strong>mountain</strong> ranges to <strong>the</strong> Huachuca Mountains are<br />

within <strong>the</strong> possible range <strong>of</strong> an adult <strong>lion</strong>: <strong>the</strong> Santa Rita<br />

Mountains (with about 47 mi 2 <strong>of</strong> <strong>lion</strong> habitat) lie <strong>27</strong> miles<br />

northwest; <strong>the</strong> Whetstones (with 22 mi 2 <strong>of</strong> habitat) lie 15 miles<br />

north; 17 miles to <strong>the</strong> east and across <strong>the</strong> San Pedro River lie<br />

<strong>the</strong> Mule Mountains (with 23 mi 2 <strong>of</strong> habitat); and 22 miles to<br />

<strong>the</strong> west are <strong>the</strong> Patagonia Mountains (with 8 mi 2 <strong>of</strong> habitat).<br />

These estimates <strong>of</strong> <strong>lion</strong> habitat are based on areas above 5000<br />

feet, which approximately delineate <strong>the</strong> transition from<br />

grasslands to <strong>the</strong> encinal vegetation zone. We note that even<br />

this rough estimate <strong>of</strong> <strong>the</strong> amount <strong>of</strong> <strong>lion</strong> habitat indicates that<br />

no single <strong>mountain</strong> range contains habitat for a single <strong>lion</strong>,<br />

particularly for males.<br />

The Canelo Hills, a rolling terrain varying in<br />

elevation between 4700 and 6000 feet is composed primarily<br />

<strong>of</strong> pinyon-juniper-oak woodlands, may act as a natural conduit<br />

between <strong>the</strong> Huachuca Mountains and <strong>the</strong> Santa Rita<br />

Mountains to <strong>the</strong> nor<strong>the</strong>ast and <strong>the</strong> Whetstone Mountains to<br />

<strong>the</strong> north (Figure 1). A number <strong>of</strong> drainages run north-south<br />

throughout <strong>the</strong> Canelo Hills, including Post Creek, O'Donnell<br />

Creek, Turkey Creek, and Lyle Creek. Four <strong>of</strong> <strong>the</strong> routes (No.<br />

3,5,6,7) follow drainages in <strong>the</strong> area (Figure 1). The<br />

remaining routes are located between <strong>the</strong> drainages in country<br />

which is characterized by wooded mesas. The routes were<br />

chosen to transect <strong>the</strong> study area approximately parallel to <strong>the</strong><br />

trend <strong>of</strong> <strong>the</strong> hills, <strong>the</strong>reby intersecting <strong>the</strong> hypo<strong>the</strong>tical<br />

corridors passing through <strong>the</strong> area.<br />

At <strong>the</strong> present, <strong>the</strong> Canelo Hills track count (Table 2)<br />

is monitoring possible corridors along <strong>the</strong> western side <strong>of</strong> <strong>the</strong><br />

Huachuca Mountains, where development pressures have been<br />

light. In <strong>the</strong> future, we hope to extend <strong>the</strong> track count to<br />

include possible corridors through <strong>the</strong> more heavily urbanized<br />

eastern margin <strong>of</strong> <strong>the</strong> Huachuca Mountains where Fort<br />

Huachuca and <strong>the</strong> city <strong>of</strong> Sierra Vista have impacted <strong>the</strong><br />

connective links to <strong>the</strong> San Pedro River Valley and Mule<br />

Mountains to <strong>the</strong> east.<br />

To date fewer <strong>lion</strong> tracks have been recorded in <strong>the</strong><br />

Canelo Hills (0.06 tracks per mile <strong>of</strong> route) compared to <strong>the</strong><br />

track density recorded on <strong>the</strong> FHMR in 1995 (0.28 tracks per<br />

mile <strong>of</strong> route). Even when <strong>the</strong> months <strong>of</strong> adverse wea<strong>the</strong>r are<br />

not included in <strong>the</strong> calculation, <strong>the</strong> recorded density <strong>of</strong> tracks<br />

(0.12 tracks per mile <strong>of</strong> route) is less than half that recorded<br />

on <strong>the</strong> FHMR. Additionally <strong>the</strong> number <strong>of</strong> bear tracks<br />

recorded has been comparable to <strong>the</strong> number <strong>of</strong> <strong>lion</strong> tracks<br />

(0.15 tracks per mile <strong>of</strong> route versus 0.12). We interpret this<br />

correlation as evidence that <strong>the</strong> Canelo Hills corridors are not<br />

restricted to use by <strong>lion</strong>s. Lion tracks generally have been<br />

recorded in <strong>the</strong> drainage areas (routes 3,5,6 and 7), while <strong>the</strong><br />

bear tracks have been observed in <strong>the</strong> interdrainage areas<br />

(routes 1 and 2).<br />

The monthly scheduling <strong>of</strong> <strong>the</strong> track count has<br />

proved to be affected by adverse wea<strong>the</strong>r conditions. Poor<br />

wea<strong>the</strong>r (primarily rain), and associated poor tracking<br />

conditions resulted in no tracks being recorded for three <strong>of</strong> <strong>the</strong><br />

eight months (September 1995, December 1995, and February<br />

1996), which represents more than a third <strong>of</strong> <strong>the</strong> track surveys.<br />

As a possible solution to <strong>the</strong> problem, we plan to conduct <strong>the</strong><br />

track count quarterly starting in June 1996, surveying <strong>the</strong><br />

routes only after a week <strong>of</strong> dry wea<strong>the</strong>r. In addition, we plan<br />

to repeat <strong>the</strong> track counts after 3-5 days, following <strong>the</strong> method<br />

employed by <strong>the</strong> Fort Huachuca track count, to provide a more<br />

complete survey <strong>of</strong> <strong>the</strong> routes.<br />

Given <strong>the</strong> short time <strong>the</strong> Canelo Hills track count has<br />

been conducted, <strong>the</strong> interpretations presented above are

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

Saved successfully!

Ooh no, something went wrong!