I Don't Think It's An Emergency, But...  ·  Saturday Special  ·  #002
FIELD ADVISORY — COMMS / ANIMAL CONTROL / ANYONE WITH BINOCULARS
🐅
Regional Unusual Animal Desk Special Situations Unit
Dispatch Training Package — Weekend Deployment Copy
DOCUMENT TYPE: Saturday Special / BTC Exercise
CLEARANCE: Floor Staff, Supervisors, Curious Skeptics
INCIDENT REF: WA-2012-PUY-TIGER-MAYHEM
PREPARED BY: Training & Questionable Wildlife Affairs
DATE BASIS: May 24–25, 2012
STATUS: NO TIGER LOCATED — PANIC LOCATED IMMEDIATELY
LIKELY STRIPED
Pierce County / River Road near Puyallup / Public Curiosity Event

The Puyallup Tiger, Probably or: how one giant maybe-cat became everybody's problem for an afternoon

Saturday Special  ·  Based on a real 2012 false-alarm animal sighting that became local folklore almost instantly

It is a perfectly normal day until somebody in Pierce County calls 911 and reports a large striped cat near his property. Then another caller reports the same thing. Then the search starts. Then traffic starts. Then the jokes start. Then somebody places an authentic-looking stuffed tiger on a van along River Road near Puyallup, which does not improve the situation in any measurable way.

Historically, that is more or less what happened on May 24, 2012: deputies and animal control searched for roughly two hours after callers described a tiger-like animal; the reports may have involved a bobcat, an exotic pet, or a very ambitious misunderstanding, and no tiger was found. Later prank-related calls were tied to a stuffed tiger display, while the whole story took off online and on social media.

Which makes it perfect for a weekend BTC exercise, because beneath the camp there is a real dispatch question: what do you do with a call that sounds ridiculous right up until it doesn't? Weird-animal calls, impossible-sounding caller reports, rumor contamination, public spectacle, ambiguous jurisdiction, and CAD notes that had better be crystal clear — that's the actual exercise hiding underneath the stripes.

Have fun with it. Be just serious enough to do the job right, and just self-aware enough to admit that somewhere in Washington there was a meeting where adults in uniform had to look each other in the eye and say "possible tiger" out loud, and then keep going like that was a normal sentence.

Dispatch Thought Exercise — Four Questions
Alright. Big cat energy. Now what?
Open each card when ready. There are no wrong answers. There are, however, several bad notes and at least one stuffed tiger on a van.

The exercise is not really about whether the caller is right. It's about whether the caller is reporting something specific, immediate, and potentially dangerous. In the real incident, callers described a large blond cat with black stripes, and one witness was adamant he was not looking at a coyote. Another concern was livestock safety — chickens, goats, the usual tiger buffet concerns.

So what do you want from the caller? Size comparison. Direction of travel. Distance from people, homes, or animals. Behavior. Whether it is still visible. Whether this is a glimpse, a silhouette, or a sustained observation. If the caller sounds calm but specific, that matters. If a second caller from the same area reports a similar thing, that matters more.

The point is not to become a zoologist in real time. The point is to identify whether the risk profile justifies action even if the story sounds absurd. Sometimes "that can't be right" and "we still need to send someone" are both true.

Field Note Dispatchers are not required to believe in roaming tigers. They are required to recognize when a caller is giving enough detail that dismissing it would be the riskier mistake.

This is where BTC exercises become useful again. Real life rarely hands you a clean dropdown match. In 2012, deputies and animal control both responded, and public reporting reflected uncertainty from the outset: maybe bobcat, maybe illegal exotic pet, maybe not there anymore.

Your code choice may be imperfect, but your notes cannot be. Units need the best available picture: large striped cat reported near residences, two callers, last seen near brush line, possible threat to livestock, animal control requested, law response notified. That gives responders something usable even if the code itself is a compromise.

And yes, this is one of those calls where the notes may do more work than the title. If your CAD only says ANIMAL COMPLAINT and the units discover the animal complaint has stripes, claws, and a local media following, they will remember you forever — but not in the fun way.

