Alert archive / Texas / Freeze Warnings in 2008
Freeze Warning 3, NWS Brownsville, TX
NWS Brownsville, TX issued this freeze warning at Jan 19, 2008, 8:34 PM CST for Brooks County, Jim Hogg County, Zapata County, Texas. It took effect at Jan 20, 2008, 3:00 AM CST. It was in force for 5 hr. No storm report in the archive falls inside the area while it was in force.
The area
The counties it named.
The facts
- Issued
- Jan 19, 2008, 8:34 PM CST (02:34 UTC)
- In effect from
- Jan 20, 2008, 3:00 AM CST
- Expired
- Jan 20, 2008, 8:00 AM CST
- In force
- 5 hr
- Issued by
- NWS Brownsville, TX
Counties Brooks County, TX, Jim Hogg County, TX, Zapata County, TX
The radar
The Corpus Christi radar (KCRP), 144 km from the middle of the area, began a volume at 02:33 UTC, the scan nearest the moment this went out.
Open the radar archive at this moment
The archived warnings, watches and discussions in force at that minute are drawn over the scan, this one among them.
What forecasters said that day
The local office's own words before this freeze warning went out, as it sent them, from the Iowa Environmental Mesonet's archive of National Weather Service text.
NWS Brownsville, TX wrote its last area forecast discussion before this freeze warning went out at Jan 19, 8:17 PM CST, 17 minutes earlier.
Area forecast discussion, Jan 19, 8:17 PM CST, 17 minutes before
<!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>Hazardous weather outlook, Jan 19, 8:32 PM CST, 2 minutes before
<!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>Nearby
Sources
The product and its follow-ups from the Iowa Environmental Mesonet's archive of National Weather Service and Storm Prediction Center text; radar from the NEXRAD Level II archive.