<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
>

<channel>
	<title>The Company Officer &#187; Crew Management</title>
	<atom:link href="http://thecompanyofficer.com/category/crew-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecompanyofficer.com</link>
	<description>Sharing in-depth, quality information for today&#039;s Company Officer</description>
	<lastBuildDate>Tue, 17 Apr 2012 02:06:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<!-- podcast_generator="Blubrry PowerPress/3.0.1" -->
	<itunes:summary>Sharing in-depth, quality information for today&#039;s Company Officer</itunes:summary>
	<itunes:author>The Company Officer</itunes:author>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://thecompanyofficer.com/wp-content/plugins/powerpress/itunes_default.jpg" />
	<itunes:subtitle>Sharing in-depth, quality information for today&#039;s Company Officer</itunes:subtitle>
	<image>
		<title>The Company Officer &#187; Crew Management</title>
		<url>http://thecompanyofficer.com/wp-content/plugins/powerpress/rss_default.jpg</url>
		<link>http://thecompanyofficer.com/category/crew-management/</link>
	</image>
		<item>
		<title>New Sensor System Tracks Firefighters Where GPS Fails</title>
		<link>http://thecompanyofficer.com/2011/12/06/new-sensor-system-tracks-firefighters-where-gps-fails/</link>
		<comments>http://thecompanyofficer.com/2011/12/06/new-sensor-system-tracks-firefighters-where-gps-fails/#comments</comments>
		<pubDate>Wed, 07 Dec 2011 02:05:27 +0000</pubDate>
		<dc:creator>Christopher Naum</dc:creator>
				<category><![CDATA[building construction]]></category>
		<category><![CDATA[Buildingsonfire.com]]></category>
		<category><![CDATA[christopher naum]]></category>
		<category><![CDATA[Crew Management]]></category>
		<category><![CDATA[Fire Fighter Safety]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Crew management]]></category>
		<category><![CDATA[Firefighter Accountabilty Location System]]></category>
		<category><![CDATA[Firefighter Safety]]></category>
		<category><![CDATA[Firefighting GPS Systems]]></category>
		<category><![CDATA[Firefighting Search and Rescue]]></category>
		<category><![CDATA[National Science Foundation (NSF)]]></category>
		<category><![CDATA[Sensor System Tracks Firefighters]]></category>
		<category><![CDATA[Sentrix Tracking Unit]]></category>
		<category><![CDATA[thecompanyofficer.com]]></category>
		<category><![CDATA[TRX Systems]]></category>

		<guid isPermaLink="false">http://thecompanyofficer.com/?p=2103</guid>
		<description><![CDATA[New Sensor System Tracks Firefighters Where GPS Fails. Portable device locates missing firefighters--saves time and maybe lives
]]></description>
			<content:encoded><![CDATA[<p><object width="470" height="264" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="src" value="http://www.nsf.gov/js/video/player.swf" /><param name="wmode" value="transparent" /><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="flashvars" value="file=science_nation/SN108firefightertracker.flv&amp;streamer=rtmp://nsfgov.flash.internapcdn.net/nsfgov_vitalstream_com/_definst_/video/&amp;image=http://www.nsf.gov/news/special_reports/science_nation/covers/images/sn_cover.jpg&amp;smoothing=true&amp;controlbar=over" /><embed width="470" height="264" type="application/x-shockwave-flash" src="http://www.nsf.gov/js/video/player.swf" wmode="transparent" allowfullscreen="true" allowscriptaccess="always" flashvars="file=science_nation/SN108firefightertracker.flv&amp;streamer=rtmp://nsfgov.flash.internapcdn.net/nsfgov_vitalstream_com/_definst_/video/&amp;image=http://www.nsf.gov/news/special_reports/science_nation/covers/images/sn_cover.jpg&amp;smoothing=true&amp;controlbar=over" /></object></p>
<p>New Sensor System Tracks Firefighters Where GPS Fails</p>
<div><em>Portable device locates missing firefighters&#8211;saves time and maybe lives</em></div>
<p>Firefighter Ray Hodgson hits the talk button on his walkie-talkie: &#8220;I have fire showing, possibility of a rescue on the third floor. Engine 35, initiate a rescue group. Also back him up with a hose line.&#8221;</p>
<p>A fire has been set in a three story building at the Maryland Fire and Rescue Institute, where firefighters hone their skills and test equipment. In this case they&#8217;re testing a device they hope will save firefighters&#8217; lives. Everyone taking part in the drill knows how difficult and dangerous it is to locate a missing firefighter in a smoky inferno.</p>
<p>&#8220;When you go into a burning building, you don&#8217;t really see anything. You can&#8217;t see your hand in front of your face; you&#8217;re going on instincts. It&#8217;s almost a surreal experience,&#8221; says Matt Leonard, a firefighter in the District of Columbia and a deputy chief in Prince George&#8217;s County, Md.</p>
<p>&#8220;We&#8217;ve had instances where we&#8217;ve lost firefighters in a building and had a hard time finding them. It&#8217;s very frustrating,&#8221; says Hodgeson, a firefighter for 44 years. He knows firsthand the sinking feeling of hearing the dreaded words that one of his colleagues is missing. That&#8217;s why this team of experienced firefighters is taking time to test out a new type of sensor that can track their whereabouts deep inside buildings, where standard GPS units often don&#8217;t work.</p>
<p>&#8220;This has been a need for a long time,&#8221; says Carol Politi, CEO of TRX Systems, the company developing the sensor. &#8220;Sept. 11 was widely publicized and there was not even an understanding of whether certain firefighters were actually in the buildings at the time of that tragedy.&#8221;</p>
<p>With support from the National Science Foundation (NSF), electrical engineer Politi and her team at TRX Systems are developing a portable device called the Sentrix Tracking Unit. It straps on like a belt and consists of a suite of sensors. &#8220;The sensors include accelerometers and gyroscopes. Those are sensors similar to what you have in your Wii for example&#8211;pressure sensors ranging sensors. It allows us to create a picture of what a user has done,&#8221; says Politi.</p>
<p>&#8220;The sensors monitor the movement of the user,&#8221; explains Ben Funk, vice president of Engineering at TRX. &#8220;So when the user moves forward or backwards, left or right, it determines how far a person moved in each direction.&#8221;</p>
<p>During the fire drill the sensors create a map of the building as the firefighters move through the smoke.</p>
<p>&#8220;Twenty-eight-nineteen, we have a mayday on the third floor from the rescue group,&#8221; Hodgson relays. &#8220;Initiate a search.&#8221;</p>
<p>During the demonstration, Hodgson assumes the role as incident commander as the others move through the burning building in teams of two. One of the firefighters, outfitted with a sensor, crawls through the smoke and purposely gets lost. The Sentrix Tracking Unit maps his location at every twist and turn, sending the data to a nearby base station&#8211;in this case, the incident commander&#8217;s laptop. The system can transmit via a variety of different radio-waves to accommodate different receivers.</p>
<p>&#8220;The tracker advises they&#8217;re on the back Delta Charlie quadrant in the back bedroom,&#8221; says Hodgson into his walkie-talkie.</p>
<p>In minutes the firefighter is located by a member of his team.</p>
<div>
<p><strong>For the Full Article From the National Science Foundation Web Site, <a href="http://www.nsf.gov/news/special_reports/science_nation/firefightertracker.jsp">HERE</a> All rights reserved </strong></p>
<p>Wriiten by: <a href="http://www.nsf.gov/news/special_reports/science_nation/producers/obrien.jsp">Miles O&#8217;Brien</a>, Science Nation Correspondent and <a title="Meet the Producer Ann Kellan" href="http://www.nsf.gov/news/special_reports/science_nation/producers/kellan.jsp">Ann Kellan</a>, Science Nation Producer</p>
<div>
<div><a href="http://nsfgov.http.internapcdn.net/nsfgov_vitalstream_com/science_nation/SN108firefightertracker_long.mov">Download video</a></div>
</div>
<div>
<div> </div>
<div>
<p><a href="javascript:openW('popup/firefightertracker/horsefire.jsp','horsefire',550,675,'scrollbars=1','center')"><img src="http://www.nsf.gov/news/special_reports/science_nation/images/firefightertracker/horsefire190.jpg" alt="view of smoke from wildfire" width="190" height="143" /></a></p>
<div><a href="javascript:openW('popup/firefightertracker/horsefire.jsp','horsefire',550,675,'scrollbars=1','center')">Enlarge image</a></div>
<div> </div>
<div>Within 24 hours of the eruption of a wildfire in the Cleveland National Forest near San Diego, communications expert Hans-Werner Braun and his collaborators from the NSF-supported High Performance Wireless Research and Education Network (HPWREN) were on the scene. The HPWREN researchers set up hardware at key points to allow firefighters in remote locations to communicate by a wireless link from the wildfire incident command post to the Internet. Find out more in this <a href="http://www.nsf.gov/news/news_summ.jsp?cntn_id=107121">news release</a>.<br />
<em>Credit: HPWREN</em></div>
<div> </div>
<p><a href="javascript:openW('popup/firefightertracker/penny.jsp','penny',550,700,'scrollbars=1','center')"><img src="http://www.nsf.gov/news/special_reports/science_nation/images/firefightertracker/penny190.jpg" alt="a penny shows the scale of a Golem Dust mote" width="190" height="178" /></a></p>
<div><a href="javascript:openW('popup/firefightertracker/penny.jsp','penny',550,700,'scrollbars=1','center')">Enlarge image</a></div>
<div> </div>
<div>A sensor is any device that can take a stimulus, such as heat, light, magnetism, or exposure to a particular chemical, and convert it to a signal. While the concept of sensors is nothing new, the technology of sensors is undergoing a rapid transformation. Learn more in this <a href="http://www.nsf.gov/news/special_reports/sensor/convergence.jsp">Special Report</a>.<br />
<em>Credit: Brett Warneke, Kris S.J. Pister, Berkeley Sensor &amp; Actuator Center, University of California, Berkeley</em></div>
<div><em></em> </div>
</div>
</div>
<div>Related Links</div>
<div> </div>
<div>
<div><a href="http://www.nsf.gov/eng/iip/about.jsp">Industrial Innovation and Partnerships Division (IIP) </a></div>
<div>The Division of Industrial Innovation and Partnerships (IIP) of the Directorate for Engineering serves the entire foundation by fostering partnerships to advance technological innovation, and plays an important role in the public-private innovation partnership enterprise. The focus of IIP is to successfully invest in engineering research and innovation by leveraging federal, small business, industrial, university, state and community colleges resources.</div>
<div> </div>
<div><a href="http://www.nsf.gov/news/news_summ.jsp?cntn_id=115762">Radio Waves &#8216;See&#8217; Through Walls</a></div>
<div>University of Utah engineers showed that a wireless network of radio transmitters can track people moving behind solid walls. The system could help police, firefighters and others nab intruders, and also rescue hostages, fire victims and elderly people who fall in their homes.</div>
</div>
<div id="centercol"> </div>
</div>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://thecompanyofficer.com/2011/12/06/new-sensor-system-tracks-firefighters-where-gps-fails/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://thecompanyofficer.com/2011/12/06/new-sensor-system-tracks-firefighters-where-gps-fails/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Checking your Compass</title>
		<link>http://thecompanyofficer.com/2011/10/21/checking-your-compass/</link>
		<comments>http://thecompanyofficer.com/2011/10/21/checking-your-compass/#comments</comments>
		<pubDate>Fri, 21 Oct 2011 13:17:57 +0000</pubDate>
		<dc:creator>Christopher Naum</dc:creator>
				<category><![CDATA[Buildingsonfire.com]]></category>
		<category><![CDATA[christopher naum]]></category>
		<category><![CDATA[command-leadership]]></category>
		<category><![CDATA[Commandsafety.com]]></category>
		<category><![CDATA[company officer]]></category>
		<category><![CDATA[Crew Management]]></category>
		<category><![CDATA[Fire Fighter Safety]]></category>
		<category><![CDATA[firefighting-operations]]></category>
		<category><![CDATA[KSA]]></category>
		<category><![CDATA[Leaderhip]]></category>
		<category><![CDATA[Adaptive Fireground Management]]></category>
		<category><![CDATA[Building Construction for the Fire Service]]></category>
		<category><![CDATA[Building Construction Training]]></category>
		<category><![CDATA[Building Knowledge=Firefighter Safety]]></category>
		<category><![CDATA[Christopher Naum. Thecompanyofficer.com]]></category>
		<category><![CDATA[Command copression]]></category>
		<category><![CDATA[community risk]]></category>
		<category><![CDATA[company officer training]]></category>
		<category><![CDATA[Firefighter Safety]]></category>
		<category><![CDATA[Firefighting operations]]></category>
		<category><![CDATA[fireground tactics]]></category>
		<category><![CDATA[incident command]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[legacy construcion]]></category>
		<category><![CDATA[operational safety]]></category>
		<category><![CDATA[Predicative Strategic Process]]></category>
		<category><![CDATA[Tactical Entertainment]]></category>
		<category><![CDATA[Tactical Patience]]></category>
		<category><![CDATA[thecompanyofficer.com]]></category>
		<category><![CDATA[training]]></category>

		<guid isPermaLink="false">http://thecompanyofficer.com/?p=1992</guid>
		<description><![CDATA[As a Company Officer; have you checked your compass lately? Do you know where you are?]]></description>
			<content:encoded><![CDATA[<p><a href="http://thecompanyofficer.com/files/2011/10/6-15-2009-7-44-39-PM.jpg"><img class="aligncenter size-medium wp-image-1999" title="6-15-2009 7-44-39 PM" src="http://thecompanyofficer.com/files/2011/10/6-15-2009-7-44-39-PM-300x224.jpg" alt="" width="300" height="224" /></a>How much thought and efforts do you place on looking beyond the suggested &#8220;routiness&#8221; of your response operations? You know, the redundancy, routiness and frequency of typical calls you run, the types of fire you engage in and the manner in which your company interfaces with the balance of the alarm response when working a job or multiple alarm operation. We talk about nothing being routine, yet we have a pace, a rhythm and regularity, a consistency that is predicatable yet, uncertain; expected but when presented; off-guard.</p>
<p>When things go wrong, they can go wrong at an escalating rate that may at times not be apparent. Think about the issues that affect Errors, Omissions, Unknown or Unrecognized Building Profile or Construction, Wrong Tactics, Lack of Resources, Dysfunctional Command, Inadequate skills, High Risk-No Value, Situational Awareness failure, Command Compression, Tactical Entertainment…</p>
<p>From a company level, what are your concerns related to the routiness or regularity of your operations?</p>
<p>How would you relate to the fact that: “It’s NOT always business as usual”.</p>
<p>The complexities of the modern and evolving fireground demand an understanding of the building-occupancy relationships and the integral functionals related to;</p>
<ul>
<li>construction and systems,</li>
<li>predictive occupacny performance</li>
<li>occupancy profile risk</li>
<li>fire dynamics and fire behavior,</li>
<li>risk respect</li>
<li>firefighting capabilities</li>
<li>safety consciousness</li>
<li>situational awareness</li>
<li>tactical patience</li>
<li>fluid and adaptive incident command management,</li>
<li>diligent company level supervision and</li>
<li>task level company competencies,</li>
<li>exceptional individual skills</li>
</ul>
<p>Without the sum of these; You are derelict and negligent and <em>“not “everyone may be going home”.</em></p>
<p><em>How much knowledge and formal training have you had as a Commanding Officer or Company Officer on Building Construction?</em></p>
<p><em></em> </p>
<p style="text-align: center;"><a href="http://thecompanyofficer.com/files/2011/10/6-15-2009-7-39-58-PM.jpg"><img class="aligncenter size-full wp-image-2000" title="6-15-2009 7-39-58 PM" src="http://thecompanyofficer.com/files/2011/10/6-15-2009-7-39-58-PM.jpg" alt="" width="550" height="412" /></a></p>
<p>Have any clue on the performance of <a href="http://thekitchentable.firerescue1.com/2009/08/structural-stability-of-engineered.html">Engineered Structural Systems</a>….?</p>
<p>Are your strategic plans and tactics aligned with <a href="http://commandsafety.blogspot.com/2009/08/its-occupancy-risk-not-occupancy-type.html">Occupancy Risk </a>and projected Building Performance, company capabilities and the fire dynamics?</p>
<p><a href="http://thecompanyofficer.com/files/2011/10/4-16-2011-10-33-29-AM.jpg"><img class="aligncenter size-medium wp-image-2006" title="4-16-2011 10-33-29 AM" src="http://thecompanyofficer.com/files/2011/10/4-16-2011-10-33-29-AM-300x221.jpg" alt="" width="300" height="221" /></a></p>
<p>There’s a lot that can be gleaned from your surroundings on any given day. We sometimes take for granted the subtle changes that are happening all around us as we take care of business on our rounds, runs and calls. We tend to focus in on the immediacy of the events that are happening in front of us that demand our attention but fail to take a look around to pick up on information, data and insights that can help us on that next run or down the road in the future.</p>
<p><a href="http://thecompanyofficer.com/files/2011/10/DSC_0706.jpg"><img class="aligncenter size-medium wp-image-1996" title="DSC_0706" src="http://thecompanyofficer.com/files/2011/10/DSC_0706-300x201.jpg" alt="" width="300" height="201" /></a></p>
<p>Take a look at the construction that might be going up in your areas. I’m certain you’re paying close attention to what’s happening in your first-due, but what about that third-due area, that neighboring jurisdiction or the mutual-aid area that you occasionally run in to? When you’re on that next EMS run or an investigation of an odor or alarm bells service call, take a few extra minutes to walk through the occupancy. Conduct your own mini company level pre-plan.</p>
<p>Look at the layout, features, access and construction features. If you have a chance, verify the <a href="http://commandsafety.blogspot.com/2009/08/structural-stability-of-engineered.html">structural support systems </a>employed by the building for the floor and roof <a href="http://commandsafety.blogspot.com/2009/08/new-lexicon-and-challenges.html">systems</a>. If you have time, take the company on a quick site visit to that building that’s <a href="http://commandsafety.blogspot.com/2009/07/buildings-under-construction.html">under construction </a>or the renovations that are again underway in that commercial or business occupancy around the corner from quarters.</p>
<p style="text-align: center;"> <a href="http://thecompanyofficer.com/files/2011/10/10-21-2011-9-07-25-AM1.jpg"><img class="aligncenter size-full wp-image-2004" title="10-21-2011 9-07-25 AM" src="http://thecompanyofficer.com/files/2011/10/10-21-2011-9-07-25-AM1.jpg" alt="" width="350" height="360" /></a></p>
<p>These continuing challenging economic times places a great deal of influence on what’s being built, how it might be constructed, the manner in which a building may be operational one day, <a href="http://commandsafety.blogspot.com/2009/07/firefighter-safety-at-vacant-structures.html">vacant </a>the other and under renovation the next. Sometimes these transformations occur literally overnight.</p>
<p>Take a good look around, this is your town…your district, your response area. <a href="http://www.firerescue1.com/fire-news/503121-building-construction-command-risk-management-and-firefighter-safety/">Know your buildings</a>, understand their performance profiles, and assess the <a href="http://commandsafety.blogspot.com/2009/08/predictability.html">predictability of performance.</a> Remember; <a href="http://www.firerescue1.com/fire-attack/articles/503322-Firefighting-and-the-Built-Environment/">Building Knowledge = Firefighter Safety. </a></p>
<p><strong><em>If you think these factors are not important OR you dismiss them as being non-material-think again; </em></strong></p>
<p><strong><em>Do you know where you&#8217;re going? Have you checked your compass lately to see if you are still on the right track?</em></strong></p>
<p><strong><em>They are Mission Critical for firefighter safety and incident mitigation</em></strong></p>
<p><object width="420" height="315" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/aDNPhq5ggoE?version=3&amp;hl=en_US&amp;rel=0" /><param name="allowfullscreen" value="true" /><embed width="420" height="315" type="application/x-shockwave-flash" src="http://www.youtube.com/v/aDNPhq5ggoE?version=3&amp;hl=en_US&amp;rel=0" allowFullScreen="true" allowscriptaccess="always" allowfullscreen="true" /></object></p>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://thecompanyofficer.com/2011/10/21/checking-your-compass/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://thecompanyofficer.com/2011/10/21/checking-your-compass/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Deployment Decisions: Defining Operations on the First-Due</title>
		<link>http://thecompanyofficer.com/2011/08/09/deployment-decisions-defining-operations-on-the-first-due/</link>
		<comments>http://thecompanyofficer.com/2011/08/09/deployment-decisions-defining-operations-on-the-first-due/#comments</comments>
		<pubDate>Tue, 09 Aug 2011 14:14:47 +0000</pubDate>
		<dc:creator>Christopher Naum</dc:creator>
				<category><![CDATA[building construction]]></category>
		<category><![CDATA[Buildingsonfire.com]]></category>
		<category><![CDATA[christopher naum]]></category>
		<category><![CDATA[command-leadership]]></category>
		<category><![CDATA[Commandsafety.com]]></category>
		<category><![CDATA[company officer]]></category>
		<category><![CDATA[Crew Integrity]]></category>
		<category><![CDATA[Crew Management]]></category>
		<category><![CDATA[Fire Fighting]]></category>
		<category><![CDATA[firefighting-operations]]></category>
		<category><![CDATA[KSA]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[Command Compression]]></category>
		<category><![CDATA[command officer]]></category>
		<category><![CDATA[decision-making]]></category>
		<category><![CDATA[defining operations on the first-due]]></category>
		<category><![CDATA[extreme fire behavior]]></category>
		<category><![CDATA[fire behavior]]></category>
		<category><![CDATA[fire ground decision-making]]></category>
		<category><![CDATA[Firefighter Safety]]></category>
		<category><![CDATA[firefighting tactics]]></category>
		<category><![CDATA[naturalistic decision making for the fire service]]></category>
		<category><![CDATA[occupancy risk]]></category>
		<category><![CDATA[occupancy type]]></category>
		<category><![CDATA[operational integrity command performance]]></category>
		<category><![CDATA[RPDM]]></category>
		<category><![CDATA[Tactical Patience]]></category>
		<category><![CDATA[thecompanyofficer.com]]></category>

		<guid isPermaLink="false">http://thecompanyofficer.com/?p=1823</guid>
		<description><![CDATA[
First-due company operations are influenced by a number of parameters and factors; some deliberate and dictated, others prescribed and prearranged and yet others subjective, biased, predisposed or at times accidental, [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><a href="http://thecompanyofficer.com/files/2011/08/untitled.bmp"><img class="aligncenter size-full wp-image-1824" title="untitled" src="http://thecompanyofficer.com/files/2011/08/untitled.bmp" alt="" width="403" height="267" /></a></p>
<p>First-due company operations are influenced by a number of parameters and factors; some deliberate and dictated, others prescribed and prearranged and yet others subjective, biased, predisposed or at times accidental, casual and emotional. For many of you riding the seat or arriving assuming command; you understand the connotations and implications I&#8217;m making here.</p>
<p>Here’s an excellent discussion and debate point to bring up, when time permits today or this evening with your company or personnel; one that leads to a multitude of viewpoints, opinions and divisions.</p>
<p>On the first-due; what are the three or four key parameters when confronted with arrival indications of a fire within a structure that define your deployment and transition into operations?</p>
<p>Now, before everyone gets worked up; we all realize there are numerous variables affecting key decision-points that must be recognized, imputed, synthesized , analyzed and decisions made, assignments formulated and the task deployed; this list can be long &#8211; very long.</p>
<p>However, giving a building and occupancy with indications of a fire within, what has your experience provided you with the KEY influencing parameters? Are there key factors, or are there &#8220;lists&#8221; of factors based upon yet another &#8220;list&#8221; of conditions. The question is rhetorical the answeres are not.</p>
<p>Is it occupancy type, occupancy risk, fire behavior or fire dynamics, time, risk, communicated information, past performance factors (experience), presumed or known life hazards, predicated building or system performance, crew KSA sets or other factors, etc? Does naturalistic or RPDM decision-making influence; is the deployment tactically driven or predisposed by SOP, SOG or personal attributes and biases? Safety Conscious or aggressively driven? You get the picture&#8230;..</p>
<p>Try to distill them down to three or four mission critical key issues (if you can). This is a great exercise to see what everyone else considers the key factors to be or should be when deploying and  going into operations; sometimes it’s more complex than just “pulling the line” or getting in….</p>
<p>Take the time to use some critical thinking and don’t be subjective….think about the responses and ask why?</p>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://thecompanyofficer.com/2011/08/09/deployment-decisions-defining-operations-on-the-first-due/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://thecompanyofficer.com/2011/08/09/deployment-decisions-defining-operations-on-the-first-due/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Near-Miss Report of the Week</title>
		<link>http://thecompanyofficer.com/2011/07/15/near-miss-report-of-the-week/</link>
		<comments>http://thecompanyofficer.com/2011/07/15/near-miss-report-of-the-week/#comments</comments>
		<pubDate>Fri, 15 Jul 2011 17:38:31 +0000</pubDate>
		<dc:creator>Christopher Naum</dc:creator>
				<category><![CDATA[Buildingsonfire.com]]></category>
		<category><![CDATA[christopher naum]]></category>
		<category><![CDATA[command-leadership]]></category>
		<category><![CDATA[Commandsafety.com]]></category>
		<category><![CDATA[company officer]]></category>
		<category><![CDATA[Crew Management]]></category>
		<category><![CDATA[Fire Fighter Safety]]></category>
		<category><![CDATA[firefighter-safety-health]]></category>
		<category><![CDATA[History Repeating Event]]></category>
		<category><![CDATA[Near-Miss Reporting]]></category>
		<category><![CDATA[Christopher Naum. Thecompanyofficer.com]]></category>
		<category><![CDATA[Fire fighter Safety]]></category>
		<category><![CDATA[Fire Officer Resources]]></category>
		<category><![CDATA[firefighter near-miss reporting]]></category>
		<category><![CDATA[IAFC]]></category>
		<category><![CDATA[National Firefighter Near-Miss Reporting System]]></category>
		<category><![CDATA[National Near Miss Reporting System]]></category>
		<category><![CDATA[Near-Miss Reporting Tool Box]]></category>
		<category><![CDATA[ROTW]]></category>
		<category><![CDATA[thecompanyofficer.com]]></category>

		<guid isPermaLink="false">http://thecompanyofficer.com/?p=1791</guid>
		<description><![CDATA[As an officer, you need to stay abreast of operational issues and situations in order to be knowledgeable and conversant with the variables that may affect company deployments and subsequent operations.]]></description>
			<content:encoded><![CDATA[<div id="attachment_1792" class="wp-caption aligncenter" style="width: 493px"><a href="http://thecompanyofficer.com/files/2011/07/7-15-2011-12-46-17-PM.jpg"><img class="size-full wp-image-1792 " title="7-15-2011 12-46-17 PM" src="http://thecompanyofficer.com/files/2011/07/7-15-2011-12-46-17-PM.jpg" alt="" width="483" height="429" /></a><p class="wp-caption-text">Firefighternearmiss.com The Report of the Week</p></div>
<p>As an officer, you need to stay abreast of operational issues and situations in order to be knowledgeable and conversant with the variables that may affect company deployments and subsequent operations. The National Fire Fighter Near Miss Reporting System (FFNMRS) has a vast collection of resources that are a few keystrokes and links away.</p>
<p>One of the most useful tools in the FFNMRS Tool Box of resources is the <strong>Near-Miss Report of the Week (ROTW).</strong> The direct link to the page is<a href="http://www.firefighternearmiss.com/index.php/home"> here.</a></p>
<p>Take some time to look over the content and subject matter available to you in the form of the weekly publication. The information provides insights and examples of situational near miss events and close calls that provide the lessons learned so that, when confronted with similar precursors or subtle indications, you may be able to draw from the ROTW and the from the lessons and insights of other Near Miss Reports that may prevent a similar close-call/near miss event or from escalating into a more serious event.</p>
<p>Take the time to review the ROTW, sign up for the weekly email delivery and most importantly- read the reports and integrate them into your training, drills, discussions, tabletops, chalk board or podcast talks. <em>Get the FFNMRS reports embedded into your psyche.</em></p>
<p><span style="color: #ff0000;"><strong>Here&#8217;s what was sent out this week&#8230;.</strong></span></p>
<p>Multiple units responding to the same incident from different directions creates the potential for unscheduled arrivals at intersecting points. These points are most frequently intersections that are in one form or another controlled by devices ranging from stop signs to traffic lights. In this week&#8217;s ROTW, report <a href="http://www.firefighternearmiss.com/googlemini2/h11-0000179.html">11-179</a>, reminds us that a green light does not necessarily guarantee the way is safe to proceed.</p>
<p><em>[ ] Brackets denote reviewer de-identification.</em></p>
<p><em>&#8220;A municipal ALS equipped engine and a third service county ALS ambulance were dispatched by the same dispatch, on the same radio channel, to a local park for a trauma patient. While enroute, and less than two miles from our station, we approached a heavy traffic intersection, which is blind to the south side. Upon approach, the [brand deleted] signal preemption system (which both the engine and ambulance are equipped with) was delayed in capturing the light. The driver of the engine began to reduce speed and decelerate toward the intersection. As we approached the intersection we captured the light with the signal preemption system, giving us a GREEN light, but for whatever reason, the driver of the engine made a complete stop at the intersection. Just then the ambulance blew through the intersection, not stopping for the RED light. To our surprise, we didn&#8217;t hear or see this ambulance until they were in the intersection. Only because of the driver&#8217;s situational awareness and intuition (gut feeling) did we come to a complete stop to avoid a collision.&#8221; </em></p>
<p>Right of way rules, line of sight approaches, traffic light pre-emption devices and emergency response SOPs all support apparatus arriving at the scene of an emergency call. Despite all these efforts, human factor plays a role in the safe arrival of all units to their dispatched destination.</p>
<p>Once you have read the entire account of <a href="http://www.firefighternearmiss.com/googlemini2/h11-0000179.html">11-179</a>, and the related reports, consider the following with your colleagues.</p>
<ol>
<li>Many departments now have specific rules requiring units to stop at all red lights during emergency response. If your department has such rules in effect, are there any other recommendations for intersection travel to consider?</li>
<li>The reporter states the driver&#8217;s &#8220;situational awareness and intuition&#8221; contributed to collision avoidance. How large of a role do you believe the two factors played? How do you promote/teach the effect of the &#8220;gut feeling&#8221; in your driver training sessions?</li>
<li>How often do you encounter intersection situations with crossing emergency vehicle traffic? Given your estimate, what is your assessment of the likelihood of a collision based on the frequency?</li>
<li>If your agency uses traffic pre-emptive signaling, how often is the system calibrated/fault-checked to ensure accuracy?</li>
<li>How many &#8220;blind side&#8221; intersections exist in your response area? What is the significance of knowing where they are?</li>
</ol>
<p>Emergency response ranges from high frequency, high risk to low frequency and high risk depending on how many calls for service a department receives. Reducing the risk associated, whether the frequency is high or low is an essential element of keeping our promise to the communities we serve. Doing your part by keeping your speed under control and being on the lookout for hazardous situations like intersections, will promote getting you to the scene quickly and returning for the next run.</p>
<p><strong>Related Reports &#8211; Topical Relation: Driving: Intersections   </strong></p>
<ul>
<li><a href="http://www.firefighternearmiss.com/googlemini2/h07-0000806.html">07-806</a></li>
<li><a href="http://www.firefighternearmiss.com/googlemini2/h07-0000839.html">07-839</a></li>
<li><a href="http://www.firefighternearmiss.com/googlemini2/h07-0000932.html">07-932</a></li>
<li><a href="http://www.firefighternearmiss.com/googlemini2/h07-0001162.html">07-1162</a></li>
<li><a href="http://www.firefighternearmiss.com/googlemini2/h08-0000042.html">08-042</a></li>
<li><a href="http://www.firefighternearmiss.com/googlemini2/h10-0000057.html">10-057</a></li>
</ul>
<p>Experience a near miss with another piece of apparatus while responding? Submit your report to <a href="http://www.firefighternearmiss.com/">www.firefighternearmiss.com</a> today.</p>
<p><em>Note: The questions posed by the reviewers are designed to generate discussion and thought in the name of promoting firefighter safety. They are not intended to pass judgment on the actions and performance of individuals in the reports.</em></p>
<p><em>To Sign up to receive the Near-Miss Report of the Week by email, forward  your request to <a href="mailto:atippett@iafc.org">atippett@iafc.org</a></em></p>
<p><em>Firefighternearmiss.com is funded by a grant from the U.S. Department of Homeland Security&#8217;s Assistance to Firefighters Grant program. Founding dollars were also provided by <a href="http://www.ffic.com/" target="_blank">Fireman&#8217;s Fund Insurance Company</a>. The project is managed by the International Association of Fire Chiefs and supported by <a href="http://www.firefighterclosecalls.com/" target="_blank">FireFighterCloseCalls.com</a> in mutual dedication to firefighter safety and survival.</em><em> </em></p>
<p><span style="color: #ff0000;"><strong>We’ve provided some direct links from the ROTW webpage here, but there is a lot more on the firefighternearmiss.com site.</strong></span></p>
<div id="attachment_1793" class="wp-caption aligncenter" style="width: 560px"><a href="http://thecompanyofficer.com/files/2011/07/7-15-2011-12-53-06-PM.jpg"><img class="size-full wp-image-1793 " title="7-15-2011 12-53-06 PM" src="http://thecompanyofficer.com/files/2011/07/7-15-2011-12-53-06-PM.jpg" alt="" width="550" height="64" /></a><p class="wp-caption-text">Firefighternearmiss.com</p></div>
<p><strong><span style="color: #ff0000;">FFNMR &#8211; Report of the Week Archives  [Direct Link, <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives">HERE</a>] </span></strong></p>
<table border="0">
<tbody>
<tr>
<td colspan="2">Page 1 of 7</td>
<td align="right">1  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/155">2</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/156">3</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/157">4</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/158">5</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/159">6</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/160">7</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/155"><img src="http://www.firefighternearmiss.com/images/btn_next.gif" border="0" alt="" /></a></td>
</tr>
<tr>
<td>File Title</td>
<td align="center">File Size</td>
<td>File Description</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTWBinderCoverandSpine2010_v2.pdf" target="blank">ROTW Binder, Cover and Spine Label</a></li>
</td>
<td align="center" valign="top">990 KB</td>
<td>Cover and Spine Label to make your own ROTW Binder.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/2006_Report_of_the_Week_Library.zip" target="blank">2006 Report of the Week Library</a></li>
</td>
<td align="center" valign="top">14.8 MB</td>
<td>Complete 2006 Report of the Week Library. ZIP File.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_122107.pdf" target="blank">ROTW 122107: What&#8217;s in your pockets? (07-1116)</a></li>
</td>
<td align="center" valign="top">35 KB</td>
<td>FF becomes entangled in wires.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_121407.pdf" target="blank">ROTW 121407: The deafening silence of culture. (07-1142)</a></li>
</td>
<td align="center" valign="top">38 KB</td>
<td>Safety issues overlooked during emergency response.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_120707.pdf" target="blank">ROTW 120707: &#8216;Sun&#8217; and &#8216;Block&#8217; take on a new meaning. (07-1119)</a></li>
</td>
<td align="center" valign="top">36 KB</td>
<td>Sunshine fould driver&#8217;s vision.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_DOC_113007.doc" target="blank">ROTW 113007: Use 3D for vacant and burning: distance, defensive, deluge. (05-618)</a></li>
</td>
<td align="center" valign="top">49 KB</td>
<td>Fighting fire in a vacant structure, concerns addressed.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_111607.pdf" target="blank">ROTW 111607: Probies are not expendable. (07-776)</a></li>
</td>
<td align="center" valign="top">35 KB</td>
<td>Aerial stabilizer narrowly misses firefighter.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_110907.pdf" target="blank">ROTW 110907: Nearly done in by our own kind. (07-1108)</a></li>
</td>
<td align="center" valign="top">35 KB</td>
<td>Re-opening a roadway requires coordination.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_110207.pdf" target="blank">ROTW 110207: The importance of using wheel locks and its effects. (06-173)</a></li>
</td>
<td align="center" valign="top">37 KB</td>
<td>Wildland/urban interface fire reveals personnel/equipment needs.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_102607.pdf" target="blank">ROTW 102607: Contractor Mishap. (07-1043)</a></li>
</td>
<td align="center" valign="top">37 KB</td>
<td>Apparatus electrified during test by contractor.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_101907.pdf" target="blank">ROTW 101907: Asleep at the wheel and no one noticed. (07-752)</a></li>
</td>
<td align="center" valign="top">35 KB</td>
<td>Driver falls asleep on EMS call.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_101207.pdf" target="blank">ROTW 101207: Faster than you can call a Mayday&#8230; (05-567)</a></li>
</td>
<td align="center" valign="top">38 KB</td>
<td>Roof collapse ignites bedroom injuring firefighter.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_100507.pdf" target="blank">ROTW 100507: It&#8217;s not &#8216;just a car fire&#8230;&#8217; (07-800)</a></li>
</td>
<td align="center" valign="top">28 KB</td>
<td>Engine contacts downed powerline at accident scene.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_092807.pdf" target="blank">ROTW 092807: Intuition adverts danger. (05-553)</a></li>
</td>
<td align="center" valign="top">38 KB</td>
<td>Structure fire in concealed ceiling causes collapse, nearly trapping interior crews.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_092107.pdf" target="blank">ROTW 092107: Blowout on the front apron. (07-910)</a></li>
</td>
<td align="center" valign="top">34 KB</td>
<td>Tire blows following apparatus check.</td>
</tr>
<tr>
<td>
<li><a href="http://www.firefighternearmiss.com/Resources/Report_of_the_Week_Archives/ROTW_1/ROTW_PDF_091407.pdf" target="blank">ROTW 091407: Leave your eyes to Z87.1. (07-964)</a></li>
</td>
<td align="center" valign="top">35 KB</td>
<td>Safety glasses do their job during extrication.</td>
</tr>
<tr>
<td colspan="2">Page 1 of 7</td>
<td align="right">1  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/155">2</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/156">3</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/157">4</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/158">5</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/159">6</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/160">7</a>  <a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives/155"><img src="http://www.firefighternearmiss.com/images/btn_next.gif" border="0" alt="" /></a></td>
</tr>
</tbody>
</table>
<p> For some Program insights, check out the recent posting on <strong><a href="http://commandsafety.com">CommandSafety.com</a></strong>: <a title="Permanent link to National Firefighter Near-Miss Reporting System; Untapped Resource" rel="bookmark" href="http://commandsafety.com/2011/06/national-firefighter-near-miss-reporting-system-untapped-resource/">National Firefighter Near-Miss Reporting System; Untapped Resource</a></p>
<p>or go Directly to the <strong>Firefighternearmiss.com </strong>site, <a href="http://www.firefighternearmiss.com/index.php/home">HERE</a></p>
<div id="attachment_1794" class="wp-caption aligncenter" style="width: 603px"><a href="http://www.firefighternearmiss.com/index.php/home"><img class="size-full wp-image-1794   " title="7-15-2011 1-22-12 PM" src="http://thecompanyofficer.com/files/2011/07/7-15-2011-1-22-12-PM.jpg" alt="" width="593" height="264" /></a><p class="wp-caption-text">Clip from Home Page</p></div>
<p> <strong><span style="color: #ff0000;">These are some of the Site File Categories; </span></strong></p>
<div>
<p><strong><img src="http://www.firefighternearmiss.com/images/hd_file_cats.gif" border="0" alt="" /></strong></p>
</div>
<ul id="categories">
<li><a href="http://www.firefighternearmiss.com/Resources/2011_Calendar/Near-MissCalendar2011.pdf">2011 Calendar/Annual Report</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/2011-calendar-modules">2011 Calendar Modules</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/2010-calendar-2009-annual-report">2010 Calendar / 2009 Annual Report</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/2009-near-miss-calendar">2009 Near-Miss Calendar</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/annual-reports">Annual Reports</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/anthology">Anthology</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/crew-resource-management">Crew Resource Management</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/endorsements">Endorsements</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/equipment-information">Equipment Information</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/featured-reports">Featured Reports</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/hfacs">HFACS</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/illustrated-case-studies">Illustrated Case Studies</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/investigation-reports">Investigation Reports</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/media-center">Media Center</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/near-miss-matters-enewsletter">Near-Miss Matters eNewsletter</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/near-miss-trainers">Near-Miss Trainers</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/presentations">Presentations</a></li>
<li id="current"><a href="http://www.firefighternearmiss.com/index.php/report-of-the-week-archives">Report of the Week Archives</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/reports-for-training">Reports for Training</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/sample-policies-a-training-tools">Sample Policies &amp; Training Tools</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/state-training-resources">State Training Resources</a></li>
<li><a href="http://www.firefighternearmiss.com/index.php/table-top-training-exercises">Table Top Training Exercises</a></li>
</ul>
<p><strong>National Firefighter Near Miss Reporting System on Facebook, <a href="http://www.facebook.com/firefighternearmiss">HERE</a></strong></p>
<p><strong>For a direct point of contact at the NFFNMRS;</strong></p>
<p>Rynnel Gibbs, Program Coordinator<br />
National Fire Fighter Near-Miss Reporting System<br />
4025 Fair Ridge Drive    Fairfax, VA 22033<br />
P: 703-537-4858     F: 703-273-0920    <a href="mailto:rgibbs@iafc.org">rgibbs@iafc.org</a>      <a href="http://www.firefighternearmiss.com/">www.firefighternearmiss.com</a></p>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://thecompanyofficer.com/2011/07/15/near-miss-report-of-the-week/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://thecompanyofficer.com/2011/07/15/near-miss-report-of-the-week/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Texas Captain; 2010 LODD Report Issued with Lessons Learned</title>
		<link>http://thecompanyofficer.com/2011/07/04/texas-captain-2010-lodd-report-issued-with-lessons-learned/</link>
		<comments>http://thecompanyofficer.com/2011/07/04/texas-captain-2010-lodd-report-issued-with-lessons-learned/#comments</comments>
		<pubDate>Tue, 05 Jul 2011 02:45:42 +0000</pubDate>
		<dc:creator>Christopher Naum</dc:creator>
				<category><![CDATA[building construction]]></category>
		<category><![CDATA[Buildingsonfire.com]]></category>
		<category><![CDATA[christopher naum]]></category>
		<category><![CDATA[Collapse]]></category>
		<category><![CDATA[command-leadership]]></category>
		<category><![CDATA[Commandsafety.com]]></category>
		<category><![CDATA[company officer]]></category>
		<category><![CDATA[Crew Integrity]]></category>
		<category><![CDATA[Crew Management]]></category>
		<category><![CDATA[Fire Fighter Safety]]></category>
		<category><![CDATA[Fire Suppression]]></category>
		<category><![CDATA[firefighter-safety-health]]></category>
		<category><![CDATA[firefighting-operations]]></category>
		<category><![CDATA[fires]]></category>
		<category><![CDATA[LODD]]></category>
		<category><![CDATA[NIOSH Reports]]></category>
		<category><![CDATA[Reports]]></category>
		<category><![CDATA[Risk Assessment]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[thecompanyofficer.com]]></category>
		<category><![CDATA[Christpoher Naum]]></category>
		<category><![CDATA[Command Compression]]></category>
		<category><![CDATA[Command Training]]></category>
		<category><![CDATA[Disorientation]]></category>
		<category><![CDATA[Enclosed Structure]]></category>
		<category><![CDATA[fire behavior]]></category>
		<category><![CDATA[Firefighter LODD]]></category>
		<category><![CDATA[Frefighter LODD 2010]]></category>
		<category><![CDATA[hris Naum]]></category>
		<category><![CDATA[ICS]]></category>
		<category><![CDATA[incident command]]></category>
		<category><![CDATA[Large area Search]]></category>
		<category><![CDATA[large windowless]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[limited access structure]]></category>
		<category><![CDATA[Maxim Egg Farm Fire 2010]]></category>
		<category><![CDATA[Maxim Egg Farm Fire Texas LODD 2010]]></category>
		<category><![CDATA[NFPA 1500]]></category>
		<category><![CDATA[Operational Span of Control]]></category>
		<category><![CDATA[risk - benefit analysis]]></category>
		<category><![CDATA[RIT]]></category>
		<category><![CDATA[safety]]></category>
		<category><![CDATA[Safety Officer]]></category>
		<category><![CDATA[search and rescue]]></category>
		<category><![CDATA[SFMO]]></category>
		<category><![CDATA[SFMO Case Number FY10-01]]></category>
		<category><![CDATA[Situational Awareness]]></category>
		<category><![CDATA[Span of Control]]></category>
		<category><![CDATA[Strategy and Tactics]]></category>
		<category><![CDATA[Texas State Fire Marshal's Office issued the Fire Fighter Fatality Investigation Report]]></category>
		<category><![CDATA[Two in and Two Out]]></category>
		<category><![CDATA[Wharton Volunteer Fire Department]]></category>
		<category><![CDATA[Wharton Volunteer Fire Department Captain Thomas Araguz III]]></category>

		<guid isPermaLink="false">http://thecompanyofficer.com/?p=1752</guid>
		<description><![CDATA[Captain Araguz, a 30 year old, 11-year veteran of the Wharton Volunteer Fire Department made Captain in 2009. ]]></description>
			<content:encoded><![CDATA[<div id="attachment_1753" class="wp-caption aligncenter" style="width: 323px"><a href="http://thecompanyofficer.com/files/2011/07/7-4-2011-3-39-57-PM.jpg"><img class="size-full wp-image-1753" title="7-4-2011 3-39-57 PM" src="http://thecompanyofficer.com/files/2011/07/7-4-2011-3-39-57-PM.jpg" alt="" width="313" height="362" /></a><p class="wp-caption-text">Captain Thomas Araguz III</p></div>
<p> </p>
<p>Captain Araguz, a 30 year old, 11-year veteran of the Wharton Volunteer Fire Department made Captain in 2009. He lost his life while battling a multiple alarm fire a the Maxim Egg Farm located at 3307 FM 442, Boling, Texas on July 3, 2010.  The Texas State Fire Marshal&#8217;s Office issued the Fire Fighter Fatality Investigation Report, SFMO Case Number FY10-01 that provides a detailed examination of the incident, operations and yeilds findings and recommendations. A full version of the report is available at the Texas SFMO web site <a href="http://www.tdi.state.tx.us/reports/fire/documents/fmloddaraguz.pdf">HERE.</a></p>
<p> On July 3, 2010, Wharton Volunteer Fire Department Captain Thomas Araguz III was fatally injured during firefighting operations at an egg production and processing facility. At 9:41 PM, Wharton County Sheriff’s Office 911 received a report of a fire at the Maxim Egg Farm located at 3307 FM 442, Boling, Texas. Boling Volunteer Fire Department and the Wharton Volunteer Fire Department responded first, arriving approximately 12 minutes after dispatch. Eventually, more than 30 departments with 100 apparatus and more than 150 personnel responded. Some departments came as far as 60 miles to assist in fighting the fire.</p>
<div id="attachment_1754" class="wp-caption aligncenter" style="width: 543px"><a href="http://thecompanyofficer.com/files/2011/07/7-4-2011-3-42-01-PM.jpg"><img class="size-full wp-image-1754 " title="7-4-2011 3-42-01 PM" src="http://thecompanyofficer.com/files/2011/07/7-4-2011-3-42-01-PM.jpg" alt="" width="533" height="543" /></a><p class="wp-caption-text">Aerial View</p></div>
<p> </p>
<p>The fire involved the egg processing building, including the storage areas holding stacked pallets of foam, plastic, and cardboard egg cartons and boxes. It was a large windowless, limited access structure with large open areas totaling over 58,000 square feet. A mixed construction, it included a two-story business office, the egg processing plant, storage areas, coolers, and shipping docks. It was primarily metal frame construction with metal siding and roofing on a concrete slab foundation with some areas using wood framing for the roof structure.</p>
<p>Captain Araguz responded to the scene from the Wharton Fire Station, approximately 20 miles from the fire scene, arriving to the front, south side main entrance 20 minutes after dispatch. Captain Araguz, Captain Juan Cano, and Firefighter Paul Maldonado advanced a line through the main entrance and along the south, interior wall to doors leading to a storage area at the Southeast corner.</p>
<p>Maldonado fed hose at the entry door as Captains Araguz and Cano advanced through the processing room. Araguz and Cano became separated from the hose line and then each other. Captain Cano found an exterior wall and began kicking and hitting the wall as his air supply ran out. Firefighters cut through the exterior metal wall at the location of the knocking and pulled him out. Several attempts were made to locate Captain Araguz including entering the building through the hole and cutting an additional hole in the exterior wall where Cano believed Araguz was located. Fire conditions eventually drove the rescuers back and defensive firefighting operations were initiated.</p>
<p>Captain Cano was transported to the Gulf Coast Medical Center where he was treated and released. Captain Araguz was recovered at 7:40 AM, the following morning. Initially transported by ambulance to the Wharton Funeral Home then taken to the Travis County Medical Examiner’s Office in Austin, Texas for a post-mortem examination.</p>
<div id="attachment_1756" class="wp-caption aligncenter" style="width: 534px"><a href="http://thecompanyofficer.com/files/2011/07/Site-Plan-Diagram-1.jpg"><img class="size-full wp-image-1756 " title="Site Plan Diagram 1" src="http://thecompanyofficer.com/files/2011/07/Site-Plan-Diagram-1.jpg" alt="" width="524" height="643" /></a><p class="wp-caption-text">Site Plan of Building Complex</p></div>
<p><strong>Building Structure and Systems</strong></p>
<p>The fire incident building was located on the property of Maxim Egg Farm, located within an unincorporated area of Wharton County. The 911 address is 580 Maxim Drive, Boling, Texas 77420.</p>
<p>Wharton County has no adopted fire codes, or model construction codes, and no designated Fire Marshal on staff that conducts fire safety inspections within their jurisdiction.</p>
<p><em>National Fire Protection Association (NFPA) Standard 101, Life Safety Code, 2009 Edition</em>, is adopted by the State Fire Marshal’s Office, and is the applicable standard for fire and life safety inspections in the absence of an adopted fire code within unincorporated areas of a county by an applicable authority. All references regarding evaluation of the incident building in relation to minimum life safety requirements are based on <em>NFPA 101, Life Safety Code, 2009 Edition. </em></p>
<p>Maxim Farm property includes 23 chicken coops known as layer barns that average 300 feet long and 50 feet wide holding between 15,000 to 25,000 chickens each. These layer barns inter-connect to a central processing building by a series of enclosed conveyor belts transporting over one million eggs daily.</p>
<ul>
<li>The property includes integrated feed silos, water tanks, and waste management facilities. Additional areas on the property include equipment barns, shipping offices, loading docks, coolers, storage areas, and business offices.</li>
</ul>
<p><strong> </strong><strong>Overall Building Description </strong></p>
<p>The main processing structure was an irregularly shaped mixed construction of metal, concrete block, and wood framing on a concrete slab foundation with approximately 58,000 square feet of space. Three dry-storage rooms connected by a wide hallway lined the east side of the plant. A concrete block (CMU) wall separated the egg processing area from the East Hallway and storage rooms. Coolers were located north of the processing room with the loading docks along the west side of the structure. The loading docks were accessible from the processing room, Cooler 3, and Cooler 2. Cooler 1 was located at the north end of Dry Storage 2. A two-story building housing the business office was attached to the main processing plant at the southwest corner.</p>
<p><strong>Construction Features </strong></p>
<p>The building construction was classified as an NFPA 220, Type II-000 construction with an occupancy classification by the <em>Life Safety Code </em>as Industrial with sub-classification as special-purpose use. The <em>Life Safety Code </em>imposes no minimum construction requirements for this type of occupancy.</p>
<p>The predominant use of the building was to process and package fresh eggs for shipment after arriving by automated conveyor directly from a laying house adjacent to the building. The general floor plan of the building consisted of a large egg processing room, with surrounding areas used for storage of packing materials and two large drive-in coolers for holding packaged eggs prior to shipping.</p>
<p>Building construction consisted of a combination of steel and wood framing with a sheet metal exterior siding and roofing over a low-pitch roof on a concrete slab foundation. Structural elements within the interior of the building were exposed and unprotected with no fire-resistance rated materials applied. The load bearing structural elements consisted of steel beams, and steel pipe columns, with steel open web trusses supporting the roof structure.</p>
<ul>
<li>Wood components were also used as part of the load bearing elements and wall framing.</li>
<li>Perimeter walls of the cooler compartments were constructed of concrete masonry units (CMU).</li>
<li>The building was not separated between other areas of use by fire-resistance rated assemblies.</li>
<li>Ancillary facilities located within the building used for administrative offices and other incidental spaces were constructed of wood framing with a gypsum wallboard finish.</li>
</ul>
<p><strong>Detailed Construction Features </strong></p>
<p>The front of the structure faced to the south where the main entrance to the processing room and business offices was located approximately 4 feet above the parking lot grade level and accessed by a series of steps. The business office was a two-story wood frame construction with a vinyl exterior siding under a metal roof on a concrete slab foundation. Additional separate, single-story, wood frame structures with offices located to the west of the main business office connected by covered walkways.</p>
<p><strong>Processing Room </strong></p>
<p>The egg processing room was 141 feet along the east and west walls and approximately 100 feet along the north and south walls. The processing room received the eggs transported from the layer barns on the conveyer belt system. The room contained the processing equipment and conveyor systems where eggs were cleaned, graded, packaged and moved to large coolers to await shipment. The construction of the processing room was sheet metal panels embedded into the concrete slab foundation supported by 8-inch wide metal studs. Sheet metal panels lined the exterior and interior sides of the south and west walls with fiberglass insulation sandwiched between.</p>
<div id="attachment_1757" class="wp-caption aligncenter" style="width: 310px"><a href="http://thecompanyofficer.com/files/2011/07/7-4-2011-9-29-24-PM.jpg"><img class="size-medium wp-image-1757" title="7-4-2011 9-29-24 PM" src="http://thecompanyofficer.com/files/2011/07/7-4-2011-9-29-24-PM-300x194.jpg" alt="" width="300" height="194" /></a><p class="wp-caption-text">Main Processing Area</p></div>
<p>The north wall separated the processing room from Cooler 3 and consisted mainly of interlocking insulated metal panels embedded into the slab locked at the top in metal channels. Their interior surface was polyurethane laminate.</p>
<p>The east wall was mainly of concrete block (CMU) construction. A USDA office and a mechanics room were accessed through doors in the east wall of the processing room. The northeast corner of the processing room extended into the north end of the east hallway, forming an 18 feet by 18 feet area with wood frame construction on a concrete stem wall with fiber cement board (Hardy board) and metal panel siding. A 6-feet wide opening between the processing and dry-storage areas with a vinyl strip door allowed unrestricted access.</p>
<p>Along the south wall of the processing room, a walkway between the processing equipment and exterior wall led to swinging double doors at the southeast corner to enter into Dry Storage 3. Conveyors carried the eggs from the north and south layer barns through openings in the walls of the extension of the processing room. The conveyors from the north and south layer barns entered the building suspended overhead. As the conveyors approached the entrance to the main processing room, they gradually descended to 3.5 feet above floor level and were supported by metal brackets attached to the floor. Electric drive motors attached to the conveyors at several points along their lengths to power their movement.</p>
<p>The roof consisted of steel columns and girders with metal panel roofing attached to metal purlins supported by steel rafters. Wire mesh supported fiberglass insulation under the roof deck. The roof gable was oriented north to south.</p>
<p><strong> </strong></p>
<p><strong>Dry Storage </strong></p>
<p>The plant included three dry-storage rooms along the eastern side of the building connected by an east hallway. Dry Storage 1 and Dry Storage 2 were located in the northeast corner of the plant under a common sloping metal roof. The dry-storage rooms held pallets of containers including polystyrene egg crates, foam egg cartons, pulp egg cartons, and cardboard boxes.</p>
<p><strong> </strong></p>
<p><strong>Dry Storage 1 </strong>was approximately 123 feet long and 50 feet wide and was 4 feet below the grade of the rest of the plant. It was added to the east side of Dry Storage 2 in 2008. Dry Storage 1 was a concrete slab and 4-feet high concrete half wall topped with wood framing and metal siding. The metal roof sloped from 11 feet high above the west side to 10 feet high above the east wall. The roof attached to 2 inch x 8 inch wood joists supported by two rows of steel support columns and steel girders. The two rows of seven columns were oriented in a north-south direction.</p>
<p>A concrete ramp at the south end facilitated access to the East Hallway and Dry Storage 2 and the main level of the processing room. A concrete ramp at the northeast corner of Dry Storage 1 provided access to the rear loading dock. The rear dock was secured on the interior at the top of the ramp by a wood frame and metal double door with a wooden cross member and a chain and padlock. An additional wood frame and screened double door secured on the interior.</p>
<p>The conveyor belt from the north layer barns ran the length of the west side of Dry Storage 1 where it turned to the west, crossing Dry Storage 2 and the East Hallway into the main processing room.</p>
<p>Dry Storage 1 contained 29 rows of pallets, seven to eight pallets deep, of mainly Styrofoam egg crates stacked between 7 and 10 feet high, depending on their location. Corridors between the rows were maintained to provide access to the pallets with an electric forklift. Fluorescent light fixtures attached to the wood rafters in rows north to south with their conductors in PVC conduit. Skylights spaced evenly above the west side allowed for natural light. Pallets of stock material were single stacked below the locations of the light fixtures to keep clearance and prevent damage.</p>
<p><strong>Dry Storage 2, </strong>located west of and 4 feet above Dry Storage 1, stored pallets of flattened cardboard box stock. The room was approximately 81 feet long and 40 feet wide. The south wall was the processing room extension and was approximately 25 feet long. The east side of the room was open to Dry Storage 1 with 4 inch x 4 inch unprotected wood studs spaced unevenly from 4 feet to 9 feet, supporting the metal roof. The west wall was CMU construction and was the exterior wall of Cooler 3. The metal roof sloped from the top of the west wall approximately 12 feet high to approximately 11 feet above the east side.</p>
<p>The room was accessed from the south end at the top of the ramp leading down into Dry Storage 1. Pallets of folded cardboard boxes were stacked along the entire length of the west wall extending 16 to 20 feet to the east. The rows of pallets were without spacing for corridors. One row of six fluorescent light fixtures attached to wood rafters near the north-south centerline.</p>
<p>The <strong>East Hallway </strong>was approximately 118 feet long and 37 feet wide running along the length of the east side of the processing room. The East Hallway connected Dry Storages 1 and 2 with Dry Storage 3 by a corridor at the south end. The East Hallway allowed access between the storage room areas and into utility rooms including the Boiler Room at the north end and a mechanics room and small utility closet. Pallets of polystyrene egg crates were stored along the east wall in rows of three pallets each. Seven pallets of polystyrene egg crates were stored along the conveyors.</p>
<p>The west wall was concrete block construction (CMU) until it connected to the extension of the processing area constructed of wood frame covered by Hardy board and sheet metal. The east wall was sheet metal embedded in the concrete slab supported by 2 inch x 4 inch wood studs with Hardy board interior. The metal roof sloped from a height at 12 feet at the west wall to 10 feet high at the east wall, supported by 4 inch x 6 inch wood columns and 2 inch x 8 inch wood joists.</p>
<p>Two conveyors entered the south end of the east hallway from Dry Storage 3. The conveyors ran parallel for approximately 80 feet along the west wall and entered the processing room through openings in the extension at the north end of the east hallway. They were 6 feet from the west wall and gradually descended from a height of 9 feet at the south end to 3.5 feet at the north. Each conveyor was 31 inches wide and combined was approximately 7 feet wide. Two compressor machines and a pressure washer were located along the west wall near the south end.</p>
<p>The <strong>Boiler Room, </strong>located at the northeast corner of the East Hall, housed two propane fired boilers, a water treatment system and two vacuum pumps. It was wood frame construction with metal siding under a metal roof on a combination concrete slab and concrete pier and wood beam foundation. A small utility room with service panels was constructed of concrete block on a concrete slab under a metal roof and was also located along the west wall of the East Hallway. An approximately 10 feet wide corridor connected the East Hallway to Dry Storage 3.</p>
<p><strong>Dry Storage 3 </strong>extended south from the main processing room and East Hallway to the south dock area where tractor-trailers parked to unload the pallets of supplies. Two parallel conveyors suspended 9 feet overhead from the roof extended along the length of the east wall where it passed through the south wall toward the south layer houses.</p>
<p>The plant&#8217;s main power conductors entered the west wall of Dry Storage 3 from load centers and transformers mounted to the slab outside approximately 15 feet south of the main processing room exterior wall. Stacks of wood pallets were stored in Dry Storage 3. Corridors wide enough for forklifts provided access to the south cargo dock area.</p>
<p><strong>Fire Ground Operations and Tactics </strong></p>
<p><em>Note: The following sequence of events was developed from radio transmissions and firefighter witness statements. Those events with known times are identified. Events without known times are approximated in the sequence of the events based on firefighter statements regarding their actions and/or observations. A detailed timeline of radio transmissions is included in the appendix. </em></p>
<p>On July 3, 2010, at <strong>21:41:10</strong>, Wharton County Sheriff’s Office 911 received a report of a fire at the Maxim Egg Farm located on County Road 442, south of the city of Boling, Texas. The caller, immediately transferred to the Wharton Police Department Dispatch, advised there was a “big fire” in the warehouse where egg cartons were stored. Boling Volunteer Fire Department was dispatched and immediately requested aid from the Wharton Volunteer Fire Department. Wharton VFD became Command as is the usual practice for this county.</p>
<p>Wharton Assistant Chief Stewart (1102) was returning to the station having been out on a response to a vehicle accident assisting the Boling Volunteer Fire Department when the call came in for the fire. He responded immediately and at <strong>21:50 </strong>reported seeing “heavy fire” coming from the roof at the northeast corner of the building as he approached the plant from the east on County Road 442. When he arrived he was eventually directed to the east side of the building (D side) to the rear loading dock. Asst. Chief Stewart worked for several minutes with facility employees to gain access to the fire building before being led to the northeast loading dock.</p>
<p>An employee directed him on the narrow caliche drive behind the layer barns and between the waste ponds to the loading dock. Wharton Engine 1134 followed 1102 to the east side and backed into the drive leading to the loading dock. Asst. Chief Stewart’s immediate actions included assessing the extent of the fire on the interior of the building by looking through the doors at the loading dock to Dry Storage 1. Unable to see the fire through the smoke at the doors of the loading dock, an attack was eventually accomplished by removing a metal panel from the east exterior wall of Dry Storage 1 and using one 1¾”-inch cross lay. After a few minutes, the deck gun on Engine 1134 was utilized, directing water to the roof above the seat of the fire near the south end of Dry Storage 1.</p>
<p>Water supply became an immediate concern and 1102 made efforts to get resources for resupply. Requests for mutual aid to provide water tankers were made to area communities. During the incident, re-supplying tankers included a gravity re-fill from the on-site water supply storage tanks and from fire hydrants in the City of Boling, 3 miles from the scene and the City of Wharton, nearly 11 miles. The City of Boling water tower was nearly emptied during the incident.</p>
<p>The radio recording indicates there were difficulties accessing the location of the fire as apparatus were led around the complex by multiple employees. Heavy rains during the previous week left many roadways muddy and partially covered with water, which added to problems with apparatus access. In addition, fire crews were not familiar with the layout of the facility and there are no records of pre-fire plans. Asst. Chief Stewart worked for several minutes with facility employees to gain access to the fire building before being led to the northeast loading dock.</p>
<p>Wharton Fire Chief Bobby Barnett (1101) arrived on scene at <strong>21:56:14, </strong>and ordered incoming apparatus to stage until he could establish an area of operations at the front, south side of the plant (A side). Chief Barnett directed Engine 1130 to position approximately 50 feet from the front main entrance of the plant. At <strong>22:09:16</strong>, Chief Barnett (1101) established a command post on A side and became the Incident Commander; 1101 directed radio communications for the fireground to be TAC 2 and called for mutual aid from the Hungerford and El Campo Fire Departments. Chief Barnett described the conditions on side A as smoky with no fire showing. Light winds were from the east, side D, pushing the smoke toward the area of the processing room, and the front, side A, of the building.</p>
<p>Maxim Egg Farm Manager David Copeland, a former Wharton VFD Chief, advised Command and firefighters that the fire was in the area of the Boiler Room and should be accessed by breaching an exterior wall in the employee break area. Chief Barnett ordered Wharton crews to the breach attempt. Captain Thomas Araguz III, Captain John Cano and Firefighter Paul Maldonado were involved with this operation. The crews working in this area were in full structural personnel protective clothing and SCBA.</p>
<p>At <strong>22:10, </strong>Command ordered Engine 1130 and Tanker 1160 to set up at the front entrance using Tanker 1160 for portable dump tank operations for water re-supply.</p>
<p>On D side, difficulty accessing the fire from the exterior of the building was reported by Asst. Chief Stewart and the crews. Heavy doors, locked loading dock doors and steel exterior paneling, required the crews to spend extra time forcing entry.</p>
<p>At <strong>22:17:23, </strong>Wharton County Chief Deputy Bill Copeland (3122), once a Wharton FD volunteer firefighter, notified Command that the fire was now through the roof over Dry Storage 1.</p>
<p>Chief Barnett noticed smoke conditions improving at the main plant doorway and ordered crews to advance lines into the processor room. Chief Barnett stated he assigned Captain Araguz, Captain Cano and Firefighter Maldonado because they were the most experienced and senior crews available.</p>
<p>Positive Pressure Ventilation (PPV) was in place at the main entry door when Captain Cano, Captain Araguz and Firefighter Maldonado entered the structure into the processing room. There are no radio transmissions to verify exact entry times.</p>
<p>Captain Cano stated that an employee had to assist fire crews with entry into the main plant through a door with keypad access. Captain Cano reported the door to processing was held open by a three-ring binder that he jammed under the door after entry. Cano stated there was low visibility and moderate heat overhead. Captain Cano and Captain Araguz made entry on a right-hand wall working their way around numerous obstacles. The line was not yet charged and they returned to the doorway and waited for water. Wharton Engine 1130’s driver reported in his interview that he had difficulty establishing a draft from the portable tank later determined to be a linkage failure on the priming pump. 1160 connected directly to 1130 and drafted from the folding tank.</p>
<p>As the crew entered into the structure through the main entry door, several plant employees began entering into the administration offices through the area of the main entry door to remove files and records. This was reported to Command at <strong>22:23 </strong>and after several minutes Chief Barnett ordered employees to stay out of the building and requested assistance from the Sheriff’s Office to maintain scene security.</p>
<p>At <strong>22:31</strong>, once the line was charged, the two captains continued into the processor on the right wall leaving Maldonado at the doorway to feed hose. Captain Cano was first with the nozzle and described making it 20 feet into the building.</p>
<p>Cano states in his interview that he advised Command over the radio that there was high heat and low visibility, although the transmission is not recorded. Cano also reported in his interview, he could not walk through the area and had to use a modified duck walk. Cano projected short streams of water towards the ceiling in a “penciling” motion and noted no change in heat or smoke conditions. They advanced until the heat became too great and they retreated towards the center of the processor. Cano stated that they discussed their next tactic and decided to try a left-handed advance.</p>
<p>At <strong>22:33, </strong>Chief Barnett advised, <em>“advancing hose streams in main building to try to block it.” </em></p>
<p>Captain Araguz took the nozzle and Captain Cano advanced with him holding onto Araguz’ bunker gear. The crew advanced along the south wall of the processing room toward the double doors to Dry Storage 3 and lost contact with the hose line.</p>
<p>The investigation found the couplings between the first and second sections of the hose lodged against a threaded floor anchor (see photo) preventing further advancement of the line. How the team lost the hose line remains uncertain.</p>
<p>Captain Cano stated in his interview that Captain Araguz told him to call a Mayday. Captain Cano stated that he was at first confused by the request, but after some time it became apparent they lost the hose line. Captain Cano reported calling Mayday on the radio but never received a reply. Captain Cano now believes he may have inadvertently switched channels at his previous transmission reporting interior conditions. Captain Araguz had a radio but it was too damaged to determine operability. There are no recorded transmissions from Captain Araguz.</p>
<p>At <strong>22:37, </strong>Deputy Chief Copeland advised Command that the fire had breached a brick wall and was entering the main packing plant. Command responded that there was a hose team inside.</p>
<p>At <strong>22:42:50, </strong>Command radioed <em>“Command to hose team 1, Cano.” </em>This was the first of several attempts to contact Captain Cano and Captain Araguz. At <strong>22:47:17, </strong>Command ordered Engine 1130 to sound the evacuation horn. At <strong>22:50:44, </strong>Command announced Mayday over the radio, stating <em>“unlocated fireman in the building.” </em></p>
<ul>
<li>Captain Cano stated in his interview that they made several large circles in an attempt to locate the fire hose.</li>
<li>Cano became entangled in wiring, requiring him to doff his SCBA.</li>
<li>After re-donning his SCBA, Captain Cano noted he lost his radio, but found a flash light. He remembered that his low air warning was sounding as he and Araguz searched for the hose. Cano stated that they made it to an exterior wall and decided to attempt to breach the wall. Working in near zero visibility,</li>
<li>Captain Cano reported losing contact with Captain Araguz while working on breaching the wall.</li>
<li>Shortly after he lost contact, Captain Cano ran out of air and removed his mask. Captain Cano continued working to breach the exterior wall until he was exhausted.</li>
</ul>
<p>At <strong>22:54, </strong>crews working on the exterior of the building near the employee break area reported hearing tapping on the wall in the area of the employee break room.</p>
<ul>
<li>Crews mustered tools and began to cut additional holes through the building exterior.</li>
<li>After making two openings, Captain Cano was located and removed from the building.</li>
<li>Captain Cano reported that Captain Araguz was approximately 15 feet inside of the building ahead of him.</li>
<li>Firefighters made entry through the exterior hole but were unsuccessful in locating Captain Araguz. Cano was escorted to the folding water tank and got into the tank to cool down.</li>
</ul>
<p><a href="http://thecompanyofficer.com/files/2011/07/7-4-2011-3-54-31-PM.jpg"><img class="aligncenter size-medium wp-image-1759" title="7-4-2011 3-54-31 PM" src="http://thecompanyofficer.com/files/2011/07/7-4-2011-3-54-31-PM-300x210.jpg" alt="" width="300" height="210" /></a></p>
<p><a href="http://thecompanyofficer.com/files/2011/07/7-4-2011-3-54-04-PM.jpg"><img class="aligncenter size-medium wp-image-1758" title="7-4-2011 3-54-04 PM" src="http://thecompanyofficer.com/files/2011/07/7-4-2011-3-54-04-PM-300x225.jpg" alt="" width="300" height="225" /></a></p>
<p>Rapid Intervention Crews (RIC) were established using mutual aid members from the Hungerford and El Campo Fire Departments. The first entry made was at the main entry door where Firefighter Maldonado was located. Maldonado was relieved and escorted to the ambulance for rehab. An evacuation horn sounded and the first RIC abandoned the interior search and exited the building.</p>
<p>A rescue entry by a second RIC was through the breached wall of Dry Storage 3. After several minutes inside, the evacuation signal sounded due to the rapidly spreading fire and deteriorating conditions. Two additional RICs entered the structure through the loading dock doors of Dry Storage 3. Chief Barnett states that there were a total of four RICs that made entry after the Mayday. After approximately 45 minutes, all rescue attempts ceased.</p>
<p>As the fire extended south toward Dry Storage 3, smoke conditions became so debilitating that Chief Barnett ordered all crews staged near the front of the building on side A to move back and apparatus to relocate. Command assigned Chief Hafer of the Richmond Fire Department to “A” side operations and defensive operations were established. Captain Cano and Firefighter Maldonado were transported to Gulf Coast Medical Center and treated for smoke inhalation.</p>
<p>Fire ground operations continued through the night. Captain Araguz was recovered at approximately</p>
<p><strong>07:40 AM</strong>. Command transferred to the Richmond Fire Department Chief Hafer at approximately</p>
<p><strong>07:56 AM </strong>as 1101 and the Wharton units escorted Captain Araguz from the scene. All Wharton units cleared the scene at <strong>08:02 AM</strong>.</p>
<p>Captain Araguz was transported to the Travis County Medical Examiner’s Office for autopsy. The Travis County Medical Examiner’s Office performed post mortem examinations on July 4, 2010. Captain Araguz died from thermal injuries and smoke inhalation.</p>
<p><strong>Findings and Recommendations </strong></p>
<ul>
<li><em>Recommendations are based upon nationally recognized consensus standards and safety practices for the fire service. </em></li>
<li><em> </em></li>
<li><em>All fire department personnel should know and understand nationally recognized consensus standards, and all fire departments should create and maintain SOGs and SOPs to ensure effective, efficient, and safe firefighting operations. </em></li>
</ul>
<p style="text-align: center;"><strong><a href="http://thecompanyofficer.com/files/2011/07/Locations1.jpg"><img class="aligncenter size-full wp-image-1762" title="Locations" src="http://thecompanyofficer.com/files/2011/07/Locations1.jpg" alt="" width="547" height="648" /></a></strong></p>
<p><strong><a href="http://thecompanyofficer.com/files/2011/07/Locations.jpg"></a></strong></p>
<p><strong>There were several factors that, when combined, may have contributed to the death of Captain Araguz. It is important that we honor him by learning from the incident.</strong></p>
<ul>
<li>Water supply became an immediate concern.</li>
<li>Although there are two water storage tanks on the facility with the combined capacity of nearly 44,000 gallons, refilling operations to tankers were slow, accomplished by gravity fill through a 5-inch connection.</li>
<li>A fire department connection attached to the plant’s main water supply pump and plant personnel familiar with the system could have sped up the refilling process at the plant.</li>
<li>Most tankers were sent to hydrants in the City of Boling 3 miles away, which in turn quickly depleted the city water supply.</li>
<li>Other tanker refilling was accomplished at hydrants on the City of Wharton water system, as far as 15 miles away.</li>
</ul>
<p>Fire protection systems are not required by <em>National Fire Protection Association (NFPA) Standard 101, Life Safety Code, 2009 Edition </em>for this classification of facility. Fire sprinkler and smoke control systems may have contained the fire to one area, preventing the spread of fire throughout the plant.</p>
<p><strong>Findings and recommendations from this investigation include:</strong></p>
<p><strong><em><span style="text-decoration: underline;"> </span></em></strong></p>
<p><span style="color: #ff0000;"><strong><em><span style="text-decoration: underline;">FINDING 1:</span></em></strong></span></p>
<p><strong><em>There were no lives to save in the building. An inadequate water supply, lack of fire protection systems in the structure to assist in controlling the spread of the smoke and fire, and the heavy fire near the windward side facilitated smoke and fire spread further into the interior and toward “A” side operations. Along with the size of the building, the large fuel load, and the time period from fire discovery, interior firefighters were at increased risk. </em></strong></p>
<p><span style="color: #ff0000;"><strong>Recommendation: </strong></span>Fire departments should develop Standard Operating Guidelines and conduct training involving risk management and risk benefit analysis during an incident according to Incident Management principles required by NFPA 1500 and 1561.</p>
<p><em>The concept of risk management shall be utilized on the basis of the following principles: </em></p>
<p><em>(a)  </em><em>Activities that present a significant risk to the safety of personnel shall be limited to situations where there is a potential to save endangered lives</em></p>
<p><em>(b) Activities that are routinely employed to protect property shall be recognized as inherent risks to the safety of personnel, and actions shall be taken to reduce or avoid these risks. </em></p>
<p><em>(c) No risk to the safety of personnel shall be acceptable where there is no possibility to save lives or property. </em></p>
<p><em>(d) In situations where the risk to fire department members is excessive, activities shall be limited to defensive operations. NFPA 1500 Chapter 8, 8.3.2 </em></p>
<p><em>NFPA 1500 ‘Standard on Fire Department Occupational Safety and Health Program’, 2007 ed., and NFPA 1561’Standard on Emergency Services Incident Management System’, 2008 ed. Texas Commission on Fire Protection Standards Manual, Chapter 435, Section 435.15 </em></p>
<p><em>(b)  </em><em>The Standard operating procedure shall: </em></p>
<p><em>(1) Specify an adequate number of personnel to safely conduct emergency scene operations; </em></p>
<p><em>(2) limit operations to those that can be safely performed by personnel at the scene; </em></p>
<p><span style="color: #ff0000;"><strong><em><span style="text-decoration: underline;">FINDING 2:</span></em></strong></span></p>
<p><strong><em>Initial crews failed to perform a 360-degree scene size-up and did not secure the utilities before operations began. </em></strong></p>
<p><span style="color: #ff0000;"><strong>Recommendation: </strong></span>Fire departments should develop Standard Operating Guidelines that require crews to perform a complete scene size-up before beginning operations. A thorough size up will provide a good base for deciding tactics and operations. It provides the IC and on-scene personnel with a general understanding of fire conditions, building construction, and other special considerations such as weather, utilities, and exposures. Without a complete and accurate scene size-up, departments will have difficulty coordinating firefighting efforts.</p>
<p><em>Fireground Support Operations 1st Edition, IFSTA, Chapter 10 Fundamentals of Firefighting Skills, </em></p>
<p><em>NFPA/IAFC, 2004, Chapter 2 </em><strong><em><span style="text-decoration: underline;"> </span></em></strong></p>
<p><span style="color: #ff0000;"><strong><em><span style="text-decoration: underline;">FINDING 3 </span></em></strong></span></p>
<p><strong>The Incident Commander failed to maintain an adequate span of control for the type of incident. Safety, personnel accountability, staging of resources, and firefighting operations require additional supervision for the scope of incident. Radio recordings and interview statements indicate the IC performing several functions including: Command, Safety, Staging, Division A Operations, Interior Operations and Scene Security. </strong></p>
<p><span style="color: #ff0000;"><strong>Recommendation: </strong></span>Incident Commanders should maintain an appropriate span of control and assign additional personnel to the command structure as needed. Supervisors must be able to adequately supervise and control their subordinates, as well as communicate with and manage all resources under their supervision. In ICS, the span of control of any individual with incident management supervisory responsibility should range from three to seven subordinates, with five being optimal. The type of incident, nature of the tasks, hazards and safety factors, and distances between personnel and resources all influence span-of-control considerations.</p>
<p><em>U.S. Department of Homeland Security &#8211; Federal Emergency Management Agency Incident Command Systems </em><span style="text-decoration: underline;">http://www.fema.gov/emergency/nims/ICSpopup.htm#item5 </span><em>NFPA 1500 Standard on Fire Department Occupational Safety and Health Program, Chapter 8</em>, 2007 ed.</p>
<p><strong><em><span style="text-decoration: underline;"> </span></em></strong></p>
<p><span style="color: #ff0000;"><strong><em><span style="text-decoration: underline;">FINDING 4 </span></em></strong></span></p>
<p><strong><em>The interior fire team advanced into the building prior to the establishment of a rapid intervention crew (RIC). </em></strong></p>
<p><span style="color: #ff0000;"><strong>Recommendation: </strong></span>Fire Departments should develop written procedures that comply with the <strong>Occupational Safety and Health Administration’s Final Rule, 29 CFR Section 1910.134 (g) </strong>(<strong>4) </strong>requiring at least two fire protection personnel to remain located outside the IDLH (Immediate Danger to Life or Health) atmosphere to perform rescue of the fire protection personnel inside the IDLH atmosphere. One of the outside fire protection personnel must actively monitor the status of the inside fire protection personnel and not be assigned other duties. <strong><em>NFPA 1500 8.8.7 </em></strong>At least one dedicated RIC shall be standing by with equipment to provide for the rescue of members that are performing special operations or for members that are in positions that present an immediate danger of injury in the event of equipment failure or collapse.</p>
<p><em>U.S. Occupational Safety and Health Administration Respiratory Protection Standard, CFR 1910.134 (g) (4); Texas Commission on Fire Protection Standards §435.17 &#8211; Procedures for Interior Structure Fire Fighting (2-in/2-out rule) NFPA 1500 Standard on Fire Department Occupational Safety and Health Program, Chapter 8, 2007 ed. NFPA 1720 Standard on Organization and Deployment Fire Suppression Operations by Volunteer Fire Departments, 2004 ed. </em><strong><em><span style="text-decoration: underline;"> </span></em></strong></p>
<p><span style="color: #ff0000;"><strong><em><span style="text-decoration: underline;">FINDING 5 </span></em></strong></span></p>
<p><strong>The interior team and Incident Commander did not verify the correct operation of communications equipment before entering the IDLH atmosphere and subsequently did not maintain communications between the interior crew and Command. Although Chief Barnett stated he communicated with Captain Cano, there was no contact with Captain Araguz. </strong></p>
<p><span style="color: #ff0000;"><strong>Recommendation: </strong></span>Fire Departments should develop written policies requiring the verification of the correct operations of communications equipment of each firefighter before crews enter an IDLH atmosphere. Fire Departments should also include training for their members on the operation of communications equipment in zero visibility conditions.</p>
<p><em>U.S. Occupational Safety and Health Administration Respiratory Protection Standard, CFR 1910.134(g)(3)(ii) NFPA 1500 Standard on Fire Department Occupational Safety and Health Program, Chapter 8</em>, 2007 ed.</p>
<p><strong><em><span style="text-decoration: underline;"> </span></em></strong></p>
<p><span style="color: #ff0000;"><strong><em><span style="text-decoration: underline;">FINDING 6 </span></em></strong></span></p>
<p><strong>The interior operating crew did not practice effective air management techniques for the size and complexity of the structure. Interviews indicate the crew expended breathing air while attempting to breach an exterior wall for approximately 10 minutes, then advanced a hose line into a 15,000 square feet room without monitoring their air supply. During interviews Captain Cano estimated his consumption limit at 15 – 20 minutes on a 45 minute SCBA. </strong></p>
<p><span style="color: #ff0000;"><strong>Recommendation</strong>:</span> Crews operating in IDLH atmospheres must monitor their air consumption rates and allot for sufficient evacuation time. Known as the point of no return, it is that time at which the remaining operation time of the SCBA is equal to the time necessary to return safely to a non-hazardous atmosphere. The three basic elements to effective air management are:</p>
<ul>
<li>Know your point of no return (beyond 50 percent of the air supply of the team member with the lowest gauge reading).</li>
<li>Know how much air you have at all times.</li>
<li>Make a conscious decision to stay or leave when your air is down to 50 percent.</li>
</ul>
<p><em>IFSTA [2008]. Essentials of Fire Fighting and Fire Department Operations, 5th ed., Chapter 5, Air Management, page 189 Fundamentals of Firefighter Skills, 2<sup>nd </sup>edition, NFPA and International Association of Fire Chiefs, Chapter 17, Fire Fighter Survival. </em></p>
<p><strong><em><span style="text-decoration: underline;"> </span></em></strong></p>
<p><span style="color: #ff0000;"><strong><em><span style="text-decoration: underline;">Finding 7</span></em></strong></span></p>
<p><strong>Captains Araguz and Cano became separated from their hoseline. While it is unclear as to the reason they became separated from the hose line, interviews with Captain Cano indicate that while he was finding an exterior wall and took actions to alert the exterior by banging and kicking the wall, he lost contact with Captain Araguz. </strong></p>
<p><strong><em>**Captain Cano credits his survival to the actions he learned from recent Mayday, Firefighter Safety training. </em></strong></p>
<p><span style="color: #ff0000;"><strong>Recommendation: </strong></span>Maintaining contact with the hose line is critical. Losing contact with the hose line meant leaving the only lifeline and pathway to safety. Team integrity provides an increased chance for survival. All firefighters should become familiar with and receive training on techniques for survival and self-rescue.<em> </em></p>
<p><em>United States Fire Administration’s National Fire Academy training course “Firefighter Safety: Calling the Mayday” Fundamentals of Firefighter Skills, 2<sup>nd </sup>edition, NFPA and International Association of Fire Chiefs, Chapter 17, Fire Fighter Survival. </em></p>
<p><span style="color: #ff0000;"><strong>Additional References Related to Surviving the Mayday and RIT operations from 2011 Safety Week at CommandSafety.com;</strong></span></p>
<p><strong><a href="http://commandsafety.com/"><img title="CommandSafety.com" src="http://thecompanyofficer.com/files/2011/06/TESTlogo-300x43.png" alt="" width="300" height="43" /></a></strong></p>
<p><strong>Day One: </strong><a title="Permanent link to Fire/EMS Safety, Health &amp; Survival Week 2011: Day One- Are You Ready?" rel="bookmark" href="http://commandsafety.com/2011/06/fireems-safety-health-survival-week-2011-day-one-are-you-ready/">Fire/EMS Safety, Health &amp; Survival Week 2011: Day One- Are You Ready?</a></p>
<p><strong>Day Two: </strong><a title="Permanent link to Fire/EMS Safety, Health and Survival Week: Day Two- Building Knowledge = Fire Fighter Safety" rel="bookmark" href="http://commandsafety.com/2011/06/fireems-safety-health-and-survival-week-day-two-building-knowledge-fire-fighter-safety/">Fire/EMS Safety, Health and Survival Week: Day Two- Building Knowledge = Fire Fighter Safety</a></p>
<p><strong>Day Three:</strong> <a title="Permanent link to Fire/EMS Safety, Health and Survival Week: Day Three-The New Rules of Engagement" rel="bookmark" href="http://commandsafety.com/2011/06/fireems-safety-health-and-survival-week-day-three-the-new-rules-of-engagement/">Fire/EMS Safety, Health and Survival Week: Day Three-The New Rules of Engagement</a></p>
<p><strong>Day Four:</strong> <a title="Permanent link to Fire/EMS Safety, Health and Survival Week: Day Four -The New Fire Ground" rel="bookmark" href="http://commandsafety.com/2011/06/fireems-safety-health-and-survival-week-day-four-the-new-fire-ground/">Fire/EMS Safety, Health and Survival Week: Day Four -The New Fire Ground</a></p>
<p><strong>Day Five:</strong> <a title="Permanent link to Fire/EMS Safety, Health and Survival Week 2011: Day Five: Near-Misses, Maydays and Floor Collapses" rel="bookmark" href="http://commandsafety.com/2011/06/fireems-safety-health-and-survival-week-2011-near-misses-maydays-and-floor-collapses/">Fire/EMS Safety, Health and Survival Week 2011: Day Five: Near-Misses, Maydays and Floor Collapses</a></p>
<p><strong>Day Six:</strong> <a title="Permanent link to Fire/EMS Safety, Health and Survival Week 2011, Day Six; From Waldbaum’s to Hackensack-Worcester to Charleston; Legacies for Operational Safety" rel="bookmark" href="http://commandsafety.com/2011/06/fireems-safety-health-and-survival-week-2011-day-six-from-waldbaum%e2%80%99s-to-hackensack-worcester-to-charleston-legacies-for-operational-safety/">Fire/EMS Safety, Health and Survival Week 2011, Day Six; From Waldbaum’s to Hackensack-Worcester to Charleston; Legacies for Operational Safety</a></p>
<p><strong>Day Seven:</strong> <a title="Permanent link to Fire/EMS Safety, Health and Survival Week 2011, Day Seven; Fire Fighter, Fire Officer and Command Training and Preparedness" rel="bookmark" href="http://commandsafety.com/2011/06/fireems-safety-health-and-survival-week-2011-day-seven-fire-fighter-fire-officer-and-command-preparedness/">Fire/EMS Safety, Health and Survival Week 2011, Day Seven; Fire Fighter, Fire Officer and Command Training and Preparedness</a></p>
<p><strong>Day Eight Plus One: </strong><a title="Permanent link to Mayday and Rapid Intervention Realities: The Phoenix Perspective" rel="bookmark" href="http://thecompanyofficer.com/2011/06/25/mayday-and-rapid-intervention-realities-the-phoenix-perspective/">Mayday and Rapid Intervention Realities: The Phoenix Perspective</a></p>
<p><a title="Permanent link to 188 Days of Opportunity to make a Difference: Surviving the Fire Ground" rel="bookmark" href="http://commandsafety.com/2011/06/days-of-opportunity-to-make-a-difference-surviving-the-fire-ground/">188 Days of Opportunity to make a Difference: Surviving the Fire Ground</a></p>
<p><strong>Other Links:</strong></p>
<ul>
<li><a href="http://www.khou.com/home/2-firefighters-injured-1-missing-after-massive-warehouse-fire-97762599.html">http://www.khou.com/home/2-firefighters-injured-1-missing-after-massive-warehouse-fire-97762599.html</a></li>
<li><a title="Fire marshal finds mistakes made in fatal Wharton County egg farm fire" rel="bookmark" href="http://www.khou.com/home/Fire-marshal-Mistakes-were-made-in-fatal-Wharton-County-egg-farm-fire-124631559.html">Fire marshal finds mistakes made in fatal Wharton County egg farm fire</a></li>
<li><a title="Raw:  Aerials over egg farm fire" rel="bookmark" href="http://www.khou.com/video/featured-videos/Raw--Aerials-over-egg-plant-fire-97776084.html">Raw: Aerials over egg farm fire</a></li>
<li><a title="Raw:  Fire captain killed battling 4-alarm blaze" rel="bookmark" href="http://www.khou.com/video/yahoo-video/Raw--Fire-captain-killed-battling-4-alarm-blaze-97776284.html">Raw: Fire captain killed battling 4-alarm blaze</a></li>
<li><a title="Egg farm fire that killed firefighter ruled accidental" rel="bookmark" href="http://www.khou.com/home/Egg-farm-fire-that-killed-firefighter-ruled-accidental-98171234.html">Egg farm fire that killed firefighter ruled accidental</a></li>
</ul>
<ul>
<li>Video: <a href="http://www.khou.com/home/2-firefighters-injured-1-missing-after-massive-warehouse-fire-97762599.html">KHOU: Wharton County fire captain killed battling 4-alarm blaze at &#8230;</a></li>
<li><a href="http://www.whartonfire.com/">Wharton, Texas Fire Department</a></li>
<li><a href="http://www.chron.com/disp/story.mpl/metropolitan/7093660.html">Chronicle: Wharton firefighter killed in massive egg plant blaze</a></li>
<li><a href="http://abclocal.go.com/ktrk/story?section=news/local&amp;id=7531334">ABC: Firefighter dies in four-alarm farm blaze</a></li>
</ul>
<p><script src="http://www.khou.com/templates/belo_embedWrapper.js?storyid=97776084&amp;pos=top&amp;swfw=470"></script><object id="bimvidplayer0" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="446" height="251" s_getdomindex="function () {      return eval(instance.CallFunction(&quot;&lt;invoke name=\&quot;&quot;+name+&quot;\&quot; returntype=\&quot;javascript\&quot;&gt;&quot; + __flash__argumentsToXML(arguments,0) + &quot;&lt;/invoke&gt;&quot;));   }" s_gettrackclickmap="function () {      return eval(instance.CallFunction(&quot;&lt;invoke name=\&quot;&quot;+name+&quot;\&quot; returntype=\&quot;javascript\&quot;&gt;&quot; + __flash__argumentsToXML(arguments,0) + &quot;&lt;/invoke&gt;&quot;));   }" s_getaccount="function () {      return eval(instance.CallFunction(&quot;&lt;invoke name=\&quot;&quot;+name+&quot;\&quot; returntype=\&quot;javascript\&quot;&gt;&quot; + __flash__argumentsToXML(arguments,0) + &quot;&lt;/invoke&gt;&quot;));   }" s_getpagename="function () {      return eval(instance.CallFunction(&quot;&lt;invoke name=\&quot;&quot;+name+&quot;\&quot; returntype=\&quot;javascript\&quot;&gt;&quot; + __flash__argumentsToXML(arguments,0) + &quot;&lt;/invoke&gt;&quot;));   }" s_getpageurl="function () {      return eval(instance.CallFunction(&quot;&lt;invoke name=\&quot;&quot;+name+&quot;\&quot; returntype=\&quot;javascript\&quot;&gt;&quot; + __flash__argumentsToXML(arguments,0) + &quot;&lt;/invoke&gt;&quot;));   }" s_getmovieid="function () {      return eval(instance.CallFunction(&quot;&lt;invoke name=\&quot;&quot;+name+&quot;\&quot; returntype=\&quot;javascript\&quot;&gt;&quot; + __flash__argumentsToXML(arguments,0) + &quot;&lt;/invoke&gt;&quot;));   }" s_getversion="function () {      return eval(instance.CallFunction(&quot;&lt;invoke name=\&quot;&quot;+name+&quot;\&quot; returntype=\&quot;javascript\&quot;&gt;&quot; + __flash__argumentsToXML(arguments,0) + &quot;&lt;/invoke&gt;&quot;));   }" s_getcharset="function () {      return eval(instance.CallFunction(&quot;&lt;invoke name=\&quot;&quot;+name+&quot;\&quot; returntype=\&quot;javascript\&quot;&gt;&quot; + __flash__argumentsToXML(arguments,0) + &quot;&lt;/invoke&gt;&quot;));   }" s_getswfurl="function () {      return eval(instance.CallFunction(&quot;&lt;invoke name=\&quot;&quot;+name+&quot;\&quot; returntype=\&quot;javascript\&quot;&gt;&quot; + __flash__argumentsToXML(arguments,0) + &quot;&lt;/invoke&gt;&quot;));   }"><param name="_cx" value="11800" /><param name="_cy" value="6640" /><param name="FlashVars" /><param name="Movie" value="http://media.bimvid.com/designvideo/bimvid_player-3_2_7.swf" /><param name="Src" value="http://media.bimvid.com/designvideo/bimvid_player-3_2_7.swf" /><param name="WMode" value="Window" /><param name="Play" value="0" /><param name="Loop" value="-1" /><param name="Quality" value="High" /><param name="SAlign" value="LT" /><param name="Menu" value="-1" /><param name="Base" /><param name="AllowScriptAccess" value="always" /><param name="Scale" value="NoScale" /><param name="DeviceFont" value="0" /><param name="EmbedMovie" value="0" /><param name="BGColor" value="000000" /><param name="SWRemote" /><param name="MovieData" /><param name="SeamlessTabbing" value="1" /><param name="Profile" value="0" /><param name="ProfileAddress" /><param name="ProfilePort" value="0" /><param name="AllowNetworking" value="all" /><param name="AllowFullScreen" value="true" /></object><script src="http://www.khou.com/templates/belo_embedWrapper.js?storyid=97776084&amp;pos=bottom"></script></p>
<p><embed id="otvPlayer" type="application/x-shockwave-flash" width="400" height="268" src="http://cdn.abclocal.go.com/static/flash/embeddedPlayer/swf/otvEmLoader.swf?version=&amp;station=ktrk&amp;section=&amp;mediaId=7530805&amp;cdnRoot=http://cdn.abclocal.go.com&amp;webRoot=http://abclocal.go.com&amp;configPath=/util/&amp;site=" allowfullscreen="true" allownetworking="all" allowscriptaccess="always"></embed></p>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://thecompanyofficer.com/2011/07/04/texas-captain-2010-lodd-report-issued-with-lessons-learned/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://thecompanyofficer.com/2011/07/04/texas-captain-2010-lodd-report-issued-with-lessons-learned/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Front Seat Responsibilities; On Both the LEFT and RIGHT Sides</title>
		<link>http://thecompanyofficer.com/2011/06/11/front-seat-responsibilities-on-both-the-left-and-right-sides/</link>
		<comments>http://thecompanyofficer.com/2011/06/11/front-seat-responsibilities-on-both-the-left-and-right-sides/#comments</comments>
		<pubDate>Sat, 11 Jun 2011 18:30:58 +0000</pubDate>
		<dc:creator>Christopher Naum</dc:creator>
				<category><![CDATA[Attitude]]></category>
		<category><![CDATA[christopher naum]]></category>
		<category><![CDATA[Commandsafety.com]]></category>
		<category><![CDATA[company officer]]></category>
		<category><![CDATA[Crew Integrity]]></category>
		<category><![CDATA[Crew Management]]></category>
		<category><![CDATA[Fire Fighter Safety]]></category>
		<category><![CDATA[firefighting-operations]]></category>
		<category><![CDATA[Health and Safety]]></category>
		<category><![CDATA[apparatus driving]]></category>
		<category><![CDATA[Apparatus engineer]]></category>
		<category><![CDATA[fire truck]]></category>
		<category><![CDATA[thecompanyofficer.com]]></category>

		<guid isPermaLink="false">http://thecompanyofficer.com/?p=1703</guid>
		<description><![CDATA[


Front Seat Responsibilities Artwork by Paul Combs All Rights Reserved


 A few days ago I posted an article entitled here on TCO: Front Seat Responsibilities; On Both the LEFT and RIGHT [...]]]></description>
			<content:encoded><![CDATA[<div class="mceTemp mceIEcenter" style="text-align: center;">
<dl id="attachment_1704" class="wp-caption aligncenter" style="width: 529px;">
<dt class="wp-caption-dt"><a href="http://thecompanyofficer.com/files/2011/06/COMBSNoTimeToStop2.jpg"><img class="size-full wp-image-1704  " title="COMBSNoTimeToStop" src="http://thecompanyofficer.com/files/2011/06/COMBSNoTimeToStop2.jpg" alt="" width="519" height="415" /></a></dt>
<dd class="wp-caption-dd">Front Seat Responsibilities Artwork by Paul Combs All Rights Reserved</dd>
</dl>
</div>
<p> A few days ago I posted an article entitled here on TCO: <strong>Front Seat Responsibilities; On Both the LEFT and RIGHT Sides</strong>, however the original article was lost as a result of the site’s melt down on Friday; thus resulting in the loss of the posting (which I didn’t save-anywhere).</p>
<p>Thus, we have a more subdued post and insights in response to the publication and media attention brought forward from Orange County (FLA) fire and Rescue with the release of a video clip depicting less that desirable defensive driving techniques and questionable public relations and sensitivity. The media clip shows Orange County (FLA) Fire Rescue Engine 58 while enroute to a reported MVA with entrapment becomes embroiled in a vivid example of fire truck road rage with a POV which almost contributed to an accident and loss of control of the apparatus and the potential for serious repercussions to the entire crew of the engine. The mounted dash cam within the cab of the engine captures the entire event and provides a shining example of what NOT to do while engaged in emergency response OR what to emulate in the form of company officer leadership.</p>
<p style="text-align: center;"><embed style="width: 583px; height: 342px;" type="application/x-shockwave-flash" width="583" height="342" src="http://www.youtube.com/v/8IZLvk4yKVM?version=3" allowfullscreen="true" allowscriptaccess="always"></embed></p>
<p>In the video, the apparatus drive and the company officer can be seen tailgating a car and continuously trying to alert the driver by using the horn over and over again, even with the sirens blaring.</p>
<p>Fire officials said the apparatus driver could have veered into the other two lanes, which were open, to avoid confrontation, but instead he tried to cut off the driver of the car while dash cameras caught officer flipping off the driver.</p>
<p>The Orange County Fire Department said Fire Fighter David Jordan and Lt. Thomas Veal were caught on the dash cameras of the fire truck driving recklessly, hitting a curb and giving a driver the middle finger. FF Jordan, the driver of Engine 58 who had been with the Orange County Fire Department for 22 years, was fired and Lt. Veal was demoted.</p>
<p>The Orange County Fire Department stated, &#8220;If this car in the video would have stopped he would have no choice but to run the vehicle into the back of the car,&#8221; a fire official said. The Fire Department said it is apologizing for the bad behavior of the two firefighters. &#8220;It&#8217;s at the point where he put the community at risk and his crew,&#8221; the official said. A Division Fire Chief said it&#8217;s the closest thing to road rage he&#8217;s ever seen from a firefighter. &#8220;I don&#8217;t know what the actual road rage definition is, but would I say it&#8217;s overly aggressive? Yes. We&#8217;re not going to tolerate that here,&#8221; said Orange County Fire and Rescue Division Chief Brian Morrow. &#8220;(They&#8217;re) very, very lucky (it was) a near miss. They didn&#8217;t roll the truck and they never would have made it to the call.&#8221;</p>
<p>The video also showed FF Jordan running over a curb at 40 miles per hour and then the fire truck swerving back into the lane as it continued to respond to the emergency.</p>
<p>&#8220;We are very lucky for what we call a near miss. They didn&#8217;t roll the truck, and they never would have made it to the call,&#8221; the official said. There was a compliment of a four firefighters on the apparatus at the time of the event. Officials said the video also showed Lt. Veal not wearing a seat belt. This was the second time the company officer was found not wearing his seat belt.<strong> </strong></p>
<p style="width: 450px;"><a href="http://www.myfoxorlando.com/dpp/news/orange_news/060811-firefighter-demoted-after-road-rage-caught-on-tape">Firefighter demoted after road rage caught on tape: MyFoxORLANDO.com</a></p>
<p style="text-align: center;"> <embed type="application/x-shockwave-flash" width="300" height="450" src="http://orlandosentinel.vid.trb.com/player/PaperVideoTest.swf" salign="l" flashvars="&amp;titleAvailable=true&amp;playerAvailable=true&amp;searchAvailable=false&amp;shareFlag=N&amp;singleURL=http://orlandosentinel.vidcms.trb.com/alfresco/service/edge/content/fa9405de-bb53-4ac4-bc3e-e7bfb57d6a06&amp;propName=orlandosentinel.com&amp;hostURL=http://www.orlandosentinel.com&amp;swfPath=http://orlandosentinel.vid.trb.com/player/&amp;omAccount=tribglobal&amp;omnitureServer=orlandosentinel.com" allowscriptaccess="always" allowfullscreen="true" menu="true" bgcolor="#ffffff" devicefont="false" wmode="transparent" scale="showall" loop="true" play="true" quality="high" align="middle" name="PaperVideoTest"></embed></p>
<p> </p>
<p>We often talk about the responsibilities of riding the seat; which is typically in reference to the right front or Officer&#8217;s Seat. But in reality; Front Seat Responsibilities; On Both the LEFT and RIGHT Sides of the apparatus cab are paramount, integrated and shared. It is the ultimate responsibility of the company officer (assigned, acting or covering) to monitor, control and provide leadership in the conduct of all operations of the company; its crew, the apparatus and its subsequent operations and tasks.</p>
<p>It also is the obligation, requirement and duty of the Apparatus Driver (Chauffeur, engineer, operator) to operate, control and drive the apparatus safely with due diligence, defensively and conscientiously. What the driver does or doesn’t do will affect the entire riding crew as will the commissions, omissions and derelictions of the company officer.  </p>
<p>It would be naive to think the occurrence depicted from Orange County Fire and Rescue is an isolated instance.  This type of behavior and driving habits has occurred and is occurring in other organizations around the country to varying degrees.</p>
<p>Some under the radar and obscured; in others, obviously apparent and blatantly condoned.  Just look at state and national firefighter injury and LODD statistics to see our track record related to apparatus response, operations and driving.  More importantly; look at your own company, department or crew.</p>
<p>For the driver and officer of Orange County Fire and Rescue Engine 58; they just “didn’t get it”. In most organizations, the Company officer and Apparatus Engineer; “Do Get it”. The leadership of Orange County Fire &amp; Rescue took prompt actions to address the seriousness of the issues resulting from this event.</p>
<p>Let’s learn from this incident, look for opportunities and ways to enhance and improve our Front Seat Responsibilities; from supervisory actions, accountability and leadership, to defensive driving, safety conscious behaviors and attitudes, safer emergency response methods and improved and directed responsibilities towards our entire crew and the public at-large.  The next time you’re riding the seat or behind the wheel- think about what’s going on as you make your way in response to that incident or returning to quarters. What are you doing to maintain the safety of your company and contribute towards the safety of the public we are sworn to serve.</p>
<ul>
<li><strong>The Front Seat Responsibilities are on both the left and right sides of the cab and must be shared.</strong></li>
<li><strong> And, are also in the seats riding backwards (buckling up).</strong></li>
<li><strong>The question is; “Do YOU get it?”</strong></li>
</ul>
<p><strong>Links and Resources</strong></p>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://thecompanyofficer.com/2011/06/11/front-seat-responsibilities-on-both-the-left-and-right-sides/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://thecompanyofficer.com/2011/06/11/front-seat-responsibilities-on-both-the-left-and-right-sides/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Survivability Profiling: Taking it to the Streets</title>
		<link>http://thecompanyofficer.com/2011/04/16/survivability-profiling-taking-it-to-the-streets/</link>
		<comments>http://thecompanyofficer.com/2011/04/16/survivability-profiling-taking-it-to-the-streets/#comments</comments>
		<pubDate>Sun, 17 Apr 2011 03:11:24 +0000</pubDate>
		<dc:creator>Christopher Naum</dc:creator>
				<category><![CDATA[building construction]]></category>
		<category><![CDATA[Buildingsonfire.com]]></category>
		<category><![CDATA[christopher naum]]></category>
		<category><![CDATA[Commandsafety.com]]></category>
		<category><![CDATA[company officer]]></category>
		<category><![CDATA[Crew Integrity]]></category>
		<category><![CDATA[Crew Management]]></category>
		<category><![CDATA[Fire Fighter Safety]]></category>
		<category><![CDATA[Fire Suppression]]></category>
		<category><![CDATA[firefighter-safety-health]]></category>
		<category><![CDATA[firefighting-operations]]></category>
		<category><![CDATA[Research]]></category>
		<category><![CDATA[Risk Assessment]]></category>
		<category><![CDATA[Situational Awareness]]></category>
		<category><![CDATA[Strategy and Tactics]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Adaptive Fireground Management]]></category>
		<category><![CDATA[Building Constrution for the Fire Service Chris Naum]]></category>
		<category><![CDATA[Buildingonfire.com]]></category>
		<category><![CDATA[Can They Be Saved? Utilizing Civilian Survivability Profiling to Enhance Size-Up and Reduce Firefighter Fatalities in the Fire Department]]></category>
		<category><![CDATA[Captain STEPHEN MARSAR FDNY]]></category>
		<category><![CDATA[Chris Naum]]></category>
		<category><![CDATA[City of New York]]></category>
		<category><![CDATA[Emerging Fire Suppression Theory]]></category>
		<category><![CDATA[Executive Fire Officer Program]]></category>
		<category><![CDATA[FDNY]]></category>
		<category><![CDATA[Fire]]></category>
		<category><![CDATA[fire behavior]]></category>
		<category><![CDATA[Fire Dynamics]]></category>
		<category><![CDATA[fire dynamics and fire behavior]]></category>
		<category><![CDATA[fire ground operations]]></category>
		<category><![CDATA[Fire Research]]></category>
		<category><![CDATA[Firefighternetcast.com]]></category>
		<category><![CDATA[National Fire Academy's 2010 Annual Outstanding Research Award]]></category>
		<category><![CDATA[STEPHEN MARSAR]]></category>
		<category><![CDATA[Survivability Profiling]]></category>
		<category><![CDATA[Tactical Patience]]></category>
		<category><![CDATA[Taking it to the Streets Radio Program]]></category>
		<category><![CDATA[Taking it to the Streets with Christopher Naum]]></category>
		<category><![CDATA[the IAFC ROE]]></category>
		<category><![CDATA[The Rules of Fire Engagement]]></category>
		<category><![CDATA[thecompanyofficer.com]]></category>

		<guid isPermaLink="false">http://thecompanyofficer.com/?p=1522</guid>
		<description><![CDATA[Live and Online Taking it to the Streets with your host Christopher Naum will present another timely and insightful look at an emerging element of today&#8217;s evolving fire ground.
 
 
Join in [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_2178" class="wp-caption alignleft" style="width: 580px"><a href="http://commandsafety.com/files/2011/04/4-16-2011-9-00-48-PM.jpg"><img class="size-full wp-image-2178  " title="4-16-2011 9-00-48 PM" src="http://commandsafety.com/files/2011/04/4-16-2011-9-00-48-PM.jpg" alt="" width="570" height="404" /></a><p class="wp-caption-text">Live Online April 20th at 9pm ET</p></div>
<div class="mceTemp"><span style="color: #ff0000;"><strong>Live and Online Taking it to the Streets with your host Christopher Naum will present another timely and insightful look at an emerging element of today&#8217;s evolving fire ground.</strong></span></div>
<div class="mceTemp"><span style="color: #ff0000;"><strong> </strong></span></div>
<div class="mceTemp"><span style="color: #ff0000;"><strong> </strong></span></div>
<div class="mceTemp"><span style="color: #000000;">Join in on <strong>Wednesday April 20th at 9pm ET</strong> for a very special and exciting program discussing the concepts and theory of </span><strong>Survivability Profiling.</strong></div>
<div class="mceTemp"><strong> </strong></div>
<div class="mceTemp">Joing the program will be special guest, <strong><a href="http://www.nyc.gov/html/fdny/html/events/2011/040411a.shtml">Captain Stephen Marsar</a></strong>, FDNY assigned to Engine Co. 8 in the <a href="http://www.carolinasfirepage.com/fr_template05.htm">Third Division</a>, Manhattan, NYC.</div>
<div class="mceTemp">Captain Marsar, FDNY has researched and developed insights into the theory and application of <strong>Survivability Profiling</strong>.</div>
<div class="mceTemp">The Department of Homeland Security&#8217;s U.S. Fire Administration announced on April 4 that Capt. Stephen Marsar, Engine 8, is one of three fire service executives from across the country who was selected to receive the National Fire Academy&#8217;s 2010 Annual Outstanding Research Award.</div>
<div class="mceTemp">
<p>The award recognizes Executive Fire Officer Program students for exceptional research projects.</p>
<p>Capt. Marsar&#8217;s project, titled<em> Can They Be Saved? Utilizing Civilian Survivability Profiling to Enhance Size-Up and Reduce Firefighter Fatalities in the Fire Department, City of New York</em>, was selected as the Executive Leadership Course award winner. The National Fire Academy said it was chosen from among the more than 60 Applied Research Projects submitted this year, the highest number in the program&#8217;s 26-year history.</p>
<p>The Executive Fire Officer Program provides senior fire officers with information and education on various facets of fire administration. After a four-year course of study, participants are required to complete an applied research project that attempts to resolve a problem in their own organization.</p>
<p>View Capt. Marsar&#8217;s project: <a href="http://www.usfa.dhs.gov/pdf/efop/efo44310.pdf">http://www.usfa.dhs.gov/pdf/efop/efo44310.pdf</a></p>
<p>Grab a cup of coffee and sit down for a special one hour program with Taking it to the Streets on FirefighterNetcast.com where we’ll be discussing the concept, research and application of Survivability Profiling with Captain Marsar and the manner in which it might be implemented in today&#8217;s emerging and evolving fire ground operational methodologies with Christopher Naum and this outstanding fire service leader.</p>
<div id="attachment_2184" class="wp-caption alignleft" style="width: 206px"><a href="http://commandsafety.com/files/2011/04/4-16-2011-9-15-20-PM.jpg"><img class="size-medium wp-image-2184" title="4-16-2011 9-15-20 PM" src="http://commandsafety.com/files/2011/04/4-16-2011-9-15-20-PM-245x300.jpg" alt="" width="196" height="240" /></a><p class="wp-caption-text">Capt. Stephen Marsar, FDNY</p></div>
<p><span style="color: #ff0000;"><strong>STEPHEN MARSAR </strong></span>is a captain in the Fire Department of New York, covering in Engine Company 8 in Manhattan. He has previously served in Engine Company 16 and Ladder Companies 7 and 11. An ex-commissioner in the Bellmore (NY) Fire Department, he has certifications as a national and New York State fire instructor, NY instructor coordinator, and NY State Department of Health regional faculty member.</p>
<p>He serves on the adjunct faculty for the Nassau Community College, NY Fire Science Degree Program, and teaches for the FDNY and Nassau County, Long Island, Fire and EMS academies. He has a bachelor’s degree in fire science and emergency services administration and is enrolled in the Executive Fire Officer Program at the National Fire Academy.</p>
<p><strong>Taking it to the Streets<sup>TM</sup></strong> is a monthly radio show featured on BlogTalk Radio and is hosted by Christopher Naum and is a <a href="http://buildingsonfire.com/">Buildingsonfire.com</a> Series and <a href="http://firefighternetcast.com/">FireFighternetcast.com</a> Production, © 2011 All Rights Reserved</p>
<p>Join in on the live open discussion with other fire service personnel from around the country. Check out the latest <a href="http://www.firefighternetcast.com/category/our-shows/taking-it-to-the-streets-our-shows/">downloads</a> of recent programs in the archives by visiting Taking it to the Street’s webpage on <a href="http://www.firefighternetcast.com/our-shows/taking-it-to-the-streets/">Firefighternetcast.com</a> or for program insights at <a href="http://commandsafety.com/blogradio/">CommandSafety.com.</a></p>
<ul>
<li><strong>Tune in to the Program Wednesday evening April 20<sup>th</sup> at 9:00 pm ET, </strong><a href="http://www.blogtalkradio.com/firefighternetcast"><strong>HERE</strong></a></li>
<li><strong>Firefighternetcast.com </strong><a href="http://www.firefighternetcast.com/"><strong>HERE</strong></a></li>
<li><strong>Taking it to the Streets Radio Programs, </strong><a href="http://www.firefighternetcast.com/our-shows/taking-it-to-the-streets/"><strong>HERE</strong></a><strong> and </strong><a href="http://commandsafety.com/blogradio/"><strong>HERE</strong></a></li>
</ul>
</div>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://thecompanyofficer.com/2011/04/16/survivability-profiling-taking-it-to-the-streets/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://thecompanyofficer.com/2011/04/16/survivability-profiling-taking-it-to-the-streets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>First-Due Arriving Companies; Are You Prepared?</title>
		<link>http://thecompanyofficer.com/2010/11/23/first-due-arriving-companies-are-you-prepared/</link>
		<comments>http://thecompanyofficer.com/2010/11/23/first-due-arriving-companies-are-you-prepared/#comments</comments>
		<pubDate>Tue, 23 Nov 2010 17:45:35 +0000</pubDate>
		<dc:creator>Christopher Naum</dc:creator>
				<category><![CDATA[building construction]]></category>
		<category><![CDATA[Buildingsonfire.com]]></category>
		<category><![CDATA[christopher naum]]></category>
		<category><![CDATA[Commandsafety.com]]></category>
		<category><![CDATA[Crew Management]]></category>
		<category><![CDATA[Fire Dynamics]]></category>
		<category><![CDATA[Fire Suppression]]></category>
		<category><![CDATA[firefighting-operations]]></category>
		<category><![CDATA[Strategy and Tactics]]></category>
		<category><![CDATA[Taking it to the Streets]]></category>
		<category><![CDATA[building construction principles]]></category>
		<category><![CDATA[Commandsafety]]></category>
		<category><![CDATA[Dave Statter]]></category>
		<category><![CDATA[Dynamic Risk Assessment]]></category>
		<category><![CDATA[fire behavior]]></category>
		<category><![CDATA[firefighting]]></category>
		<category><![CDATA[Fireground Operations]]></category>
		<category><![CDATA[first-due fire officer]]></category>
		<category><![CDATA[First-Due Officer responsibilities]]></category>
		<category><![CDATA[flashover]]></category>
		<category><![CDATA[ironfireman.com]]></category>
		<category><![CDATA[NIOSH Reports]]></category>
		<category><![CDATA[occupancy risk]]></category>
		<category><![CDATA[risk profile]]></category>
		<category><![CDATA[Rules of Engagement of Structural Firefighting]]></category>
		<category><![CDATA[Statter911]]></category>
		<category><![CDATA[strategies and Tactics]]></category>
		<category><![CDATA[tactical]]></category>
		<category><![CDATA[Tactical Patience]]></category>
		<category><![CDATA[taking it to the streets radio]]></category>
		<category><![CDATA[The First Due Fire Company]]></category>
		<category><![CDATA[thecompanyofficer.com]]></category>
		<category><![CDATA[Willie Wines]]></category>

		<guid isPermaLink="false">http://thecompanyofficer.com/?p=916</guid>
		<description><![CDATA[

As the First-Due Fire Company; Officer and crew, Are you prepared to address the fireground variables and occupancy risks upon your arrival and during the initial stages of your deployment [...]]]></description>
			<content:encoded><![CDATA[<div class="mceTemp mceIEcenter" style="text-align: left;"><a href="http://thecompanyofficer.com/files/2010/11/FirstduePrepared2.jpg"><img class="aligncenter size-full wp-image-950" title="FirstduePrepared" src="http://thecompanyofficer.com/files/2010/11/FirstduePrepared2.jpg" alt="" width="410" height="343" /></a></div>
<p style="text-align: center;">
<div class="mceTemp mceIEcenter" style="text-align: left;">As the First-Due Fire Company; Officer and crew, Are you prepared to address the fireground variables and occupancy risks upon your arrival and during the initial stages of your deployment and operations? Are you combat ready or passively engaged?  </div>
<p style="text-align: left;">It seems we’ve struck some interests over past week since we first discussed the First-Due Fire Officer  on the most recent edition of <a href="http://commandsafety.com/blogradio/"><strong>Taking it to the Streets</strong></a><strong><sup>TM </sup></strong>where we had a vibrant and insightful program in which we discussion some of the expansive facets related to the <strong>First-Due Fire Officer.</strong>     </p>
<p style="text-align: left;"> The <strong>First-Due Fire Office program</strong> can be downloaded<strong> <a href="http://www.firefighternetcast.com/category/our-shows/taking-it-to-the-streets-our-shows/">HERE</a></strong> at <a href="http://www.firefighternetcast.com/">Firefighter Netcast.com</a>   </p>
<p style="text-align: left;">The formulative discussion revolved around a variety of functional elements, traits, responsibilities and duties befalling the First-Due Officer, and was followed up with a post here on Thecompanyoffer.com. We discussed how today’s First-Due Officer must perform smarter with increased perceptions, discernments and acumens with intelligence and wisdom that is drawn from further progressing and collective fire ground response and operational experiences.   </p>
<p style="text-align: left;">My good friend Captain Willie Wines (aka The <a href="http://ironfiremen.com/">Iron Fireman</a>) posted a great follow-up article associated with the radio program on his blog associated with further interpretations of the First-Due Officer. Check out &#8220;The First-Due Officer; What are you thinking?&#8221;  <a href="http://ironfiremen.com/2010/11/the-first-due-officer-what-are-you-thinking/"><strong>HERE</strong>.</a>   </p>
<p style="text-align: left;">To further our dialog on the first-due, I’ve added a few series of video clips and images with related links to promote and stimulate your view of the first-due fireground scene as it relates to the variables and personnel perceptions; the need for diligence and cognitive situational awareness and risk assessment and being truly “prepared” both mentally and physically. By way of physically, I mean- is your gear and PPE, functional, operational and adequately in-place?   </p>
<p style="text-align: left;">  As you can see there are numerous instances where the difference in the incident outcome correlated to the level of PPE protection that was in-place and implemented at the time of adverse conditions or unexpected or unforeseen circumstances.   </p>
<p style="text-align: left;"> Here’s today’s situations to think about at the station, around the kitchen table, over a cup of coffee in the day room after your next alarm or tonight at the station for a “back step” company drill.    </p>
<ul style="text-align: left;">
<li><strong><span style="color: #888888;">What are the Adverse Conditions that might be encounted upon arrival as the First-Due?</span></strong></li>
<li><strong><span style="color: #888888;">Flashover, Backdraft, Compromised or degraded Structural Conditions, Collapsed Conditions, Structural Collapse, Wind Drive Fire Behavior, Extreme Fire Behavior, Pre-Flashover/ Post-Flashover&#8230;.</span></strong></li>
<li><strong><span style="color: #888888;">How Effective are you in Reading the Smoke?</span></strong></li>
<li><strong><span style="color: #888888;">How About Reading the Building? Do you understand Occupancy Profiling and Occupancy Risk?</span></strong></li>
<li><strong><span style="color: #888888;">Are you Taking the Time to Read the Subtle or Pronounced Fireground Indicators.; Comprehend their meaning or are you just &#8220;too engaged in the tactic or task?&#8221;</span></strong></li>
<li style="text-align: left;"><strong><span style="color: #888888;">Do you have an appreciation for Tactical Patience?</span></strong></li>
<li style="text-align: left;"><strong><span style="color: #888888;">Are your operations Tactically Driven by SOP&#8217;s and SOGs?</span></strong></li>
<li style="text-align: left;"><strong><span style="color: #888888;">What Rules of Engagment are you considering?</span></strong></li>
<li style="text-align: left;"><strong><span style="color: #888888;">Have and IAP in mind?</span></strong></li>
</ul>
<div style="text-align: left;"> <p><a href="http://thecompanyofficer.com/2010/11/23/first-due-arriving-companies-are-you-prepared/"><em>Click here to view the embedded video.</em></a></p>   </div>
<p style="text-align: left;"> There have been a lot of articles and postings on adverse conditions as companies are opening up or pushing into the structure on the initial entry. Take a look at the next two series of video clips related to flashover conditions and the impact of that fire behavior on the companies and personnel. In each instance companies were extremely fortunate that the injuries sustained were not more severe than encountered.  </p>
<ul style="text-align: left;">
<li><span style="color: #888888;"><strong>What encounters have you or your company experienced?</strong></span></li>
<li><span style="color: #888888;"><strong>In retrospect how effective was the initial risk assessment and occupancy profile-was the size-up appropriate or were key indicators missed or neglected?</strong></span></li>
<li><span style="color: #888888;"><strong>Did the fast pace of the initial arrival and subsequent deployment filter or obscure mission critical indicators that should have been identified and acted upon?  </strong></span></li>
<li><span style="color: #888888;"><strong>Did the tactical assignment and task overshadow tactical patience?</strong></span></li>
<li><span style="color: #888888;"><strong>Did someone or everyone miss reading the smoke, fire or occupancy risk?</strong></span></li>
<li><span style="color: #888888;"><strong>Did other tactical assignments contribute toward the unexpected or adverse conditions encountered, such as ventilation induced flashover? ( More on that topic for a later post; See Taking it the Streets November 4, 2010 show</strong></span></li>
</ul>
<p style="text-align: left;">    <object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="300" height="450" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="name" value="PaperVideoTest" /><param name="bgcolor" value="#ffffff" /><param name="align" value="middle" /><param name="flashvars" value="&amp;titleAvailable=true&amp;playerAvailable=true&amp;searchAvailable=false&amp;shareFlag=N&amp;singleURL=http://ktxl.vidcms.trb.com/alfresco/service/edge/content/94ae891b-cfb5-41cf-92da-014b2bbf98da&amp;propName=ktxl.com&amp;hostURL=http://www.fox40.com&amp;swfPath=http://ktxl.vid.trb.com/player/&amp;omAccount=tribglobal&amp;omnitureServer=fox40.com" /><param name="src" value="http://ktxl.vid.trb.com/player/PaperVideoTest.swf" /><param name="wmode" value="transparent" /><param name="allowfullscreen" value="true" /><param name="quality" value="high" /><embed type="application/x-shockwave-flash" width="300" height="450" src="http://ktxl.vid.trb.com/player/PaperVideoTest.swf" flashvars="&amp;titleAvailable=true&amp;playerAvailable=true&amp;searchAvailable=false&amp;shareFlag=N&amp;singleURL=http://ktxl.vidcms.trb.com/alfresco/service/edge/content/94ae891b-cfb5-41cf-92da-014b2bbf98da&amp;propName=ktxl.com&amp;hostURL=http://www.fox40.com&amp;swfPath=http://ktxl.vid.trb.com/player/&amp;omAccount=tribglobal&amp;omnitureServer=fox40.com" allowfullscreen="true" bgcolor="#ffffff" wmode="transparent" quality="high" align="middle" name="PaperVideoTest"></embed></object>      </p>
<p style="text-align: left;">
<p style="text-align: center;">
<div id="attachment_922" class="wp-caption aligncenter" style="width: 378px"><a href="http://thecompanyofficer.com/files/2010/11/flashoverNC.jpg"><img class="size-full wp-image-922 " title="flashoverNC" src="http://thecompanyofficer.com/files/2010/11/flashoverNC.jpg" alt="" width="368" height="270" /></a><p class="wp-caption-text">Firefighter Will Gregory exits the home with his PPE on fire. Photo by Brian Haney, The Daily Record.</p></div>
<p style="text-align: left;">There are a series of photos  from a previous posting at STATter911 <a href="http://statter911.com/2009/12/17/special-to-statter911-com-must-see-series-of-photos-of-flashover-that-ignites-firefighters-gear-the-story-from-erwin-north-carolina/">HERE</a> that depicts firefighers working to push-in on a fire in a small residential occupancy. The ensuing flashover ignites the PPE of one firefighter. Look at the series of photographs and  take note of the fire and smoke conditions, the size and profile of the occupancy ( remember it&#8217;s Occupancy RISK not Occupancy Type).   </p>
<ul style="text-align: left;">
<li><strong><span style="color: #ff0000;">Think about the sequencing of your initial operations. </span></strong></li>
<li><strong><span style="color: #ff0000;">Think about the mission critical 360; </span></strong></li>
<li><strong><span style="color: #ff0000;">how does that play into your initial incident actions plan (IAP)?</span></strong></li>
</ul>
<p style="text-align: left;"><strong> </strong>  </p>
<p class="mceTemp mceIEcenter" style="text-align: left;">
<dl id="attachment_939" class="wp-caption aligncenter" style="width: 546px;">
<dt class="wp-caption-dt"><a href="http://thecompanyofficer.com/files/2010/11/FlashoversequenceHouse1.jpg"><img class="size-full wp-image-939  " title="FlashoversequenceHouse" src="http://thecompanyofficer.com/files/2010/11/FlashoversequenceHouse1.jpg" alt="" width="536" height="341" /></a></dt>
<dd class="wp-caption-dd">The Dynamics of the Fireground in Seconds</dd>
</dl>
<p style="text-align: left;">Companies were dispatched for an assignment for a house fire. Both E807 and TK807 responded with crews of 4 personnel each. E813 arrived on the scene and reported light smoke showing on side Alpha. Upon arrival on the scene, the crew from TK807 (four staff) made entry to the house. The following series of events led to conditions in the house that presented a flashover environment. The hose line from E813 burst, a backup line was not charged due to no established water supply, and the house was not yet ventilated. Without the protection of a hose line, the crew was committed to the house when the room flashed. One firefighter was apparently far enough in the house to avoid any injury, A second FF received 2nd degree burns to his right shoulder, and a third FF received the full force of the flashover suffering second-third degree burns to his face, hands, and the majority of his torso. (Original incident information posted at the time of the event)   </p>
<ul>
<li> <strong><span style="color: #ff0000;">Photo 1:</span> Firefighters don PPE and SCBA with light smoke visible in this first of four pictures shot by Tony George of PGFD Station 813  </strong></li>
<li><strong> <span style="color: #ff0000;">Photo 2</span>: Six seconds later a small amount of fire and darker smoke can be seen at the sliding glass door. </strong></li>
<li><strong> <span style="color: #ff0000;">Photo3:</span> Forty-eight seconds after the initial picture, more fire and darker smoke are apparent. </strong></li>
<li><strong> <span style="color: #ff0000;">Photo 4:</span> Exactly two-minutes after the first picture was shot, flashover occurs with firefighters inside. </strong></li>
</ul>
<p>For a complete narrative and futher incident details of this previous <strong>STATter911 postings related to this event go </strong><a href="http://statter911.com/2008/11/21/two-prince-georges-county-md-firefighters-burned-in-flashover/"><strong>HERE,</strong></a><strong> and </strong><a href="http://statter911.com/2008/11/21/series-of-pictures-shows-how-quickly-conditions-deteriorated-at-maryland-fire-that-left-a-firefighter-seriously-burned/"><strong>HERE</strong></a><strong> </strong> </p>
<p>Take a good look at the performance of PPE when utilized and implemented correctly&#8230;. </p>
<p style="text-align: left;">Don&#8217;t ever underestimate the dynamics and uncertainty of the evolving fireground during your operations. The video clip here depicts how quickly operations can change from an investigation to a major mass casualty incident.</p>
<p style="text-align: left;">For a comprehensive look at this event go here are two links for you to visit, <a href="http://commandsafety.com/2010/03/shopping-center-explosion-fluid-risk-assessment/">HERE</a> at Commandsafety.com and the <a href="http://www.cdc.gov/niosh/fire/reports/face200913.html">NIOSH Report HERE</a></p>
<p style="text-align: left;">
<object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="480" height="385" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/OARnApeVkro?fs=1&amp;hl=en_US" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="480" height="385" src="http://www.youtube.com/v/OARnApeVkro?fs=1&amp;hl=en_US" allowfullscreen="true" allowscriptaccess="always"></embed></object>     </p>
<div class="mceTemp mceIEcenter" style="text-align: left;">Be prepared for the unexpected and always use extreme caution and heightened situational awareness and fluid risk assessment and reconnaissance processing to stay atop of any undefined and evolving incident. Do not allow the potential lack of severity; of what may have all the indications of an unremarkable/uneventful and common call run such as a gas odor investigation or a natural gas leak cause your companies to have less than a high level of alert, focus and attentive accretions through all phases and deployments of the incident. <strong>Don’t become complacent.</strong></div>
<p class="mceTemp mceIEcenter" style="text-align: left;"><strong>In addition, take a look at some</strong> information relate to another tragic incident response to a reported gas leak that occurred in December, 1983 that lead to five fire fighter LODD’s in Buffalo, New York. <a href="http://commandsafety.com/2009/12/buffalo-box-191-north-division-december-27-1983/">HERE</a> </p>
<div class="mceTemp mceIEcenter" style="text-align: left;">
<ul>
<li>Archived Report From STATter911, from May, 2009 <a href="http://www.wusa9.com/news/columnist/blogs/2009/05/5-firefighters-and-1-gas-company.html">HERE</a> and recent 2010 update <a href="http://statter911.com/2010/03/18/niosh-report-on-prince-georges-county-shopping-center-natural-gas-explosion-cites-sogs-rit-and-staffing/">HERE</a> with fireground Audio</li>
<li>Prince George’s County (MD) Fire Press Release from May 7, 2009, <a href="http://cms.princegeorgescountymd.gov/FireEMSNews/default.aspx?itemid=989">HERE</a></li>
<li>Slide Show from WUSA9.com <a href="http://www.wusa9.com/9slideshows/Gas_Explosion/">HERE</a> </li>
<li>BING mapping Images, <a href="http://www.bing.com/maps/#JnE9eXAuRG9ubmVsbCtEcml2ZStGb3Jlc3R2aWxsZSUyYytNRCU3ZXNzdC4wJTdlcGcuMSZiYj0zOC44NDU1Mjk4NDEyNzU1JTdlLTc2Ljg4MjI0NTI5NjQ0NzclN2UzOC44NDM1MjMzNjMwMDQ1JTdlLTc2Ljg4NDQ5ODM3OTg3MjM=">HERE</a></li>
</ul>
</div>
<p>  Here&#8217;s a series of Reports worth your time to read related to the First-Due:</p>
<li><strong>City of Charleston Post Incident Assessment and Review Team Phase I Report, </strong><a href="http://www.firehouse.com/mz/images/2007/11/charleston_phase_one_report.pdf"><strong>HERE</strong></a></li>
<li><strong>Routley Final Phase II Report </strong><a href="http://www.firerescue1.com/data/pdfs/5-15-08_CharlestonReport.pdf"><strong>HERE</strong></a></li>
<li><strong>NIOSH Investigative Report, </strong><a href="http://www.cdc.gov/niosh/fire/reports/face200718.html"><strong>HERE</strong></a></li>
<p><strong></p>
<li>Fire Fighting Tactics Under Wind Driven Conditions Report, <strong><a href="http://fire.nist.gov/bfrlpubs/fire09/PDF/f09002.pdf">HERE</a></strong></li>
<li>Reference Data <strong><a href="http://www.fire.gov/WDF/index.htm">HERE</a></strong></li>
<li>The report is also available for download at the NIST, <strong><a href="http://www.nist.gov/bfrl/fire_research/upload/Report-on-Residential-Fireground-Field-Experiments.pdf">HERE</a></strong></li>
<li>Synopsis <strong><a href="http://commandsafety.com/2010/04/nist-report-on-residential-fireground-field-experiments-issued/">HERE</a></strong></li>
<p></strong></p>
<li><strong>Report:</strong> <a href="http://fire.nist.gov/bfrlpubs/fire03/art024.html">Trends in Firefighter Fatalities Due to Structural Collapse1979-2002 </a></li>
<li><strong>Colerain Township (OH) </strong><strong>Fire and EMS Department Final Report <strong>Investigation Analysis of the Squirrels Nest Lane Firefighter Line of Duty Deaths </strong></strong>Incident Overview, <strong><a href="http://commandsafety.com/2010/07/eleven-minutes-to-mayday-what-you-need-to-know/">HERE</a></strong>; NIOSH Report, <strong><a href="http://www.cdc.gov/niosh/fire/reports/face200809.html">HERE</a>; </strong>Investigative Report, <strong><a href="http://www.wlwt.com/download/2010/0618/23947480.pdf">HERE</a></strong></li>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://thecompanyofficer.com/2010/11/23/first-due-arriving-companies-are-you-prepared/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://thecompanyofficer.com/2010/11/23/first-due-arriving-companies-are-you-prepared/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The First-Due Fire Officer</title>
		<link>http://thecompanyofficer.com/2010/11/21/the-first-due-fire-officer/</link>
		<comments>http://thecompanyofficer.com/2010/11/21/the-first-due-fire-officer/#comments</comments>
		<pubDate>Sun, 21 Nov 2010 16:39:01 +0000</pubDate>
		<dc:creator>Christopher Naum</dc:creator>
				<category><![CDATA[Buildingsonfire.com]]></category>
		<category><![CDATA[christopher naum]]></category>
		<category><![CDATA[Commandsafety.com]]></category>
		<category><![CDATA[company officer]]></category>
		<category><![CDATA[Crew Integrity]]></category>
		<category><![CDATA[Crew Management]]></category>
		<category><![CDATA[Fire Fighter Safety]]></category>
		<category><![CDATA[firefighting-operations]]></category>
		<category><![CDATA[Leaderhip]]></category>
		<category><![CDATA[Professional Development]]></category>
		<category><![CDATA[Situational Awareness]]></category>
		<category><![CDATA[Strategy and Tactics]]></category>
		<category><![CDATA[Taking it to the Streets]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[command officer]]></category>
		<category><![CDATA[Crew resource management]]></category>
		<category><![CDATA[fire ground decision-making]]></category>
		<category><![CDATA[fire ground operations]]></category>
		<category><![CDATA[Fire Officer Leadership]]></category>
		<category><![CDATA[Fire Officer Role]]></category>
		<category><![CDATA[Fire Officer Training]]></category>
		<category><![CDATA[Firefighter Safety]]></category>
		<category><![CDATA[Firefighternetcast.com]]></category>
		<category><![CDATA[First-due]]></category>
		<category><![CDATA[First-due Command Officer]]></category>
		<category><![CDATA[First-due Company Officer]]></category>
		<category><![CDATA[first-due fire officer]]></category>
		<category><![CDATA[First-Due Officer responsibilities]]></category>
		<category><![CDATA[Risk Assessment]]></category>
		<category><![CDATA[Strategic or Tactical Decisions]]></category>
		<category><![CDATA[Tactical Entertainment]]></category>
		<category><![CDATA[Tactical Patience]]></category>
		<category><![CDATA[taking it to the streets radio]]></category>
		<category><![CDATA[thecompanyofficer.com]]></category>

		<guid isPermaLink="false">http://thecompanyofficer.com/?p=885</guid>
		<description><![CDATA[
On the most recent edition of Taking it to the StreetsTM we had a vibrant and insightful program in which we discussion some of the expansive facets related to the [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><a href="http://thecompanyofficer.com/files/2010/11/fire.jpg"><img class="size-full wp-image-886 aligncenter" title="fire" src="http://thecompanyofficer.com/files/2010/11/fire.jpg" alt="" width="512" height="384" /></a></p>
<p>On the most recent edition of <strong><a href="http://commandsafety.com/blogradio/">Taking it to the Streets</a><sup>TM </sup></strong>we had a vibrant and insightful program in which we discussion some of the expansive facets related to the <strong>First-Due Officer.</strong> The discussion revolved around a variety of functional elements, traits, responsibilities and duties befalling the First-Due Officer.</p>
<p><strong>Taking it to the Streets: The First-Due Officer</strong></p>
<h5>On Your Street, In Your City, Across the Country, Around the WorldTM</h5>
<h5>To listen or download the program, <a href="http://www.firefighternetcast.com/2010/11/nov-17-taking-it-to-the-streets-the-first-due-officer/">HERE</a></h5>
<p>Regardless if you’re the First-Due Company Officer or the First-Due Commanding Officer, you have a tremendous level of responsibilities and the obligation to formulate and initiate immediate actions that require effective and efficient; identification, assessment, analysis and integration in the evolving fireground environment.</p>
<p><em>Or is it just; “pullin’ the line”, or “opening up” or “arriving on scene and assuming the command?”</em></p>
<p>The First-Due Officer has many facets, functions and pitfalls. Leadership, determination, fortitude, skills, resilience, strength, conviction, temperance, restraint and the courage to be safe are but a few of descriptors that define the role or could it be recklessness, ineptitude, incompetent, self-indulging, careless or dangerous: all in the name of tactical entertainment.</p>
<p>There are numerous avenues that a discussion can take when talking about the street level issues affecting the First-Due Officer. First and foremost, the First-Due Officer should have a solid foundation of requisite skill sets, knowledge and training tempered with experience and fortified with empathy and identification with crew and company integrity and safety. </p>
<p>Today’s First-Due Officer must perform smarter with increased perceptions, discernments and acumens with intelligence and wisdom that is drawn from further progressing and collective fire ground response and operational experiences. It’s no longer just brute force and physical determination that defines our fire ground operations, especially when we relate to the duties and responsibilities of the First-Due Officer.  </p>
<p>Here are some things to think about today at the station, around the kitchen table or over a cup of coffee in the day room after your next alarm;</p>
<p><strong>What defines the First Due Officer in your organization or company?</strong></p>
<p><strong>What effect and consequences does the First Due Officer have on Incident Operations?</strong></p>
<ul>
<li>Is the First Due Officer defined by the level of aggressiveness they select and implement in their IAP on a consistent basis?</li>
<li>Is there a correlation and parallel between Risk Management, Building Construction, Firefighter Survival and Aggressive Intervention that the First Due Officer must balance?</li>
</ul>
<p><strong>What is the Role of the First Due Officer?</strong></p>
<ul>
<li>Strategic, Tactical or Task level Operations?</li>
<li>Can they truly perform all of the functional facets required or implied by current fire ground operational models and practices?</li>
<li>Can Risk Management really be implemented by the First-Due Officer? Is it being done in organization or company? Or is it just getting the “job done”?</li>
<li>Company Level Crew Integrity and Safety &amp; Survival</li>
<li>Maintaining Fluid Situational Awareness</li>
<li>Evolving and Expanding Operational Concerns</li>
<li>Company Integrity</li>
<li>Having Appropriate Technical Competencies, Knowledge and Skill Sets</li>
<li>Confidence Experience and Operational Fortitude</li>
<li>Abilities to Predict &amp; Maintain; Focus, Forecast,</li>
<li>Command &amp; Leadership Presence in Strategic and/or Tactical deployments and Assignments</li>
</ul>
<p><strong>If you are an emerging, aspiring or seasoned Company or Command Officer;</strong></p>
<ul>
<li>What are your First-Due Strategic or Tactical Decisions Based Upon?</li>
<li>What is the Sum of your Experiences and Training?</li>
<li>What Factors formulate your Risk Assessment Process &amp; Action Planning?</li>
<li>What is the Basis of your Decision-Making Process?</li>
<li>What Do you really Know, Assume or Consider in the Buildings, Occupancies, Events &amp; Incidents you interface with?</li>
<li>Do “Fire Service Traditional Expectations” Cloud your Ability to “SEE” the Big Picture?</li>
<li>What Defines you:
<ul>
<li>Aggressive, Forceful, Dynamic, Influential, Passive, Conservative, Decisive, Measured,    </li>
<li>Leadership, Determination, Fortitude, Skilled, Resilience, Strength, Conviction, temperance, restraint and the courage to be safe  </li>
<li>Reckless, Inept, Incompetent, Self-indulging, Careless, Uncontrolled or Dangerous</li>
</ul>
</li>
<li>Are your deployments and operations Delineated in the name of Tactical Entertainment or Defined by Tactical Patience?</li>
</ul>
<p><strong>Remember this; </strong><strong>It’s not the uniform, rank or helmet color that defines a person; it’s what you do that defines who you are.</strong><strong></strong></p>
<ul>
<li>We must have the fortitude and courage to be both safety conscious and measured in the performance of our sworn duties while maintaining the appropriate balance of risk and bravery.</li>
<li>The demands and requirements of modern firefighting will continue to require the placement of personnel within situations and buildings that carry risk, uncertainty and inherent danger.</li>
<li>Adequately and Effectively Prepare yourself for those First-Due Officer responsibilities; you have a tremendous level of responsibilities and obligations, Be all you can be, your companies an personnel are counting on you.   </li>
</ul>
<p>Check out the latest <a href="http://www.firefighternetcast.com/category/our-shows/taking-it-to-the-streets-our-shows/">downloads</a> of recent programs in the archives by visiting Taking it to the Street’s webpage on <a href="http://www.firefighternetcast.com/our-shows/taking-it-to-the-streets/">Firefighternetcast.com</a> or for program insights at <a href="http://commandsafety.com/blogradio/">CommandSafety.com.</a></p>
<p><strong>Taking it to the Streets Radio Program, </strong><a href="http://www.firefighternetcast.com/our-shows/taking-it-to-the-streets/"><strong>HERE</strong></a><strong> and </strong><a href="http://commandsafety.com/blogradio/"><strong>HERE</strong></a></p>
<p><strong>Taking it to the Streets<sup>TM</sup></strong> is a monthly radio show featured on BlogTalk Radio and is hosted by Christopher Naum and is a Buildingsonfire.com Series and Firefighternetcast.com Production,  © 2010 All Rights Reserved</p>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://thecompanyofficer.com/2010/11/21/the-first-due-fire-officer/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://thecompanyofficer.com/2010/11/21/the-first-due-fire-officer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NIOSH: Uncoordinated ventilation caused flashover</title>
		<link>http://thecompanyofficer.com/2010/09/30/niosh-uncoordinated-ventilation-caused-flashover/</link>
		<comments>http://thecompanyofficer.com/2010/09/30/niosh-uncoordinated-ventilation-caused-flashover/#comments</comments>
		<pubDate>Thu, 30 Sep 2010 11:59:01 +0000</pubDate>
		<dc:creator>dougcline</dc:creator>
				<category><![CDATA[command-leadership]]></category>
		<category><![CDATA[company officer]]></category>
		<category><![CDATA[Crew Management]]></category>
		<category><![CDATA[Culture]]></category>
		<category><![CDATA[Doug Cline]]></category>
		<category><![CDATA[Strategy and Tactics]]></category>
		<category><![CDATA[Buildingsonfire.com]]></category>
		<category><![CDATA[competencies]]></category>
		<category><![CDATA[decision-making]]></category>
		<category><![CDATA[fire behavior]]></category>
		<category><![CDATA[incident command]]></category>
		<category><![CDATA[Risk Assessment]]></category>
		<category><![CDATA[safety]]></category>
		<category><![CDATA[Situational Awareness]]></category>
		<category><![CDATA[size-up]]></category>

		<guid isPermaLink="false">http://thecompanyofficer.com/?p=799</guid>
		<description><![CDATA[NIOSH: Uncoordinated ventilation caused flashover killing Ill. firefighterInvestigators say crews failed to recognize signs of an imminent flashover; firefighters were between the fire and ventilation points
By Ken Robinson
FireRescue1 Associate Editor
HOMEWOOD, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://thecompanyofficer.com/files/2010/09/Ventilation.jpg"><img class="alignright size-full wp-image-804" title="Ventilation" src="http://thecompanyofficer.com/files/2010/09/Ventilation.jpg" alt="" width="220" height="220" /></a>NIOSH: Uncoordinated ventilation caused flashover killing Ill. firefighterInvestigators say crews failed to recognize signs of an imminent flashover; firefighters were between the fire and ventilation points<br />
By Ken Robinson<br />
FireRescue1 Associate Editor<br />
HOMEWOOD, Ill. — Uncoordinated ventilation caused a flashover that killed one firefighter and injured another when both failed to recognize signs of rapidly deteriorating conditions, investigators found.</p>
<p>Insufficient staffing was also cited as a key contributing factor in the incident, as crews on scene were stretched thin according to a NIOSH report released Tuesday.</p>
<p>Rookie Homewood Fire Department Firefighter-Paramedic Brian Carey was killed of smoke inhalation on March 30 while assisting in search and rescue of a reported victim trapped in a house fire, the report said.</p>
<p>Responding to reports of a downed brother, firefighters conducting a search discovered Firefighter-Paramedic Carey entangled in a hoseline and not wearing his helmet or facepiece, and without a hood.</p>
<p>Firefighter-Paramedic Karra Kopas, who had entered the structure along with him, was injured in the fire and had to be rescued four feet from the front door where she said her gear melted to the living room carpet.</p>
<p>At the time of the flashover, firefighters performing ventilation were not coordinating with hoseline and search and rescue crews inside the house, according to the investigation.</p>
<p>Both Firefighters Carey and Kopas were between the fire and the ventilation source.</p>
<p>&#8220;One firefighter accounts heavy, turbulent, black smoke pushing from a window on the B-side after it was broken,&#8221; the report said.</p>
<p>&#8220;Shortly after, the house sustained an apparent ventilation-induced flashover.&#8221;</p>
<p>NISOH says the thick, black and heavily pressurized smoke that exited through ventilation should have been acted upon as a warning sign.</p>
<p>&#8220;The IC, and individuals working on the exterior, need to recognize this as a potential for extreme fire behavior and evacuate interior crews,&#8221; the report said.</p>
<p>In addition, investigators recommend training firefighters under realistic conditions to indentify the signs of an imminent flashover.</p>
<p>&#8220;Obtaining proper training and hands-on experience through the use of a flashover simulator may assist interior firefighters in making sound decisions on when to evacuate a structure fire,&#8221; the report said.</p>
<p>The inability to appropriately coordinate fireground operations may have been directly tied to inadequate staffing.</p>
<p>&#8220;Due to short staffing, the ambulance personnel were tasked with fire suppression activities, thus taking them out-of-service as a medical unit,&#8221; the report said.</p>
<p>The incident commander, a Lieutenant, was also required to ride and operate as the officer of an Engine Crew due to short staffing.</p>
<p>&#8220;This removed him from his command response vehicle which would have allowed him to command at a tactical level versus having to potentially perform tasks,&#8221; the report said.</p>
<p>Investigators also found an accountability system was never put in place and a personnel accountability report was never conducted following the incident.</p>
<p>As a result of the incident, NIOSH made the following key recommendations for fire departments to follow:</p>
<ul>
<li>Ensure that a complete 360-degree situational size-up is conducted on dwelling fires and others where it is physically possible and ensure that a risk-versus-gain analysis and a survivability profile for trapped occupants is conducted prior to committing to interior firefighting operations.</li>
</ul>
<p> </p>
<ul>
<li>Ensure that interior fire suppression crews attack the fire effectively to include appropriate fire flow for the given fire load and structure, use of fire streams, appropriate hose and nozzle selection, and adequate personnel to operate the hose line.</li>
</ul>
<p> </p>
<ul>
<li>Ensure that firefighters maintain crew integrity when operating on the fireground, especially when performing interior fire suppression activities.</li>
</ul>
<p> </p>
<ul>
<li>Ensure that firefighters and officers have a sound understanding of fire behavior and the ability to recognize indicators of fire development and the potential for extreme fire behavior<br />
Ensure that incident commanders and firefighters understand the influence of ventilation on fire behavior and effectively coordinate ventilation with suppression techniques to release smoke and heat.</li>
</ul>
<p><a href="http://thecompanyofficer.com/files/2010/09/Ventilation.jpg"></a></p>
<ul>
<li>Ensure that firefighters use their self-contained breathing apparatus (SCBA) and are trained in SCBA emergency procedures.</li>
</ul>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://thecompanyofficer.com/2010/09/30/niosh-uncoordinated-ventilation-caused-flashover/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://thecompanyofficer.com/2010/09/30/niosh-uncoordinated-ventilation-caused-flashover/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

