<?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/"
	>

<channel>
	<title> &#187; Uncategorized</title>
	<atom:link href="http://wikirfm.cyclicandcollective.net/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://wikirfm.cyclicandcollective.net</link>
	<description></description>
	<lastBuildDate>Sat, 24 Jul 2010 08:07:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>HOT Spots</title>
		<link>http://wikirfm.cyclicandcollective.net/2010/07/hot-spot/</link>
		<comments>http://wikirfm.cyclicandcollective.net/2010/07/hot-spot/#comments</comments>
		<pubDate>Sun, 04 Jul 2010 20:54:17 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[BoatPix]]></category>
		<category><![CDATA[time building]]></category>

		<guid isPermaLink="false">http://wikirfm.cyclicandcollective.net/?p=1606</guid>
		<description><![CDATA[This week I&#8217;m headed down to San Francisco to do a few hours of time building with BoatPix. In preparation, I&#8217;ve been reviewing the airspace (much busier than I&#8217;m used to) and the airport layout. The airport looks like it has a fair bit of helicopter traffic, and you can see several &#8220;helicopter alighting areas&#8221; [...]]]></description>
			<content:encoded><![CDATA[<p>This week I&#8217;m headed down to San Francisco to do a few hours of time building with <a href="http://r22.us/">BoatPix</a>. In preparation, I&#8217;ve been reviewing the airspace (much busier than I&#8217;m used to) and the airport layout. The airport looks like it has a fair bit of helicopter traffic, and you can see several &#8220;helicopter alighting areas&#8221; (lower left corner). One thing I wasn&#8217;t familiar with were the 4 areas marked &#8220;HOT.&#8221; No airport I&#8217;d ever flown out of had anything like this, and I had no idea what they were. The legend for the airport diagrams wasn&#8217;t much help either&#8211;it just identifies them as Hot spots.</p>
<p><a href="http://wikirfm.cyclicandcollective.net/wp-content/uploads/2010/07/HOT-spots.jpg"><img class="aligncenter size-full wp-image-1609" title="HOT spots" src="http://wikirfm.cyclicandcollective.net/wp-content/uploads/2010/07/HOT-spots.jpg" alt="" width="365" height="431" /></a></p>
<p>Right after the legend though, there&#8217;s an index of all the HOT Spots, similar to how you&#8217;d see alternate minimums or departure procedures listed in the TERPs. The preface describes the HOT spots as movement areas with a history or risk of collision or runway incursion. Makes sense&#8211;all these HOT spots are at complex intersections or intersections with high intersection angles. The number then refers to an index of explanations for each spot. In this case, 2 of the spots identify areas where pilots often make wrong turns, another is for the complex intersection of Rwy 01R-19L, Twy J, Twy A, Twy C, and Twy K, and the last is a hold-short area for 32L. The FAA lists about <a href="http://www.faa.gov/airports/runway_safety/hotspots/hotspots_list/">90 airports</a> that have identified HOT spots.</p>
<p>Unfamiliar airport, airspace, and aircraft, not to mention that I have only 6 hours in the R22 in the last 30 days. Should be a daunting flight. Wish me luck and good weather.</p>
]]></content:encoded>
			<wfw:commentRss>http://wikirfm.cyclicandcollective.net/2010/07/hot-spot/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>FACT-ICD</title>
		<link>http://wikirfm.cyclicandcollective.net/2010/01/fact-icd/</link>
		<comments>http://wikirfm.cyclicandcollective.net/2010/01/fact-icd/#comments</comments>
		<pubDate>Tue, 19 Jan 2010 01:55:16 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wikirfm.cyclicandcollective.net/?p=1301</guid>
		<description><![CDATA[That&#8217;s how I remember the reporting requirements specified under NTSB 830.5: F Flight controls A Accident C Crew member illness or injury T Turbine components I In-flight fire C Collision D Damage to property It&#8217;s not perfect, since you also have to remember Overdue Aircraft, and it ignores the rules for large multi-engine aircraft (which [...]]]></description>
			<content:encoded><![CDATA[<p>That&#8217;s how I remember the reporting requirements specified under NTSB 830.5:</p>
<table style="text-align: left; width: 453px; height: 42px;" border="0" cellspacing="3" cellpadding="2">
<tbody>
<tr>
<td style="text-align: center; width: 20px;">F</td>
<td>Flight controls</td>
</tr>
<tr>
<td style="text-align: center; width: 20px;">A</td>
<td>Accident</td>
</tr>
<tr>
<td style="text-align: center; width: 20px;">C</td>
<td>Crew member illness or injury</td>
</tr>
<tr>
<td style="text-align: center; width: 20px;">T</td>
<td>Turbine components</td>
</tr>
<tr>
<td style="text-align: center; width: 20px;">I</td>
<td>In-flight fire</td>
</tr>
<tr>
<td style="text-align: center; width: 20px;">C</td>
<td>Collision</td>
</tr>
<tr>
<td style="text-align: center; width: 20px;">D</td>
<td>Damage to property</td>
</tr>
</tbody>
</table>
<p>It&#8217;s not perfect, since you also have to remember Overdue Aircraft, and it ignores the rules for large multi-engine aircraft (which at this stage in my career just isn&#8217;t much of a big deal). Recently, the NTSB added a few <a href="http://www.aopa.org/advocacy/articles/2010/100114finalrule.html?WT.mc_id=100115epilot&amp;WT.mc_sect=gan" target="_blank">new reporting requirements</a> that go into effect March 8, some of which are definitely relevant for rotorcraft operations:</p>
<ul>
<blockquote>
<li>Failure of any internal turbine engine component that results in the escape of debris other than out the exhaust path;</li>
<li>Any event in which an aircraft operated by an air carrier lands or departs on a taxiway, incorrect runway, or other area not designed as a runway, or experiences a runway incursion that requires the operator or the crew of another aircraft or vehicle to take immediate corrective action to avoid a collision.</li>
<li>Release of all or a portion of a propeller blade from an aircraft, excluding release caused solely by ground contact;</li>
<li>A complete loss of information, excluding flickering, from more than 50 percent of an aircraft’s cockpit displays, known as Electronic Flight Instrument System displays, Engine Indication and Crew Alerting System displays, Electronic Centralized Aircraft Monitor displays, or other such displays;</li>
<li>Airborne Collision Avoidance System (ACAS) resolution advisories issued either (1) when an aircraft is being operated on an instrument flight rules (IFR) flight plan and compliance with the advisory is necessary to avert a substantial risk of collision between two or more aircraft, or (2) to an aircraft operating in class A airspace;</li>
<li>Damage to helicopter tail or main rotor blades, including ground damage, that requires major repair or replacement of the blade(s);</li>
</blockquote>
<p>So now we have flight control failure, aircraft accident, crew member illness or injury, turbine components other than blades and vanes, in-flight fire, mid-air collision, property damage &gt;$25,000, and overdue aircraft <em>plus</em> turbine debris, propeller breaks, glass cockpit failure, collision avoidance in IFR or class A, helicopter rotor blades, and air carrier runway incursions. How about this one: FACTOR DIM GRunT P</p>
<table style="text-align: left; width: 453px; height: 42px;" border="0" cellspacing="3" cellpadding="2">
<tbody>
<tr>
<td style="text-align: center; width: 20px;">F</td>
<td>Flight control failure</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">A</td>
<td>Accident</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">C</td>
<td>Crew illness or injury</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">T</td>
<td>TCAS alert in IFR or Class A</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">O</td>
<td>Overdue aircraft</td>
</tr>
<tr>
<td style="text-align: center;">R</td>
<td>Rotor blade damaged</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">D</td>
<td>Damage to property</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">I</td>
<td>In flight fire</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">M</td>
<td>Mid-air collision</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">G</td>
<td>Glass cockpit</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">Run</td>
<td>Runway incursion by air carrier</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">T</td>
<td>Turbine components or debris</td>
</tr>
<tr>
<td style="width: 30px; text-align: center;">(P)</td>
<td>Propeller</td>
</tr>
</tbody>
</table>
<p>Anybody got a better idea? Oh, and I&#8217;m adding my PPL/CPL/IRH <a href="http://wikirfm.cyclicandcollective.net/ground-lessons/acronymns-and-mnemonics/">Mnemonics and Memory Aids</a> under the ground school lesson. If you want it as a PDF file, become a contributor to the site, and drop me an email.</ul>
]]></content:encoded>
			<wfw:commentRss>http://wikirfm.cyclicandcollective.net/2010/01/fact-icd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stuck Pedals</title>
		<link>http://wikirfm.cyclicandcollective.net/2009/09/stuck-pedals/</link>
		<comments>http://wikirfm.cyclicandcollective.net/2009/09/stuck-pedals/#comments</comments>
		<pubDate>Sun, 20 Sep 2009 19:42:19 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wikirfm.cyclicandcollective.net/?p=594</guid>
		<description><![CDATA[Seems like every 8-12 months, somebody posts a question on one or another of the forums asking about stuck pedal procedures. What ensues depends on who&#8217;s reading the forums at the time. On a good day there are a couple of high-time pilots hanging around that will take the time tell us initiates how they [...]]]></description>
			<content:encoded><![CDATA[<p>Seems like every 8-12 months, somebody posts a question <a href="http://helicopterforum.verticalreference.com/helicopterforum/index.php?showtopic=11654&amp;hl=stuck+pedal" target="_blank">on one</a> or <a href="http://rotorheadforums.com/index.php?topic=403.0">another</a> of the forums asking about stuck pedal procedures. What ensues depends on who&#8217;s reading the forums at the time. On a good day there are a couple of high-time pilots hanging around that will take the time tell us initiates how they have <em>actually</em> handled a stuck pedal or tail rotor failure. On a bad day, there&#8217;s somebody in there that&#8217;s confused about what exactly a stuck pedal is, and the thread becomes a mess of replies. Sorting out the good from the bad is a tedious process, and ultimately doesn&#8217;t matter since the thread disappears from the forum after a short time.</p>
<p>I tried taking the best of the advice from the most recent VR stuck pedal thread and developing 3 ground lessons. The first one is for a complete loss of the tail rotor. The procedure is pretty straightforward, and it&#8217;s in the R22/R44 POH. Interestingly, in a RHC newsletter a few months ago, they had the story of a pilot who didn&#8217;t follow the procedure and still made a successful landing after he lost his tail rotor; that article is attached to the lesson. Anyway, I wanted that lesson up just so there&#8217;s no confusion that the other 2 lessons are about a different problem.</p>
<p>A stuck pedal is a situation where the tail rotor is still producing thrust, but you cannot control it. Saying you have a stuck &#8220;right&#8221; pedal is confusing, since it&#8217;s irrelevant which pedal is stuck. What matters is which way the nose ends up yawing.</p>
<p>Last word on this is a photo in the book, <a href="http://www.amazon.com/gp/richpub/listmania/fullview/R38ECJFS9UUXBS/ref=cm_lm_pthnk_view?ie=UTF8&amp;lm_bb=">Fatal Traps for Helicopter Pilots</a>. The photo was through the chin bubble of an EC-120, and you can see the pilot&#8217;s mobile phone wedged nicely up against the control arm for the right pedal. There are a few interesting points about this case&#8230;the first being that the pilot and controllers had a considerable discussion about what to do in this situation. That right there may suggest a lack of training, but more importantly it indicates that the pilot kept his cool throughout the emergency. Ultimately, he chose doing a running landing (best choice?) to a concrete runway (instead of a grassy area!), and landed without injury or damage to the aircraft. I like to have a pen handy when I&#8217;m pre-flighting so I can record my Hobbs time, weather, last-minute changes to HIGE/HOGE, and clearance instructions. It&#8217;s this picture that always flashes through my mind when I&#8217;m doing my final cockpit check before jumping in the helicopter.</p>
<p>Here are links to the <a href="http://wikirfm.cyclicandcollective.net/ground-lessons/stuck-pedal-left/">Stuck Pedal (Left)</a> and <a href="http://wikirfm.cyclicandcollective.net/ground-lessons/stuck-pedal-right/">Stuck Pedal (Right)</a> ground lessons. I don&#8217;t want to be a test pilot, so I&#8217;m looking forward to seeing how these evolve from what I&#8217;m starting with (which is admittedly incomplete) into tips and tricks from guys who&#8217;ve practiced these in factory courses or dealt with them in real life.</p>
]]></content:encoded>
			<wfw:commentRss>http://wikirfm.cyclicandcollective.net/2009/09/stuck-pedals/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
