Wiki · beta

Fairfax Presbyterian Church

A maintained knowledge base built from council and commission meetings — updated as new meetings land. Last synced Aug 22, 2026.

Overview

through Jul 19, 2026

Proposal at a glance

	Existing	Proposed
Floor area	43,000 sq ft	—
Dwelling units	0	10
Affordable units	—	10
Stories	—	3
Site area	—	8.25 acres

Tax map parcel(s): 57 1 02 123A, 57 1 02 122

Extracted from the city's submitted documents; each figure traces to the text it came from.

Floor area (existing) — "existing 43,000 square foot church with day care and parking"
Dwelling units (existing) — "The Property is currently used as a Religious Institution with an accessory Day Care Center."
Dwelling units (proposed) — "the Property may be developed with up to ten (10) townhouses"
Affordable units (proposed) — "ten new affordable residential townhouses in the northeast corner of the Property"
Stories (proposed) — "All ten units will have three levels, three bedrooms, two bathrooms"
Site area (proposed) — "Parcel 57-1-02-122-A (3.02 acres), and Parcel 57-1-02-123 (5.23 acres), for a total of 8.25 acres"

Official record

The applicant, Fairfax Presbyterian Church, is proposing to add ten (10) townhouses to be developed on site in conjunction with an existing church and day care. The ten (10) townhouses are proposed as rear entry garage units that range from 1,600 sf to 2,400 sf. A maximum height of 40 feet is anticipated for the proposed townhouses. There are 30 proposed parking spaces for the townhouses. The applicant intends to provide these units as affordable dwelling units in partnership with Habitat for Humanity of Northern Virginia, Inc. The proposed plan also rearranges parking for the existing church and day care.

Requests: The applicant is requesting a Rezoning from RH Residential High to PD-M Planned Development-Mixed Use and approval of a Master Development Plan with modifications to allow ten (10) townhouses in addition to the existing 43,000 square foot church with day care and parking. The applicant also proposes to develop up to 30 parking spaces in the southwest corner of the property.
Address: 10723 Main Street, Fairfax, VA 22030
Applicant: Fairfax Presbyterian Church David S. Houston, Attorney Bean, Kinney & Korman, PC
City record

In this wiki

Positions & open questions
Impact analysis — screening estimates with assumptions and ranges
Documents — the city's published record for this project

Positions & open questions

through Jul 19, 2026

Open questions

No unresolved questions recorded.

Member commentary

No recorded member positions yet.

Impact analysis

through Jul 19, 2026

Screening-level estimates of the economic and fiscal effects of Fairfax Presbyterian Church. Figures are decision-support context with named assumptions and sensitivity ranges — not predictions. The full analysis has the interactive assumptions panel and maps; methods documents every formula.

Headline estimates

metric new-residents unavailable — households x persons per multifamily unit (Rutgers CUPR bedroom-mix multipliers)
metric annual-capture-project-s-own-ground-floor-retail unavailable — Huff model over individual retail POIs: joint destination+mode choice, P(j,m) ~ A_j * w_m * exp(-b_m t_mj), CES category spend; clusters are a reporting rollup; own retail competes as a destination
metric new-annual-spending-arriving-on-foot unavailable — walk-mode share of the joint destination+mode Huff choice, summed over businesses; walking loses to driving with walk time, so the remainder of the mode-split budget arrives by car
metric real-estate-tax-increase unavailable — projected minus current RE tax
metric net-annual-fiscal-impact-naive-per-capita-method unavailable — incremental new recurring revenue minus service cost (upper-bound cost framing; allocates fixed citywide costs)
metric net-annual-fiscal-impact-marginal-framing unavailable — incremental new recurring revenue minus service cost (only services that scale with new residents)

Method notes, caveats, and non-headline metrics live on the analysis page.

Documents

through Jul 30, 2026

Documents published in the city's project record, in the order the city lists them. Labels are the city's own and usually carry the document date, format, and size.

Page history

Log

2026-07-19

Seeded from the tracker profile and official records.

2026-07-28

Pipeline refresh.
Pipeline refresh.
Pipeline refresh.

2026-07-30

Pipeline refresh.

2026-08-22

Pipeline refresh.