No access/tours to Carnarvon Range (Katjarra) WA 2015
Submitted: Thursday, Apr 02, 2015 at 09:02
ThreadID:
117317
Views:
2347
Replies:
0
FollowUps:
0
This Thread has been Archived
Phil B (WA)
Hi folks,
Please be advised that there wont be any tours to
Carnarvon Range (Katjarra) WA in 2015. Here is the media brief:
After exploring every possible option the Central Desert Native Title Service (CDNTS) has been unable to secure financial support for the opening of the
Carnarvon Ranges in 2015. While the Traditional Owners are keen to open the Ranges for limited periods they will only do so if their
Ranger Teams are there to host visitors and to spend time on country with them.
Last year, the Traditional Owners did this through a month-long trial event called ‘Katjarra in July’. The cost of staging such an event is significant and the CDNTS has approached a number of corporates and businesses and explored all possible government funding opportunities to support a similar event this year but has been unsuccessful. Unfortunately, the cost of staging these events greatly exceeds the revenue generated from visitors through permit and camping fees. Given the cost pressures on remote communities and in managing remote environments, a financial loss cannot be carried by the Traditional Owners at this time, even though the value of social, cultural and reconciliation outcomes from spending time together on country at Katjarra (for both the Birriliburu mob and whitefellas) is recognised.??
The CDNTS and the Birriliburu mob appreciate your interest in Katjarra and your patience during the decision making process, and apologise for any disruption to your travel plans. The CDNTS will continue to work to secure a business model that can support the opening in future years. Until then the
Carnarvon Range will be closed to all access. If you or your network could support CDNTS in developing a business or funding model to support the opening, please contact hamishmorgan@centraldesert.org.au.
The website (www.carnarvonranges.com.au/Default.aspx) will be updated in early April to reflect this latest advice.