Kidnapping reports in Chicago

Unlawful restraint reports as IUCR coded them

Kidnapping on the CPD extract is the primary type assigned when the report was written that way. Unlawful restraint, parental-dispute, and other fact patterns can appear under this label or under other types depending on the code. This page does not invent those subtotals. The headline is 168 rows labeled Kidnapping.

News language ("abduction") is not an IUCR field. Quote CPD's primary type. Do not upgrade a missing-person or runaway event into this total unless the row itself carries this type.

Missing-person cases are not automatically kidnapping. Only rows CPD labeled Kidnapping sit in the 168 among 410,083 city incidents. LocalCrimeVault does not upgrade other types into this total from news language.

Cite 168 among 410,083 Chicago incidents. Missing-person rows are not automatically kidnapping. News language is not an IUCR field. Keep 168 attached to CPD's primary type. Small counts should not be ranked across community areas.

Share of the Chicago extract

Among 410,083 indexed city incidents, 168 kidnapping rows are a very small share. Rarity on a police extract is still 168 reports that deserve a precise label. Official community area names are the city's 77 areas. Maps use block-level geography and must not be treated as identifying a child or a household.

Small counts swing hard in percent terms if someone computes a trend from two harvests. This packet has one count, 168. No prior-year figure is quoted.

Parental and non-parental fact patterns, if distinguished on IUCR codes, belong on the table. This packet has one total. Small counts should not be ranked across community areas. Official community area names are the 77-area list.

Amber Alert criteria differ from IUCR. They will not equal 168. Geography is block-level, not a child's address. Official community area names are the 77-area list. An arrest flag is not a conviction. LocalCrimeVault does not reclassify charges or narrate individual cases.

Reading the kidnapping table

Filter the 168 rows by date and community area. Arrest flags are not convictions. Missing geography stays blank. LocalCrimeVault does not impute a community area or a name.

This narrative stays aggregate. Graphic or identifying detail is not added. The legitimate use of the table is report volume, timing, and official geography.

Amber Alert logs use different criteria. They will not equal 168. Quote CPD IUCR primary type Kidnapping. Geography is block-level, not a child's address. An arrest flag is not a conviction. This page does not narrate individual cases.

What 168 is not

It is not an Amber Alert tally, not an FBI kidnapping program total, and not a court caseload. Those systems use different rules. Quote 168 as IUCR primary type Kidnapping among 410,083 Chicago incidents.

CPD and the City of Chicago publish the incidents. LocalCrimeVault does not reclassify charges. People are not named here.

Chicago hub placement

The kidnapping type hub holds the live table. The Chicago hub places these 168 rows beside the rest of the 410,083-incident mix so a rare type remains visible without crowding the high-volume IUCR categories. A cross-city page follows other agencies' kidnapping labels, which may include or exclude parental cases differently.

Cite 168 as Chicago Police Department incident rows with IUCR primary type Kidnapping among 410,083 city reports. News language such as abduction is not an IUCR field. Quote CPD's primary type. Do not upgrade a missing-person row into this total unless the row itself carries this type.

Parental-dispute and other fact patterns can appear under this label or under other types depending on the code. This packet has one total, 168, not a parental subtotal. Read IUCR codes on the table. This page does not describe individual cases.

Citing a rare IUCR type without news language

Amber Alert issuances and FBI program totals use different rules. They are not 168. Small counts swing hard in percent terms if someone computes a trend from two harvests. This packet has one count. No prior-year figure is quoted.

Maps must stay coarse. Block-level ranges and official community area names (77 areas) are not identifications of a child or a household. Record the 168 / 410,083 harvest pair. An arrest flag is not a conviction. LocalCrimeVault does not reclassify charges.

Questions

How many kidnapping reports are in the Chicago CPD index?

This extract lists 168 Chicago incidents with IUCR primary type Kidnapping, in a city file of 410,083 reports. The source is Chicago Police Department open data. The figure counts police reports, not unique victims, Amber Alerts, or convictions. LocalCrimeVault does not reclassify CPD charges. Kidnapping is 168 rows among 410,083 indexed Chicago incidents.

Does kidnapping in this data include parental disputes?

It can, if CPD assigned this primary type. Other fact patterns can also appear. The packet facts give one total, 168, not a parental subtotal. Read IUCR codes and descriptions on the table. Do not assume every row is a stranger abduction. This page does not describe individual cases.

Does a kidnapping row mean a conviction?

No. Public incident rows are reports. They can exist without an arrest or after charges change. The 168 count is report volume among 410,083 indexed Chicago incidents. Court outcomes live in other systems. The 168 count is report volume among 410,083 city incidents, not convictions.

Are exact addresses shown?

CPD's public extract uses block-level ranges and official community areas, not street-number addresses of victims. Treat geography as coarse. Use the type table and Chicago hub for aggregate location as published, not to identify people. The 168-row map uses CPD block ranges, not victim street-number addresses.