Lincoln National Forest, Crooked Creek Fire Update June 27

Crooked Creek Fire transitioning to a Type IV organization

Alamogordo, NM (June 27, 2018) – Tomorrow, Thursday June 28, fire managers on the Lincoln National Forest are planning to transfer command of the Crooked Creek Fire to a smaller local organization led by Incident Commander Joe Kimble. All forward progress of the fire has been successfully halted and the containment is now being reported at 70%. The fire footprint remains at 6800 acres. Several resources are being released from the Crooked Creek incident to be available to provide protection in their respective jurisdictions.

The remaining Type 4 organization will be “right sized” for the reduced complexity of the incident. Crews will continue to improve fire control lines, mop up smoldering materials, and perform suppression repair activities while patrolling the fireline for any flareups that can still occur along the fire’s edge.

Yesterday there was lightning activity throughout the Lincoln National Forest. Resources from the Crooked Creek Fire are available to assist with  suppression efforts of any new fire starts alongside forest personnel.

A strong chance of afternoon thunderstorms exists over the next several days as monsoonal moisture moves into the region bringing with it an increasing chance of rain.

Smoke may continue to affect the local area.  Smoke-sensitive individuals and people with respiratory or heart disease are encouraged to take precautionary measures. Information on air quality and protecting your health can be found online at the NM Department of Health’s website at

Jurisdiction: Guadalupe Ranger District, Lincoln National Forest

Containment:  70%

Size: Approximately 6,800 acres

Cause:  Lightning

Date/Time Detected: June 15, 2018, 11:16 am

Location: Crooked Canyon

Lat/Long: 32 30.462, -105 1.590

Firefighting Resources:  151 total personnel

Values at Risk: None

Fuel Type:  Grass with open Piñon-Juniper

PIO: Bill Morse, 602-529-5924

Comments are closed.

%d bloggers like this: