Whoa, this set-up seems to be quite old: no THRottle_RANGE statement and the analog values still in the original 'reversed' sense - you must have noticed this when flying, haven't you?
Instead of using a lindworm like
Rem Throttle Settings allow full range with WEP being engaged after the last indent
THR 5 39 (0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48 50 52 54 56 58 60 62 64 66 68 70 72 85 86 100) LOCK(THR,100%) LOCK(THR,96%) LOCK(THR,93%) LOCK(THR,90%) LOCK(THR,87%) LOCK(THR,84%) LOCK(THR,81%) LOCK(THR,78%) LOCK(THR,75%) LOCK(THR,72%) LOCK(THR,70%) LOCK(THR,67%) LOCK(THR,64%) LOCK(THR,61%) LOCK(THR,58%) LOCK(THR,55%) LOCK(THR,52%) LOCK(THR,50%) LOCK(THR,48%) LOCK(THR,45%) LOCK(THR,42%) LOCK(THR,40%) LOCK(THR,37%) LOCK(THR,34%) LOCK(THR,31%) LOCK(THR,28%) LOCK(THR,25%) LOCK(THR,22%) LOCK(THR,19%) LOCK(THR,16%) LOCK(THR,13%) LOCK(THR,10%) LOCK(THR,8%) LOCK(THR,5%) LOCK(THR,2%) LOCK(THR,0%) ^ WEP ^
which reduces the resolution of your input travel to 36 steps for the analog output, and the resolution of your analog output to steps of 2 respectively 3 percents (with the values being reversed, BTW: the sense has been fixed ages ago), you should rather use the THRottle_RANGE statement (which has been introduced with v.2 IIRC) to compress your throttle's full analog range to the travel range of e.g. min. to something before the max. (I always use 90% so I don't aengage WEP any time I just want full throttle):
USE THR_RANGE (0%, 90%)
THR 5 1 (99 100) WEP
This way you'll keep the full resolution of the input as well as of the output for its full range!
Just a suggestion...