Transylvania County

Where it stands

request withdrawn Sept 8 by the chief; the Axon taser and body-camera purchase is still pending and was not on the Sept 21 or Oct 5 agendas or the Sept 28 Public Safety Committee agenda; next check the committee on Oct 26

The systems

• Flock Safety. The sheriff's office began installing 8 cameras in August 2024 with no commission vote found; DeFlock maps about 13 countywide and a commissioner put the number at about 14 on Aug 24, 2026. No transparency portal or published policy.Chuck Owenby
• Axon. Offered to Brevard: 3 fixed plate readers at no charge inside a five-year, ~$80,000 package of tasers and body cameras, plus monthly data-storage fees. The draft policy and contract are posted. Chief Wentzell withdrew the plate-reader request at the start of the Sept 8, 2026 council meeting; no vote was taken. The taser and body-camera purchase the cameras were attached to remains pending.What Axon Contracts Do

Next

• Monday, October 12, 6:00 PM: Transylvania County Board of Commissioners. Agenda not yet posted.
• Monday, October 26, 3:30 PM: Brevard City Council Public Safety Committee. Agenda not yet posted.

Brevard posted its documents before deciding: the draft policy and the Axon contract were posted, the city’s question session was held Sept 1, and at the start of the Sept 8 council meeting Police Chief Christy Wentzell withdrew the plate-reader request without a vote. The taser and body-camera purchase the three cameras were attached to is still pending, so the question can return. The county sheriff’s cameras have been up since 2024 with no commission vote found, and the county board first took the subject up on Aug 24, after residents raised it.

Timeline

Links of note

• The Sept 8 council meeting: the city’s recording; the withdrawal is at 0:05:50
• The Sept 1 session audio and the chief’s slides: the city’s own record of the information session
• Transylvania Times on the withdrawal: the chief pulls the request, Sept 8
• Transylvania Times on the Brevard decision: the Axon bundle and public-input recommendation
• Transylvania Times on the sheriff’s cameras: the 2024 county deployment
• Brevard City Council on YouTube: official council video

Who decides here

Chuck Owenby (sheriff, unopposed) · Brevard: Dean Lytle, Aaron Baker, Mayor Maureen Copelof, Chief Christy Wentzell. County commission: Chair Teresa McCall, Vice Chair Larry Chapman (asked for the sheriff’s briefing on Aug 24), Jason Chappell, Jake Dalton, Chase McKelvey.

The Brevard request, withdrawn Sept 8

The “free” cameras come with monthly data-storage fees. The city attorney reviewed it favorably; the deputy chief previously ran Hendersonville’s Flock system.

The request was withdrawn without a vote, and the purchase it rode on is still pending, so the same documents apply if it returns. The chief, on the recording: “If Brevard Police Department was ever to consider ALPR technology again, it would require significant budget requests that would come before council.” Everything on this site (the contract record, Camera network misuse, documented cases, how other communities negotiated) is there for anyone who shows up with questions.

The county

Sheriff Owenby credits his cameras with locating six missing persons and “reduction of crime”: no independent evaluation of either claim has been published. The count is unsettled: the Transylvania Times reported 8 cameras at installation in 2024, DeFlock maps about 13 countywide, and on Aug 24, 2026 a county commissioner put the sheriff’s number at about 14. A briefing from the sheriff, if the board schedules one, would settle it. No transparency portal exists for the sheriff’s system, and no policy manual is published; the office does appear on Henderson County’s list of 2,048 agencies with access to Henderson’s reads.

The county’s own meeting record, checked. We machine-searched the captions of 24 county commission meetings from June 2025 through August 2026 (one, April 13, 2026, has no captions and is not yet covered). Before August 2026 the cameras come up in substance once. At the March 23, 2026 meeting, an annual law enforcement report to the board described the county’s speed trailer as carrying a mobile Flock camera, and described the network’s reach in the presenter’s own terms: once an agency is in the Flock system it can search nationwide, because it is paying into the system (the county’s meeting video, March 23, 0:19:45). No meeting in the set shows the board considering or authorizing the cameras.

