TempReach USA connects Washington homeowners with independent local HVAC technicians. This page is built from the metro's own Census housing data, ZIP codes and climate record — the heating and cooling problems described here are the ones Washington homes actually have.
Call center hours: Mon-Fri 7:00 AM-10:00 PM ET | Sat 8:00 AM-10:00 PM ET | Sun 7:00 AM-9:00 PM ET
The median Washington home was built in 1983; 46.0% of the stock predates 1980, and the pattern this metro's own data ranks first is the refrigerant transition reaching older systems. TempReach USA is a referral service, not an HVAC company: one call connects you with an independent local HVAC technician serving your ZIP code.
Read Washington through its counties and the picture sharpens. District of Columbia, Charles, Frederick, Montgomery, Prince George's, Arlington, Clarke, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, Spotsylvania, Stafford, Warren, Alexandria city, Fairfax city, Falls Church city, Fredericksburg city, Manassas city, Manassas Park city, Jefferson were not built in the same decades or for the same households, and their heating and cooling carries those differences: an older core where 21.5% of the metro's homes predate 1960, growth corridors where the subdivisions arrived in waves, and edges still being built out. The metro-wide medians — a middle home built in 1983, 2,483,270 housing units in all — are the average of those local stories, and the sections below are organised by the patterns the combined record produces, from the oldest equipment generations to the newest failure modes.
There is an equipment timeline buried in Washington's housing figures, and it reads like a technician's diary. The 533,903 homes from before 1960 were heated first and cooled later, their ducts added around floor plans that never imagined them. The 608,401 that followed between 1960 and 1979 mixed those retrofits with the first planned central systems. Then came the 697,799 homes of 1980-1999, fitted with matched systems as standard. Each band of that timeline is now a band of characteristic failures, arriving in the order the equipment tires — which is why a home's build year, in this metro, is the single most predictive fact about its heating and cooling.
Uniformity is the newer stock's defining trait. A subdivision in Arlington or Alexandria went up in a handful of years, fitted with one generation of equipment, one duct design, one thermostat class. That uniformity writes a calendar the whole street shares: the first heating wave, the first cooling wave, the first questions about refrigerant and charge arrive together, years before the same streets need anything structural. With 25.9% of the metro built since 2000, that calendar governs a large and growing share of Washington's HVAC work — predictable work, if a household reads the calendar early.
The weather's part in this is written at WASHINGTON DC DULLES AP, VA US, where an average year carries 43.24 inches of precipitation, 32.7 days at ninety degrees or more and 101.7 nights at freezing or below. Systems experience that year as workload and as stakes in roughly equal measure — the workload in the run hours, the stakes on the single coldest night and the single hottest week. The problem ranking further down is simply the housing profile above, read under this sky.
Two public records, one metro: what was built here, and what the sky does to it.
Break the stock down by building era and the profile sharpens. Before 1960: 21.5% of homes, roughly 533,903 of them. From 1960 to 1979: 24.5%, about 608,401. From 1980 to 1999: 28.1%, about 697,799. Since 2000: 25.9%, about 643,167. Four eras, four equipment generations — and the balance among them is this metro's HVAC character in a single paragraph.
This metro's stock was mostly built in HVAC's transitional decades, 1980 to 1999, and it shows a particular failure calendar: not the deep-design sagas of the old metros, but the wear-out wave of everything installed in those years arriving together — capacitors, igniters, control boards, the first of the modern systems ageing into their verdicts. Washington's HVAC story for the next decade is largely written: it is the story of that installed base reaching its limits neighbourhood by neighbourhood.
Behind the leading era, the growth band: 25.9% of homes arrived since 2000. Their systems are uniform by construction — one generation of equipment, one approach to duct design — which writes a shared calendar the whole street keeps. Reading that calendar early is most of what separates a planned replacement from a weekend emergency in Washington's newest districts.
Translate the climate record into HVAC terms and it comes out as three working conditions. Condition one, the freeze count — 101.7 nights a year when a heating failure stops being a comfort issue and becomes a household one. Condition two, the heat count — 32.7 days that load condensers, ducts and tempers simultaneously. Condition three, the moisture: 43.24 inches of precipitation arriving as humidity the cooling coil must remove. Washington's systems are engineered, installed and aged inside those three conditions, and their failures carry the conditions' fingerprints.
Hold the two halves together and the rest of this page explains itself: the problems ranked highest here are the ones where Washington's dominant housing era and its climate record overlap. Change either dataset and the ranking changes — which is precisely why this profile is rebuilt from the records for every metro instead of carried over from the last one.
Sequenced by this metro's own problem ranking, not by a national catalogue order.
Every repair through TempReach USA follows the same order: diagnosis at the equipment, findings explained, quote given before work begins, and a full test cycle before the technician leaves your Washington home.
Ask what fills an AC repair diary in Washington and the answer is written in its housing. The median home was built in 1983, and a good share of the metro's cooling equipment is older than the homes' current owners realise — units sized for a different era of insulation, charged with refrigerant generations that have since been phased down. A system in District of Columbia County that cools a little less each summer is telling a story in instalments, and the repair visit reads the whole story: pressures, airflow, the coil's condition, the duct losses behind the walls. With a median build year of 1983, most of the metro's 2,483,270 housing units are working through the same ageing curve.
Count the exposure from the Census side: a median build year of 1983 across 2,483,270 housing units means half the metro's air conditioners are older than the systems in the growth suburbs around Arlington, and summer runtime is the statistic that matters — the repair calls follow it street by street.
Where this service gets booked in Washington follows the map on this page: the older districts generate the deep-end work, the post-2000 subdivisions the wear-and-tear work, and the 697,799 homes in between split the difference. Telling the call center your home's build decade — most Washington owners know it within a few years — puts the right kit on the van the first time.
Post-renovation is the clearest case in the trade. Drywall dust and sanding residue settle through every open register, and one thorough cleaning after the work ends removes in hours what the system would otherwise circulate for years.
Duct cleaning in Washington is booked in waves that follow the housing: after the renovation seasons in the older districts, at move-in across the subdivisions, alongside system replacements everywhere. The work pairs naturally with the inspection that surrounds it — leaking joints found and sealed, a disconnected run in an attic discovered, insulation fallen where it should not be. The cleaning is the appointment; the findings are often the value. From Arlington to Alexandria, the pattern repeats wherever the housing era matches.
Count the systems and the diary fills itself: 2,350,158 households breathing through ductwork daily, the oldest of it in homes from the 1980s and the newest in the subdivisions past Germantown. What the cleaning finds follows the biography — dust in proportion to years, debris in proportion to renovations.
One local habit worth copying: Washington homeowners who mention their street's building era when they book get a better-matched visit, because a technician heading to a the 1980s home in District of Columbia County loads different parts than one heading to a new-build subdivision in Arlington. The service is the same; the preparation is local.
A tune-up is scheduled while the system still works, which is the entire point: measurements taken in mild weather find the parts that hard weather would have found instead, at its own chosen hour.
Maintenance in Washington is a calendar with two appointments a year, written by the climate: one before the 32.7 hot days arrive, one before the 101.7 freezing nights do. The cooling visit works the outdoor unit — coils washed, refrigerant pressures read, capacitors and contactors tested, the condensate drain cleared before the humid weeks can clog it. The heating visit works the furnace or heat pump — burners and ignition, the exchanger's condition, venting, airflow. Between them they catch the failures this metro's systems rehearse every year, while those failures are still small. Locally the workload concentrates where the stock is oldest — the districts built around the 1980s first.
The maintenance caseload is the installed base itself: 2,483,270 housing units whose systems each face 32.7 hot days and 101.7 freezing nights a year. Around Silver Spring (82,129 residents) as in the old core, the twice-yearly visit is what stands between that calendar and the emergency diary.
In Washington this service is booked most often through the problem patterns at the top of this page — the metro's housing data, not habit, sets the order. If your home is in the 46.0% built before 1980, mention its age on the call: it changes the parts the technician loads before heading to Washington and the rest of the metro.
Every furnace repair routed through TempReach USA ends with a full heating cycle run under observation in the Washington home — ignition to steady operation — because a repair is finished when it is proven.
There is a safety grammar to furnace repair in Washington that every visit observes: combustion checked, venting verified, the exchanger's integrity read before comfort is discussed. A cracked exchanger or a lazy flame is not a comfort fault wearing a disguise; it is the one finding that changes the visit's whole direction. In a metro where 1,142,304 homes predate 1980 and their furnaces have been swapped into ageing duct systems more than once, that grammar is the difference between a repair and a recommendation — and honest technicians here will show the homeowner the evidence either way. In Washington that holds across 347 ZIP codes, from Washington out to Alexandria.
Under Washington's winters lie 4,604 heating degree days a year, and the furnaces answering them include the ageing units of the 1,142,304 pre-1980 homes alongside the electronic systems of the new subdivisions. The repair diary in Dale City reads both ends of that stock in a single week.
In Washington this service is booked most often through the problem patterns at the top of this page — the metro's housing data, not habit, sets the order. If your home is in the 46.0% built before 1980, mention its age on the call: it changes the parts the technician loads before heading to Washington and the rest of the metro.
The visit ends with the household better armed than it began: the switch's location known, the early signals named, the difference learned between a symptom to report promptly and one to endure until it becomes this.
Preparation is the quiet half of emergency work in Washington, and it is written in the metro's figures: a housing stock of 2,483,270 units, median vintage 1983, spread over 347 ZIP codes, will produce its no-heat and no-cooling nights on a schedule the climate roughly predicts. The households that come through those nights with the least damage are rarely the lucky ones; they are the ones who know where the system's shutoffs and breakers are, keep the number where it can be found, and treat the system's small warnings — the odd noise, the short cycle, the room that drifts — as the appointments they were. That is the daily reality for the 2,350,158 households spread across District of Columbia, Charles, Frederick, Montgomery, Prince George's, Arlington, Clarke, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, Spotsylvania, Stafford, Warren, Alexandria city, Fairfax city, Falls Church city, Fredericksburg city, Manassas city, Manassas Park city, Jefferson.
The emergency caseload is written in the extremes: 32.7 days of serious heat and 101.7 freezing nights a year, against systems whose median home was built in 1983. In Gaithersburg as across the metro, the urgent calls arrive when the weather and the equipment's age meet.
Where this service gets booked in Washington follows the map on this page: the older districts generate the deep-end work, the post-2000 subdivisions the wear-and-tear work, and the 697,799 homes in between split the difference. Telling the call center your home's build decade — most Washington owners know it within a few years — puts the right kit on the van the first time.
Replacement in Washington begins with a load calculation across District of Columbia, Charles, Frederick, Montgomery, Prince George's, Arlington, Clarke, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, Spotsylvania, Stafford, Warren, Alexandria city, Fairfax city, Falls Church city, Fredericksburg city, Manassas city, Manassas Park city, Jefferson: the independent local professional measures the home — not the old unit's label — and quotes the full scope before work begins.
With 2,483,270 homes and a median build year of 1983, Washington heating stock spans every era of furnace and flue — each installation assessed on its own house, not on the outgoing unit's label.
Heat pump services in Washington test the whole year-round system: the independent local professional covering District of Columbia, Charles, Frederick, Montgomery, Prince George's, Arlington, Clarke, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, Spotsylvania, Stafford, Warren, Alexandria city, Fairfax city, Falls Church city, Fredericksburg city, Manassas city, Manassas Park city, Jefferson reads charge and airflow in both modes, proves defrost, and checks auxiliary heat logic before quoting any work.
Ductless installation in Washington is surveyed room by room across District of Columbia, Charles, Frederick, Montgomery, Prince George's, Arlington, Clarke, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, Spotsylvania, Stafford, Warren, Alexandria city, Fairfax city, Falls Church city, Fredericksburg city, Manassas city, Manassas Park city, Jefferson: the independent local professional calculates each space's load, plans line and drain routes, and quotes the complete design before work begins.
In Washington, air work follows the climate ledger: 4,604 heating degree days dry the indoor air out each winter while 1,233 cooling degree days load it with humidity each summer — most homes here need the humidity answer in both directions across the year.
From Washington to the metro's edge, Washington's 2,483,270 homes run every system type there is — single-stage furnaces, two-stage equipment, heat pumps with auxiliary heat — and each gets a control matched to its terminals, not a shelf guess.
Across District of Columbia, Charles, Frederick, Montgomery, Prince George's, Arlington, Clarke, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, Spotsylvania, Stafford, Warren, Alexandria city, Fairfax city, Falls Church city, Fredericksburg city, Manassas city, Manassas Park city, Jefferson, one climate ledger drives the calendar: 4,604 heating degree days and 1,233 cooling degree days mean roof units work both seasons hard, so the spring and fall visits each carry a full checklist here.
Ask where this metro's HVAC diary fills up and the answer is a short story: The refrigerant transition reaching older systems first, leaky ducts losing air and energy close behind, and the services that answer them doing the bulk of the booked work. Everything else on the list above is the supporting cast — necessary, frequent enough, but not what Washington's housing stock, at its age and in its climate, principally demands. Read the service list as a weather report for the metro's systems and it stops looking like a catalogue.
Chosen by this metro's own housing and weather data — the same two records this whole page is built from.
It is worth saying plainly what the transition is not. It is not a mandate to replace working equipment, not a deadline after which older systems become unusable, and not a verdict on the many R-22 and early R-410A systems still cooling Washington homes adequately. Systems are retired by economics and condition, not by calendar. What the transition changes is the slope of those economics: each year, the older generation's refrigerant and parts grow scarcer while the machine itself grows older, so the repair-versus-replace crossing arrives a little earlier than the same failure would have suggested a decade ago. Honest service practice in this metro states that slope openly and lets the household's own numbers — the unit's age, its condition, its history — make the call. The refrigerant in the pipes has become a fact of the house, like its roof's age: not urgent every day, and unwise to leave unexamined.
The mechanics underneath the policy are simple. A refrigerant is the working fluid of the cooling cycle: it evaporates indoors to absorb heat and condenses outdoors to release it, thousands of times a season. Each generation of fluid was engineered to improve on the last one's environmental profile and operating pressures, and each required its own hardware — compressors built for different pressures, oils that mix with one fluid and not another, metering set for one fluid's characteristics. That is why the generations cannot be swapped like brands of the same product, and why 'topping up' an older system always means its own fluid, sourced from whatever supply its generation still commands. In Washington, where systems from all three generations stand in neighboring yards, the diversity is a service reality: diagnosis begins with identification, because the same symptom — a system low on charge — carries three different expense structures depending on the nameplate.
The regulatory facts are the foundation: R-22 production and import ended in the United States in 2020, leaving reclaimed stock as the supply, while new equipment has moved through R-410A to the current lower-impact generation. In Washington every generation still stands in service — the transition is not coming to this metro; it is distributed across it, yard by yard.
There is also a quieter loss running underneath the comfort loss: what leaks out was paid to condition. Every run of the system heats or cools a volume of air; the share that escapes into the attic or crawl space is work done for no room, repeated cycle after cycle, season after season. In a Washington home the arithmetic is worst exactly when the load is highest — the 32.7 hot days push the longest runs through the hottest attics — so the loss curve and the demand curve rise together. Sealing is unglamorous work: mastic on joints, connections re-made and supported, insulation restored where it has fallen. But it is one of the few interventions whose benefit the household can feel at the register on the first run afterward, in air that arrives at the temperature and volume the system produced.
The construction details explain the timeline. Duct joints are mechanical connections, and the sealants asked to make them permanent have finite lives: cloth-backed tape dries and releases, foil tape lifts at edges, and even mastic can crack where runs move with the building. Flex duct, common in the metro's later building decades, fails at its connections and where its inner liner is pierced or crushed — and a crushed section quietly throttles every room downstream of it. Meanwhile the spaces the ducts cross work against them: attic temperatures in a Washington summer turn an uninsulated or leaking run into a heat exchanger pointed the wrong way, and winter reverses the argument in the crawl space. A duct system is therefore not a fixed asset but a slowly changing one, and its delivered performance in any given year is an empirical question, not a memory of its installation day.
The load figures complete the case: 1,233 cooling degree days and 4,604 heating degree days at WASHINGTON DC DULLES AP, VA US mean the network is in service in earnest at both ends of the year. Duct loss here is not a summer inefficiency or a winter one; it is a twelve-month tax on a system that works both seasons.
What ageing systems reward, above all, is records. A Washington household that can say when its system was installed, what has been replaced, and what last year's readings were gives a technician a running machine to assess rather than a mystery to open. The metro's housing makes this more valuable, not less: with 2,483,270 housing units and equipment of every era in service, the difference between a system with a history and one without is the difference between a plan and a guess. Age itself is not the enemy — plenty of well-kept systems in this metro heat and cool reliably deep into their second decade and beyond. Unrecorded, unmeasured age is the enemy, because it converts a manageable slope into a cliff edge that only reveals itself in extreme weather, when every option is at its most expensive in time and trouble.
Judge an ageing system by its trend line, never by its kindest day. On its kindest day — mild weather, light load — almost any system in Washington can still argue for itself. The trend line is written elsewhere: in run times lengthening season over season, in the setting creeping to hold the same comfort, in the rooms that quietly dropped out of the system's reach. WASHINGTON DC DULLES AP, VA US's climate record ensures the trend will be tested at both ends of the year — 32.7 hot days and 101.7 freezing nights in an average year. The households that read their trend early choose the terms of the ending, whether that ending is a renewed component, a planned replacement in a shoulder season, or a few more good years bought with honest maintenance. The households that wait for the system's verdict receive it in the weather least suited to hearing it.
The arithmetic is straightforward: 2,483,270 housing units in Washington, a median build year of 1983, and equipment that turns over far more slowly than it ages. At any given moment, a large share of the metro's systems are in the second half of their working lives — being maintained there, or being discovered there.
Winter examines a furnace the way a long journey examines an older car: not with one dramatic test, but with sustained demand that finds every tired component in turn. In Washington, the examination runs for months — 4,604 heating degree days of it — and the components sit it in order of their wear. Igniters, which glow and cool with every cycle, are the classic first casualty of a long season. Motors follow, their bearings carrying the season's hours. What surprises households is the clustering: a furnace that needed nothing for years can ask for two repairs in one hard winter, not because the first repair failed, but because the cold is auditing the whole machine at once and reporting its findings in sequence.
Judge a furnace by its coldest week, not its kindest. In its coldest week a Washington furnace shows its true condition: whether it lights first time every time, whether it holds the house through the night without the temperature sagging, whether its sounds are the sounds it made when it was younger. WASHINGTON DC DULLES AP, VA US's record — 101.7 freezing nights in an average year — makes the examination annual and unsparing. Households that come through it without drama have usually done one unglamorous thing: they treated the autumn symptoms as the season's advance copy. A furnace rarely fails without having filed its intentions first, in a slower start, a louder cycle, a room that stopped keeping up. The winter merely publishes what the furnace had already written.
Housing adds its evidence: with a median build year of 1983, much of Washington's heating plant serves homes whose ductwork and insulation ask more per cold night than modern construction would. The furnace wears against the house as well as the weather.
The aftermath has a pattern too. Freeze heating failures in Washington are audited at the thaw — twice: once by the technician restoring the system, and once by the water, which reports every pipe the cold found while the heat was off. A burst discovered then is not a separate misfortune; it is the same event's second act, and preventing it is a matter of the first act's management: water shut down and drained where the exposure demanded it, exposed runs protected while the house was cold, the thaw watched rather than assumed. Households that have lived one freeze failure tend to emerge with a written household plan — valve locations, the order of actions, the number to call — because the event teaches what no mild season can: that in this climate, heating is not a comfort system with a plumbing neighbor, but a single system whose failure modes arrive together.
The physics of the risk run on a simple clock. A house loses heat through its envelope at a rate set by the temperature difference across it; in a hard freeze that difference is the widest of the year, so the indoor temperature of an unheated house falls fastest exactly when the consequences of falling are gravest. The fall is uneven: rooms over unheated spaces and against the wind cool first, wall cavities housing pipes cool faster than the rooms they serve, and a pipe can reach freezing beside a room that still feels merely chilly. That unevenness is the trap in a household's intuition — the thermostat's reading is the house's average story, while the pipes live in its coldest footnotes. In Washington the margin between a cold night and a damaging one is often a single night's depth of freeze against a house whose heat failed that morning, which is why the response sequence treats hours as the unit of value.
The climate record is the whole brief: 101.7 nights a year at or below freezing and 4,604 heating degree days at WASHINGTON DC DULLES AP, VA US. In Washington, a heating failure is never only a heating failure in those weeks — it is a timed exposure for every pipe the heat was guarding, and the record brings the test back annually.
What the shoulders reward is a habit of finishing seasons properly. The last cold week is the time to note the heating system's report card while it is still legible; the last hot week, the cooling system's. Between them sits a window — mild days, an unhurried diary for local technicians, a system that can be opened and tested without the household depending on it that night — that neither deep season gives. In Washington that window opens twice a year on a climate of 32.7 hot days and 101.7 freezing nights, and the households that use it convert the two most failure-prone transitions of the year into the two calmest appointments on their calendar.
The season loads Washington's systems the way its record at WASHINGTON DC DULLES AP, VA US says it will: 4,604 heating degree days against 1,233 cooling degree days in an average year, against a housing stock whose median build year is 1983. The households that read the season early — filters, drains, a system run before the extreme weeks — are the ones whose calls stay schedulable.
There is a supply-side depth as well. A shrinking refrigerant does not vanish; it circulates — recovered from retired systems, reclaimed to specification, and returned to service at an expense that reflects the shrinking pool. In Washington that means the R-22 in a system serviced this year may have cooled three other homes before it, and may cool another after this system retires, provided it is recovered rather than vented. The chain gives older equipment a managed twilight rather than a cliff: service remains possible, performed by technicians qualified for the work, for as long as the economics hold for the household. Understanding that chain replaces two common errors — that old systems are already unserviceable, and that they can be serviced forever as cheaply as ever — with the true picture: a gradually tightening supply, a gradually aging fleet, and a decision that improves with information and worsens with delay.
The numbers underneath it, for Washington: 2,483,270 housing units, a median build year of 1983, and a climate record at WASHINGTON DC DULLES AP, VA US of 4,604 heating degree days against 1,233 cooling degree days. Cross the housing record with the weather record and this pattern is what falls out at the top — rarely the most dramatic problem in heating and cooling, but the one this metro's stock and climate manufacture most steadily.
Experienced local practice starts with the simple certainties — the observations that take minutes and decide the most:
PROBLEM
SOLUTIONPopulation 672,079
Population 235,463
Population 156,788
Population 90,521
Population 82,541
Population 82,129
Population 80,617
Population 72,793
Population 71,885
Population 69,225
Population 67,403
Population 67,218
Also in the Washington metro: Reston (population 63,542), Bowie (population 57,771).
Beyond Washington itself, the metro takes in Arlington (235,463 residents), Alexandria (156,788) and the rest of the communities in the grid above — each fitted with heating and cooling in its own building era, which is why two streets in the same metro can need entirely different HVAC conversations. The ZIP list below is the full coverage footprint: if your code is on it, this page was written about your housing stock.
Beyond the largest communities sit Germantown (90,521), Waldorf (82,541), Silver Spring (82,129), Frederick (80,617), Dale City (72,793) — smaller places across District of Columbia, Charles, Frederick, Montgomery, Prince George's, Arlington, Clarke, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, Spotsylvania, Stafford, Warren, Alexandria city, Fairfax city, Falls Church city, Fredericksburg city, Manassas city, Manassas Park city, Jefferson, covered on the same terms. Their housing tends to be older on average than the big suburbs', and their calls follow the older patterns on this page. One routing covers them all: find your ZIP code below and the rest is a phone call.
Every metro has a first city and a supporting cast, and the census figures draw the billing plainly here: Washington first, with 672,079 residents; Arlington second at 235,463; Alexandria third at 156,788; then the long tail of smaller communities in the grid above. The billing matters less than the building dates — each of these places was fitted with heating and cooling in its own decade, by its own builders — but between them they account for nearly every housing era, equipment generation and failure pattern this page describes.
Administratively the metro is drawn from District of Columbia, Charles, Frederick, Montgomery, Prince George's, Arlington, Clarke, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, Spotsylvania, Stafford, Warren, Alexandria city, Fairfax city, Falls Church city, Fredericksburg city, Manassas city, Manassas Park city, Jefferson — 23 in all — with District of Columbia County at its centre. County lines do not change how a system runs, but they do shape the paperwork around the work: permits, inspections and code details are county and city business, which is one reason the professional who serves your street is a local one.
This page ends at the metro boundary, but the region does not: Winchester, VA, Hagerstown, MD and Baltimore, MD continue the coverage in their own directions, each with a profile built from its own Census and NOAA figures. If your home sits near the line between metros, go by your ZIP code — it places you in the dataset that describes your housing.
Set Washington among its neighbours and the contrasts sharpen the profile: Winchester, VA — metro population 152,332, median build year 1989 — sits 55 miles away; Hagerstown, MD (315,280, median 1984) 59 miles; Baltimore, MD (2,857,781, median 1975) 59 miles. Three different housing stocks under three nearby skies, which is why each keeps its own page and its own problem ranking rather than borrowing this one.
The stock has a shape as well as a size. Owners hold 63.5% of it and renters 36.5%, a split that decides who notices a comfort problem first and who arranges the repair. The generations split 1.8-to-one in favour of the pre-1980 homes. And the map divides into 14 named communities across District of Columbia, Charles, Frederick, Montgomery, Prince George's, Arlington, Clarke, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, Spotsylvania, Stafford, Warren, Alexandria city, Fairfax city, Falls Church city, Fredericksburg city, Manassas city, Manassas Park city, Jefferson, each carrying its era's share of the 2,483,270 housing units the Census counts here.
Washington by the derived numbers — median home age 43 years · owners in 1,492,350 homes, renters in 857,808 · each covered ZIP code carrying about 1,539 pre-1960 homes · a heating-to-cooling degree-day ratio of 3.73 · 1,098 mm average annual rainfall.
County pages carry the local detail — land area, climate normals and the heating and cooling pressures on the ground in each county.
More plain-language help: the TempReach USA heating & cooling guides
Describe the problem and the call center routes you to an independent local HVAC technician who works in the Washington metro.
Call center hours: Mon-Fri 7:00 AM-10:00 PM ET | Sat 8:00 AM-10:00 PM ET | Sun 7:00 AM-9:00 PM ET