Replies

How long do you think typing that information took? We won't know until later, but suffice it to say that at least a few seconds elapsed between the time of the first radio call and the time that the dispatcher finished typing the information and hit "Enter." Each of those four entries is not the time of the radio call, but the time that the information was entered into the computer.

Let's say there is a 7 second delay between call-in and entry into the computer. Wouldn't that 7 second delay apply to all the times on the dispatcher's log? I don't get how this would increase the 10 seconds time period between report of sighting and report of shooting.

That timeline has now changed.

Instead of 10 seconds between the initial dispatch and the report of gunshots fired, it is now 6 seconds.

https://local.nixle.com/alert/5081815/

Let's say there is a 7 second delay between call-in and entry into the computer. Wouldn't that 7 second delay apply to all the times on the dispatcher's log?

That is an excellent point, something I hadn't considered. What struck me about the timeline was that the first item was about the creation of the incident in response to a radio call from the deputies, and the other three items were just about radio calls from the deputies. The computer would take a certain amount of time to open a new incident number, and then all subsequent calls from that patrol car would be logged under that incident until it was over. Using my Sheriff's Office radio codes, the log might look something like this, if the deputy's ID was 340K:

1514:15 340K 647A [suspicious person] MOORLAND/W ROBLES
1514:19 340K 905 [urgent assistance needed]
1514:25 340K 998 [deputy involved in shooting]
1514:41 340K NEED AMBULANCE [there's no radio code for this]

So it seems to me that it would take a few seconds more to type in the street names and have the computer create the incident than it would to type in the three-digit radio codes. I will be interested to see if I'm right when the actual radio log comes out.