North Carolina Just Ran Austin's Parking Experiment at State Scale

North Carolina's new parking law spends four subsections on what a city may no longer require inside a parking lot. It spends no words on fire apparatus access for apartment buildings. None on the Americans with Disabilities Act. None on loading docks, trash-truck turning radii, or the parking ratio a construction lender will size a loan against.

House Bill 162, the Parking Lot Reform and Stormwater Control Act, was signed by Gov. Josh Stein on July 6, 2026, and chaptered as Session Law 2026-39 the next day, July 7. Part I takes effect January 1, 2027, and strikes off-street parking minimums out of the zoning code of nearly every city and county in the state.

No transit buffer, no metro-region boundary. By geographic scope it's the broadest state-level parking repeal in the country.

Scope is also the wrong thing to measure. Whether a parking lot shrinks depends on the other rulebooks that size pavement, and HB 162 touches none of them for multifamily, commercial, or mixed-use buildings.

The bill's one fire-code concession is scoped, inside its own sentence, to developments of one- or two-family dwellings. Multifamily isn't in that sentence. The word "accessible" never appears next to a ratio. Loading and solid waste aren't in the bill at all.

So the useful question on a live site plan is narrower than the headline. Before you assume the lot shrinks, check what fire apparatus access still demands for the building type you're actually drawing, what accessible-space count and geometry the provided parking triggers on its own, whether a loading bay and a collection-truck pad still have to fit somewhere, and what ratio the construction lender is underwriting. On a Charlotte apartment site in 2027, all four survive the repeal. Any one of them can hold the pavement right where it is.

The market has already said so out loud. Andrew Phelan, a development director at Greystar, the largest apartment developer in the country, told Axios Charlotte that the firm builds about 1.3 spaces per unit in Charlotte. Five months ahead of the effective date, the repeal doesn't change that number. More flexibility on paper. Same ratio on the ground, because Charlotte renters drive.

What HB 162 Actually Preempts

The operative language rewrites G.S. 160D-702(c), the list of things a local development regulation may not do. The ratified text adds a new subsection (2a) prohibiting a locality from requiring a minimum number of off-street parking spaces, "regardless of occupancy or use."

That's the headline, and that's the entire repeal.

Everything else in Part I is dimensional. A city can't require a parking space larger than nine feet by twenty feet, and spaces designated for handicap, parallel, or diagonal parking are carved out of even that cap.

Subsection (3) covers fire apparatus access roads, and it does less work than its placement suggests. A fourth provision caps pavement design standards at NCDOT minimums.

Counties covered by the Coastal Area Management Act definition at G.S. 113A-103 keep their authority to set minimums. Twenty counties sit on that list, running from Currituck at the Virginia line down to Brunswick.

Coverage of the bill has settled on roughly 90 percent of the state's population living outside them, which is where the repeal actually binds. The statute itself doesn't say that. It just names the counties.

Inside those coastal counties, historic districts and designated landmarks don't get the exemption. They stay subject to the statewide repeal, an inversion almost no coverage of the bill caught.

Brunswick County officials told Port City Daily they expect little operational change from the parking provisions, because most of the county already qualifies for the coastal exemption. New Hanover sits on the same list, so the same reasoning holds there, whether or not anyone at the county has said so.

That's an accurate read of the statute, and the least interesting thing about it. The counties where the repeal binds hardest are the ones where its silences bind hardest too.

The Fire-Code Exemption Stops at Two-Family Homes

Subsection (3) prohibits a locality from requiring additional fire apparatus access roads beyond what the North Carolina Residential Code's fire provisions already require. Then it names the buildings it applies to: developments of one- or two-family dwellings.

Multifamily isn't in that sentence. Neither is any commercial or mixed-use building.

Which means the General Assembly identified fire apparatus access as a real constraint on parking-lot geometry, wrote relief for it, and scoped that relief to houses and duplexes. Apartments, shopping centers, and office parks sit outside it.

That matters because apparatus access is where Austin's 2023 repeal ran out of room. The code that governs apartment buildings in North Carolina is a different book from the one the carve-out points at. It's the state Fire Prevention Code, adopted from the International Fire Code, the same family Austin's numbers come out of.

Those numbers are geometry, not policy: the same 25-foot lane, 150-foot hose-lay, and 26-foot aerial corridor the parent piece laid out. North Carolina's fire-code figures come out of the same family, and they land on the same square footage the parking minimum used to claim.

A designer who deletes surface parking on January 2, 2027, expecting to recover the area, finds the fire lane already sitting on most of it. The geometry is stricter than the parking minimum ever imposed.

The stall count came out of the zoning code. The drivable, load-rated, turnaround-equipped corridor is still in the fire code, and HB 162 left it there for every building bigger than a duplex.

ADA, Loading, and the Lender Are Not in the Bill

Federal accessibility ratios key off provided parking. What a city requires never enters the calculation.

Build 60 spaces because your lender wants 60 spaces, and the IBC ratio table imposes three accessible spaces, one of them van-accessible. Then come stall dimensions, access-aisle widths, signage, and a compliant route of travel from the right-of-way to every public entrance.

No state legislature can repeal that, and HB 162 doesn't try. The bill's own dimensional cap concedes the point by exempting those spaces from the nine-by-twenty limit.

Minneapolis ended citywide minimums in a 2021 zoning overhaul and wrote the same concession into its code explicitly. A share of whatever parking a project provides in commercial, industrial, multifamily, and mixed-use buildings has to be accessible parking, sized to national disability-prevalence data. Repeal the minimum, keep the ratio.