On August 24, after residents spoke at public comment, Vice Chair Larry Chapman asked the board to have the sheriff explain how his office uses the cameras, cited a recent recovery of two abducted girls, and corrected a figure circulating on social media: not 1,400 cameras in the county, about 14 (Aug 24 video, 3:09:48). A second commissioner said he did not know how the cameras had arrived and that the discussion had never entered that forum (3:16:40). The board’s next meeting falls after September 11, so the sheriff’s briefing, if scheduled, comes after Brevard votes. A resident at the same meeting made a point our own August 27 check of Flock’s portals confirms: Henderson County’s sheriff publishes a transparency portal and Transylvania’s does not, so a Transylvania resident cannot see which agencies have access to the county’s reads (0:11:31). The county’s video is published on Vimeo without speaker labels, so the lines above are descriptions with timestamps rather than quotations; the caption text is machine-generated and is not reproduced. Brevard PD publishes three documents on PowerDMS (mission, use of force, an organization chart); its draft plate-reader policy is posted separately on the city’s ALPR page and is read in full below. Transylvania has no 287(g) agreement with ICE (ICE list, Aug 21, 2026). The sheriff is unopposed in November, which removes the one direct check on his cameras for four more years (What the Law Lets the County Do).

Video: county commissioners are on Vimeo (no auto-captions); Brevard City Council is on YouTube. The Transylvania Times owns this beat. No organized local opposition group exists yet, which, given the pending public-input meeting, is the gap most worth filling in all of WNC.

The September sequence, dated

• Tuesday, Sept 1, Mary C. Jenkins Community Center: the city’s ALPR information session, held, staffed by Brevard PD and city staff in a question-and-answer format. It was a city event rather than a noticed meeting, so there is no agenda packet and no minutes; the city posted the audio and the slides afterward, and the timeline above carries what was said. The draft ALPR policy and the Axon contract remain posted on the city’s ALPR page, which by late August also carried the city’s own list of questions and answers about the proposal.
• The decision is a first adoption, not a renewal. At the Aug 17 council meeting a council member said the city has no plate readers today, that the cameras in the county are run by the sheriff and by a private business, and that concerns about existing cameras belong with the county (the meeting video, 2:13:05). One week later the county board heard exactly that from residents (above).
• Tuesday, Sept 8, 5:30 PM, City Council, 95 W Main St: the decision meeting, item M.3 on the agenda. The chief withdrew the request at the start of the meeting; council voted 3 to 2 to approve a modified agenda without it, and no vote on the cameras was taken (the recording, 0:05:50 to 0:11:17). Documents from Flock’s chief executive were due to the U.S. Senate the same day (Garrett Langley); on Sept 2 the same subcommittee wrote to Axon, with documents due Sept 16 (the letter).
• What was on offer: three Axon Outpost fixed plate readers at no charge, inside a five-year, ~$80,000 Axon package of tasers and body cameras, plus monthly data-storage fees. Asheville’s contract shows what the same vendor’s terms look like at full size.
• The committee record so far: Council member Aaron Baker wants the city “rock solid on the protections part of it” and says the Axon end of the agreement is his main concern; Dean Lytle says “the chief deserves to answer those questions to the public before it’s implemented.” The mayor and the other three members have not spoken publicly, and no Transylvania County commissioner has said anything about the sheriff’s existing Flock cameras.

The posted documents, read (Aug 26, 2026)

Brevard posted two documents before deciding, and that sequencing deserves to be said plainly: documents first, questions second, vote last. Asheville signed first and read later. We read both Brevard documents in full; archived copies with checksums are in our records. (The city’s ALPR page · our archive of the page · of the contract)

The draft policy (General Order 400-32, watermarked DRAFT, signed by Chief Christy Wentzell) is stronger than most in this region, and the specifics deserve credit:

