top of page

🏡 Sky Harbour: What the Developers Actually Built (and What They Didn’t)

 

A Historical Analysis of Intent vs. What Exists Today

When you step back and read the original documents as a whole—not selectively, not out of order—a very different picture emerges than the one currently being enforced.

This was not designed to be a perpetual enforcement regime.

It was something else entirely.

 

📜 1. A System Designed to End — Not Last Forever

Across multiple sections of Sky Harbour, the same endpoint appears:

January 1, 1990

Not just once. Not in one section.

System-wide.

Even sections created later—closer to the mid-1970s—still terminate at the exact same date.

What that implies:

  • This was a planned, coordinated sunset

  • Not independent documents accidentally sharing a date

  • Not a rolling or renewable structure

👉 This looks like a master-planned expiration, not an oversight.

 

🔚 2. No Automatic Renewal Language

Modern HOAs almost always include language like:

  • “Automatically renews for successive periods…”

  • “Unless amended, these restrictions continue indefinitely…”

That language is missing here.

Instead, what we see is:

  • A fixed duration

  • Amendment mechanisms tied to that duration

  • No clear provision extending the life of the entire framework beyond 1990

Why this matters:

Without explicit renewal language, the default reading is simple:

It ends when it says it ends.

 

🏘️ 3. The HOA Wasn’t Built as an

Enforcement Authority

The original corporate structure matters more than people realize.

1972 Articles of Incorporation:

  • Organized as a community / social club

  • Recreational purpose

  • Not a regulatory enforcement body

1974 Amendment:

  • Changes the name to “Sky Harbour Homeowners Association, Inc.”

  • Explicitly states:

    Nothing else is changed

What didn’t change:

  • The purpose

  • The structure

  • The nature of the organization

👉 They changed the label—not the function.

 

🤝 4. A Community Model

— Not a Compliance Machine

The overall design reflects something fundamentally different from modern HOAs:

  • Community-oriented

  • Social and recreational focus

  • Limited-duration governance

  • Built-in exit point

This aligns with a 1970s development philosophy:

Establish order early → let the community stand on its own later

Not:

Establish permanent control indefinitely

 

🏕️ 5. The “Boy Scouts Clause”

— A Window Into Intent

One of the most revealing provisions is the idea that:

If property wasn’t maintained, it could pass to organizations like the Boy Scouts or Girl Scouts.

Think about what that means.

That clause only makes sense if:

  • The system was temporary

  • There was a defined window where upkeep mattered

  • There was a concern about early-stage development stability

Now combine that with the duration clause:

“Until January 1, 1990”

The unavoidable question:

  • After 1990… what happens to that consequence?

Either:

  1. The consequence disappears (most logical), or

  2. The clause creates absurd retroactive obligations decades later (clearly not intended)

👉 This reinforces that the entire framework—including its incentives—was meant to end.

 

⚖️ 6. A Uniform Shutdown

— Not a Perpetual Regime

When you connect all the pieces:

  • Same termination date across sections

  • No automatic renewal language

  • A non-enforcement corporate structure

  • Temporary incentive mechanisms (like the Scouts clause)

You don’t get a perpetual HOA.

You get something closer to:

A transitional governance system for a developing neighborhood.

 

🧠 7. The Modern Interpretation

Creates Contradictions

The current enforcement model requires believing that:

  • Lot owners are bound forever

  • But key enforcement mechanisms expired in 1990

  • And the governing entity was never formally structured for enforcement

  • And the documents themselves clearly define an endpoint

That interpretation doesn’t just stretch the documents—

It conflicts with them.

 

🧭 Conclusion: What This Was Meant To Be

Everything points to the same conclusion:

Sky Harbour was designed to mature into a self-sustaining community—not remain under indefinite control.

The developers:

  • Set boundaries

  • Created temporary structure

  • Built in a clear endpoint

They did not create a permanent enforcement regime.

 

🔍 A Final Thought

If the original intent had truly been perpetual control, we would expect to see:

  • Explicit renewal language

  • A purpose-built enforcement entity

  • No fixed system-wide termination date

  • Permanent enforcement mechanisms

We see none of that.

What we do see is something much simpler:

A plan that ended in 1990—and was never properly let go.
​
​
​
This analysis does not claim to prove subjective intent, but instead examines what the original documents, structure, and timelines collectively indicate.

© 2026 by How Do You Like Them Apples, Inc. (a fictitious corporation)

bottom of page