When North Carolina's State Highway Patrol or other state law enforcement agencies collect statistics on traffic stops, is the identity of the officer who made each stop a public record, or can the state keep officer names confidential?
Plain-English summary
In the late 1990s, debates about racial profiling and disparate traffic enforcement intensified across the United States. North Carolina was one of the first states to require state-level law enforcement agencies to collect detailed data on traffic stops, including the race, ethnicity, age, and gender of drivers stopped, and the disposition of the stop. The data was meant to enable rigorous analysis of whether traffic stops were being conducted in a racially neutral manner.
When North Carolina enacted the requirement, a sensitive question emerged: should the identity of the individual officer who made each stop be part of the publicly released data? Proponents of identifying officers argued that officer-level analysis was essential to identify problematic patterns by specific personnel. Opponents argued that public release of officer names alongside individual stops would enable harassment of officers, would chill candid enforcement practices, and would expose officers and their families to safety risks.
The General Assembly resolved the tension in House Bill 1840 (Session Law 2000-67), signed into law by Governor Hunt on June 30, 2000. Section 17.2(a) of HB 1840 amended N.C. Gen. Stat. § 114-10(2a) to add two operational rules. First, the agency could meet its identification obligation by assigning anonymous identification numbers to each officer. Second, the correlation between an anonymous number and the officer's actual name was explicitly not a public record and could not be disclosed except by court order.
The Secretary of Crime Control and Public Safety asked the AG to clarify two questions in the wake of the amendment.
Question 1: Is the identity of the officer making a traffic stop a public record?
The AG said no. The amended § 114-10(2a) was unambiguous. The Legislature's intent to keep officer identities confidential was plain on the face of the statute. Under Utilities Comm. v. Edmisten, the North Carolina Supreme Court instructs courts to give clear and unambiguous statutory text its plain meaning. The location of the traffic stop, by contrast, was part of the public record under the same statutory framework.
Question 2: How does the new state rule interact with federal law?
The Secretary had identified a potential conflict between state and federal rules about officer identification in traffic stop data. The AG observed that whatever difference may have existed before HB 1840 was eliminated by the amendment. Federal law in 42 U.S.C. § 3789g prohibits federal grantees from releasing research data "identifiable to any specific private person." The amended § 114-10(2a) made officer identities confidential in state-collected traffic stop data. After the amendment, state and federal law were aligned: officer identities, in this data context, were protected.
The opinion was short and direct because the General Assembly had recently legislated the answer. The AG's role was to confirm the operative reading of the new statute and to put it on the record.
Currency note
This opinion was issued in 2000. Subsequent statutory amendments, court decisions, or later AG opinions may have changed the analysis. Treat this page as historical context, not current legal advice. North Carolina's traffic stop data collection regime has been amended significantly since 2000, including expansion to local law enforcement agencies and changes to the data fields collected. The public records and officer privacy balance has been revisited in legislation and litigation. Anyone working with current traffic stop data or current public records requests should consult current statutes (including the post-2000 reforms to traffic stop data collection in N.C. Gen. Stat. § 143B-903 and related provisions) and current case law.
Background and statutory framework
The racial profiling research context. Through the late 1990s and early 2000s, a number of states and federal agencies began to require traffic stop data collection to enable empirical assessment of whether traffic enforcement was being conducted in a racially neutral way. North Carolina was a leader; the state's data collection requirements were among the earliest and most comprehensive. The data was used by academic researchers and by state policymakers to analyze patterns of enforcement.
The dual purpose of the data. Traffic stop data has two analytical uses. First, aggregate analysis looks at patterns across an entire agency or across the state, asking whether the demographics of drivers stopped match the demographics of drivers on the road. Second, officer-level analysis looks at patterns by individual officer, asking whether specific personnel are conducting stops in a racially skewed manner. Aggregate analysis does not require officer identification; officer-level analysis does, at least at the internal-review level.
The HB 1840 compromise. The General Assembly preserved the ability to do officer-level analysis (via the anonymous identification numbers) while protecting the privacy and safety of officers (via the confidentiality of the correlation between numbers and names). The data could still be analyzed at the officer level by researchers and internal reviewers using the anonymous IDs; the agency could still investigate problematic patterns by specific officers internally by accessing the correlation; but the public could not get the name-to-number mapping without a court order.
This compromise reflects a recognizable pattern in statutory design: protecting privacy while preserving analytical utility through pseudonymization. The HIPAA Privacy Rule's de-identification standards work on a similar logic.
The location-of-stop public-record component. While officer identities are confidential, the location of each stop is public. Researchers can analyze enforcement patterns by geography (urban vs. rural, specific corridors, specific jurisdictions) without needing officer names. The General Assembly retained this transparency channel.
The plain-meaning canon. The AG's invocation of Utilities Comm. v. Edmisten is the standard North Carolina approach to clear statutory text. When the legislature has spoken plainly, courts apply the words as written. The 2000 opinion does not have to do much interpretive work because the amended statute is so direct about the confidentiality result.
The federal harmonization point. Section 3789g of Title 42 (the Crime Control Act of 1973's data privacy provisions) limits federal grantees' release of research data identifiable to specific individuals. North Carolina's law enforcement agencies often receive federal funding for data collection and analysis efforts, so they are subject to § 3789g. Before HB 1840, the federal rule and the state public records rule could have produced inconsistent obligations: federal law restricting release of identifiable data, state public records law (potentially) requiring release. The state amendment closed the gap by making the state confidentiality rule consistent with the federal rule.
The court-order exception. The amended statute allows release of the correlation between anonymous ID numbers and real names "when required by order of a court." This preserves the ability of litigants and prosecutors to obtain officer identification in specific cases where doing so is necessary for legal proceedings (criminal defendants challenging stop legality, civil rights plaintiffs, internal disciplinary investigations conducted with court oversight). The exception keeps the data accountable where accountability is most acute.
Subsequent evolution of the framework. Since 2000, North Carolina has expanded traffic stop data collection to local law enforcement, modified the data fields, and integrated the data with broader criminal justice transparency frameworks. The basic statutory architecture (anonymous IDs in the data, confidentiality of the correlation) has remained, but the implementation details have evolved. The current statutory framework is principally in N.C. Gen. Stat. Chapter 143B, Part 30E (Criminal Justice Education and Training Standards Commission) and related provisions.
Common questions
Q: Can I as a member of the public see traffic stop statistics in North Carolina?
A: Yes. Aggregate traffic stop data, including stop locations and driver demographics, has been published by state agencies. Specific anonymous-officer-level data may also be available depending on the dataset. What you cannot get without a court order is the correlation between an officer's anonymous ID number and the officer's actual name.
Q: Why are officer names confidential when so much of law enforcement work is on the public record?
A: The General Assembly balanced two interests. Aggregate transparency about enforcement patterns serves public accountability. But public listing of officers' names attached to individual stops, in a publicly distributable database, could enable harassment, retaliation, and safety risks. The compromise preserves analytical utility while protecting individual officers.
Q: Can a defendant in a criminal case get the officer's name connected to a specific traffic stop?
A: Yes, through standard discovery procedures. The traffic stop documentation in a specific criminal case identifies the officer; the confidentiality rule in § 114-10(2a) applies to the public records database, not to criminal case records. The statute's court-order exception also confirms that judicial process can obtain the correlation.
Q: What about civil rights litigation analyzing traffic stop patterns?
A: Civil rights plaintiffs can use the aggregate data and anonymous-officer-level data in litigation. If a case requires identifying specific officers (for example, to assess patterns by individual officer), the plaintiffs can seek a court order to obtain the correlation. Federal civil rights cases have done this in various states.
Q: How does this compare to traffic stop data laws in other states?
A: Many states adopted traffic stop data laws in the 2000s and 2010s. The specific privacy treatment of officer identities varies. Some states make officer names public; some use anonymization similar to North Carolina's; some collect officer-level data but restrict its analysis. The North Carolina approach is at the more protective end of the spectrum.
Citations
State statutes
- N.C. Gen. Stat. § 114-10(2a), as amended by Session Law 2000-67 — collection of traffic stop data; officer identities may be anonymized via ID numbers; correlation between numbers and names not a public record except by court order.
- Session Law 2000-67 (HB 1840) — June 30, 2000 enactment that amended § 114-10(2a).
Federal statute
- 42 U.S.C. § 3789g — federal restriction on release by federal grantees of research data identifiable to specific private persons.
Cases
- Utilities Comm. v. Edmisten, Attorney General, 291 N.C. 451, 232 S.E.2d 184 (1977) — North Carolina rule that clear and unambiguous statutory text is given its plain meaning without statutory construction.
Source
Original opinion text
Re: Advisory Opinion; Traffic Law Enforcement Statistics; Public Records; G.S. § 114-10(2a)
Dear Mr. Dugdale:
By letters dated May 9, 2000 and June 21, 2000, you requested, on behalf of the Secretary of Crime Control and Public Safety, the opinion of this office concerning whether the identity of a state law enforcement officer making a traffic stop and the location of the traffic stop is a public record. These requests for opinions have been held by this office pending action by the General Assembly on HB 1840.
The Legislature recently enacted HB 1840 and it was signed into law by the Governor on June 30, 2000. See CH. SL 00.0067. Section 17.2(a) amends G.S. § 114-10(2a) to provide that the identity of a state law enforcement officer making a traffic stop and the location of the stop must now be collected and maintained. It further provides that "[t]he identity of the law enforcement officer making the stop . . . may be accomplished by assigning anonymous identification numbers to each officer" and that "[t]he correlation between the identification numbers and the names of the officer shall not be a public record and shall not be disclosed by the agency except when required by order of a court."
This new legislation specifically resolves your first question. The identity of the officer is not a public record. The location of the stop, however, is part of the public record. The obvious intent of the Legislature is to keep the identity of officers making traffic stops confidential. Where the language of a statute is clear and unambiguous, there is no room for statutory construction and the statute must be given its plain meaning. Utilities Comm. v. Edmisten, Atty. General, 291 N.C. 451, 232 S.E.2d 184 (1977).
In your letter of June 21, 2000, you also ask for our guidance in resolving differences between state and federal law with respect to access to the identity of officers making traffic stops. Any difference that heretofore existed between state and federal law with respect to the confidentiality of the identity of law enforcement officers making traffic stops was eliminated by the adoption of HB 1840. State law and federal law, as they relate to this information, are now the same. Compare G.S. § 114-10(2a) as amended and 42 USC § 3789g (prohibiting release by federal grantees of research data "identifiable to any specific private person.")
We hope that this opinion has provided you the guidance you need. If you need further assistance, please do not hesitate to contact us.
Signed by:
James J. Coman
Senior Deputy Attorney General
Isaac T. Avery, III
Special Deputy Attorney General