Swift Response Contained Agricultural Vehicle Fire Near Thrasher Road
Statistics
Narrative
Elk Creek Township, PA – This afternoon, shortly after 3:30 PM, first responders from the Cranesville Volunteer Fire Department were dispatched to a reported combine fire, in a field, near 9800 Thrasher Road. Within four minutes of the initial dispatch, Engine 602, Engine 604, and Utility 609 were en route to the scene. While the units were still responding, 64L1, who was in the vicinity, confirmed that the combine was fully engulfed in flames and positioned approximately 200-250 yards off the roadway within the field.
Upon arrival, Chief 600 took command of the incident and directed the suppression efforts. Utility 609, a brush truck designed for off-road maneuverability as opposed to a fire engine, made its way into the field to begin fire suppression operations. After assessing field conditions and confirming they were firm enough for transit, Engine 602 entered the field to support operations by providing additional water to refill Utility 609 and deploying an extra handline to enhance fire suppression. Engine 604 remained at the road.
Through a coordinated effort, crews were able to contain the fire, and Chief 600 reported the fire to be under control at approximately 3:54 PM, roughly 20 minutes after the initial dispatch. The swift response and effective teamwork of the Cranesville Volunteer Fire Department units prevented the fire from spreading into the field and minimized further damage to the surrounding area. Fortunately, no injuries were reported during the incident. The cause of the fire remains under investigation.
Overall, this incident highlights the importance of rapid response and strong coordination in successfully managing rural fire scenarios, especially when dealing with challenging off-road access and heavy equipment fires.
Response Timeline
Disclaimer: The timeline provided is for illustrative purposes only and may not be entirely accurate due to potential errors in recorded transmissions. Consequently, this timeline should not be used to evaluate responses to incidents. If you notice a significant discrepancy, please contact [email protected].