What ninety-seven county filings reveal about the apartment plan for Ridge Road
There is a particular kind of quiet that belongs to small towns. Damascus has it. Ridge Road runs north through the middle of town, two lanes, past the post office and the pizza shops, past houses that have been there longer than anyone can remember, and if you drive it slowly enough you will pass a low-slung commercial building at 26134 with food trucks parked out front and a for-lease sign at the sidewalk. Short term only, the listing says. The property is being developed.
What is being developed there, on 4.73 acres of what used to be the Burdette carwash and laundromat, is a 107-unit apartment building. Four stories. Fifty-five feet tall, the maximum the zoning allows. One hundred percent of the units reserved for households earning 60 percent or less of the area median income, financed in large part with federal tax credits. It would be one of the largest residential projects proposed in Damascus in recent years, and it has divided the town's sense of itself: a place that has always thought of itself as a small town, now being asked to absorb something built at a scale the town's own master plan never envisioned for that ground.
The group opposing it calls itself Damascus Residents for Responsible Development. They are not opposed to development. Their flyers, their website, their testimony all say the same thing: build here, but build what the plan allows, at a scale the town can absorb, on infrastructure that exists. What follows is not their press release. It is what the public record says, document by document, about the proposal itself. Ninety-seven filings sit on the county's development review pages for this project. Read together, they tell a story stranger and sloppier than anything the opponents have alleged.
Every development fight has a number at its center. Here the number is 36.
The application covers 4.73 acres. But acreage on a cover sheet and buildable land are different things. At a December 2025 community meeting, the applicant's engineer acknowledged that the usable portion of the site is about 2.96 acres (per attendee accounts). A stream buffer takes more. Divide 107 units by 2.96 acres and you get roughly 36 units per acre.
The 2006 Damascus Master Plan, the document that is supposed to govern what gets built in the town center, sets residential density guidance at 15 to 20 dwelling units per acre. The exact table sits on printed page 97: 20 units per acre in the outer town center, 15 in the inner core. Thirty-six is roughly 81 percent above the top of that range.
This is the core of the residents' case, and it is arithmetic, not ideology. The plan also contains a safety valve the residents quote often: at the time of subdivision or site plan review, the Planning Board may limit development below what the zoning allows to ensure compatibility of scale, height, and proportion with adjoining neighborhoods. The zone maximum, in other words, is not a promise.
The zone maximum, in other words, is not a promise.
To understand why 36 units per acre landed so badly in Damascus, you have to understand what the town told itself it was.
The 2006 master plan opens with a sentence that functions as a mission statement: "Damascus is a small town surrounded by the agricultural and rural open spaces of the County's Agricultural Reserve." Affordable housing, the plan says, should be "suitable to the small town character of Damascus." Zoning should emphasize "proportion, design, and an architectural context of structures." The town center is to have "compact town-scale intensity." Buildings should be oriented toward streets. New development near single-family neighborhoods must be reviewed for "scale, height, and proportion." Transition areas should "replicate the scale, design and pattern of historic small town residential neighborhoods."
Now look at what is proposed. The architectural drawings, prepared by Miner Feinstein Architects and dated November 2025, show a contemporary four-story apartment bar: double-loaded corridors, reddish-brown brick and fiber-cement siding, flat parapet roofs, Juliet balconies, the building fronting Ridge Road with surface parking lots to the side and rear. It is, in typology, a suburban garden apartment complex. There is nothing town-scale about a 55-foot bar built to the maximum the zoning allows. The county's own design reviewer flagged the facades and materials. Three separate county reviewers told the applicant the proposed public open space does not meet the code's definition or design requirements. Eight separate corrections from Montgomery County Fire and Rescue, covering hydrants, apparatus access, and walkable grade around the building, sat unresolved for months.
The renderings are handsome in the way renderings always are. They show a crisp, modern building on a sunny day, viewed across its own parking lot. The building fronts Ridge Road, with the parking to the side and rear. But the master plan asks for more than a building near the street. It asks for compact town-scale intensity, and for scale, height, and proportion compatible with adjoining neighborhoods. Four stories and 55 feet, the maximum the zoning allows, answers a different question.
If the design is the substance of the objection, the paperwork is its character witness. And the paperwork is a mess.
Ninety-seven documents across the preliminary plan, site plan, and forest conservation filings were reviewed for this article. What they contain is not a conspiracy. It is something more ordinary and, for a $55 million project, more startling: carelessness at a scale that suggests nobody was checking anyone's work.
Start with who the applicant is. The applications name Olympus Real Estate LLC, with Brian Gallagher as the contact. But the traffic study's scoping form, signed by county planning, transportation, and state highway staff, names a different developer entirely: "Brian Kim; AGC - Damascus, LLC." The project's noise study is addressed to Brian Kim at AGC's Fulton office and states that AGC contracted the work. The architectural cover sheet lists AGC - Damascus, LLC of Fulton, Maryland as the developer and calls the project "Damascus Apartments." Three filings, three appearances of a developer who appears nowhere else in the applications. Whether AGC is a partner, a predecessor, or a clerical ghost, the county record does not say.
Then there is the question of how many units are being built. The early filings said "up to 123": the traffic scoping form, the forest conservation notice letter, the sediment plan. The more recent filings have settled on 107, and to be fair, that looks like a correction. But the traffic study on record today, dated October 2025, still states three times that its intersection analysis used "up to 123 units" as a conservative case, without ever showing the 123-unit numbers. The typo got fixed. The analysis built on it did not.
The applications cannot agree with themselves on basic facts. The statements of justification say the sewer category is S-1; every plan cover sheet says S-3. Some sheets place the site's watershed in Class I-P; others say Class III-P. One sheet puts the property in Election District No. 4; the rest say District No. 12. The site plan application lists its filing date as "829," with no year. The forest conservation application references "Preliminary Plan 120250070," a different case number, not the 120260020 it belongs to. A sight-distance evaluation form, the document that is supposed to certify drivers can see safely out of the driveway, was filed completely blank: no plan number, no project name, no signature, no seal.
And then there are the signatures. On the preliminary plan application, the certification offers three choices: sole owner, authorized representative, or contract purchaser. All three boxes are blank, though Brian Gallagher signed it. On the forest conservation application, all three boxes are blank too. On the site plan application, Gallagher checked the first box: "the sole owner of the subject property." The application's own owner section, two pages earlier, names "Harry H Burdette Et Al." State land records agree: the Burdette heirs own the property. Gallagher does not. On the second extension request, filed September 2026, the form checks "Owner" for Olympus Real Estate LLC while listing its affiliation as "Contract Purchaser." The county's own land records say otherwise.
The sloppiness spread into the county's own paperwork. The applicant's transposed plan numbers turned up in state and county memos. The site plan's statement of justification is a word-for-word copy of the preliminary plan's, down to calling itself a preliminary plan application. One expected traffic attachment never made it into the file at all. And for a project beside a stream valley, no standalone environmental or geotechnical report exists anywhere in the record, only concept drawings.
The noise study, fourteen pages from HUSH Acoustics, has the same disease. Its computer model could not reproduce the field measurements, so the analysts raised the modeled speeds on Ridge Road to 38 miles per hour, above the measured speeds and above the posted 30, until the model matched. That 38 then went into the 2045 forecast "to be conservative," though the county's highway plan targets 25 for that stretch of road. The report argues the site falls under both the 55-decibel county standard and the 65-decibel highway corridor standard and never says which applies. Its traffic growth rate was computed by comparing a 2008 count at one intersection with a 2025 count at another, seventeen years apart. Like the traffic study, it is addressed to Brian Kim at AGC-Damascus.
None of this is a finding of wrongdoing. It is a finding of a file that contradicts itself, repeatedly, on matters as basic as who is applying, how many units are proposed, and who owns the land. A planning board is entitled to ask whether an applicant this careless on paper will be careful with a neighborhood.
A planning board is entitled to ask whether an applicant this careless on paper will be careful with a neighborhood.
Every development of this size needs a traffic study, and this one has it: fifty-four pages from Gorove Slade, a respected Bethesda transportation firm, dated October 2025. The study's conclusions are clean. Three intersections analyzed, all passing, no mitigation required.
The foundations are less clean. The traffic counts were taken on a single Thursday in September 2024, two years before the study would matter to a planning board. The two large townhome developments built along Ridge Road in 2023 through 2025, with 109 units between them, do appear in the study's background traffic, but the trip estimates for them are borrowed from old analyses, one of them dating to 2015.
Then the study starts arguing with itself. Its trip-generation table is built on 107 units and subtracts traffic credit for the existing 3,410-square-foot office building, producing a net increase of 39 morning trips and 38 evening trips. But the text states, three times, that the analysis used "up to 123 units." And it also states that "since the existing site is currently vacant, the full trip generation of the proposed development was added to the road network rather than the net new increase." The site is not vacant. There is an office building on it, in poor repair, with food trucks, sheds for sale, a bus, and tractor trailers across the lot. A reader cannot tell whether the intersection results reflect 107 units or 123, net trips or full trips, a vacant site or an occupied one.
Read closely enough and the study starts to look assembled from other jobs. Its improvement tables evaluate a "Retail Store Curb Cut," a "Hardware Store Driveway," and a "Shopping Center Driveway," none of which exist at a residential redevelopment of a small office. One page footer reads "Sunday, October 27, 2025." That date was a Monday. The text claims 44 morning and 43 afternoon net new trips; its own tables say 39 and 38. Two printed pages are numbered 5, two more numbered 7, page 6 is missing entirely, and the word "Burdette" never appears once in fifty-four pages.
The bicycle section misreads the county's own bike plan. The plan designates separated bike lanes on Ridge Road by the site, two-way, on the east side. The study calls them the "north side" in its text and the "south side" in its tables, on a road that runs north-south, then declares the lanes infeasible for lack of right-of-way and proposes a sidepath instead, while conceding the right-of-way defeats the sidepath too. Meanwhile the county is spending its own money designing pedestrian and bicycle facilities for the Damascus area.
Meanwhile, the county's own transportation review has gone quiet. In January 2026, transportation staff told the applicant it owed a $2,000 review fee and that the traffic statement and storm drain were "currently under review." Nine months later, no approval, no revised study, no fee receipt, and no state highway decision on the single curb cut onto Route 27 appears anywhere in the public record. The September extension memo lists every outstanding issue in the case, fire access, stormwater, open space, parking, landscaping, architecture, and never mentions transportation at all.
Set the paperwork aside and look at Damascus itself, because the strongest argument against this project may not be what is wrong with the application but what is true about the town.
Damascus Elementary School is operating at about 126 percent of its program capacity. John T. Baker Middle School is at about 111 percent, with portable classrooms out back. These are not projections. They are this year's numbers, from the school system's own facilities plan. The county is planning a replacement high school because the cluster is outgrowing its buildings.
The town has one bus. Route 90 runs from Damascus to the Shady Grove Metro station, weekdays only, roughly every half hour starting around 5:15 in the morning. There is no Saturday service. About 1.5 percent of Damascus commuters use transit. The county's own assessment ranks the Germantown-Damascus corridor among its worst transit areas.
The county's planning data puts about 2,500 jobs in the Damascus policy area against nearly 9,850 working residents: roughly one local job for every four workers. Half of one percent of the county's employment sits in Damascus. The average commute is 37.6 minutes, and 62 percent of workers drive alone. There is no rail, no major employer, and no published list of Damascus businesses that amounts to an employment center.
None of this means working families should not live in Damascus. It means a 107-unit development whose residents will overwhelmingly need cars, whose children will need classrooms, and whose workers will need jobs elsewhere is being placed in the part of the county least equipped to absorb it. The question is not whether affordable housing belongs in Damascus. Four hundred or so income-restricted units already exist there, in five properties built between 1979 and 2023. The question is whether this project, at this scale, on this site, with this application, is the right next one.
The project is proposed as 100 percent affordable, financed with 4 percent federal Low-Income Housing Tax Credits paired with tax-exempt bonds. This is worth understanding, because the financing shapes everything about the deal.
The tax credit program does not give developers cash. It gives them tax credits, which they sell to corporate investors, generating equity that covers roughly a third of development costs. The rest comes from bonds and gap loans, here projected as $3.5 million from the state's Rental Housing Works program. That $3.5 million appears in the state's pipeline report with estimated closing in April 2027, accompanied by the standard disclaimer that the listing "is not a reservation or commitment of funds." A February 2026 state notice proposed up to $33 million in private-activity bonds naming AGC Ridge Road LP as the owner-operator. No bond issuance has been found in any public record since.
Every dollar attached to this project, in other words, is on paper: proposed bonds, projected gap financing, nothing committed or disbursed. Meanwhile, a commercial building permit for the address sits "in process" declaring a $30.7 million construction value, filed before the plans it would build have been approved.
There is a further problem, and it sits in the program's own rulebook. Maryland does not award these credits competitively. It applies thresholds, and thresholds are pass-fail paperwork. The sponsor must prove site control. The zoning for the use and the density must already be in place. The project description must be fixed enough to underwrite. This file names two different sponsors, spent a year disagreeing with itself on the unit count, and proposes a density the town's master plan does not support. The financing this project needs is gated behind exactly the paperwork this project cannot get straight.
The tax credit program has well-documented criticisms, and they deserve attribution rather than assertion. A federal accountability review found per-unit costs going unmonitored. Academic analysis has estimated developers capture around half the subsidy. Tens of thousands of units nationally have left affordability restrictions through legal exit provisions. None of that is an accusation against anyone in Damascus. It is context for what the program is: a system that can produce genuinely needed housing and genuinely profitable deals at the same time, with the public's ability to tell the difference depending entirely on scrutiny.
Here is the timeline. Plans accepted in January 2026. A development review committee in late January produced a long list of corrections: incomplete traffic analysis, unpaid fees, parking dimensions, open space that does not meet the code, fire access, stormwater, architecture. The applicant sought its first extension in April, granted 5-0, extending review to October. It sought a second in September, granted in October, extending review to January 2027.
In all that time, the applicant has not filed a single revised drawing. The latest plan sheets on record date to January. The latest staff reports to April.
The second extension request contains a sentence worth reading twice. In the box asking why more time is needed, the applicant wrote: "The Applicant needs additional time to develop design changes that are intended to achieve better master plan compliance and compatibility, as well as to provide the required open space on site."
Read that plainly. After nine months of review, the applicant's own signed form says the design does not yet comply with the master plan and does not yet provide the required open space. The residents have been saying so since the first community meeting. It took the applicant until September to agree with them in writing.
Strip away the acronyms and the filing defects and the dueling unit counts, and the question before Damascus is simple. A developer wants to build one of the largest apartment projects proposed in recent town history on a 4.73-acre former carwash site, at a density roughly 81 percent above the master plan's guidance, in a town whose elementary school is a quarter over capacity, whose only bus does not run on weekends, and whose job base covers a quarter of its working residents.
The residents' group has a name for what it wants instead: responsible development. Build at the scale the plan envisions. Fix the design until it complies. Count the traffic honestly. Show the open space. Demonstrate the infrastructure can take it. These are not extraordinary demands. They are, in large part, the county's own rules, cited back to the county by the people who live with the consequences.
The planning board will decide by January 2027. Between now and then, the applicant has to do what nine months have not yet produced: a plan that works as filed. The paper trail suggests that will take more than an extension. It will take starting over, on paper and possibly on the drawing board, with the care this town deserves and this file has not yet shown.