<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
If we go this route, I for one will definitely quit.<BR>
<BR>
We already have new sequences designed for 2011 for all the classes. And we have been adopting a maneuver here and there from the FAI sequences. They will be presented in the K-factor sometime in the future. There are even two different sequences put together for Masters. One is the traditional length and the other is the same length as FAI.<BR>
<BR>
The new FAI sequence for next year is a real good example not to flat out adopt a P sequence as it is.<BR> <BR>
<HR id=stopSpelling>
From: burtona@atmc.net<BR>To: nsrca-discussion@lists.nsrca.org<BR>Date: Mon, 19 Oct 2009 11:56:40 -0400<BR>CC: tom_babs@bellsouth.net<BR>Subject: Re: [NSRCA-discussion] Rules proposal 11-6 question<BR><BR>
<STYLE>
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.ecxMsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
.ExternalClass p
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass span.ecxEmailStyle19
{font-family:'Calibri','sans-serif';color:#1F497D;}
.ExternalClass .ecxMsoChpDefault
{font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;}
.ExternalClass div.ecxSection1
{page:Section1;}
</STYLE>
<DIV class=ecxSection1>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">It seems to me that adopting the FAI “P” schedule for the Masters class with “changes” is not the way to go. A better alternative IMO is to fly FAI P schedule under FAI rules as a separate class. Those of us with some age remember when this was done years ago as “D” expert and “D” Novice classes. As I remember AMA class “D” was the FAI event back then. This would have the advantages of two classes flying under the same rules and the benefits of more flyers/judges familiar with the same rules and maneuvers. It would also eliminate the work involved in coming up with a new Masters sequence every three or so years as a new schedule would be automatically be invoked FAI changed. I’d like to see a proposal for this change submitted to the Contest Board.</SPAN></P>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Dave Burton </SPAN></P>
<P class=ecxMsoNormal><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=ecxMsoNormal><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>Vicente "Vince" Bortone<BR><B>Sent:</B> Monday, October 19, 2009 11:29 AM<BR><B>To:</B> General pattern discussion<BR><B>Subject:</B> Re: [NSRCA-discussion] Rules proposal 11-6 question</SPAN></P></DIV></DIV>
<P class=ecxMsoNormal> </P>
<DIV>
<DIV>
<SPAN style="COLOR: black; FONT-FAMILY: 'Arial','sans-serif'">Hi Lance,</SPAN><BR>
<SPAN style="COLOR: black; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><BR>
<P style="MARGIN-BOTTOM: 12pt"><SPAN style="COLOR: black; FONT-FAMILY: 'Arial','sans-serif'">Just to clarify. I am not the only one making this proposal. Don Ramsey and Charlie Rock helped me to put it together. I am going to try to respond to your questions below. Please read below in <STRONG><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">bold. </SPAN></STRONG>Thanks for bringing this discussion to the list. <BR><BR>Vicente "Vince" Bortone<BR><BR>----- Original Message -----<BR>From: "Lance Van Nostrand" <patterndude@tx.rr.com><BR>To: "NSRCA Mailing List" <nsrca-discussion@lists.nsrca.org><BR>Sent: Sunday, October 18, 2009 11:51:30 PM GMT -06:00 US/Canada Central<BR>Subject: [NSRCA-discussion] Rules proposal 11-6 question</SPAN></P>
<DIV>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Arial','sans-serif'">I know official discussion hasn't started but this list is one of the good vetting forums. Vince proposed Masters flying FAI P, which is clear <STRONG><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">(this is for sure the most important statement)</SPAN></STRONG>, but if the logic behind the proposal as written causes confusion it may make a less convincing case. <STRONG><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">Good point. We assumed that was easy for someone that is very familiar to pattern to digest the intent of the proposal. Your conclusions are correct. We are assuming that the current procedures we use to design the Master schedule are not changed. We adopt the current FAI P schedule with the appropriate changes to suit the Master class. This is the reason why we didn't try to discuss other details. </SPAN></STRONG>For example, it says "there is an evident pile up f pilots in the Masters class" but never clearly states how flying the same sequence would change that. He may be implying that people will more freely move between classes to balance the lines because they are flying a similar sequence but the sequences may not be identical and the judging rules are not identical. <STRONG><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">Correct. You actually saw what happened in Tulsa this year. There were 10 pilots in Masters and you decided to divide the group in two and five flew Masters and five flew FAI. This also happened already in other local contest around KC. It happens at Fort Scott contest also. Pilots will be more willing to do this we fly the same schedule. </SPAN></STRONG>At another point it says "This will make judging of both classes very accurate" but doesn't address the obvious differences in judging criteria between AMA and FAI, which is the current burden that Masters and FAI pilots currently bear when the fly one class and judge the other.<STRONG><SPAN style="FONT-FAMILY: 'Arial','sans-serif'"> I am sure that we will agree that it will be a lot easier to deal with these differences if we fly the same schedules. The proposal intent is not to address the differences in judging criteria between AMA and FAI. I believe that it will become natural as we start to fly the same schedule and the differences will go away with time. </SPAN></STRONG>Finally, there is no exact wording proposed on the form where it is expected, but later in the logic it refers to the idea of replacing some FAI maneuvers where appropriate. <STRONG><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">We are assuming that the current procedure to design the schedules is still in place. The committee will check the current FAI P schedule and proposed a final one with the changes to make it suitable for Masters. For example, P11 the only portion I will change is the integrated half loop on the figure M. I will suggest something like 2 of 4 or 1/2 roll on bottom to replace the integrated 1/2 roll. I believe that all other maneuvers are suitable for Masters. </SPAN></STRONG>Without exact wording, its not clear how this is done, or if the maneuver descriptions will be re-written in the AMA rules, or referenced to the FAI descriptions like the sequence. <STRONG><SPAN style="FONT-FAMILY: 'Arial','sans-serif'">The committee will decide whatever is appropriate. If they feel that the FAI descriptions are appropiate we could use it as is.</SPAN></STRONG> Oh, and how does AMA deal with the fact that FAI changes schedules in odd years?<STRONG><SPAN style="FONT-FAMILY: 'Arial','sans-serif'"> We will need to follow FAI schedule. I think that this is very possible and should not be a problem. </SPAN></STRONG></SPAN><SPAN style="COLOR: black; FONT-FAMILY: 'Arial','sans-serif'"></SPAN></P></DIV>
<DIV>
<P class=ecxMsoNormal><SPAN style="COLOR: black; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN></P></DIV>
<DIV>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Arial','sans-serif'">My intent is simply to point out aspects that detract from it's thoroughness. I do not yet have a stance on the issue.<STRONG><SPAN style="FONT-FAMILY: 'Arial','sans-serif'"> We put this together just taking at the 2008 Nats. I remember that I have to judge FAI and I never had the chance to judge FAI before the Nats. I was trying to study the FAI schedule at the same time that I was trying to fly my own contest. This is clearly an additional pressure on the contestant. If this proposal pass it will make our life easier at the local contest and when we judging at the Nats or any other contest. Also, clearly will make the judging level very high because Masters and FAI pilots will be very familiar with the schedules we fly and the details requires to judge each of the maneuvers. Finally, the balance in local contest will be easier to fix since we will more willing to fly FAI when required. </SPAN></STRONG></SPAN><SPAN style="COLOR: black; FONT-FAMILY: 'Arial','sans-serif'"></SPAN></P></DIV>
<DIV>
<P class=ecxMsoNormal><SPAN style="COLOR: black; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN></P></DIV>
<DIV>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Arial','sans-serif'">--Lance</SPAN><SPAN style="COLOR: black; FONT-FAMILY: 'Arial','sans-serif'"></SPAN></P></DIV>
<P class=ecxMsoNormal><SPAN style="COLOR: black; FONT-FAMILY: 'Arial','sans-serif'"><BR>_______________________________________________ NSRCA-discussion mailing list NSRCA-discussion@lists.nsrca.org http://lists.nsrca.org/mailman/listinfo/nsrca-discussion</SPAN></P></DIV></DIV></DIV> <br /><hr />Hotmail: Free, trusted and rich email service. <a href='http://clk.atdmt.com/GBL/go/171222984/direct/01/' target='_new'>Get it now.</a></body>
</html>