What is the Crowsnest Annexation?

The Crowsnest Annexation is a proposal to add approximately 795 acres of unincorporated Douglas County land into the City of Castle Pines, allowing for a large-scale development of about 4,000 residential units and 500,000–1.1 million square feet of commercial/mixed-use space. It's being considered by the City Council, but it could strain city resources and change our community's character. The community would sit on 749.7 acres while the rest would be the annexed Crowfoot Valley Rd.

Where is the proposed Crowsnest site located?

The site is along Crowfoot Valley Road, about 3–5 miles southeast of Castle Pines' current core, bordering the Town of Parker on 3 sides. It's not directly bordering our city—it's connected via a narrow "flagpole" strip of road (Crowfoot Valley Rd.), creating a remote island that raises concerns about accessibility and service delivery. Drive over to Crowfoot Valley Rd. and Chambers to see it!

Why is it called a flagpole annexation?

A "flagpole" annexation uses a thin corridor (here, Crowfoot Valley Road) to connect distant land to the city, like a flag on a pole. This setup worries the taxpayers of Castle Pines because it creates an isolated enclave, making it harder and more expensive for the City to provide services like police, fire, and road maintenance equally to all residents.

What about the "1/6 contiguity" rule?

Colorado law (C.R.S. § 31-12-104(1)(a)) requires that at least one-sixth (1/6) of the perimeter of the land proposed for annexation must be directly contiguous (touching) the existing city boundaries. This is meant to prevent disconnected or leapfrog annexations.

The developer claims compliance by annexing a narrow strip along Crowfoot Valley Road in four separate maps, arguing that this strip meets the 1/6 threshold when measured against the total perimeter of the proposed area. However, many residents and the Town of Parker argue this is a loophole: the "contiguity" is artificial and created solely by the flagpole corridor itself, not a meaningful shared boundary with the city core. Critics say it doesn't reflect true integration and allows remote land to be annexed without genuine connection, leading to the isolated "island" concerns. 

For the developer's explanation and maps showing their 1/6 contiguity claim, see the official Crowsnest Annexation Petition (filed January 9, 2026) on the City of Castle Pines website. (The claim appears in paragraph 3 on page 1: "Not less than one-sixth (1/6) of the perimeter of the Property is contiguous with the City’s current municipal boundaries." Annexation maps in Exhibit C illustrate the corridor.)

Leapfrog Annexation Process? What is that?

The 4-step leapfrog process (also called a serial flagpole annexation or leapfrog annexation) is a legal strategy used by developers to annex remote, non-contiguous land into a municipality under Colorado's Municipal Annexation Act of 1965 (C.R.S. § 31-12-101 et seq.). It is specifically designed to satisfy the 1/6 contiguity requirement (C.R.S. § 31-12-104(1)(a)) when the main body of land does not directly border the city.

In the context of the Crowsnest annexation, the developer (VT Crowfoot Valley Landco LLC) used this exact method, as described in their Petition and annexation maps. Here’s how the 4-step leapfrog process works:

Step 1: Annex a thin "flagpole" corridor first

The developer annexes a narrow strip of land (in this case, a portion of Crowfoot Valley Road right-of-way) that does directly touch the existing city boundary. This strip becomes the "pole."

Step 2: Repeat with additional corridor segments

Additional separate annexation petitions are filed to extend the corridor farther along the same road. Each new segment touches the previously annexed strip, creating a chain. (Crowsnest used four separate maps to build this chain.)

Step 3: Annex the main "flag" (the large remote parcel)

Once the corridor is long enough, the developer files a final petition to annex the main body of land (the ~795-acre Crowsnest site). The law only requires 1/6 of the total perimeter of the entire proposed area (corridor + main parcel) to be contiguous with the city. The developer claims the cumulative corridor meets this threshold.

Step 4: City approves the final annexation

If the City Council finds the 1/6 contiguity requirement is met (even though the main parcel is miles away and only connected by the artificial corridor), the entire area—including the remote island—becomes part of the city in one final ordinance.

How would Crowsnest affect Castle Pines' population?

The development could add around 11,200 new residents (at full buildout), increasing our current population of about 17,000 by 64%—meaning nearly 39% of the expanded city would live in this remote area. If commercial space shifts to more housing through the amendment process, it could push that to 41–43%, potentially overwhelming schools, parks, and public safety without proportional infrastructure.

What happens if commercial space becomes more residential?

The Planning Development zoning allows flexibility for commercial areas (121 acres) to convert to housing, potentially adding 300–600 units and erasing most of the projected millions in annual sales tax. This could flip the surplus to a $4.5 million deficit, leaving taxpayers to cover higher service demands for a denser, less revenue-generating development.

What are the concerns for wildlife and open space?

The proposal dedicates only 9.4% (70 acres) to open space—mostly Lemon Gulch—far below the standard for Castle Pines (for instance, The Canyons' 38%). This fragments critical wildlife corridors for elk, deer, and raptors, risking habitat loss and conflicts, contrary to the Comprehensive Plan's goals for preserving natural features and minimizing environmental impacts. Many neighbors have posted pictures on Next Door and Facebook showing the elk migration and bald eagles that migrate through that land. 

How would Crowsnest affect traffic and infrastructure?

It adds ~44,000 daily trips to Crowfoot Valley Road, a failing corridor with crashes and queues already exceeding capacity. The Traffic Impact Study understates risks, ignoring full widening needs—potentially costing millions in maintenance and safety upgrades that taxpayers would inherit, while straining water/sewer without a firm PWSD commitment.

Why should taxpayers worry about property values?

Shifting to high-density (5.78–6.92 units/acre vs. our 1.37 average) could devalue existing homes by flooding the market with denser "comps" and eroding our premium small-town appeal—buyers seeking open space and low traffic may look elsewhere, as warned in the 2025 Community Survey.

How would Crowsnest impact my taxes and city services?

Servicing this remote site could add millions annually for road maintenance alone Crowfoot Valley Rd. and the interior roads), plus strains on police/fire response times and schools (adding ~2,400 students with no dedicated site). Without guarantees, taxpayers may face higher mills or reduced services citywide to subsidize the island's isolation. Castle Pines already has the highest mills in the Denver area. 

What about water?

Parker Water & Sanitation has only provided a preliminary letter (dated November 3, 2025) stating that service is "anticipated" but not guaranteed. The letter explicitly says it is not a will-serve commitment and is based on very limited information. Service depends on:

-- The property being successfully included into PWSD boundaries (requires Board approval).

-- The developer petitioning for inclusion.

-- Sufficient water rights being dedicated.

-- Payment of potentially massive inclusion fees, tap fees, and infrastructure costs.

-- Compliance with PWSD rules and capacity evaluations.

No will-serve letter means no guaranteed water or sewer—a huge red flag for a project adding 11,000+ people. It’s a taxpayer risk the City of Castle Pines should not accept without ironclad proof of service.