Flood, Creek
- When
- October 9, 8:00 PM CST to October 10, 5:00 AM CST
- Where
- Creek forecast zone
- Reported by
- OFFICIAL NWS OBS.
- Coordinates
- 35.903, -96.371 (the zone’s center; the record gives no point)
Polecat Creek near Sapulpa rose above its flood stage of 21 feet during the afternoon of October 9 after heavy rain in excess of 3 inches feel the night before. 4 feet that evening before falling below its flood stage during the pre-dawn hours of the 10th.
Every event with a place to put it; 1 filed by county or forecast zone are drawn at its center, in a lighter ring. Tap one for its entry below.
Deaths and injuries are direct and indirect together, as the offices filed them. Damage is property and crops in the dollars of the year, not adjusted for inflation, and only where an office estimated it.
The episode as NWS TSA wrote it up.
Polecat Creek near Sapulpa rose above its flood stage of 21 feet during the afternoon of October 9 after heavy rain in excess of 3 inches feel the night before. The river crested at 22.4 feet that evening before falling below its flood stage during the pre-dawn hours of the 10th.
The local office's own words before the first event, as it sent them, from the Iowa Environmental Mesonet's archive of National Weather Service text.
NWS Tulsa, OK wrote its last area forecast discussion before the first event at Oct 9, 1:17 PM CST, 6 hours 43 minutes earlier.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Service Notice</title>
<link rel="stylesheet" href="index.css">
</head>
<body>
<main class="wrap">
<section class="card" role="status" aria-live="polite">
<div class="status" id="status">Temporary Notice</div>
<h1 id="headline">This service is currently unavailable.</h1>
<p id="message1">
The site you requested is temporarily down for maintenance or an unexpected outage.
</p>
<p id="message2">
Please try again in a few minutes.
</p>
<p class="small" id="detail">
If you are an administrator, restore upstream service and remove the redirect/fallback rule when normal operations resume.
</p>
</section>
</main>
<script src="index.js"></script>
</body>
</html><!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Service Notice</title>
<link rel="stylesheet" href="index.css">
</head>
<body>
<main class="wrap">
<section class="card" role="status" aria-live="polite">
<div class="status" id="status">Temporary Notice</div>
<h1 id="headline">This service is currently unavailable.</h1>
<p id="message1">
The site you requested is temporarily down for maintenance or an unexpected outage.
</p>
<p id="message2">
Please try again in a few minutes.
</p>
<p class="small" id="detail">
If you are an administrator, restore upstream service and remove the redirect/fallback rule when normal operations resume.
</p>
</section>
</main>
<script src="index.js"></script>
</body>
</html>The national radar mosaic for the moment the first event began.
1 flood. Local standard time, as filed.
After NWS Directive 10-1605, the rules offices file Storm Data by.
Every storm in Oklahoma in 2003Every state in 2003This day in weather historyWarnings in Oklahoma, October 2003
NOAA National Centers for Environmental Information, Storm Events Database, compiled from the National Weather Service’s monthly Storm Data. Complete through 2026-06; NCEI adds each month about 75 days after it ends and revises past years a few times a year. Rebuilt 2026-09-30. Each event’s entry at NCEI: 5371267.