Professional Starlink deployment on residential property — HOA-governed community
Field Advisory10 min read

When Homeowners Ask for Permission,
Boards Respond as Approvers

Across 100+ HOA-governed deployments, the difference between a routine 30-day review and an indefinite stall is usually not the dish or the community. It is whether the submission is framed as a federally protected deployment or a permission request.

Updated April 2026
Eric Enk, Founder & Lead Engineer
100+
HOA Deployments
Northern Virginia
94%
Approval Rate
First Submission
47 CFR
§ 1.4000
OTARD Protection
< 30
Days Average
To Approval

Where HOA Submissions Typically Fail

Across 100+ HOA-governed deployments, the pattern is consistent. Homeowners who ask for permission invite discretionary review. Homeowners who cite federal protection force the board into a narrower question: compliance, not approval.

Most failures begin with a false assumption: that the board has approval authority everywhere. In most cases involving exclusive-use space, it does not. The FCC's OTARD rule (47 CFR § 1.4000) preempts local restrictions on satellite dishes under 1 meter in areas you exclusively control. When the submission is framed as a request, the board behaves like a gatekeeper and delay becomes procedural rather than technical.

The pattern is consistent: federal framing narrows the review. Permission framing expands it.

The second failure point is documentation. Submissions without OTARD citations, site photos, or a credible deployment plan give the board room to defer, request another meeting cycle, or deny pending "further review." The objective is not persuasion. It is a package with no reasonable basis for delay.

The Federal Framework: FCC OTARD Rule

The Over-the-Air Reception Devices rule (47 CFR § 1.4000) is the governing framework for the entire HOA interaction. Once the board understands the deployment is federally protected, the conversation shifts from discretionary approval to narrow compliance questions.

Size Protection

OTARD protects dishes under 1 meter (39 inches). Starlink falls comfortably within that limit, so size is rarely the real issue.

Exclusive-Use Protection

The strongest protection applies in space you exclusively use and control: balconies, patios, private yards, and roofs with exclusive-use designation. This is the factor that decides most disputes.

Safety & Historic Exceptions

HOAs may enforce reasonable safety standards and certain historic-preservation requirements, but not as a pretext to block service. The standard is reasonableness, not board convenience.

Reference: Include the official FCC OTARD fact sheet with every HOA submission. The board should be responding to the governing federal rule, not interpreting covenant language in isolation.

OTARD Applicability — Decision Flow

Dish ≤ 1 meter?
Starlink: Yes (19" × 12")
Exclusive-use space?
Roof, yard, balcony, patio you control
YES → OTARD Protected
Submit notification
NO → Board Review
Common area rules apply

Protected vs. Restricted Deployment Areas

This distinction is the decisive variable in HOA navigation. Where the dish is deployed determines whether the board has meaningful standing. Across deployments in Fairfax County, Loudoun County, and across Northern Virginia, this is where most board disputes are resolved.

OTARD-Protected Areas

  • +Private balconies with exclusive-use rights
  • +Patios and enclosed outdoor areas you control
  • +Private yards (deeded or designated exclusive-use)
  • +Roofs with exclusive-use designation
  • +Any area you rent, lease, or own exclusively

May Require Board Engagement

  • Common areas (shared lawns, community structures)
  • Shared roofs (multi-unit buildings)
  • Front-facing visible areas with specific covenant restrictions
  • Exterior building walls in attached-unit communities
  • Historic-district properties with preservation rules

Submission Protocol: Day 1 Through Approval

This is the protocol we use for HOA-governed deployments. When the package is assembled correctly, resolution typically lands inside 30 days. Most failures begin at step one, when homeowners submit before determining which restrictions are actually enforceable.

1

Covenant Analysis

Day 1

Obtain and analyze the CC&Rs, architectural guidelines, and any satellite policy before contacting the board. The objective is to separate enforceable restrictions from language already preempted by federal law.

  • Request full CC&Rs and architectural bylaws
  • Identify satellite-specific restrictions and the exact covenant language
  • Determine whether your deployment location is exclusive-use space
  • Note submission deadlines and required documentation
2

Federal Framework Documentation

Day 1–2

Assemble the OTARD foundation. The package should establish the deployment as a federally protected activity in exclusive-use space, not a discretionary request.

  • Download FCC OTARD fact sheet (47 CFR § 1.4000)
  • Confirm dish diameter is under 1 meter (Starlink qualifies)
  • Document exclusive-use designation for your deployment area
  • Prepare OTARD reference summary for the board package
3

Submission Package Assembly

