<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>When Dave, Verne and myself left the Sequence Committee, I knew everything would go to hell. The three of us always tried to keep a reality check on things. Obviously, I wasted a lot of my time preparing the guidelines which were designed to help limit
creep. It didn't. I have always considered myself a middle of the road Masters pilot. I am totally against adopting anything FAI. Knife edge maneuvers and integrated rollers are almost impossible to truly judged accurately. Anyone saying otherwise is fooling
themselves. Judging has become a bigger and bigger burden. If anything I'd like Masters to be ratcheted back a hair. I may have some Contra units for sale dirt cheap at the end of the season. Stay tuned. LOL.<br>
</p>
<p><br>
</p>
<p>I do think designing 3 well thought out sequences to be rotated every 2 or 3 years for Intermediate and Advanced is a great idea. This had been on my mind when I was directly involved. Right now you could probably adopt at least two of the last 3 sequences
for these sequences. Maybe some tweaking here and there. So it shouldn't be that daunting a task to come up with a third. And maybe every four to six years rotate in something new to change things up a little for the lifers in those classes.
</p>
<p><br>
</p>
<p>Guys it doesn't matter what we do, pattern will continue to decline do to the time and money required to be at least somewhat competitive. Sometimes I yearn for the days where I could take my plane out two weeks before the first contest of the season and
be somewhat competitive. I have been hearing excuses from some guys and some of these guys are good friends who are blowing off attending a contest because they haven't been able to get enough practice to feel that they could be competitive.
</p>
<p><br>
</p>
<p><br>
<br>
</p>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="width: 98%; display: inline-block;">
<div id="divRplyFwdMsg" dir="ltr"><font color="#000000" face="Calibri, sans-serif" style="font-size: 11pt;"><b>From:</b> NSRCA-discussion <nsrca-discussion-bounces@lists.nsrca.org> on behalf of Jon Lowe via NSRCA-discussion <nsrca-discussion@lists.nsrca.org><br>
<b>Sent:</b> Friday, June 16, 2017 5:58 AM<br>
<b>To:</b> Atwood, Mark<br>
<b>Cc:</b> NSRCA<br>
<b>Subject:</b> Re: [NSRCA-discussion] NSRCA Leadership / New Sequences - My thoughts - Long</font>
<div> </div>
</div>
<div>
<div dir="auto">Just reviewed the sequence committee's proposed Masters F pattern against the published NSRCA sequence guide on the NSRCA website. Multiple violations, including too many K5's, total K too high, simple loop/roll combinations (an entire rolling
loop cannot be considered simple), take off and landings not judged, etc, etc. Clearly, no one was paying attention.
<div dir="auto"><br>
</div>
<div dir="auto">What was the thought process behind this? Was this done with BoD oversight?<br>
<br>
<div dir="auto">Jon</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Jun 15, 2017 10:12 PM, "Atwood, Mark" <atwoodm@paragon-inc.com> wrote:<br type="attribution">
<blockquote class="quote" style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;">
<div>
<div style="-ms-word-wrap: break-word;">Umm…. Sorry guys. My DVP has been doing his best to forward minutes and documents to our D4 Mailing list as soon and as often as he can. We love him!
<div><br>
</div>
<div>I will try to attach here the sequence proposals that were sent out last night prior to the BOD Meeting (he received them last night as well, and circulated them for feedback from our District.). The resulting email firestorm and discussion is what prompted
my earlier diatribe and recommendations. </div>
<div><br>
</div>
<div></div>
</div>
<div style="-ms-word-wrap: break-word;">
<div></div>
</div>
<div style="-ms-word-wrap: break-word;">
<div></div>
</div>
<div style="-ms-word-wrap: break-word;">
<div></div>
</div>
<div style="-ms-word-wrap: break-word;">
<div></div>
</div>
<div style="-ms-word-wrap: break-word;">
<div><br>
<div>
<div style="color: rgb(0, 0, 0); text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<div style="color: rgb(0, 0, 0); text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<div style="color: rgb(0, 0, 0); text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<div style="color: rgb(0, 0, 0); text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<div style="color: rgb(0, 0, 0); text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<div style="color: rgb(0, 0, 0); text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<span style="line-height: normal; border-collapse: separate; border-spacing: 0px;">
<div style="-ms-word-wrap: break-word;"><span style="color: rgb(0, 0, 0); text-transform: none; line-height: normal; text-indent: 0px; letter-spacing: normal; font-family: "helvetica"; font-style: normal; font-variant: normal; font-weight: normal; word-spacing: 0px; white-space: normal; border-collapse: separate; border-spacing: 0px;">
<div style="-ms-word-wrap: break-word;">
<div style="margin: 0in 0in 0pt; font-family: "times new roman" ,serif; font-size: 12pt;">
<div style="font: 11pt/normal "calibri" , sans-serif; margin: 0in 0in 0pt; color: rgb(0, 0, 0); text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; font-size-adjust: none; font-stretch: normal;">
<b style="font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif;">MARK </span></b><b style="font-size: 11pt;"><span style="color: rgb(128, 189, 1); font-family: "lato" ,sans-serif;">ATWOOD</span></b></div>
<div style="font: 11pt/normal "calibri" , sans-serif; margin: 0in 0in 0pt; color: rgb(0, 0, 0); text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; font-size-adjust: none; font-stretch: normal;">
<div style="margin: 0in 0in 0pt; font-size: 11pt;">
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">o. (440) 229-2502</span></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">c. (216) 316-2489</span></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">e. </span><a style="font-size: 11pt;" href="mailto:atwoodm@paragon-inc.com"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">atwoodm@paragon-inc.com</span></a></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><br>
</div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><b><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">Paragon Consulting, Inc.</span></b><b><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;"></span></b></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">5900 Landerbrook Drive, Suite 205, Cleveland Ohio, 44124</span></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106);"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;"><a style="color: purple;" href="http://www.paragon-inc.com/">www.paragon-inc.com</a></span></span></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-size: 2pt;"> </span></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><a style="color: purple;" href="http://www.paragon-inc.com/"></a><u><span style="color: rgb(101, 100, 106);"></span></u></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><b><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 8pt;">Powering The Digital Experience</span></b></div>
</div>
</div>
</div>
</div>
</span></div>
</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div>
<div>On Jun 15, 2017, at 11:05 PM, Jon Lowe via NSRCA-discussion <<a href="mailto:nsrca-discussion@lists.nsrca.org">nsrca-discussion@lists.nsrca.org</a>> wrote:</div>
<br>
<div>
<p dir="ltr">For those of us who haven't seen the proposed sequences, what are they? Are you implying that Masters might have a P&F? Good god, I hope not. And only Masters has to change every two years, according to AMA rules. Other classes change every four
years. Further, according to the AMA rule book, NSRCA must submit the sequences to the membership for approval prior to implementation by the BoD.</p>
<p dir="ltr">We still have also not heard a peep from the BoD on the Nats situation. A month out and we still don't know who is in charge, or what the FAI and Masters finals are going to consist of?I've also heard of some sort of unpublished MOA between NSRCA
and Mike H about the NATS. Would be nice to know if that is true, and, if so, see a copy. I looked thru the BoDs book of motions, and at least thru April of this year, there is no mention of one being accepted by the BoD. There was also no mention of any particular
NATs format being accepted by the BoD.</p>
<p dir="ltr">I hope someone from the BoD will let us know soon what is going on with the NATs and the sequences.</p>
<p dir="ltr">Jon</p>
<br>
<br>
<div></div>
<hr style="margin: 0px 0px 9px; padding: 0px; border: 0px currentColor; border-image: none; width: 100%; height: 1px; color: rgb(153, 153, 153); background-color: rgb(153, 153, 153);">
<span style="color: rgb(153, 153, 153); font-size: 14px;">On Thursday, June 15, 2017 Atwood, Mark via NSRCA-discussion <<span style="color: rgb(0, 0, 160);"><a href="mailto:nsrca-discussion@lists.nsrca.org">nsrca-discussion@lists.nsrca.org</a></span>> wrote:</span><br>
<br>
<div>
<div style="-ms-word-wrap: break-word;">Recently our District VP distributed proposed new sequences for 2018, and it’s resulted in quite the brew-ha-ha in our district (D4). There’s really two issues of concern being debated in our district list and I’d like
to address them both, and open up the floor for nation-wide, full membership discussion.
<div><br>
</div>
<div>Since I suspect this could become a long post, I’ll create a quick exec summary to start. I want to emphasize that this is all simply MY opinion. It carry’s no more weight than any other member. </div>
<div><br>
</div>
<div><b>Issue #1</b>) there’s significant concern that the NSRCA Leadership isn’t listening. That they have their own set opinion, and are going to use their authority to make that opinion reality.</div>
<div><br>
</div>
<div><span style="white-space: pre;"></span>I believe that perception IS reality. Regardless of the truth of these accusations, I feel it needs to be addressed. </div>
<div><br>
</div>
<div><b>Issue #2</b>) The new sequences. The comments are that they are too hard, too many (masters P&F), no collaboration, no voice from the membership, no survey, etc. </div>
<div><br>
</div>
<div><span style="white-space: pre;"></span>I think… Sportsman, intermediate, Advanced are fine. I also think they should change less frequently, OR…ideally we create 3 sequences for each (A, B, C), and rotate them every 2 years. More on why in the details.</div>
<div><br>
</div>
<div><span style="white-space: pre;"></span>Masters - I think we should STRONGLY consider having masters fly the current FAI P pattern. Always. LOTS of supporting comments on this below. It fixes MANY problems (and as always, creates a few).</div>
<div><br>
</div>
<div><br>
</div>
<div>So the first issue is of deep concern to me, because I see people leaving the NSRCA, and Pattern in general as a result. That’s personally painful as I’ve been a member for a very long time and have always felt it was a great organization and have worked
hard to encourage others to join us. I don’t believe that anyone in the organization is trying to be a dictator, or usurp the control from the masses. But I do believe that the lack of transparency in some of the more recent issues has lead to mistrust.
And WE MUST FIX THAT. </div>
<div><br>
</div>
<div>The current issue with the Nationals is a prime example. D4 is a heavy participant at the nationals due to our geographic proximity (we LOVE Muncie!). But we understand the need to move it around and our group was a strong supporter of trying a new venue
even though we personally would all have farther to travel. Not all, but many of our regulars will be in Arkansas. But as a group, we were all in Muncie when there was collective agreement that Al Glenn had done a great job in 2016, and was selected to
be the ED for 2017, which was later confirmed by the BOD. We also knew that there was an official vote to move the Nats to Arkansas and that Mike Harrison would be facilitating that move. </div>
<div><br>
</div>
<div>Changing those rolls, making Mike the ED, Is not only seen as being horribly disrespectful to Al Glenn, but smacks us (the outside membership) as “behind closed doors” politics. Something that’s intolerable in a hobby. Mike may be the greatest ED of
all time. But there’s a process we go through, membership to communicate with and get consensus from, and general common courtesy to Al, ALL of which appears to have been laid to waste. If that’s NOT the reality… it’s clearly the perception. It may be too
late to fix the reality of who’s doing what for the nats. But I would very much like NSRCA leadership to start addressing the issue, perception or reality, in a meaningful, transparent, and communicative manner. And if decisions were made inappropriately,
simply apologize, and we’ll move on, and make an effort not to repeat them. No one here is a paid professional. EVERYONE is doing their best to promote the hobby they love. We all have opinions (I’m clearly expressing mine), and we won’t all agree. Just
remember that board members are elected to voice the opinions of their ENTIRE district, which may differ with their own personal opinions. </div>
<div><br>
</div>
<div>‘Nuff whining on that. </div>
<div><br>
</div>
<div><b>Issue 2. Sequences</b></div>
<div><br>
</div>
<div><span style="white-space: pre;"></span><b>Lower classes </b>- Meant to be the Building blocks for Pattern. Each class having increasing difficulty, measured spacing in complexity, designed to prepare the pilot for the next class. ALL classes are potential
“Destination” classes for a variety of reasons, (Time, age, interest, talent, etc). As such, changing the schedules periodically allows for some variety without moving classes. All Good. </div>
<div><br>
</div>
<div><span style="white-space: pre;"></span>But that said, creating all new sequences ever few years is both a time consuming effort, and requires strict discipline and guidelines to prevent complexity creep. So my suggestion is, rather than a new committee
making a new set of sequences every few years, that instead, we take the time to create 3 sequences for each class, an A, B and C pattern, which would allow a one time effort to produce balanced, thoughtful, progressive sequences that would effectively create
a 6 year cycle in any class before the patterns repeated (assume you flew each for 2 years). Even for the perennial Advanced flyer, that’s sufficient to provide challenge if they truly are unable to move up. As always… My $0.02</div>
<div><br>
</div>
<div><span style="white-space: pre;"></span><b>MASTERS</b>. This one I have strong opinions on so bear with me. We have numerous issues to solve…</div>
<div><br>
</div>
<div><span style="white-space: pre;"></span>*<span style="white-space: pre;"> </span>
Bored perennial Masters pilots that want ever increasing complexity but who lack the desire to attempt to fly the F pattern in FAI. </div>
<div><span style="white-space: pre;"></span>*<span style="white-space: pre;"> </span>
An every increasing complexity gap as FAI continues to push the boundaries of what our aircraft can do</div>
<div><span style="white-space: pre;"></span>*<span style="white-space: pre;"> </span>
A dwindling FAI class due to that gap, and a Masters sequence that does little to truly prep a pilot for FAI</div>
<div><span style="white-space: pre;"></span>*<span style="white-space: pre;"> </span>
Judging challenges, as ever increasing complexity in our routines makes them harder to judge if you’re not intimately familiar with the sequence.</div>
<div><span style="white-space: pre;"></span>* <span style="white-space: pre;"> </span>
Contest Logistics - Too many in one class, not enough in another (typically Masters vs FAI)</div>
<div><span style="white-space: pre;"></span></div>
<div><br>
</div>
<div>In my mind, ONE thing fixes all of this. <b>Adopting the P pattern as our Masters class sequence.</b></div>
<div><br>
</div>
<div><span style="white-space: pre;"></span>In the rest of the world, The P pattern IS the pattern for those not flying the full FAI program. It’s designed with that in mind. It’s complex, but very much on par with our typical Masters programs. It will
challenge those bored pilots and changes reliably every 2 years with NO effort!</div>
<div><span style="white-space: pre;"></span>As FAI adds new maneuvers, they put components of them into the P pattern. More snaps, some KE segments, introductory integrated rolling, etc. Without this, the gap between FAI and Masters will continue to widen,
making the jump for all but a few virtually impossible.</div>
<div><br>
</div>
<div><span style="white-space: pre;"></span>By flying the P pattern for the season, should a masters pilot choose to try FAI, they only have one additional pattern to learn. It’s a less daunting exercise than suddenly having 2 new sequences. In reverse, should
there be limited FAI participants at a contest, eliminating the FAI class for logistical reasons allows the one or two FAI pilots to simply fly Masters at the local event and not have it be a complete unknown. Or alternatively, several of the top Masters
pilots could opt to fly with the FAI group, and possibly agree not to fly the F sequence. Bottom line, there are more options.</div>
<div><br>
</div>
<div><span style="white-space: pre;"></span>Judging - BOTH classes benefit tremendously from improved judging as more people will know the nuances of the sequence they’re judging as an active flyer of it. No more missed zeros because they don’t know it. </div>
<div><br>
</div>
<div><span style="white-space: pre;"></span>There are so many reasons (ok, in MY mind) why this makes sense that I don’t really understand the opposition to it. Yes, the FAI crew throws in a half integrated loop here and there and I know some are deathly opposed
to that. I also recall the first time we told masters pilots to roll both right AND left… 1998. My world came to an end. But we learned. Our planes roll so easily now by comparison to a curare that we should expect the maneuvers to advance with them. </div>
<div><br>
</div>
<div>Ok, I’ll get off my soap box. These are MY opinions. I think they’re born from a good deal of experience, but they’re still just one person’s thoughts. We need to get back to open discussion, survey’s, and consensus. No, we won’t please everyone.
But we do need to please “most”. We all love this niche of the hobby. We all want it to grow. We all have good intentions. Let’s go into conversations with that in mind. </div>
<div><br>
</div>
<div>-Mark</div>
<div><br>
</div>
<div> </div>
<div>
<div>
<div style="text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<div style="text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<div style="text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<div style="text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<div style="text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<div style="text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal; -ms-word-wrap: break-word;">
<span style="line-height: normal; border-collapse: separate; border-spacing: 0px;">
<div style="-ms-word-wrap: break-word;"><span style="text-transform: none; line-height: normal; text-indent: 0px; letter-spacing: normal; font-family: "helvetica"; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal; border-collapse: separate; border-spacing: 0px;">
<div style="-ms-word-wrap: break-word;">
<div style="margin: 0in 0in 0pt; font-family: "times new roman" ,serif; font-size: 12pt;">
<div style="margin: 0in 0in 0pt; text-transform: none; line-height: normal; text-indent: 0px; letter-spacing: normal; font-family: "calibri" ,sans-serif; font-size: 11pt; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal;">
<b style="font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif;">MARK </span></b><b style="font-size: 11pt;"><span style="color: rgb(128, 189, 1); font-family: "lato" ,sans-serif;">ATWOOD</span></b></div>
<div style="margin: 0in 0in 0pt; text-transform: none; line-height: normal; text-indent: 0px; letter-spacing: normal; font-family: "calibri" ,sans-serif; font-size: 11pt; font-style: normal; font-weight: normal; word-spacing: 0px; white-space: normal;">
<div style="margin: 0in 0in 0pt; font-size: 11pt;">
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">o. (440) 229-2502</span></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">c. (216) 316-2489</span></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">e. </span><a style="font-size: 11pt;" href="mailto:atwoodm@paragon-inc.com"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">atwoodm@paragon-inc.com</span></a></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><br>
</div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><b><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">Paragon Consulting, Inc.</span></b><b><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;"></span></b></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;">5900 Landerbrook Drive, Suite 205, Cleveland Ohio, 44124</span></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106);"><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 10pt;"><a style="color: purple;" href="http://www.paragon-inc.com/">www.paragon-inc.com</a></span></span></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><span style="color: rgb(101, 100, 106); font-size: 2pt;"> </span></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><a style="color: purple;" href="http://www.paragon-inc.com/"></a><u><span style="color: rgb(101, 100, 106);"></span></u></div>
<div style="margin: 0in 0in 0pt; font-size: 11pt;"><b><span style="color: rgb(101, 100, 106); font-family: "lato" ,sans-serif; font-size: 8pt;">Powering The Digital Experience</span></b></div>
</div>
</div>
</div>
</div>
</span></div>
</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
</div>
_______________________________________________<br>
NSRCA-discussion mailing list<br>
NSRCA-<a href="mailto:discussion@lists.nsrca.org">discussion@lists.nsrca.org</a><br>
<a href="http://lists.nsrca.org/mailman/listinfo/nsrca-discussion">http://lists.nsrca.org/mailman/listinfo/nsrca-discussion</a>_______________________________________________<br>
NSRCA-discussion mailing list<br>
<a href="mailto:NSRCA-discussion@lists.nsrca.org">NSRCA-discussion@lists.nsrca.org</a><br>
http://lists.nsrca.org/mailman/listinfo/nsrca-discussion</div>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</body>
</html>