<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>ChrisElyea.com</title>
	
	<link>http://chriselyea.com</link>
	<description>Much analysis brings triumph, little analysis brings disaster</description>
	<lastBuildDate>Sun, 24 Jan 2010 13:02:20 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ChrisElyea" /><feedburner:info uri="chriselyea" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><image><link>http://chriselyea.com</link><url>http://farm3.static.flickr.com/2645/3874986593_fdd8c25558_t.jpg</url><title>Chris Elyea at the Arc de Triomphe in Paris</title></image><feedburner:emailServiceId>ChrisElyea</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Prince Philip on Design</title>
		<link>http://feedproxy.google.com/~r/ChrisElyea/~3/8fWiXqke18s/</link>
		<comments>http://chriselyea.com/design-lessons-learned/the-royal-vcr-is-a-royal-pain/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 13:02:20 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[Design - Lessons Learned]]></category>
		<category><![CDATA[bad design]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[design awards]]></category>
		<category><![CDATA[designer]]></category>
		<category><![CDATA[elegance]]></category>
		<category><![CDATA[elegant design]]></category>
		<category><![CDATA[elegant solution]]></category>
		<category><![CDATA[empowerment]]></category>
		<category><![CDATA[ergonomics]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[functional]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[passion]]></category>
		<category><![CDATA[poor design]]></category>
		<category><![CDATA[Prince Philip]]></category>
		<category><![CDATA[Prince Philip Designers Prize]]></category>
		<category><![CDATA[solution]]></category>
		<category><![CDATA[The Royal Channel]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">http://chriselyea.com/?p=451</guid>
		<description><![CDATA[H.R.H. wonders why it’s necessary to lay beneath the TV with a flashlight in his teeth to program his VCR.]]></description>
				<content:encoded><![CDATA[<p style="text-align: justify;">H.R.H. Prince Philip shared his genuine frustration with poor design in this insightful interview upon the 50<sup>th</sup> anniversary of the Prince Philip Designers Prize.  He believes that consumers have become too tolerant of bad design.  The next time I’m trying to squirm between the entertainment unit and the wall, with a cable between my teeth, a flashlight in one hand and a wiring diagram in the other, I’ll take comfort in knowing that even the Royal Family shares my pain!</p>
<p style="text-align: center;"><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="480" height="295" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param value="http://www.youtube.com/v/0W8lESZ2XNg&amp;hl=en_US&amp;fs=1&amp;rel=0" /><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/0W8lESZ2XNg&amp;hl=en_US&amp;fs=1&amp;rel=0" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="480" height="295" src="http://www.youtube.com/v/0W8lESZ2XNg&amp;hl=en_US&amp;fs=1&amp;rel=0" allowscriptaccess="always" allowfullscreen="true"></embed></object><br />
<a rel="nofollow" href="http://www.youtube.com/watch?v=0W8lESZ2XNg" target="_blank">Link to the interview on YouTube</a></p>
<p style="text-align: justify;">Asked about how design has changed over the past 50 years, Prince Philip replied that the trend to design by corporate or government committee has reduced the chances of producing exceptional designs.</p>
<p style="text-align: justify;">He also feels that designers on contract create more innovative designs than staff designers.   This is because a contractor knows that her employment is temporary, while an employee always fears that hers is!  Thus employee designers are inclined to play it safe by complying with their employer’s opinions rather than truly expressing themselves.  He has observed that success results from giving a designer the authority to make design decisions. I would call this concept "empowerment" and say it's still all too rare, despite being a popular management buzzword.</p>
<img src="http://feeds.feedburner.com/~r/ChrisElyea/~4/8fWiXqke18s" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://chriselyea.com/design-lessons-learned/the-royal-vcr-is-a-royal-pain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chriselyea.com/design-lessons-learned/the-royal-vcr-is-a-royal-pain/</feedburner:origLink></item>
		<item>
		<title>Seth Godin shows how “This Is Broken”</title>
		<link>http://feedproxy.google.com/~r/ChrisElyea/~3/7m5ghTMGKvQ/</link>
		<comments>http://chriselyea.com/design-lessons-learned/this-is-broken/#comments</comments>
		<pubDate>Thu, 21 Jan 2010 13:25:04 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[Design - Lessons Learned]]></category>
		<category><![CDATA[bad design]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[poor design]]></category>
		<category><![CDATA[Seth Godin]]></category>
		<category><![CDATA[This Is Broken]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">http://chriselyea.com/?p=438</guid>
		<description><![CDATA[A video of examples of poor design!]]></description>
				<content:encoded><![CDATA[<p style="text-align: justify;">Seth Godin is a prolific author and blogger on marketing and other business subjects.  This is his hilarious presentation about how poor design turns off customers.  So many things to learn from here!  How can we make these flaws look as obvious to us at the design phase as they look to the user of the finished product?</p>
<p style="text-align: center;"><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="400" height="300" 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://vimeo.com/moogaloop.swf?clip_id=4246943&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" /><embed type="application/x-shockwave-flash" width="400" height="300" src="http://vimeo.com/moogaloop.swf?clip_id=4246943&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
<p>Link to the video: <a rel="nofollow" href="http://vimeo.com/4246943" target="_blank">Seth Godin at Gel 2006</a> from <a rel="nofollow" href="http://vimeo.com/gelconference" target="_blank">Gel Conference</a> on <a rel="nofollow" href="http://vimeo.com" target="_blank">Vimeo</a>.</p>
<img src="http://feeds.feedburner.com/~r/ChrisElyea/~4/7m5ghTMGKvQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://chriselyea.com/design-lessons-learned/this-is-broken/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chriselyea.com/design-lessons-learned/this-is-broken/</feedburner:origLink></item>
		<item>
		<title>They Didn’t Teach Me Design in Engineering School</title>
		<link>http://feedproxy.google.com/~r/ChrisElyea/~3/NdvYx1Pomzs/</link>
		<comments>http://chriselyea.com/design-lessons-learned/learning-to-design/#comments</comments>
		<pubDate>Thu, 14 Jan 2010 13:25:20 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[Design - Lessons Learned]]></category>
		<category><![CDATA[architect]]></category>
		<category><![CDATA[competitive]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[creative]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Ed Medley]]></category>
		<category><![CDATA[engineer]]></category>
		<category><![CDATA[innovative]]></category>
		<category><![CDATA[learn]]></category>
		<category><![CDATA[original]]></category>
		<category><![CDATA[practical]]></category>
		<category><![CDATA[predictable]]></category>
		<category><![CDATA[problem solving]]></category>
		<category><![CDATA[product]]></category>
		<category><![CDATA[safe]]></category>
		<category><![CDATA[solution]]></category>
		<category><![CDATA[teach]]></category>

		<guid isPermaLink="false">http://chriselyea.com/?p=430</guid>
		<description><![CDATA[Architects and engineers solve problems very differently!]]></description>
				<content:encoded><![CDATA[<p style="text-align: justify;">They didn’t teach design when I went to engineering school.<sup>*</sup> It wasn’t until after graduating and beginning work that I was faced with the challenge of coming up with brand new solutions for problems.  Figuring out where to start is always the hardest part.  A blank document can be the scariest thing in the world!</p>
<p style="text-align: justify;">I once worked with an architect and it was enlightening.  You might think there’s a lot of similarity between architects and engineers, but if you do, you’re wrong.<span id="more-430"></span></p>
<p style="text-align: justify;">Both of us started our problem solving with learning as much as we could about the nature of the problem. As an engineer, my next step was to investigate and define constraints for the solution.  I needed a foundation upon which I could build.  It hadn’t even occurred to me that there was another approach.  The architect did the opposite.  He started by creating a theme.  His theme was circles.  This could not have been more foreign to me!  From there he worked out until he bumped up against the constraints, which then became boundaries for his solution.  I was amazed to watch as this simple theme evolved into a sophisticated design.</p>
<p style="text-align: justify;">The difference in results between these two approaches is startling.  When you begin from the known, your design reflects that from which you started.  This is a good thing for engineers because it results in a product that is safe and predictable.  On the other hand, when you start fresh, this results in a design that is innovative and original, which is a good thing for architects (or so I assume).</p>
<p style="text-align: justify;">Neither approach is perfect for all situations.  Competitive environments demand continuous improvement.  Evolution alone is often not sufficient; the occasional revolution is necessary.  However, starting from scratch requires a bigger investment in time and resources, and not all new ideas will result in practical products.</p>
<p style="text-align: justify;">There is great value in combining these approaches.  As Prince Philip quoted the Prince Consort, “You’ve got to have a marriage of art and manufacturing and engineering in order to produce good stuff!”</p>
<p style="text-align: justify;"><sup>*</sup> For a complete list of what else they didn’t teach me or any other engineering student (and a good laugh), you must read Ed Medley’s award-winning article <em><a rel="nofollow" href="http://edmedley.com/blog/2008/10/25/what-they-didnt-teach-me-in-engineering-school/">What They Didn’t Teach Me in Engineering School</a>. </em></p>
<img src="http://feeds.feedburner.com/~r/ChrisElyea/~4/NdvYx1Pomzs" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://chriselyea.com/design-lessons-learned/learning-to-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chriselyea.com/design-lessons-learned/learning-to-design/</feedburner:origLink></item>
		<item>
		<title>Push, Pull, or imitate Maxwell Smart?</title>
		<link>http://feedproxy.google.com/~r/ChrisElyea/~3/OdYdLYrfEJY/</link>
		<comments>http://chriselyea.com/design-lessons-learned/badly-designed-doors/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 15:02:36 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[Design - Lessons Learned]]></category>
		<category><![CDATA[bad design]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[designer]]></category>
		<category><![CDATA[door]]></category>
		<category><![CDATA[doors]]></category>
		<category><![CDATA[good design]]></category>
		<category><![CDATA[lock]]></category>
		<category><![CDATA[poor design]]></category>
		<category><![CDATA[pull]]></category>
		<category><![CDATA[push]]></category>

		<guid isPermaLink="false">http://chriselyea.com/?p=420</guid>
		<description><![CDATA[Ever been confused by a poorly designed door?]]></description>
				<content:encoded><![CDATA[<div id="attachment_421" class="wp-caption aligncenter" style="width: 310px"><a href="http://chriselyea.com/wp-content/uploads/2010/01/PushPullDoors.jpg"><img class="size-medium wp-image-421 " title="Door Handles" src="http://chriselyea.com/wp-content/uploads/2010/01/PushPullDoors-300x200.jpg" alt="Identical handles on both sides of a door at a shopping mall" width="300" height="200" /></a><p class="wp-caption-text">Efficient or lazy?  The designer used the same handles on both sides of these doors.  The little &quot;PUSH&quot; and &quot;PULL&quot; signs are required reading!  Doors are simple - why do designers force us to read instructions to use them?</p></div>
<p>Have you ever been confused by a door?  Push or pull?  Which side opens?  Is it locked?  It’s not your fault!  The designer screwed up.</p>
<p style="text-align: justify;">If you’re running a shopping mall or a store or an office, you need customers to come into your building.  Unless it has a drive-through or a take-out window, that’s a necessary requirement for business.  It’s amazing how often a poor customer experience starts right here.  Designers have no excuses.  It’s not like doors are new technology.  Everybody’s seen and used lots.  There must be some best practices guide out there somewhere.</p>
<p style="text-align: justify;">Nobody likes being embarrassed, but it’s hard to look good when you’re colliding with a door that swings opposite to what you were expecting.  Do you not tense up when approaching a bank of doors in a large building?  Many of us have even developed coping mechanisms just for this situation.  I employ logic: look for the hinges and try to devise how the door operates.  One of my friends aims between two doors, simultaneously pulling on one and pushing the other.  Others hesitate to observe and then imitate the successful users.<span id="more-420"></span></p>
<p style="text-align: justify;">Somebody did invent a hinge that will let a door open in either direction, whether pushed or pulled.  How come we don’t see more of those?</p>
<p style="text-align: justify;">Ever walk up to a set of double doors and one of them is locked?  This happens to me so often that I have begun to suspect there is a law requiring it.  I went to a convention centre to shop at a craft fair.  It was a big place and the small fair was only at one end, so most of the doors were locked.  It took a while to hunt down, by process of elimination, the unlocked doors.  Some of the doors that I expected to be locked were open, so perhaps the facility operators were also confused.  Of course, upon leaving, the problem presented itself anew, as some types of door can allow exit even when they are locked from the outside, but not all.  Which type where these and were they completely bolted or just locked to the outside?  I think designers could build in visual clues to let us know when a door is locked.</p>
<p style="text-align: justify;">In Calgary, the Plus 15 network contains many automatic doors that use a sensor to detect you and open.  That sounds good in theory, but not all applications are satisfactory.  The sensors are not always located in the same place and the timing is different for many doors.  You can never be sure if the door has detected you and will open in time, or if you need to take evasive action.  Sometimes the system is broken, has been turned off (in which case the door may still open manually), or the door has been locked.  This can result in a very convincing Maxwell Smart impression as you bang your nose on the door.  To avoid this, I have developed a technique where I lean forward as I drag my back toes, like a wide receiver making a catch along the sideline.  I can then wait for slow doors without breaking stride or stop for closed ones without breaking my nose.</p>
<p style="text-align: justify;">We all like to laugh at people that push on doors with “Pull” written on them, but we’ve all done it.  Obviously we are expecting a door to be intuitive and don’t want to read instructions to make it work.  We’re all experienced users, so when a door doesn’t work like you expect it to, there’s something wrong with the design, not you.</p>
<img src="http://feeds.feedburner.com/~r/ChrisElyea/~4/OdYdLYrfEJY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://chriselyea.com/design-lessons-learned/badly-designed-doors/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://chriselyea.com/design-lessons-learned/badly-designed-doors/</feedburner:origLink></item>
		<item>
		<title>Real or Artificial?</title>
		<link>http://feedproxy.google.com/~r/ChrisElyea/~3/zIW913hoRSg/</link>
		<comments>http://chriselyea.com/rants/real-or-artificial-christmas-tree/#comments</comments>
		<pubDate>Thu, 10 Dec 2009 21:56:27 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[artificial christmas tree]]></category>
		<category><![CDATA[christmas tree]]></category>
		<category><![CDATA[real christmas tree]]></category>

		<guid isPermaLink="false">http://chriselyea.com/?p=355</guid>
		<description><![CDATA[Real or artificial?  It's the great Christmas tree debate.]]></description>
				<content:encoded><![CDATA[<div id="attachment_407" class="wp-caption aligncenter" style="width: 176px"><img src="http://chriselyea.com/wp-content/uploads/2009/12/Tree-166x300.jpg" alt="My Artificial Christmas Tree and I wish you a very Merry Christmas!" title="Christmas Tree, Artificial" width="166" height="300" class="size-medium wp-image-407" /><p class="wp-caption-text">Merry Christmas!</p></div>
<p style="text-align: justify;">Real or artificial?  When it comes to Christmas trees, this is an ongoing and contentious debate.  I’m a hard-core proponent of the artificial tree for the following reasons:</p>
<p></br></p>
<p style="text-align: justify;"><strong>Some assembly required</strong></p>
<p style="text-align: justify;">Not much appeals more to an engineer than the opportunity to assemble something, especially when it comes in kit form and is guaranteed to go together smoothly!  Modular construction – sweet!  IKEA furniture looks like IKEA furniture, it’s true, but man is it fun to put together!  Assembling a Christmas tree could only be better if some special tools were required.</p>
<p style="text-align: justify;">The first family tree consisted of a green wooden pole and individual branches.  Some of my fondest Christmas memories are of Dad bringing out that great big box and letting us help sort out the branches.  The branches were colour-coded with a little bit of paint at the base of the stem.  Trying to differentiate between ‘red’ and ‘copper’ was a challenge I looked forward to each year.  Later, my siblings and I were allowed to drag the box out of the crawlspace and assemble the tree by ourselves.  This was probably a greater privilege than being able to use the car.  My parents might still be using that tree if the crawlspace hadn’t flooded, turning the box to pulp and making a mess of the tree.</p>
<p style="text-align: justify;">Unfortunately, Christmas tree design has advanced considerably and the tree I obtained for my first house is an umbrella style.  It does have three sections, but most of the thrill of assembly has been removed.  I am left to admire this improvement and wax nostalgic about the good ol’ days when I had to install each individual branch.  Almost makes me with I had grandkids to tell the story to.</p>
<p></br></p>
<p style="text-align: justify;"><span id="more-355"></span><strong>Déjà vu all over again</strong></p>
<p style="text-align: justify;">Engineers love standards.  An artificial tree has wonderfully uniform dimensions.  It’s always the same height and width as it was last year and the year before and the year before that, so I never have to worry about whether it will fit in the door or fill the room appropriately.  I can’t imagine trying to evaluate one of those tightly wound real trees it its fish net bag to determine if it were the correct size and shape.  An artificial tree has no good side or bad side, so it doesn’t matter how I put it up.  I know precisely where to place the base every year in order to have sufficient clearance on all sides for the ladder.</p>
<p style="text-align: justify;">I also know there is room for all of our decorations, no more, no less.  Wouldn’t it be sad if some of your ornaments wouldn’t fit on the tree and had to remain in their boxes?  What a tragedy!  Or worse, if you didn’t have enough and had to buy more at pre-Christmas prices?</p>
<p style="text-align: justify;">I also know exactly how many lights are required.  This is causing me some stress as I make the switch to LED’s – those strings are a different length, so how many will I need?  You can understand I’m losing sleep over this.  These days, you can get an umbrella-style tree with the lights built in.  That’s progress!  Yes, you lose the thrill of assembly mentioned above, but hassles are reduced even more, as discussed below.  Again, it would be useful to have grandkids so I could tell them how good they have it these days.</p>
<p></br></p>
<p style="text-align: justify;"><strong>Relatively hassle-free</strong></p>
<p style="text-align: justify;">No needles to clean up!  That’s such a huge benefit, I get to say it again:  no needles to clean up!</p>
<p style="text-align: justify;">Having managed to get my tree home in the car once, which required a highly questionable cargo and passenger configuration, I never have to do it again.  I could even have had it delivered, which is not a very common option for real trees.  I don’t have to worry about selecting the perfect tree and strapping it to my perfect car roof, only to have both of them become somewhat less than perfect during the ride home – every year.</p>
<p style="text-align: justify;">Around these parts, one can obtain a very cheap permit to cut one’s own tree.  Does that sound good to you?  If so, are you a masochist or just a rugged outdoorsperson?  Maybe those are the same thing.  Sing it with me: “I’m a lumberjack and I’m okay!”  Anyway, I don’t need to go tramping off into the snowy woods in search of the perfect natural tree in its native environment…and then ruthlessly hack it down.  Then I don’t need to somehow drag it back to the vehicle and transport it home (likely along the highway, for you’d need to travel out of town to get to the forest) without damaging it.<strong> </strong></p>
<p></br></p>
<p style="text-align: justify;"><strong>“Smoke on the water, fire in the sky” should be a lyric, not a headline</strong></p>
<p style="text-align: justify;">This is The Big One, the reason that trumps all others.  I’m no Boy Scout (I mean that in the literal sense – I am not now, nor have I ever been, a member of the Boy Scouts or any similar outdoor camping or survival organization), but I know kindling when I see it.  Back in the days of my youth, when it was not considered a mortal sin to dispose of real Christmas trees by burning them, I witnessed how quickly flame engulfed them.  If you are too young to have seen this or just had a sheltered childhood, Mythbusters lit one up a few years ago that you can occasionally catch on re-runs, and of course you can find many videos on-line.</p>
<p style="text-align: justify;">They should provide a bag of marshmallows and some sharp sticks with every real Christmas tree, so you can have a little snack while you’re waiting for the fire department to douse the smouldering embers of what used to be your home.  I’m not having one of those things in my house!</p>
<p></br></p>
<p style="text-align: justify;">Real Christmas tree fanatics will counter with a couple of points, so I will have to address them here:</p>
<p></br></p>
<p style="text-align: justify;"><strong>Tradition</strong></p>
<p style="text-align: justify;">The original Christmas trees were actual trees.  Sure, but they didn’t have engineered polymers or even indoor plumbing, and cows could kick over lanterns and burn whole cities down.  And they had The Plague, too.  Do you miss The Plague?  If you live in a stone castle or even a sod hut, then you’ll probably want a real tree, but if you’re that much of a traditionalist, you shouldn’t be on the Internet reading blogs, should you?</p>
<p></br></p>
<p style="text-align: justify;"><strong>Scent</strong></p>
<p style="text-align: justify;">The real tree fanatics maintain that part of the appeal of a Christmas tree is to fill the house with a pine scent (unless it’s a fir tree, of course).  I just want to point out that cleaning with Pine-Sol will give you the same effect all year round (unless you get the lavender-scented kind, of course).  I have no argument with the pine scent of a real tree; it’s the potential for a smoky scent I wish to avoid.</p>
<p></br></p>
<p style="text-align: justify;"><strong>The Environment</strong></p>
<p style="text-align: justify;">From an environmental standpoint, ironically it appears that cutting down a tree may be less harmful when all factors are considered.  I admit that, on this basis, a real tree does appeal to my sense of humour: “Hey, why are you cutting down that tree?”  “Well, to save the environment, of course!”  In my defence, I’ll contend that’s only if it doesn’t burn your house down.  But Christmas in conventional form is never going to win any points from a true environmentalist – it just creates too much waste and uses too much energy – so nobody’s going to win the Christmas tree debate on environmental terms.</p>
<p></br></p>
<p style="text-align: justify;">At Christmastime, they say it’s the thought that counts, so while I’m assembling my clean, predictable, and safer artificial tree in my cozy living room, I’ll be thinking of you real tree fanatics tramping around in the frozen woods or scratching up your car roof.  And I know we’ll both be happy, which is what the season is all about, so Merry Christmas!</p>
<img src="http://feeds.feedburner.com/~r/ChrisElyea/~4/zIW913hoRSg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://chriselyea.com/rants/real-or-artificial-christmas-tree/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://chriselyea.com/rants/real-or-artificial-christmas-tree/</feedburner:origLink></item>
		<item>
		<title>Nothing Good Ever Happened In A Box Canyon</title>
		<link>http://feedproxy.google.com/~r/ChrisElyea/~3/92qTJCrSGxQ/</link>
		<comments>http://chriselyea.com/failure-analysis-lessons/safety-when-no-one-is-watching/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 15:10:12 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[Failure Analysis - Lessons Learned]]></category>
		<category><![CDATA[accident investigation]]></category>
		<category><![CDATA[Afghanistan]]></category>
		<category><![CDATA[aircraft accident investigation]]></category>
		<category><![CDATA[attitude]]></category>
		<category><![CDATA[box canyon]]></category>
		<category><![CDATA[enforcement]]></category>
		<category><![CDATA[human factors]]></category>
		<category><![CDATA[incident investigation]]></category>
		<category><![CDATA[inspection]]></category>
		<category><![CDATA[inspectors]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[regulation]]></category>
		<category><![CDATA[regulators]]></category>
		<category><![CDATA[safe work]]></category>
		<category><![CDATA[safety]]></category>
		<category><![CDATA[safety attitude]]></category>
		<category><![CDATA[safety leadership]]></category>
		<category><![CDATA[safety supervision]]></category>
		<category><![CDATA[supervision]]></category>
		<category><![CDATA[working safely]]></category>

		<guid isPermaLink="false">http://chriselyea.com/?p=277</guid>
		<description><![CDATA[Does your safety depend on people who no one is watching?  The investigation into a 2004 accident raises many questions, and disturbingly, it doesn’t provide any answers.]]></description>
				<content:encoded><![CDATA[<div id="attachment_306" class="wp-caption aligncenter" style="width: 533px"><img class="size-large wp-image-306" title="CASA 212 in Afghanistan" src="http://chriselyea.com/wp-content/uploads/2009/11/AWS_Casa-212_in_afghanistan-1024x687.jpg" alt="CASA 212 in Afghanistan" width="523" height="351" /><p class="wp-caption-text">CASA 212 performing an air drop in Afghanistan</p></div>
<p style="text-align: justify;">The investigation into a 2004 accident raises many questions, and disturbingly, it doesn’t provide any answers.  Would your company work safely if there were no enforcement?  How safely would you work if you knew no one was watching?  Does your safety depend on people who no one is watching?</p>
<p style="text-align: justify;">A U.S. airline was contracted by the U.S. government to provide cargo and passenger service in Afghanistan.  Legally, they were under U.S. regulations.  Practically, they were unregulated, as there were no inspectors in Afghanistan.</p>
<p style="text-align: justify;">One morning a flight crew decided to fly into the mountains, instead of around them, just for fun.  They ended up flying into a box canyon.  ‘“At 0803:21, the first officer stated, “yeah you’re an x-wing fighter star wars man,” and the captain replied, “you’re [expletive] right. this is fun.”’<sup>*</sup> Less than 20 minutes later, as the crew attempted a 180º turn, the plane hit the canyon wall. <span id="more-277"></span></p>
<p style="text-align: justify;">Five of the six aboard were killed in the crash.  The remaining passenger survived for at least eight hours, but nobody realized the plane was missing until seven hours after the crash, and then five hours were spent searching in the wrong place.</p>
<p style="text-align: justify;">The airline did not require its pilots to file flight plans, even though this was a legal requirement.  The pilots could have filed a flight plan anyway, but they chose not to.  Why didn’t the airline require flight plans?  Why didn’t the pilots create a flight plan?  Because it gave them the freedom to be unsafe and fly into the mountains instead of flying around them?  If they had filed a flight plan into the mountains, which was not the usual route, would anyone have questioned it?  If they had filed a flight plan, knowing that no one could monitor them, would they have followed it?</p>
<p style="text-align: justify;">The pilots didn’t use oxygen, even though they were flying well above the altitude where oxygen deprivation (hypoxia) begins to affect the ability to think.  They were already making poor decisions, including this one, so hypoxia would only have made things worse.  The investigators interviewed other pilots working for the airline in Afghanistan.  They didn’t know the correct (and legally mandated) criteria for determining when to use oxygen.  These pilots were aware of the threat, yet they didn’t attempt to learn how to protect themselves.  Why not?  If they had known the correct thing to do, would they have chosen to do it?  Why didn’t the company provide better training?  The investigation determined that the plane was capable of climbing over the ridge, had the pilots started the climb at the time they realized they were in a box canyon.  Did hypoxia impair their judgment?</p>
<p style="text-align: justify;">Due to the lack of infrastructure in remote areas of Afghanistan, communications were difficult.  The airline provided the pilots with satellite telephones so they could check in.  However, the airline took no action when it became apparent that these didn’t always work effectively.  This was a violation of regulations because the airline could not know if a flight had arrived safely or not.  The pilots did not seem very concerned about this, either.  Why didn’t the airline develop another solution?  Why didn’t the pilots object to this unsafe condition?</p>
<p style="text-align: justify;">Would this accident have happened if there were inspectors to monitor the airline?  Would the pilots have behaved this way even if the airline had been more concerned about safety?</p>
<p style="text-align: justify;">We can never really know the right answers to questions like these.  We still need to try to answer them to prevent future accidents.</p>
<p style="text-align: justify;">
<p>*<a title="NTSB/AAB-06/07, Aircraft Accident Brief, Controlled Flight Into Terrain, CASA C-212-CC, N960BW, Bamiyan, Afghanistan, November 27, 2004" rel="nofollow" href="http://www.ntsb.gov/publictn/2006/AAB0607.htm" target="_blank"><em>NTSB/AAB-06/07, Aircraft Accident Brief, Controlled Flight Into Terrain, CASA C-212-CC, N960BW, Bamiyan, Afghanistan, November 27, 2004</em></a></p>
<img src="http://feeds.feedburner.com/~r/ChrisElyea/~4/92qTJCrSGxQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://chriselyea.com/failure-analysis-lessons/safety-when-no-one-is-watching/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://chriselyea.com/failure-analysis-lessons/safety-when-no-one-is-watching/</feedburner:origLink></item>
		<item>
		<title>Let’s See What This Baby Can Do!</title>
		<link>http://feedproxy.google.com/~r/ChrisElyea/~3/AUuA3Cg7rYE/</link>
		<comments>http://chriselyea.com/failure-analysis-lessons/let%e2%80%99s-see-what-this-baby-can-do/#comments</comments>
		<pubDate>Wed, 04 Nov 2009 20:06:53 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[Failure Analysis - Lessons Learned]]></category>
		<category><![CDATA[41000]]></category>
		<category><![CDATA[accident]]></category>
		<category><![CDATA[accident investigation]]></category>
		<category><![CDATA[accident report]]></category>
		<category><![CDATA[air traffic control]]></category>
		<category><![CDATA[air traffic controller]]></category>
		<category><![CDATA[aircraft accident]]></category>
		<category><![CDATA[aircraft accident investigation]]></category>
		<category><![CDATA[aircraft accident investigation report]]></category>
		<category><![CDATA[Bombardier]]></category>
		<category><![CDATA[Canadair]]></category>
		<category><![CDATA[Canadair Regional Jet]]></category>
		<category><![CDATA[captain]]></category>
		<category><![CDATA[cover up]]></category>
		<category><![CDATA[crash]]></category>
		<category><![CDATA[CRJ-200]]></category>
		<category><![CDATA[CRJ200]]></category>
		<category><![CDATA[driving]]></category>
		<category><![CDATA[first officer]]></category>
		<category><![CDATA[flameout]]></category>
		<category><![CDATA[incident investigation]]></category>
		<category><![CDATA[investigation]]></category>
		<category><![CDATA[knowledge]]></category>
		<category><![CDATA[limits]]></category>
		<category><![CDATA[Peer pressure]]></category>
		<category><![CDATA[pickup]]></category>
		<category><![CDATA[pickup truck]]></category>
		<category><![CDATA[pilot]]></category>
		<category><![CDATA[plane crash]]></category>
		<category><![CDATA[report]]></category>
		<category><![CDATA[repositioning flight]]></category>
		<category><![CDATA[safe]]></category>
		<category><![CDATA[stall]]></category>
		<category><![CDATA[thrill seeker]]></category>
		<category><![CDATA[thrill seeking]]></category>
		<category><![CDATA[truck]]></category>
		<category><![CDATA[unsafe]]></category>

		<guid isPermaLink="false">http://chriselyea.com/?p=93</guid>
		<description><![CDATA[Testing equipment limits for fun can end very badly.  One sometimes hears, “The only thing faster than a company truck is a rental!” The Canadair Regional Jet 200 is capable of altitudes greater than 41,000 feet in the same sense as the average pickup truck is capable of 96 mph – you can do it, but there’s no valid reason to.  The captain told air traffic control, “We don’t have any passengers on board so we decided to have a little fun and come on up here.” The plane impacted the ground less than 25 minutes later.]]></description>
				<content:encoded><![CDATA[<div id="attachment_331" class="wp-caption aligncenter" style="width: 496px"><img class="size-large wp-image-331" title="Lufthansa_bombardier_crj-200_d-acrf_arp" src="http://chriselyea.com/wp-content/uploads/2009/11/Lufthansa_bombardier_crj-200_d-acrf_arp-1023x701.jpg" alt="Bombardier CRJ-200" width="486" height="334" /><p class="wp-caption-text">Bombardier CRJ200</p></div>
<p style="text-align: center;">
<p style="text-align: justify;">One sometimes hears, “The only thing faster than a company truck is a rental!”  The Canadair Regional Jet 200 (CRJ200) can carry up to 50 passengers and is capable of altitudes greater than 41,000 feet (12,497 metres).  Capable of 41,000 feet in the same sense as the average pickup truck is capable of 96 mph (155 km/h) – you can do it, but there’s no valid reason to.</p>
<p style="text-align: justify;">A “repositioning flight” is when a passenger aircraft is moved from one airport to another without passengers.  Some pilots see this as an opportunity to fly aggressively and enjoy testing the limits of the airplane.  Several accidents prove that sometimes they end up exceeding their own limits.</p>
<p style="text-align: justify;">Having just reached 41,000 feet, the captain told air traffic control, “We don’t have any passengers on board so we decided to have a little fun and come on up here.”  The plane impacted the ground less than 25 minutes later.<span id="more-93"></span></p>
<p style="text-align: justify;">Long story short, the pilots had made an error by climbing too quickly.  They fell behind the energy curve: as the plane slowed, induced drag increased, slowing the plane further.  At 41,000 feet, the engines couldn’t produce enough thrust to power the plane out of trouble.  Eventually the  plane was going so slowly that the engines stopped.  They made further errors in following the restart procedure and couldn’t get the engines going again.</p>
<p style="text-align: justify;">The captain had a B.Sc. in aeronautical sciences, had worked as a flight instructor, and had 6,900 hours of flying time, including 5,055 as pilot-in-command.  Leaving aside poor judgment, he made fundamental piloting errors and failed to detect those made by his less experienced first officer.  It’s difficult to have a true understanding of our own knowledge and abilities, and we usually overestimate them.  We need to actively maintain a margin of safety to keep from inadvertently straying over the edge.</p>
<p style="text-align: justify;">The captain initially tried to downplay the seriousness of their predicament by informing air traffic control that only one engine had failed.  The situation was therefore misinterpreted as an emergency rather than an <strong>EMERGENCY</strong> by air traffic control, who could have offered greater assistance.  The pilots used up their altitude trying to restart the engines rather than attempting to glide to an airport.  How often do we make a situation worse by trying to cover it up so nobody finds out how bad it really is?</p>
<p style="text-align: justify;">As a result of this and several other accidents, repositioning flights are now recognized as a risk and airlines routinely review flight recorder data to look for evidence of improper behaviour (but this only works for those planes legally required to carry flight data recorders).  Some trucking fleet operators have installed data recorders on their vehicles in order to perform the same kind of monitoring.  This is a reactive approach that may prevent repeat occurrences, but will only deter those who are fearful of being caught.  Prisons are full of people who didn’t think they’d get caught.</p>
<p style="text-align: justify;">Thrill seekers often require an audience to witness the incident or to be told about it after.  The airline’s pilots had an unofficial club for those who had flown at 41,000 feet.  I think this is where we can have the greatest impact, because peer pressure is a powerful motivator.  Show your disapproval for unsafe behaviour!</p>
<img src="http://feeds.feedburner.com/~r/ChrisElyea/~4/AUuA3Cg7rYE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://chriselyea.com/failure-analysis-lessons/let%e2%80%99s-see-what-this-baby-can-do/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chriselyea.com/failure-analysis-lessons/let%e2%80%99s-see-what-this-baby-can-do/</feedburner:origLink></item>
		<item>
		<title>Can Too Much Privacy Kill You?</title>
		<link>http://feedproxy.google.com/~r/ChrisElyea/~3/RNzjPRnC_-o/</link>
		<comments>http://chriselyea.com/failure-analysis-lessons/reference-checks-for-safety/#comments</comments>
		<pubDate>Wed, 28 Oct 2009 20:40:55 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[Failure Analysis - Lessons Learned]]></category>
		<category><![CDATA[accident investigation]]></category>
		<category><![CDATA[applicant]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[employee]]></category>
		<category><![CDATA[employer]]></category>
		<category><![CDATA[employment references]]></category>
		<category><![CDATA[job applicant]]></category>
		<category><![CDATA[non-compliance]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[privacy laws]]></category>
		<category><![CDATA[privacy legislation]]></category>
		<category><![CDATA[Procedures]]></category>
		<category><![CDATA[reference check]]></category>
		<category><![CDATA[references]]></category>
		<category><![CDATA[safety]]></category>

		<guid isPermaLink="false">http://chriselyea.com/?p=278</guid>
		<description><![CDATA[How would you respond to someone conducting a reference check on a worker you considered unsafe? Read about this accident and see if you agree that privacy can create a significant safety hazard.]]></description>
				<content:encoded><![CDATA[<div id="attachment_281" class="wp-caption aligncenter" style="width: 496px"><img class="size-large wp-image-281" title="King_Air_100_Instrument_Panel" src="http://chriselyea.com/wp-content/uploads/2009/10/King_Air_100_Instrument_Panel-1024x684.jpg" alt="King_Air_100_Instrument_Panel" width="486" height="325" /><p class="wp-caption-text">Beech A100 King Air Instrument Panel</p></div>
<p style="text-align: justify;">It’s not unusual for an employer to check the references of a job applicant.  Unfortunately, it is unusual for those references to be useful.  Privacy legislation and the threat of lawsuits make many afraid to provide a complete and open evaluation of a former employee.  Read about this accident and see if you agree that privacy can create a significant safety hazard.</p>
<p style="text-align: justify;">At Airline #1, a pilot was employed as a first officer.  He was reprimanded four times over two years for not following procedures.  Airline #1 gave him a letter of reference stating that he had performed well.</p>
<p style="text-align: justify;">Airline #2 hired the pilot as a captain and then demoted him to first officer for repeatedly violating standard operating procedures (SOPs).<span id="more-278"></span></p>
<p style="text-align: justify;">Airline #3 also hired the pilot as a captain and then demoted him to first officer because of “… weak systems knowledge, pre-flight planning shortcuts, fixation on minor problems, dwelling on errors, narrow attention span, and poor decision making.”<sup>*</sup> After three years, Airline #3 refused to renew his pilot proficiency check because he was unsatisfactory in crew coordination, crew resource management, and adherence to procedures.  This refusal meant that the pilot could no longer fly for this airline.  Airline #3 later “… provided the captain with a letter of reference stating that he had been employed as a captain for three and one-half years, that he was extremely knowledgeable about the aircraft he flew, and that, at times, he operated the aircraft in accordance with the SOPs.”<sup>*</sup></p>
<p style="text-align: justify;">The pilot started work as a captain for Airline #4 on May 8<sup>th</sup>, 2006.  He was killed in a crash on January 7<sup>th</sup>, 2007.  His copilot (who had far less experience) received minor injuries and their two passengers were seriously injured.  Failing to follow procedures and poor crew resource management were cited in the list of causes and contributing factors.</p>
<p style="text-align: justify;">Airline #4 had not attempted to check the pilot’s references, but it turns out that wouldn’t have mattered.  The first three airlines told the Transportation Safety Board they would not have provided any negative information about the pilot to any prospective employers that asked them.  They were concerned about breaking federal and provincial privacy laws, and being sued.  They were even reluctant to divulge this information to the investigators.  What’s probably worse than refusing to provide negative information is that, “In fact, the letters of reference the companies provided portrayed a substantially different perspective of the captain than did their training records.”<sup>*</sup></p>
<p style="text-align: justify;">As noted in the accident report, the U.S. National Transportation Safety Board identified this as a safety issue in 1988.  This eventually led to a new law, the <em>Pilot Records Improvement Act of 1996</em>.  This safety hazard remains for everyone else, employers, employees, and the public, too.</p>
<p style="text-align: justify;">
<p>*<a title="Transportation Safety Board Aviation Investigation Report Number A07C0001" rel="nofollow" href="http://www.tsb.gc.ca/eng/rapports-reports/aviation/2007/a07c0001/a07c0001.asp" target="_blank"><em>Transportation Safety Board Aviation Investigation Report Number A07C0001</em></a></p>
<img src="http://feeds.feedburner.com/~r/ChrisElyea/~4/RNzjPRnC_-o" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://chriselyea.com/failure-analysis-lessons/reference-checks-for-safety/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chriselyea.com/failure-analysis-lessons/reference-checks-for-safety/</feedburner:origLink></item>
		<item>
		<title>When Deviation Becomes the Norm</title>
		<link>http://feedproxy.google.com/~r/ChrisElyea/~3/uAymKKeHiDc/</link>
		<comments>http://chriselyea.com/failure-analysis-lessons/why-workers-deviate-from-procedures/#comments</comments>
		<pubDate>Wed, 21 Oct 2009 16:41:42 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[Failure Analysis - Lessons Learned]]></category>
		<category><![CDATA[accident investigation]]></category>
		<category><![CDATA[accident prevention]]></category>
		<category><![CDATA[adaptation]]></category>
		<category><![CDATA[deviation]]></category>
		<category><![CDATA[human factors]]></category>
		<category><![CDATA[incident investigation]]></category>
		<category><![CDATA[incident prevention]]></category>
		<category><![CDATA[non-compliance]]></category>
		<category><![CDATA[Procedures]]></category>
		<category><![CDATA[safety]]></category>
		<category><![CDATA[sop]]></category>
		<category><![CDATA[standard operating procedures]]></category>
		<category><![CDATA[task saturation]]></category>

		<guid isPermaLink="false">http://chriselyea.com/?p=253</guid>
		<description><![CDATA[A recent crash investigation yielded some very useful insights into why workers deviate from procedures.  This analysis applies to any workplace that relies on procedures for safe and reliable outcomes.]]></description>
				<content:encoded><![CDATA[<div id="attachment_256" class="wp-caption aligncenter" style="width: 515px"><img class="size-large wp-image-256" title="C-GSYN_Adlair_Aviation_Ltd_Beechcraft_King_Air_100_(BE10)_03" src="http://chriselyea.com/wp-content/uploads/2009/10/C-GSYN_Adlair_Aviation_Ltd_Beechcraft_King_Air_100_BE10_03-1024x773.jpg" alt="Beech A100 King Air" width="505" height="381" /><p class="wp-caption-text">Beech A100 King Air</p></div>
<p style="text-align: center;">
<p style="text-align: justify;">A recent crash investigation yielded some very useful insights into why workers deviate from procedures.  This analysis applies to any workplace that relies on procedures for safe and reliable outcomes.</p>
<p style="text-align: justify;">Standard operating procedures (SOPs) are a quality assurance tool.  In the context of this posting, they define parameters for working safely.  Procedures can be perceived to reduce productivity and it seems to be a natural human tendency to deviate from them.  Such deviations do not have to be malicious violations (e.g. motivated by laziness or cheating), they can be well-meaning attempts to manage a high workload (including task saturation), to simplify complexity, or to cope with situations not envisaged when the procedures were developed.</p>
<p style="text-align: justify;">With sufficient repetition, deviations can become routine and workers stop recognizing their actions as deviations.  The threat of punishment is not a deterrent because these deviations are no longer deliberate (workers don’t decide to risk punishment by deviating, they no longer realize they are deviating).  Supervision is the only way to detect deviations and bring them to the attention of workers.  Investigating the causes of such deviations can also help improve procedures to reduce the incentive for future deviation.</p>
<p style="text-align: justify;"><span id="more-253"></span>The accident report explains it extremely well:</p>
<p style="text-align: justify;">“Time and resource pressures can result in individuals making adaptations to get the job done. While SOPs are prescribed in order to set boundaries for safe operations, individuals may experiment with the boundaries in order to become more productive. This leads to adaptations of procedures and a shift beyond the prescribed boundaries described in the SOPs toward unsafe practices.<sup>32</sup></p>
<p style="text-align: justify;">“One reason for this is that humans rarely perform work with strict adherence to prescribed rules or instructions. Procedures are often developed for a particular task in isolation from the work context. Performance requirements impose constraints on operators beyond what was considered (and available) when the task instructions were written. To get the job done, people work outside the defined rules. This is why studies of humans, even those working in high-risk, complex systems, have found that operators modify instructions and violate rules in ways that are quite rational given the actual workload and timing constraints (Dekker, 2006).<sup>33</sup></p>
<p style="text-align: justify;">“Without regular supervision, education, and enforcement of the expected boundaries, individuals are likely to continue to adapt procedures and cut corners until the actual unsafe boundary is found through the occurrence of a minor or major accident. Additionally, the communication of successful adaptations between crew members … will tend to lead to the spread of these adaptations throughout an organization unless adequate supervision is applied.</p>
<p style="text-align: justify;">“The captain’s history of non-compliance indicates that he had a predisposition toward deviations from required procedures, but does not in itself support a conclusion that the non-compliance was deliberate. The crew of {the accident flight} and most of the other {regional airline’s} pilots were likely unaware that the many policy and procedural deviations identified by this investigation were actually deviations. Some of the SOP deviations were adaptations. As described {above}, adaptations occur when humans adapt their behaviour to their work. … The deviations within the {regional airline’s} operation almost certainly developed into routine practices for the flight crews and were not deliberate digressions.</p>
<p style="text-align: justify;">“Without increased supervisory surveillance to identify routine deviations, crews were unlikely to identify practices that were no longer conforming to established procedure or policy. The new disciplinary policy, designed to stop conscious deviations, was unlikely to have the rapid, broad impact that was intended because it was not accompanied by proactive identification of routine deviations.”<sup>*</sup></p>
<p style="text-align: justify;">* Quoted from <em><a title="Transportation Safety Board Aviation Investigation Report Number A07C0001" href="http://www.tsb.gc.ca/eng/rapports-reports/aviation/2007/a07c0001/a07c0001.asp" target="_blank">Transportation Safety Board Aviation Investigation Report Number A07C0001</a></em>, which listed these references:</p>
<p style="text-align: justify;">32 J. Rasmussen, “Risk management in a dynamic society: a modeling problem,” <em>Safety Science</em>, pages 197, 27 (2-3), 183-213</p>
<p style="text-align: justify;">33 Transport Canada, <em><a title="Safety Study on Risk Profiling the Air Taxi Sector in Canada" href="http://www.tc.gc.ca/civilaviation/regserv/SafetyIntelligence/AirTaxiStudy/menu.htm" target="_blank">Safety Study on Risk Profiling the Air Taxi Sector in Canada</a></em>, September 2007, RDIMS 3820455 v3, paraphrasing from S. Dekker, <em>The Field Guide to Understanding Human Error</em>, Ashgate, 2006</p>
<img src="http://feeds.feedburner.com/~r/ChrisElyea/~4/uAymKKeHiDc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://chriselyea.com/failure-analysis-lessons/why-workers-deviate-from-procedures/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chriselyea.com/failure-analysis-lessons/why-workers-deviate-from-procedures/</feedburner:origLink></item>
		<item>
		<title>Part 10:  Conclusion – Shuttle Crew Safety Could Be Improved</title>
		<link>http://feedproxy.google.com/~r/ChrisElyea/~3/rT2wp8yL5lk/</link>
		<comments>http://chriselyea.com/failure-analysis-lessons/part-10-conclusion-shuttle-safety-still-needs-improvement/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 15:41:32 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[Failure Analysis - Lessons Learned]]></category>
		<category><![CDATA[ACES]]></category>
		<category><![CDATA[advanced crew escape suit]]></category>
		<category><![CDATA[Apollo]]></category>
		<category><![CDATA[CAIB]]></category>
		<category><![CDATA[Challenger]]></category>
		<category><![CDATA[Columbia]]></category>
		<category><![CDATA[Columbia Accident Investigation Board]]></category>
		<category><![CDATA[Columbia crew survival investigation report]]></category>
		<category><![CDATA[Constellation]]></category>
		<category><![CDATA[external tank]]></category>
		<category><![CDATA[foam]]></category>
		<category><![CDATA[human spaceflight]]></category>
		<category><![CDATA[NASA]]></category>
		<category><![CDATA[Nomex]]></category>
		<category><![CDATA[nylon]]></category>
		<category><![CDATA[oxygen]]></category>
		<category><![CDATA[parachute]]></category>
		<category><![CDATA[pressure suit]]></category>
		<category><![CDATA[Procedures]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[review of human space flight plans committee]]></category>
		<category><![CDATA[review of U.S. human space flight plans committee]]></category>
		<category><![CDATA[review of u.s. human spaceflight plans committee]]></category>
		<category><![CDATA[Rogers Commission]]></category>
		<category><![CDATA[safety]]></category>
		<category><![CDATA[SCSIIT]]></category>
		<category><![CDATA[shuttle]]></category>
		<category><![CDATA[space fligh]]></category>
		<category><![CDATA[Space Shuttle]]></category>
		<category><![CDATA[space transportation system]]></category>
		<category><![CDATA[spacecraft crew survival integrated investigation team]]></category>
		<category><![CDATA[SR-71]]></category>
		<category><![CDATA[survivable]]></category>
		<category><![CDATA[training]]></category>
		<category><![CDATA[visor]]></category>

		<guid isPermaLink="false">http://chriselyea.com/?p=83</guid>
		<description><![CDATA[NASA’s conclusion from the Columbia accident seems to be, “We’ve found the problem and we won’t let it happen again.”  Yet foam fell off the external tank as the Space Shuttle Endeavour headed for orbit on July 15th, 2009.  I think a different approach is in order.]]></description>
				<content:encoded><![CDATA[<p style="text-align: justify;">
<div id="attachment_141" class="wp-caption aligncenter" style="width: 522px"><img class="size-full wp-image-141" title="10 Orion Cutaway - image from NASA" src="http://chriselyea.com/wp-content/uploads/2009/09/10-Orion-Cutaway-image-from-NASA.jpg" alt="Cutaway of Orion capsule" width="512" height="383" /><p class="wp-caption-text">The Shuttle&#39;s replacement: the Orion capsule</p></div>
<p style="text-align: justify;">Some things have changed for the better.  Debris from the Space Shuttle <em>Challenger</em> was dumped into an abandoned missile silo.  Out of sight, out of mind, perhaps.  Even the data was not catalogued for use in further investigations.  The Spacecraft Crew Survival Integrated Investigation Team (SCSIIT) lamented that, “The lack of debris for comparison and methods of data preservation made the <em>Challenger</em> data essentially unavailable for this investigation.”</p>
<p style="text-align: justify;">Not so with the debris and data from <em>Columbia</em>.  Both have been preserved to allow further investigation and research into the development of future spacecraft and crew survival equipment.  Given the timing of the <em>Columbia Crew Survival Investigation Report</em>, the SCSIIT members might not have had any other option to make their work meaningful.  Design of space vehicles for the Constellation program, which are to take astronauts to the Moon and possibly to Mars, has already begun.</p>
<p style="text-align: justify;">On the other hand, as a result of the <em>Challenger</em> accident, NASA made some substantial changes to improve the survivability of a Space Shuttle accident.  Unfortunately, the <em>Columbia</em> accident does not appear to have initiated much in the way of further improvements, despite a demonstrated need to do so.  Following the report of the Columbia Accident Investigation Board, the Shuttles were returned to service, not waiting for the <em>Columbia Crew Survival Investigation Report</em>.<span id="more-83"></span></p>
<p style="text-align: justify;">SCSIIT does not seem to have harboured any illusions that their report would impact the Shuttle program.  In fact, SCSIIT maintained confidentiality until they had published their report, although apparently they did release some interim directives internally.   It's not possible for me to say if  any of their findings benefited the first eleven missions after <em>Columbia</em>, except for the replacement of the seat belt inertial reels.</p>
<p style="text-align: justify;">NASA’s conclusion from the <em>Columbia</em> accident seems to be, “We’ve identified the problem and made changes so it probably won't happen again.  If it does, we'll find it and fix it.”  They’ve increased inspection of the external tank prior to launch, increased the quantity and quality of surveillance during ascent, developed repair kits, implemented a thorough in-orbit investigation of the Shuttle, and have a contingency plan for a second Shuttle to mount a rescue mission.</p>
<p style="text-align: justify;">Foam fell off the external tank as the Space Shuttle <em>Endeavour</em> headed for orbit on July 15<sup>th</sup>, 2009, so the threat of catastrophic damage from that remains, even if NASA is better at detecting it.  But what if there are other unknown threats?  I think a different approach is in order.</p>
<p style="text-align: justify;">
<p style="text-align: justify;"><span style="text-decoration: underline;">ADDENDUM</span></p>
<p style="text-align: justify;">The <em>Summary Report of the Review of U.S. Human Space Flight Plans Committee</em> was published on September 8th, 2009.  The Committee was set up to provide the Obama Administration with an evaluation of NASA's current plan versus its budget.  In the words of the Committee:</p>
<p style="text-align: justify;">“The Committee noted that the projected flight rate is nearly twice that of the actual flight rate since return to flight after the <em>Columbia </em>accident.  Recognizing that undue schedule and budget pressure can subtly impose a negative influence on safety, the Committee finds that a more realistic schedule is prudent. With the remaining flights likely to stretch into the second quarter of 2011, the Committee considers it important to budget for Shuttle operations through that time.”</p>
<p style="text-align: justify;">In other words, the Committee is concerned that the budget set by the Bush Administration, which retires the Shuttle fleet in 2010 so that NASA can concentrate on the next generation of space vehicle, has resulted in an overly compressed schedule for the remaining Shuttle flights.  The <em>Challenger</em> accident may be seen as an example of past reluctance to delay the program (until the known O-ring flaw could be rectified).  The Obama Administration has already allowed NASA to extend the Shuttle program into Fiscal Year 2011, but it hasn't budgeted any additional funding.  I hope the Administration acts on the Committee's recommendation to provide sufficient time and money to operate the Shuttles safely.</p>
<img src="http://feeds.feedburner.com/~r/ChrisElyea/~4/rT2wp8yL5lk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://chriselyea.com/failure-analysis-lessons/part-10-conclusion-shuttle-safety-still-needs-improvement/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chriselyea.com/failure-analysis-lessons/part-10-conclusion-shuttle-safety-still-needs-improvement/</feedburner:origLink></item>
	</channel>
</rss>
