STARE OPSThe Kansas City Stare — operators only
STARE OPSwire console
Monitor
Overview Wire sources Stare analytics Stories Storage
Coverage
Editor's desk Newsroom Day Book Futures Crime monitor Coverage study KCPD data Crime Index Judiciary
Controls
Intel / AIIS Sources Publishing Engine
kcstare.com ↗

Judiciary

The Kansas City judicial system

internal · nothing here publishes

Kansas City straddles a state line, so it is governed by two of everything. A KC matter lands in W.D. Missouri or D. Kansas depending on which side of State Line Road it happened, appeals run to the Eighth Circuit either way, and the state courts run on separate tracks entirely. This module maps that structure and the people inside it. Judges are public officials recorded in official capacity — appointment, tenure and rating are public record, and nothing here asserts anything about a decision.

Court structure

who answers to whom

The bench

judges on record, by court and seat

Judges by court

By position type

Appointments by year

Every recorded position start. Peaks are administrations seating judges, not activity.

Longest-serving, currently seated

years since first recorded seat

Composition

recorded attributes, not explanations

Read this before reading the chart. Political affiliation here is CourtListener's own coding, largely derived from who appointed the judge. It is a recorded attribute with a stated source. It is not a motive, and this corpus never uses it to explain a ruling. ABA ratings are the American Bar Association's, given at nomination.

Recorded political affiliation

ABA rating at nomination

Law schools (JD)

Where the bench that decides Kansas City cases was trained.

Financial disclosures

insurance-gated · counts only, never holdings
What this is and is not. Federal judges file annual financial disclosures. This module records that a filing exists and what it contains by count, plus a link to the PDF. It does not restate any holding as fact, and neither should you without reading the source. Three reasons, all real:
· values are reported as coded ranges, never dollar amounts;
· some rows are redacted at source;
· CourtListener flags rows whose values it inferred rather than read.
Every record here carries the insurance-bright-line gate. Nothing publishes without bound media-liability insurance and a per-piece ratification.

Filings on record, by judge

Filings by year

Cases in the corpus

By kind

By court

Filings by year

Charge verification

A criminal case ingested from docket search carries parties and dates but not counts. Verified means the counts came from the court's own criminal-count records. The gap is not an error — it is the honest state, and RECAP coverage is contributor-driven.

Repeat players — counsel of record

zero API calls · straight from stored dockets

Who actually appears in Kansas City federal court. FPD is the Federal Public Defender — its rank is a measure of how much KC federal criminal defense is publicly funded, which is a story in itself. Counsel appear here because they are on a public docket; nothing about a lawyer's clients is a claim about the lawyer.

Full table with dockets

Presiding judges in our own cases

from the corpus, not the roster

Opinions

surfaced by search — read before describing

A search hit is how an opinion was found, never a characterization of what it holds. Read it before writing a word about it.

Method and limits

what this cannot tell you

The roster is CourtListener's, not a court's. It is compiled by the Free Law Project from FJC data, court sites and public sources. Good, and not the same as an official roster.
Historical and current judges are mixed in the totals; "seated" counts only positions with no termination date.
State trial courts are not here. Jackson County's 16th Circuit and Wyandotte County District are where most KC criminal cases actually go, and Missouri's Case.net is not machine-readable. That is the single biggest hole in this module.
Bankruptcy is a financial event, never an allegation of wrongdoing against anyone. The adjacency rule applies hard: no business named near negative framing.
Every request is cached to disk so a rebuild costs nothing; the live-call count prints on every fetch run.