Day 3–5

Build a board-ready submission that shows both regulatory compliance and aesthetic discipline. The goal is a package with no reasonable basis for delay.

  • Complete HOA architectural review application
  • Include site photos with proposed dish and cable routing
  • Attach equipment specifications and professional installer credentials
  • Bundle FCC OTARD documentation as supporting exhibit
4

Board Engagement

Day 5–30

Submit through documented channels and keep communication concise. The tone stays cooperative; the legal foundation stays explicit.

  • Submit via certified mail or documented delivery
  • Request written acknowledgment of receipt
  • Attend board meeting if invited — prepared with OTARD references
  • Respond to follow-up questions within 48 hours

For properties requiring site assessment before HOA submission — particularly where obstruction analysis or alternate mounting locations are necessary — we complete the assessment first and include the findings in the board package.

Strategy Matrix: Which Approach, When

The right approach depends on the board's posture and the proposed mounting area. In most cases, the fastest resolution comes from leading with federal framing while addressing reasonable aesthetic concerns.

High Effectiveness

Lead with Federal Framework

Open with 47 CFR § 1.4000 from the start. Once the board sees the deployment as federally protected, the discussion narrows from discretionary approval to compliance review. This is the strongest position when the dish is in exclusive-use space.

Best for: Deployments on private balconies, patios, yards, or roofs with exclusive-use designation

High Effectiveness

Offer Aesthetic Concessions

Offer concealed cable routing, low-visibility placement, or paint-matched hardware when those steps do not impair signal. Boards usually de-escalate faster when visual concerns are addressed without surrendering protected rights.

Best for: Communities with appearance-focused architectural standards

Medium Effectiveness

Present Professional Deployment Plan

Include installer credentials, insurance documentation, and a clear deployment diagram. Boards resist less when the plan shows controlled workmanship rather than a vague self-install.

Best for: HOAs concerned about property damage, liability, or structural modification

Medium Effectiveness

Document Service Necessity

If the board asks why satellite service is necessary, document the lack of viable alternatives and the property's continuity requirements. This is supporting context, not the primary argument. OTARD is.

Best for: Restrictive boards that require stated rationale beyond regulatory rights

Escalation Protocol: When the Board Denies

Denial after a properly documented OTARD submission is uncommon, but it happens. Where homeowners lose leverage is by accepting the denial without demanding the precise regulatory basis. The escalation path is straightforward.

1
Request Written Basis for Denial

Require the board to identify the specific covenant language and regulatory rationale for the denial. This forces the issue out of general objection and into documented reasoning, where weak positions tend to collapse.

2
Respond with OTARD Analysis

If the deployment is in exclusive-use space and the dish is under 1 meter, OTARD preempts conflicting restrictions. Respond directly to the cited basis for denial, not the board's tone.

3
Propose Technical Compromise

Offer an alternate mount, routing change, or screening only if it preserves signal and avoids unreasonable cost or delay. Cooperation is useful; surrendering performance is not.

4
Legal Consultation

If the board continues to obstruct a protected deployment, brief counsel experienced in HOA and federal-preemption disputes. Most cases resolve quickly once counsel enters the record.

Deployment Support: We prepare submission packages, attend architectural review meetings, and design placements that satisfy signal requirements without creating avoidable HOA friction. The process is repeatable because the failure patterns are repeatable.

EE

Eric Enk

Founder & Lead Engineer

315+ deployments • 100+ HOA navigations • 94% first-submission approval

Eric has navigated HOA approval for more than 100 Starlink deployments across Northern Virginia communities, from Fairfax County townhome associations to Loudoun County estate communities. He prepares board-ready submission packages, joins review meetings, and designs deployments that satisfy signal requirements without creating avoidable friction.

The Bottom Line
Federal law protects satellite deployment in exclusive-use residential space. The practical question is not whether the right exists. It is whether the submission preserves that right or dilutes it into a permission request. The field pattern is consistent: a documented OTARD submission usually resolves within 30 days. A vague request can drift for months.
Eric Enk
Founder & Lead Engineer, The Orbit Tech

We navigate HOA approval most frequently across Fairfax County, Loudoun County, and Northern Virginia HOA-governed communities, where covenant language changes but the failure pattern does not. Related: Starlink deployment costs in Northern Virginia.

If Your Property Is HOA-Governed, Start Here

If the covenant is ambiguous or the board has pushed back before, the framing should be corrected before any meeting is scheduled. We prepare the submission package, manage board communication, and design a deployment that satisfies both signal requirements and architectural standards.