Field Note When the code is approximate, the notes become the call. Give responders the part they actually need to know before they roll up looking for a raccoon with confidence issues.

This is the real heart of the Saturday Special. Once a strange event becomes public spectacle, your information stream degrades immediately. In the historical case, prank-related calls were traced to a stuffed tiger placed on a van, and the online joke machine got rolling almost instantly, including the now-legendary @Puyallup_Tiger account.

That means your dispatch center has to split the signal from the noise without becoming cynical too early. New reports may still be legitimate. The caller who is breathless, laughing, or repeating something they saw on social media may not help much. But the caller who gives a fresh location, a direction of travel, and a clear visual description still might.

So the question is: what criteria do you use to separate fresh sightings from rumor echo? How do you flag likely duplicate information? How do you keep the floor from getting swallowed by the novelty of the call itself? Because once the tiger becomes a meme, the real work becomes managing contamination.

For reference, here is what the information environment looked like by the morning after — sourced directly from the tiger's own verified-by-nobody Twitter account, which had accumulated over a thousand followers overnight and showed no signs of slowing down:

@Puyallup_tiger · May 24, 2012
I've finally found Tiger Mountain. I've come a long way from Bacon Shakes, smoke shops to the river. I think ill make this my new home.
@Puyallup_tiger · May 25, 2012
@710ESPNSeattle @BrockandSalk Gutless move by the Mariners. Shed the deadweight already.
@shmulyt · May 24, 2012
To clarify; the lost tiger is different than the drunk cougar from happy hour. #BengalTiger #tigerhunt #puyallup
@RainiersLand replied · May 25, 2012
@Puyallup_tiger I'd love to see Carlos Peguero hit a bomb!

The tiger was doing media. It had sports takes. It was networking. Meanwhile, callers were still reporting sightings and your dispatch center had to figure out which of those to treat as live information and which were people who had just seen the Twitter feed and wanted to participate. That is not a hypothetical problem. That is the actual afternoon of May 24, 2012, in Pierce County, Washington.

Field Note The minute the public turns an incident into a joke, your job is not to stop the jokes. Your job is to preserve a usable stream of facts inside the joke storm. The tiger having Mariners opinions does not change whether the next caller has a real sighting.

Historically, public reporting by the next day reflected the same uneasy conclusion: no new reports, no tiger located, search ended empty-handed, but the story absolutely refused to die. Coverage also noted that local authorities were not treating the prank tiger and the original sightings as the same thing.

For dispatch operations, the handoff question is the valuable one. How do you brief the next shift on an unresolved event that may be over, may be nonsense, and may still trigger more calls all day? What do you tell call takers about screening follow-ons? What do you want supervisors to reinforce? What is the public-facing language that stays factual without sounding like the agency has either lost a tiger or lost the plot?

There is a clean version of the message: search completed, no animal located, prior report taken seriously, new credible sightings still need specific location and description information, prank reporting only makes the response harder. It is not glamorous. But then again, neither is explaining to your relief why the CAD history suddenly reads like a deleted scene from a safari movie.

Field Note Good public messaging does two things at once: it calms the room and preserves the path for real information to keep coming in.
Historical basis for this exercise

This package is grounded in public reporting from May 24–25, 2012. Multiple callers reported a tiger-like animal near Puyallup. Law enforcement and animal control searched for roughly two hours. No tiger was found. Prank-related calls later complicated the picture after someone placed a stuffed tiger on a van near River Road. Pierce County Sheriff's spokesman Ed Troyer — who has seen a lot of things in this county and described this one with appropriate diplomatic exhaustion — went on record to say the original sighting was real and separate from the van stunt. The story became local folklore almost immediately, partly because the jokes were good and partly because the tiger was apparently still on Twitter the next morning.

A note from the Weekend Wildlife Desk This exercise is funny on purpose, because it is easier to remember lessons wrapped in something weird. But the operational issues are real: caller credibility on improbable reports, imperfect CAD coding, rumor contamination, responder notification language, and supervisory handoff during unresolved public-curiosity incidents. Also real: somebody, somewhere, thought putting a stuffed tiger on a van was helping. It was not helping.