<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'><P>Perhaps, Joe, you have hit upon the crux of the discussion here in your first sentence. It makes me ask- what is NSRCA's charter? Is the singular goal to develop flyers skills so that they can progress through the classes or is it a more diverse set of goals that includes developing skill along with giving equal weight to things like driving membership and contest participation even if it comes at some cost to the first goal? As a relative newcomer here I will say that my impression is that is the former and not so much the latter. My opinion only.</P>
<P> </P>
<P> </P>
<P> </P>
<P> </P>
<P> </P>
<P> <BR>----- Original Message -----<BR>From: "Joe Lachowski" <jlachow@hotmail.com><BR>To: "NSRCA Discussion List" <nsrca-discussion@lists.nsrca.org><BR>Sent: Saturday, January 31, 2009 2:46:14 PM GMT -05:00 US/Canada Eastern<BR>Subject: Re: [NSRCA-discussion] K-Factor morphed into Grow Pattern<BR><BR>
<STYLE>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</STYLE>
Changing schedules yearly does not systematically help in developing(perfecting) skill sets at each level. Changing schedules every 2 ,3 or 4 yrs is more doable. I think Sportsman should be changed maybe every 6 years if deemed necessary. Intermediate and Advanced could be changed every 3 or 4 yrs with Masters changed every 2 years. Also, schedule changes for the various classes needs to be staggered. Wholesale changes is a major task. In order to make more frequent schedule changes, permanent guidelines need to be used to ensure unintended difficulty creep. Derek has the guidelines in his hands that myself and few others put together. If these guidelines are adhered to, there is no reason why we can't change schedules more frequently provided they are not under AMA control as they are now. Believe me putting together new sequences that make sense and adresses the needs at each level is not as easy as it looks. <BR> <BR>PS - As far as outright adopting FAI sequences for Masters goes, I am totally against it. I could maybe accept using an FAI sequence and then tweaking it to fit the criteria that was developed in the guidelines that were put together.<BR><BR></P>
<P>
<HR id=stopSpelling>
</P>
<P><BR>Date: Sat, 31 Jan 2009 11:43:02 -0700<BR>From: rob@koolsoft.com<BR>To: nsrca-discussion@lists.nsrca.org<BR>Subject: Re: [NSRCA-discussion] K-Factor morphed into Grow Pattern<BR><BR><BR></P>
<STYLE>
.ExternalClass .EC_shape
{;}
</STYLE>
<STYLE>
.ExternalClass p.EC_MsoNormal, .ExternalClass li.EC_MsoNormal, .ExternalClass div.EC_MsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass p.EC_MsoNormalIndent, .ExternalClass li.EC_MsoNormalIndent, .ExternalClass div.EC_MsoNormalIndent
{margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass a:link, .ExternalClass span.EC_MsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.EC_MsoHyperlinkFollowed
{color:blue;text-decoration:underline;}
.ExternalClass p.EC_MsoAutoSig, .ExternalClass li.EC_MsoAutoSig, .ExternalClass div.EC_MsoAutoSig
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass pre
{margin-bottom:.0001pt;font-size:10.0pt;font-family:'Courier New';}
.ExternalClass span.EC_HTMLPreformattedChar
{font-family:Consolas;}
.ExternalClass span.EC_E-mailSignatureChar
{;}
.ExternalClass p.EC_msolistparagraph0, .ExternalClass li.EC_msolistparagraph0, .ExternalClass div.EC_msolistparagraph0
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass span.EC_apple-style-span
{;}
.ExternalClass span.EC_apple-converted-space
{;}
.ExternalClass span.EC_emailstyle52
{;}
.ExternalClass span.EC_EmailStyle26
{font-family:'Arial','sans-serif';color:navy;}
.ExternalClass span.EC_EmailStyle27
{font-family:'Arial','sans-serif';color:navy;}
.ExternalClass span.EC_EmailStyle28
{font-family:'Calibri','sans-serif';color:#1F497D;}
.ExternalClass .EC_MsoChpDefault
{font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;}
.ExternalClass div.EC_Section1
{page:Section1;}
</STYLE>
<DIV class=EC_Section1>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">The idea around changing the routines each year is intended to provide a little change for someone that fly's the same level for more than one year. Since Sportsman and Intermediate are definitely not end levels like Master where the same competitors fly them year after year after year, the routines can be from a pool of pre approved routines. </SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Three Sportsman routines can be developed and then rotated on a 3 year basis. Same for intermediate. For that matter, you could use the past 3 different sportsman routines and just rotate them on a yearly basis. This is nice because it doesn't requires a committee to come up with a routine every year for those levels. Advanced might also fall into this category as well, but definitely not Masters. They need a routine committee because pilots can be in that class for years and years and change to keep things interesting would definitely be needed.</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P>
<DIV>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">- Robert Beaubien</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">- NSRCA, District 7 Webmaster</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">-</SPAN></P></DIV>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"></SPAN> </P>
<DIV>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=EC_MsoNormal><B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> nsrca-discussion-bounces@lists.nsrca.org [mailto:nsrca-discussion-bounces@lists.nsrca.org] <B>On Behalf Of </B>J N Hiller<BR><B>Sent:</B> Saturday, January 31, 2009 11:30 AM<BR><B>To:</B> General pattern discussion<BR><B>Subject:</B> Re: [NSRCA-discussion] K-Factor morphed into Grow Pattern</SPAN></P></DIV></DIV>
<P class=EC_MsoNormal> </P>
<P class=EC_MsoNormal><SPAN class=EC_EmailStyle27><SPAN style="FONT-SIZE: 10pt">OK guys if you are going to change the schedules every year you need to change the current mandatory advancement system as well so competitors aren’t advanced prematurely. But we kind of have that problem now.</SPAN></SPAN></P>
<P class=EC_MsoNormal><SPAN class=EC_EmailStyle27><SPAN style="FONT-SIZE: 10pt">Jim Hiller</SPAN></SPAN></P>
<P class=EC_MsoNormal><SPAN class=EC_EmailStyle26><SPAN style="FONT-SIZE: 10pt"></SPAN></SPAN> </P>
<P class=EC_MsoNormal><SPAN class=EC_EmailStyle26><SPAN style="FONT-SIZE: 10pt"></SPAN></SPAN> </P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Tahoma','sans-serif'">-----Original Message-----<BR><B>From:</B> nsrca-discussion-bounces@lists.nsrca.org [mailto:nsrca-discussion-bounces@lists.nsrca.org]<B>On Behalf Of </B>Derek Koopowitz<BR><B>Sent:</B> Saturday, January 31, 2009 10:14 AM<BR><B>To:</B> 'General pattern discussion'<BR><B>Subject:</B> Re: [NSRCA-discussion] K-Factor morphed into Grow Pattern</SPAN></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"> </P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">The AMA has indicated to us that this will be considered - it will definitely be a rules proposal if everyone agrees.</SPAN></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"> </P>
<DIV style="MARGIN-LEFT: 0.5in">
<DIV class=EC_MsoNormal style="TEXT-ALIGN: center" align=center><SPAN style="COLOR: black">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV></DIV>
<P class=EC_MsoNormal style="MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; MARGIN-RIGHT: 0in"><B><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Tahoma','sans-serif'"> nsrca-discussion-bounces@lists.nsrca.org [mailto:nsrca-discussion-bounces@lists.nsrca.org] <B>On Behalf Of </B>Budd Engineering<BR><B>Sent:</B> Saturday, January 31, 2009 9:51 AM<BR><B>To:</B> General pattern discussion<BR><B>Subject:</B> Re: [NSRCA-discussion] K-Factor morphed into Grow Pattern</SPAN></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN style="COLOR: black">Now that Dave Brown is gone we should try again.<BR><BR></SPAN></P>
<DIV>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN style="FONT-SIZE: 10.5pt; COLOR: black; FONT-FAMILY: Helvetica"><BR>Budd Engineering</SPAN></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN style="FONT-SIZE: 10.5pt; COLOR: black; FONT-FAMILY: Helvetica"><A href="mailto:jerry@buddengineering.com" target=_blank>jerry@buddengineering.com</A></SPAN></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN style="FONT-SIZE: 10.5pt; COLOR: black; FONT-FAMILY: Helvetica"><A href="http://www.buddengineering.com/" target=_blank>http://www.buddengineering.com</A></SPAN></P></DIV>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"> </P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN style="COLOR: black">On Jan 31, 2009, at 9:18 AM, Gene Maurice wrote:</SPAN></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN style="COLOR: black"><BR><BR></SPAN></P>
<DIV>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'">A BIG difference is that the IMAC schedules are an addendum to the rulebook and DON’T have to go thru a rules cycle to change. We’ve tried this and failed to get it past the AMA.</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'"></SPAN> </P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 1in; MARGIN-RIGHT: 0.5in"><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'">Gene Maurice</SPAN></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 1in; MARGIN-RIGHT: 0.5in"><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'">Plano, TX</SPAN></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 1in; MARGIN-RIGHT: 0.5in"><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'">AMA 3408 NSRCA 877</SPAN></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 1in; MARGIN-RIGHT: 0.5in"><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'">PACSS.sgmservice.com</SPAN></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"> </P></DIV></DIV><BR>
<HR>
Windows Live™ Hotmail®…more than just e-mail. <A href="http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_hm_justgotbetter_howitworks_012009" target=_blank>See how it works.</A> <BR>_______________________________________________ NSRCA-discussion mailing list NSRCA-discussion@lists.nsrca.org http://lists.nsrca.org/mailman/listinfo/nsrca-discussion</div></body></html>