• Plate data purged at 30 days by department policy (§D.4); state law, G.S. 20-183.32, allows 90. Asheville’s portal showed 90 until the week of its vote.
• Every query requires a call-for-service or incident report number, plus the officer’s name, date, and reason (§B.3, §F.2). This is materially stronger than a free-text reason box: EFF found 14% of 11.4 million Flock searches nationally justified with the single word “investigation.”
• Two-step approval before any plate goes on the department’s watch list: a supervisor checks for a “documented nexus,” then the CID Sergeant confirms (§B.5–7), with 24-hour validation.
• An annual public report to the city’s Public Safety Committee by Feb 28, “made available to the public,” whose required metrics include the number of audits completed and the number of policy violations discovered (§H.3).

What the draft leaves open, each phrased as a question the Sept 1 session can answer:

1. Everything above lives in a General Order: a document the chief signs and the chief can amend, with no council vote or public notice required (the form’s own header carries “Amends” and “Rescinds” fields). A General Order works this way in any department. The question: will council adopt the retention, sharing, and audit rules in a document only council can change?
2. The policy is silent on network participation: whether Outpost data joins any cross-agency lookup, and what the default is on day one.
3. The policy is silent on Axon’s default data program (see the contract, below).
4. Quarterly audits (§F.1) are internal, run “at the direction of the chief or designee,” with no named seat and no publication. Will the quarterly summaries be published, and who, by job title, runs them?
5. Camera locations are set by the chief on “data-driven criteria” (§B.2), with no publication requirement. Boone publishes its locations; will Brevard?
6. Sharing (§G) permits disclosure to “a criminal justice officer at a Federal, State, or local law enforcement agency” on written request, with paperwork requirements but no use-based limits. Washington State’s law names prohibited uses (immigration and reproductive-health enforcement); the documented cases behind those limits are on Camera network misuse, documented cases.
7. Alert verification is “should not rely solely on the ALPR alert” (§B.4), not “shall.” The LAPD Inspector General found a 32.3% false-positive rate on stolen-vehicle alerts; a mandatory-verification word change is free.

The posted contract is Axon’s standard Master Services and Purchasing Agreement (version 23, March 2025), all 50 pages of boilerplate. The actual purchase quote, with Brevard’s prices, line items, and subscription term, is not in the posted file; “Outpost” appears nowhere in it. The master terms that matter for a five-year decision:

• §2.2: the subscription “will automatically renew for an additional 5-year term,” with price increases up to 3% per year in renewal. A five-year deal becomes ten unless someone calendars the exit. That is version 23 of Axon’s master terms, dated March 2025. The one signed Axon contract posted in full in North Carolina, Durham’s from June 2026, is version 25, in which the automatic renewal is gone, renewal is by mutual written agreement, and some price caps became Axon’s then-current list price (What Axon Contracts Do). Which version Brevard would sign, and what sets the price at renewal in that version, is not answered by anything the city has posted.
• §3 and §6: “Payment obligations are non-cancelable.” “All sales are final.”
• §17: termination only for uncured breach or non-appropriation of funds; and if hardware was sold below sticker price, an early exit is billed at “the difference between the MSRP… and amounts paid” (§17.3). The free camera is an advance, recovered at sticker price if the city leaves.
• Cloud appendix §3, credit where due: “Customer controls and owns all rights, title, and interest in Customer Content,” with US data stored in-country.
• Cloud appendix §13: for usage data, “including query logs and metadata,” Axon is an “independent Data Controller,” processing it for its own product purposes, with third-party disclosure permitted once “anonymized, de-identified, and/or aggregated.”
• The ACEIP appendix: “By default, Customer will be a participant in ACEIP Tier 1,” Axon’s program for using customer content across customers to develop its products, with privacy-preserving extraction. Opting out requires the customer to revoke consent in writing. The draft policy does not mention it.

For comparison, Denver asked before signing and negotiated a one-year term, a camera cap, no national-database participation, and a per-query audit trail (Communities that ended or limited camera contracts). Every one of those protections was winnable by a customer that asked first, which is the position Brevard would be in again if the request returns.

Related: Western North Carolina and the state · What Axon Contracts Do · Communities that ended or limited camera contracts

Last verified: September 10, 2026