<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">Joe</div><div dir="auto">Fair enough my friend.</div><div dir="auto">Well written. I fully understand but will add that my comment is a popular sentiment among my peers.</div><div dir="auto"> It's not solvable. Nature of the beast.</div><div dir="auto"> I was told two years ago that progress was being made by some developers in Europe of an automated scoring system. It utilizes sensors being placed on the models and GPS.</div><div dir="auto"> Fully automated system.</div><div dir="auto"> If we ever achieve this it would be a true game changer.</div><div dir="auto">M2</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Verizon, Samsung Galaxy smartphone</div></div><div dir="auto"><br></div><div><br></div><div style="font-size:100%;color:#000000" dir="auto"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Jas S via NSRCA-discussion <nsrca-discussion@lists.nsrca.org> </div><div>Date: 12/22/19 9:13 AM (GMT-06:00) </div><div>To: General pattern discussion <nsrca-discussion@lists.nsrca.org> </div><div>Subject: Re: [NSRCA-discussion] P-21.14 Comet question for the experts </div><div><br></div></div>Pilots have to be able judge a class up or down or both. Depending on the turnout some even have to judge a couple above or below their class. That is part of pattern. It’s the part that many don’t enjoy, but the pilot enjoys getting an accurate score based on their flight. <div>It is up to us, the pilots, to understand the patterns enough to be able to judge them fairly. I’ve always said, patterns are just lines and loops with elements included. If you take out the elements (rolls/snaps) in F3A, you have something close to an Intermediate pattern. I do this from time to time to focus on geometry and flow, especially with new patterns. Judging does not require a pilot to be capable of flying the maneuvers, just to be able to break down each one into its basics and judge accordingly.</div><div>These discussions are good to have. This in particular because here in D3 we have had this same discussion and we came up with the conclusion the lines didn’t have to be the same. I practiced it the same so that’s what I continued to do but others did it with different line lengths. The PP didn’t specify either so we left it at that but now we know.</div><div>Another example is the Center Humpty in Masters. The aresti, while never drawn accurately since it’s inception, shows corners at the top and a half loop at the bottom. That’s not how it’s supposed to be flown though. Like the PP shows (too many pages to have on a call sheet) it’s matching 2- 1/4 loops on top and a 1/2 loop with the same radiI at the bottom. Unfortunately none did it that way during the contest and lost a handful of points because of it. </div><div>I’m not sure if pilots realize this or not, but understanding how to judge a pattern correlates to being able to improve ones flying of a pattern. Once you start to get picky about your judging, you’ll start to get picky about your flying and everything gets better. </div><div><br></div><div>Happy Holidays<br><br><div dir="ltr">Jas iP</div><div dir="ltr"><br><blockquote type="cite">On Dec 22, 2019, at 9:28 AM, mups53 via NSRCA-discussion <nsrca-discussion@lists.nsrca.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><div dir="auto">FWIW</div><div dir="auto"> Some may wonder why participation at the Nats is in decline.</div><div dir="auto"> Well this discussion is an example of why. As the complexity of the maneuvers ramps up it also makes judging them harder.</div><div dir="auto">Masters fliers for the most part are the ones who have to judge FAI. For many they don't enjoy it and instead dread having to learn it all so they can feel confident they are competent enough. After all we take on the task with a deep sense of responsibility.</div><div dir="auto"> I don't know the answer to this situation.</div><div dir="auto"> I only know it exists.</div><div dir="auto"> Merry Christmas everyone.</div><div dir="auto">Mike Mueller </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Verizon, Samsung Galaxy smartphone</div></div><div dir="auto"><br></div><div><br></div><div style="font-size:100%;color:#000000" dir="auto"><!-- originalMessage --><div>-------- Original message --------</div><div>From: GLEN WATSON via NSRCA-discussion <nsrca-discussion@lists.nsrca.org> </div><div>Date: 12/21/19 9:05 PM (GMT-06:00) </div><div>To: AC Glenn <bhzboy07@gmail.com>, General pattern discussion <nsrca-discussion@lists.nsrca.org>, J <vellum2@bellsouth.net> </div><div>Subject: Re: [NSRCA-discussion] P-21.14 Comet question for the experts </div><div><br></div></div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
This is the challenge of interpreting and applying consistent judging standards.
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
<br>
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
According to 5B.2 and 5B.10:
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
In general, turn-around manoeuvres are positioning manoeuvres. Therefore, entry and exit altitude need not be the same if the pilot wishes to make an attitude adjustment. The keywords are 'in general', this implies 5B.2 and 5B.10 would be in effect unless otherwise specified in the manoeuvre description.
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
<br>
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
P-21.14 description:
<br>Comet with consecutive two ¼ rolls in opposite directions, ½ roll. From upright, push through a 1/8 loop into a 45° downline, perform consecutively two ¼ rolls in opposite directions, pull through a ¾ loop into a 45° downline, perform a ½ roll, pull through a 1/8 loop, exit upright.
<br>
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
<br>
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
In the description of P-21.14 there is no requirement mentioned to line length or how the lines are drawn except they are 45 degrees. Therefore I surmise the standard under 5B.2 and 5B.10 should be applied.
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
<br>
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
<br>
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
Regards,
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
<br>
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
Glen Watson
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
<br>
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
<br>
</div>
<div style="font-size: 12pt; font-family: helvetica, arial, sans-serif; color: #333333;">
On December 21, 2019 at 8:15 PM AC Glenn via NSRCA-discussion <nsrca-discussion@lists.nsrca.org> wrote:
<br>
<br>
<img src="content://com.samsung.android.email.attachmentprovider/1/8658/RAW" id="ox-45308bca5e-80B871B1-8B1B-41D7-9FCF-843E925920F0-L0-001" name="com_samsung_android_email_attachmentprovider_1_8658_RAW_1577024405544" data-unique-identifier="" onmouseover="imageMousePointerUpdate(true)" onmouseout="imageMousePointerUpdate(false)">
<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
Sent from my iPhone
</div>
<div dir="ltr">
<br>
<blockquote type="cite">
On Dec 21, 2019, at 7:45 PM, J <vellum2@bellsouth.net> wrote:
<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
No they don’t. It’s a turn around maneuver that can be used for height adjustment. The power point specifically addresses this question in the downgrades.
<br>
<br>
<div dir="ltr">
Joe
</div>
<div dir="ltr">
<br>
<blockquote type="cite">
On Dec 21, 2019, at 8:29 PM, AC Glenn via NSRCA-discussion <nsrca-discussion@lists.nsrca.org> wrote:
<br>
<br>
</blockquote>
</div>
<div dir="ltr">
Yes they do
<br>
<br>
<div dir="ltr">
Sent from my iPhone
</div>
<div dir="ltr">
<br>
<blockquote type="cite">
On Dec 21, 2019, at 7:14 PM, Don Szczur via NSRCA-discussion <nsrca-discussion@lists.nsrca.org> wrote:
<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="color: black; font: 10pt arial;">
This may have been asked already, but do the lines have to be the same length?
<div>
<br>
</div>
<div>
Thanks,
</div>
<div>
Don
</div>
</div>_______________________________________________
<br> NSRCA-discussion mailing list
<br> NSRCA-discussion@lists.nsrca.org
<br>http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
</div>
</blockquote>_______________________________________________
<br> NSRCA-discussion mailing list
<br> NSRCA-discussion@lists.nsrca.org
<br>http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
</div>
</div>
</blockquote>_______________________________________________
<br>NSRCA-discussion mailing list
<br>NSRCA-discussion@lists.nsrca.org
<br>http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
</blockquote>
<div class="ox-45308bca5e-default-style" style="font-size: 12pt; font-family: helvetica,arial,sans-serif; color: #333333;">
<br>
</div>
<span>_______________________________________________</span><br><span>NSRCA-discussion mailing list</span><br><span>NSRCA-discussion@lists.nsrca.org</span><br><span>http://lists.nsrca.org/mailman/listinfo/nsrca-discussion</span></div></blockquote></div></body></html>