Editorial Note: This podcast debate summarizes published reporting, public records, and public-facing advocacy materials concerning North Royalton. Allegations remain allegations unless established by court findings or official determinations.
This podcast, from Accountable NoRo, details the first in a series of mini debates that tease out the details behind the current whistleblower firing sandal in North Royalton and Accountable NoRo’s grassroot efforts to recall the city’s Mayor.
Summary of the Debate
- The debate centers on the firing of North Royalton Police Officer Spencer Low, who was terminated after exposing the alteration of an arrest report.
- The original incident involved an OVI stop of an off-duty deputy chief who was found with loaded firearms and refused sobriety tests.
- Officer Low discovered that a felony firearm charge was removed from the arrest narrative without his consent, prompting him to download and leak the Sundance RMS audit logs to expose a perceived cover-up.
- The speaker defending the city administration argues that firing Low was a necessary enforcement of strict data security policies, as an officer cannot unilaterally extract and leak confidential data just because they disagree with a prosecutor’s legal assessment.
- The speaker defending the police union argues the termination was retaliatory against a whistleblower, highlighting a structural conflict of interest where the Mayor acted as both the Safety Director who fired Low and the official who commissioned the external review.
Debate Transcription
Speaker 1: Welcome to the debate. Um… What happens when a police officer catches his bosses, you know, altering an arrest record to protect another cop. And gets fired for pointing it out?
Speaker 2: Yeah. It is a massive question. And that is exactly the issue tearing apart the North Royalton administration right now.
Speaker 1: Right. So, it started with a late-night OVI stop. Uh, operating a vehicle impaired. Orange Village Deputy Chief Patrick O’Callaghan was pulled over. Found with three loaded firearms, and he completely refused sobriety tests.
Speaker 2: But, you know, we aren’t actually debating the stop itself today. We are debating what happened to the paperwork afterwards.
Speaker 1: Exactly. I will be arguing the city administration’s side here, that firing Officer Spencer Low was a necessary, uh, enforcement of strict data security policies.
Speaker 2: And I will be taking the police union’s perspective. Firing Low was… well, it was pure retaliation. I mean, he is a whistleblower who exposed an administration scrubbing records to protect one of their own.
Speaker 1: So let’s look at the actual mechanism of what happened here. Officer Low was proposed for termination, and his sergeant, Flo Ann Ribitzki, was demoted. And why? Because of the records. Right, because they executed an unauthorized release of confidential police records. The core allegation is that a felony firearm charge was improperly removed from O’Callaghan’s arrest narrative.
Speaker 2: Which is a huge deal.
Speaker 1: Yes, but let’s look at how and why that removal happened. A city prosecutor reviewed the bodycam footage and realized the felony gun charge simply could not be proven in court. It just didn’t meet the legal standard. Right, but editing a filed police report? Editing it for legal sufficiency is a standard part of the justice system. An officer cannot decide to go rogue, pull internal data, and leak it just because he personally disagrees with a prosecutor’s legal assessment, you know?
Speaker 2: I hear that. But you are completely glossing over how that edit was made. How so? Well, the union policy explicitly prohibits altering an arresting officer’s report without their consent. When the prosecutor decided to drop the charge, command staff didn’t communicate that to Low. Okay, but they just quietly went into the system and changed his narrative. That is what triggered Low to act. He recognized a massive red flag, so he pulled the Sundance RMS audit logs.
Speaker 1: Right. But let me stop you there. Pulling those logs and releasing them is a massive policy breach.
Speaker 2: Is it, though? Yes. I mean, if you disagree with an edit, you go up the chain of command. You don’t unilaterally extract the data. But he didn’t just extract random data. He preserved evidence. Think of a Sundance system like… um… like Wikipedia’s view history tab. Okay. It doesn’t just show the final edited arrest report; it tracks every single keystroke. It logs exactly who deleted a crucial sentence and when. Sure, it’s a basic audit trail. Exactly. So Low didn’t leak the raw report; he downloaded the revision history because he caught command staff scrubbing an executive’s arrest record. If he just goes up the chain of command, well, he is reporting the cover-up to the exact people executing it.
Speaker 1: I mean, even if we accept his suspicions, look at the collateral damage here. Breaching secure police databases shatters institutional integrity. Institutional integrity? Yes. We rely on independent investigations to handle suspicions of corruption. In this case, Mayor Larry Antoskiewicz commissioned an outside counsel, James J. Hofelich, to review the entire incident. Right, the outside counsel. And Hofelich cleared the command staff of any criminal wrongdoing regarding the report edit. The system worked.
Speaker 2: Did it, really? Let’s talk about the structure of that system. Because the institutional integrity was compromised from the top down. In what way? Well, the Mayor commissioned that outside counsel, yes. But in North Royalton, the Mayor also serves a dual role as the Safety Director. Which concentrates authority; I concede that point. It doesn’t just concentrate authority; it creates a chilling conflict of interest. The Mayor commissions the investigator who clears the administration. Right. The Mayor, acting as Safety Director, signs Officer Low’s termination notice. And theoretically, the Mayor is the one who hears Low’s first appeal. I see where you’re going. Yeah. The executive branch is basically acting as its own internal affairs. They weaponized a procedural records policy to fire the guy who caught them bending the rules.
Speaker 1: But the rules regarding data extraction have to be absolute. If you allow an exception every time an officer feels, you know, morally justified, you destroy the chain of custody that makes police records hold up in court. Even when the records are being altered? If any officer can rip audit logs out of Sundance because they suspect foul play, we just don’t have a functioning police department. A prosecutor made a call on legal sufficiency. Breaking protocol to contest that damages the entire legal framework.
Speaker 2: And I maintain that procedural technicalities regarding data access shouldn’t be used as a blunt instrument to silence officers reporting apparent misconduct.
Speaker 1: It is a tough balance. It really is. I mean, the audit logs wouldn’t be dangerous to the administration if there wasn’t something to hide.
Speaker 2: Well, it exposes a fascinating tension in modern policing. Balancing rigid institutional protocols with the absolute necessity of accountability is incredibly difficult. Especially when the lines of oversight blur. Right. There is a lot to unpack in these public records, and we encourage you to review the materials and draw your own conclusions. Exactly. It leaves us asking, you know, when the alarm bells ring, are we more concerned with how the digital door was forced open, or what the administration was trying to hide inside?
