LEOKA Data Gathering With NIBRS

LEOKA (Law Enforcement Officers Killed or Assaulted) data are not submitted via NIBRS files at this time in Connecticut. The two unique LEOKA fields (Activity and Assignment types) are not in the current versions of the vendor software in Connecticut, with one exception. We plan to ask vendors to do this in the near future.

Connecticut has the state-specific file of Police as a victim type. To assess where LEOKA incidents may have occurred, we compile a list of all incident with police as victims in which the offenses are murder or assault. The compilation is done three months after the latest month received, on a quarterly basis, to allow late submittals to be included. A year-end compilation is also done to assure that changes have been implemented and all assaults are included. The incident numbers are sent to the agencies asking that they review each case and determine if there was an assault or killing of an officer. The reports returned to the state are on the same forms used by UCR Program participants.


This procedure was needed because every submitting agency, even the most conscientiously managed, overlooked the necessity to submit LEOKA reports. All of these agencies have been doing LEOKA reports for the 21 years the UCR program has been mandated in Connecticut. We also found that the correct reporting of LEOKAs often increased the number of assaults for agencies.

Assaults on officers are often overlooked as assaults due to the confusion between a UCR/IBR offense definition and a statutory definition. The statutory charge for assault on an officer often does not occur unless the officer is injured. Therefore, when the UCR/IBR offense code definitions are applied to the gathering of LEOKA data, more aggravated and simple assaults are added to the agency offense totals. Doing LEOKA results in more complete assault data.