Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a22fc6a7fd26bdc9

Jump to content

Talk:Range 12 Fire

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 4 months ago by TheNuggeteer in topic GA review

This is the discussion page (the "Talk:" page) for the page named "Range 12 Fire". Please use this page to discuss the topic described in the corresponding page in the main namespace (i.e. the "Range 12 Fire" page here on English Wikipedia), or visit Help:Talk to learn more about talk pages.

Please do not delete

[edit]

User:SounderBruce, I'm curious as to why you felt it necessary to slap a huge deletion banner on the top of Range 12 Fire, less than two hours after I created the article. I'm finding more reliable sources, and I suppose we could move it over to the "Draft:" namespace (or my userspace), but I would prefer to collaborate with others who spend a lot of time on the Washington wildfire articles. They may not be interested until it is "out of draft". For the record, I found an academic paper and a US Government web page that both consider the fire notable:

  • Ba, Rui; Song, Weiguo; Li, Xiaolian; Xie, Zixi; Lo, Siuming (2019-02-06). "Integration of Multiple Spectral Indices and a Neural Network for Burned Area Mapping Based on MODIS Data". Remote Sensing. 11 (3): 326. doi:10.3390/rs11030326. ISSN 2072-4292.{{cite journal}}: CS1 maint: unflagged free DOI (link)
  • "Monitoring Impacts to Rare Plant Populations from Range 12 Fire - UNIVERSITY OF WASHINGTON". portal.nifa.usda.gov. Retrieved 2022-04-21.

It would be nice to not have potential editors dissuaded from helping by the enormous banner you placed on the article. -- RobLa (talk) 03:48, 21 April 2022 (UTC)Reply

@RobLa: It needs to be incubated in draftspace, then. The culling of new articles that don't meet notability standards is normal practice due to the amount of stubs that sit abandoned to rot for years, so some preventative measures are necessary. SounderBruce 03:58, 21 April 2022 (UTC)Reply

Nuclear disaster?

[edit]

I didn't realize that the locals (and others) were worried about a nuclear disaster, but I suppose it makes sense:

...and quoting the source (Vice (magazine)): "The raging inferno, called the Range 12 Fire, threatened to summit Washington's Rattlesnake Mountain, and creep down the other side toward the Hanford Nuclear Site, an aging nuclear production complex that sits along the Columbia River." Granted, the locals just call it the "Rattlesnake Hills" or "Rattlesnake Ridge" (which I know because I lived in the area in my youth). The ridge extends to Union Gap, Washington, but the high point of the ridge I guess is called "Rattlesnake Mountain". Regardless, it would seem as though both the Yakima and Tri-Cities news stations covered it, and I wouldn't be surprised if the Spokane television stations covered it in depth. It was a big deal for Eastern Washington. -- RobLa (talk) 04:19, 21 April 2022 (UTC)Reply

Adding this to my list of sources about the fire. -- RobLa (talk) 04:19, 21 April 2022 (UTC)Reply

GA review

[edit]

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


This review is transcluded from Talk:Range 12 Fire/GA1. The edit link for this section can be used to add comments to the review.

Nominator: Kline (talk · contribs) 20:49, 8 December 2025 (UTC)Reply

Reviewer: TheNuggeteer (talk · contribs) 06:10, 28 March 2026 (UTC)Reply


I will review this. 🍗TheNuggeteer🍗 (My "blotter") 06:10, 28 March 2026 (UTC)Reply

Lead

[edit]
  • live fire exercise, igniting the fire fire seems redundant here.
    Fixed. kline / talk / contribs 19:50, 28 March 2026 (UTC)Reply
  • due to questions of jurisdiction this is brought randomly and not further explained. I don't know what you mean by this.
    Should be better worded now. kline / talk / contribs 19:50, 28 March 2026 (UTC)Reply

Background

[edit]

Fire

[edit]

Effects and aftermath

[edit]
  • This section is very small for a fire that caused millions of dollars of costs and the burning of hundreds of thousands of acres. You need to expand this.
    I realistically cannot do much expansion for this. There was zero building damage, and the only damage caused was the damage done to the farms and grasslands in the area. I've already looked for sources far and wide but past August 2016, the only news about this fire and its damage is regarding the lawsuit. kline / talk / contribs 19:50, 28 March 2026 (UTC)Reply
  • The lawsuit was later dismissed in 2022 due to questions of jurisdiction. Why isn't there an elaboration on what questions of jurisdiction is?
    Elaborated on. kline / talk / contribs 19:50, 28 March 2026 (UTC)Reply

Spotcheck

[edit]
  • Source says fire started at 3:30 pm.
  • a tracer round from an M249 Squad Automatic Weapon had ricocheted and landed on brush, igniting the fire is not mentioned
Removed M249 SAW part, I'm going to trust the court document on what time it started over a news article from days after it started. kline / talk / contribs 19:54, 28 March 2026 (UTC)Reply
  • 13: checkY
  • 15: checkY
  • 17: checkY

@Kline: done with review. 🍗TheNuggeteer🍗 (My "blotter") 06:10, 28 March 2026 (UTC)Reply

@TheNuggeteer most issues addressed. I remember viewing a court document that had the info for what #11 is trying to claim, will have to look for it. kline / talk / contribs 19:50, 28 March 2026 (UTC)Reply
Addressed #11. kline / talk / contribs 19:54, 28 March 2026 (UTC)Reply
Great job! I will pass this. 🍗TheNuggeteer🍗 (My "blotter") 06:06, 29 March 2026 (UTC)Reply
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.