That's what the mechanism looks like when a city bothers to say it in writing. No North Carolina planning department has published anything comparable yet.

Loading, solid-waste maneuvering, and lender underwriting get the same treatment by omission. A striped loading bay a box truck can enter and exit forward needs a drive aisle, and so does a pad the collection truck can back to and clear. Both land on the pavement parking used to occupy.

Neither is in HB 162. Austin's ordinance skipped them too, and there the underwriting standard turned out to be the largest single constraint on built parking, sitting outside every code book a council can amend.

Austin's ordinance was written on that understanding. Zo Qadri, who sponsored the repeal through the 8-2 Council vote in November 2023, argued it would take away a requirement without taking away anyone's ability to build parking.

That was an accurate description of his own ordinance. It's also an accurate description of HB 162, three years early.

What the State's Own Market Already Says

Raleigh and Durham have been running this experiment locally for years. Raleigh's council ended parking minimums citywide 7-1 in March 2022 under Ordinance TC-11-21. Durham followed in November 2023.

North Carolina isn't a blank slate. It has two mid-size in-state precedents, four and two years ahead of the statute.

Charlotte is the one that matters, because Charlotte hadn't repealed its minimums locally. It's the largest market in the state, and the one where HB 162 has the most room to change behavior. Greystar's answer is 1.3 spaces per unit, with 1.2 under consideration in denser submarkets like South End.

That tenth of a space, if it happens, is a developer's own call. The statutory floor coming out had nothing to do with it.

Charlotte already has a building that shows what the other end looks like. The Joinery, 83 units in Optimist Park, was built with no resident parking years before HB 162, on the developer's own election.

It works for the residents who chose it for that reason. One resident told WBTV she fights for parking every day. Both things are true, which is roughly what "no minimum" produces in practice.

None of this is a completed North Carolina case study, and none of it can be yet. The law isn't effective until January 1, 2027, so no fire marshal, ADA reviewer, or lender has yet forced a project to keep parking it no longer needed.

What exists is the statutory text, an in-state precedent in Raleigh and Durham, the on-record position of the state's most active apartment builder, and one state that has been running the narrower version of this law long enough to be studied.

California Ran the Narrower Version First

AB 2097, effective in 2023, barred California cities from requiring parking within a half-mile of a major transit stop. It's the narrow version of what HB 162 does statewide, and it has now been studied.

Amy Lee, Adam Millard-Ball, and Michael Manville sampled 15 California cities, studied six in depth, and ran 25 interviews with planners, developers, and legislative staff. Their finding, published in Urban Affairs Review in 2025 and summarized in the UCLA ITS policy brief, is that one state law produced three different local responses.

The springboard cities went past what the state required and scrapped minimums citywide. Others used the law as a shield, approving low-parking projects while pointing at Sacramento, or obstructed outright, arguing over whether planned transit stops counted and slowing permits.

Manville's read on the development side is that some builders are "taking advantage of this for things they had lined up". That's movement on projects already in the pipeline. It isn't a general drop in parking.

Two states, two different preemption scopes, the same non-uniform result. In California it was local political absorption. In North Carolina it will be the untouched rulebooks.

Either way, the breadth of the statute was never the load-bearing variable.

Three No Votes in the Entire General Assembly

Nobody in Raleigh fought about the breadth either. The House passed HB 162 117-0 in March 2025, the Senate 44-1 in June 2026, and the House concurred 111-2. Three no votes total on a bill preempting local zoning authority, in a category that's usually a partisan brawl.

The North Carolina League of Municipalities opposed it on local-control grounds and lost quietly.

The sponsors sold it as pavement economics. Housing policy barely came up. Rep. Donnie Loftis (R-Gaston), the primary House sponsor, described the origin as watching big-box lots sit empty: "I kept seeing all these box stores that had to have huge amounts of parking, and it seemed like it wasn't being used until two weeks before Christmas."

Sen. Ted Alexander, the Senate sponsor, called the bill "free-market oriented" and "property rights oriented." Both readings are correct about what the bill does.

That consensus bought the broadest map in the country. Fourteen states have enacted 34 laws cutting or ending parking minimums since 2019. Since 2017, 116 cities have removed all citywide minimums, Baltimore, Buffalo, Denver, Hartford, Minneapolis, and San Francisco among them. Most of the state laws are narrower than North Carolina's, tied to a transit buffer or a named metro region. HB 162 has no buffer. It has a coastline.

"The question is who decides how much parking you should need," Sightline Institute researcher Catie Gould told Stateline in July. On that question, North Carolina answered more decisively than any state before it. Neither the map nor the margin predicts how much pavement disappears, because the parking minimum was only ever one of the numbers setting that.

Read the Silences, Not the Map

The next state to run this will pass a different statute and leave the same four questions unanswered.

Does it reach fire apparatus access for the building type in question, or only for houses? Does it address accessible-space ratios and geometry, which key off provided parking? Does it say anything about loading, solid waste, or maneuvering standards in the engineering manuals? Does it change anything a lender will underwrite?

HB 162 answers houses-only, no, no, and no. Austin's ordinance answered the same way. Both are real reforms, and both leave the interacting constraints that actually size pavement exactly where they were.

For a Charlotte or Greensboro project entitling through next year, that resolves to a date and a swap. On January 1 the zoning stall count goes away, and the drive-aisle and stacking geometry that used to hide inside your parking layout becomes the thing you're designing around. The fire marshal, the accessibility reviewer, and the lender's credit committee all start January 2 with the authority they had on December 31.

Same asphalt, different governing rule. Firms that read only the headline will spend 2027 rediscovering where it went.