Excessive ground roll distances - A/S acting up again?

The issue of landing distances was raised again in another thread. I almost replied that it was verified OK, as that is what I recalled from this thread

However, I have been feeling that the brake performance was more abysmal than I would expect in the latest versions, so I decided to have another go at verifying them.

Test setup and procedures

GW 37500 lbm

Flaps 20° -> Vref 135 KIAS (125 for minimum run)

Batumi 13 used, flown on ILS GP for nominal TCH. Dash one procedures used. Idle after crossing threshold, three second free run following touch down before applying full braking utilizing the A/S.

Flown on normal Vref.

No wind.

No significant runway slope (<0.3%)

15°C, 1013 hPa -> Landing index 100

Watch towers placed as placemarks along the R/H side of the RWY, at approximately the anticipated T/D point and at the anticipated stop points for the three configurations listed in the -1.

Published data

As per A-10A dash one:

Air distance (normal Vref) 1270’ (387 m)

Flaps 0°/no speed brakes: 2200’ (670 m) gnd roll, LDR 981 m

Flaps 20°/Full speed brakes: 1650’ (502 m) gnd roll, LDR 890 m

Flaps 20°/no speed brakes: 1950’ (594 m) gnd roll, 1058 m

RCR 23 (dry hardened runway) assumed.

Results

See the attached picture for results. To my surprise the ground roll distances are twice the published figures.

Speculation

I think the abysmal braking is due to the A/S still (again?) being over-active.

Further work

See if better results are possible using manual braking, thus confirming that the A/S modelling is at fault.

(And yes, A/S should by far outperform a human when it comes to maximum effort braking - check the dash one in general and figure A2-9 in particular if in doubt.)

Peer review to see if I made any mistakes.

Potential issues

No regard given to brake cooling.

Something seems to be amiss with the threshold crossing heights.

Slight bounces on two landings, TD measured where the wheels contacted the runway and stayed down.

I never braked to a full stop on the first attempt, so actual stopping position estimated. Good correlation with second attempt in the same configuration though.

I could have screwed up - please check my data.

Controller issues - checked in options. No conflicting axes, getting full output from Saitek pedals. In addition, seeing full input with RCtrl+Enter in game, with A/S activation indicated both on RCtrl+Enter and on the HYD gauges.

Mission file and track

http://forums.eagle.ru/attachment.php?attachmentid=63450&d=1330800793

http://forums.eagle.ru/attachment.php?attachmentid=63452&d=1330803158

Cheers,

Fred