<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2523" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I replied to the wrong email...</FONT></DIV>
<DIV><FONT face=Arial size=2>If it is not a problem, I would like to look at
your Excel Spreadsheets.</FONT></DIV>
<DIV> </DIV>
<DIV>John Ferrell <BR><A
href="http://DixieNC.US">http://DixieNC.US</A><BR></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=GAA@owt.com href="mailto:GAA@owt.com">Gordon Anderson</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=discussion@nsrca.org
href="mailto:discussion@nsrca.org">discussion@nsrca.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, January 14, 2005 8:43
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: Pattern Help</DIV>
<DIV><BR></DIV>
<DIV dir=ltr align=left><SPAN class=022593701-15012005><FONT
face="Comic Sans MS" color=#0000ff>Earl,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=022593701-15012005><FONT
face="Comic Sans MS" color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=022593701-15012005><FONT
face="Comic Sans MS" color=#0000ff>Regarding the calculation of statistics
from the scoring of a contest; I have attached a final score sheet from my
scoring program used in most of the D8 pattern contests last season. This
program is a series of excel spreadsheets and macros. I will give this to
anyone interested but you will need Microsoft Excel to use this program.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=022593701-15012005><FONT
face="Comic Sans MS" color=#0000ff>I calculate a number of statistics and plot
score distribution data that I find very useful in focusing my practice.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=022593701-15012005><FONT
face="Comic Sans MS" color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=022593701-15012005><FONT
face="Comic Sans MS" color=#0000ff>--Gordon </FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> discussion-request@nsrca.org
[mailto:discussion-request@nsrca.org] <B>On Behalf Of </B>Earl
Haury<BR><B>Sent:</B> Friday, January 14, 2005 10:35 AM<BR><B>To:</B>
Discussion List, NSRCA<BR><B>Subject:</B> Pattern Help<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial size=2>Several have mentioned the lack of help in the
form of coaches, competent observers, etc. which could help them improve their
flying skills. This is probably more common than not, and makes it
difficult for each of us to improve (even the FAI guys). I've found a couple
of ways around this that some might find useful. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The first is score analysis. Simply input raw
scores (each maneuver / each judge) into a spreadsheet. Even a 4 round contest
with 2 judges / flight will yield 8 scores / maneuver. Average each maneuver's
score set and calculate the standard deviation. This provides a feel for how
well any given maneuver was flown and a feel for consistency - the lower the
std dev the better. This info lets one see what needs improvement the most
and, over several contests, note progress.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Of course score analysis doesn't indicate just
what the problem is. There have been many good suggestions regarding seeking
that input from fellow competitors, interested observers, etc. Another method
exists that can provide valuable info.</FONT></DIV>
<DIV><FONT face=Arial size=2>That method is a datalogger. I've recently been
using the latest USB Datalogger to look at in flight parameters. <A
href="http://www.eagletreesystems.com/Plane/plane.html">http://www.eagletreesystems.com/Plane/plane.html</A>
This newest version provides a useable graphics display of flight parameters
(even more useful if the data are evaluated in a spreadsheet) - your choice as
to just what to look at. I typically log altitude, airspeed, and aileron
inputs. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The altitude inputs allow observation
of entry / exit altitudes, altitude changes in level flight, diameter
(height) of loops, cross over points, altitude loss / gain during spin entry,
altitude loss / gain during rolls, etc. All basic stuff that's important to
get right for good scores. Speed data provide clues as to where too much
/ little power is used and whether a prop works well or not. The aileron
inputs can be superimposed on the altitude data to determine roll position on
vertical lines. While not all pattern parameters lend them selves to analysis
with this technology, a good deal can be learned with it.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>While recently evaluating engine / prop
combinations (very top secret), I noted something that looks useful regarding
snaps. During both up and downline snaps the speed signal drops to zero for a
period of time roughly equivalent to snap duration. It appears that possibly
airflow separation from the wing includes the pitot tube. Upline snaps also
show a marked decline in ascent rate during the snap. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Recent snap discussions have made me curious, so
I've decided to do some snap analysis with a G-force sensor
connected to the logger. I've ordered the sensor and plan to take a
good look at "real" snaps and barrel rolls. What to bet that the G loads
spike quickly then drop dramatically during snaps, but increase
throughout the barrel rolls? I'll present this work as a K-Factor article
when finished, if anyone wants data sooner, a datalogger costs
the same as a couple of servos.</FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Earl</FONT></DIV></BLOCKQUOTE></BODY></HTML>