Wrong penalties?

[MALTBY D]

I've had a couple of overspeed under FL100 penalties recently, that I wasn't sure were right.
Got one yesterday that I was certain had to be wrong. So I examined the FS Airlines position & blackbox data and that backed up my suspicions. At the time the penalty came I was 12000ft up.
It's all listed at the bottom here if you're interested... http://www.cbfsim.co.uk/cbfsim/g-cbfs/C ... 0112242450
NB. blackbox and position data is only collected if you run the latest FSA client.

Anyway... I marked the flight for review on FSAirlines, explaining what was wrong. The FSA admin person removed the penalty.

If anyone else out there gets any penalty removed, can you let me know (in here or by PM). I'll then remove the penalty from our own CBFS stats.
All our stats pages are available from the VA home page http://www.cbfsim.co.uk/CBFS_VA.php

Thanks.
DM

P.S. I've added some fuel & weight calculations to the 'Flight Information' links on the VA home page.
So you can get a quick check on all the figures after booking a flight. Well I use it even if no one else does.

[TSR2]

Cheers DM, I'll keep an eye out. Not Flying tonight though as missus was not overly impressed with my 3 hrs at the computer last night

[Chris Trott]

Yeah, I think there's been an issue with the change to using FL100 instead of 10,000 for the 250 knot limit and landing lights, especially since the client doesn't report the detected FL and pressure when it enacts those so they could debug it. I tried getting Konrad to change it after we got some issues, but the problem was it seemed to only happen in 1 out of every 50 or so penalties and then it wasn't by much (maybe 300 feet off on the high end, not 2000+), so Konrad felt it to be an acceptable error rate.

[MALTBY D]

Just had another incorrect overspeed under FL100 during a climb.
I know for certain it was wrong and the data collected by the client confirms it.

Black box data shows 00:12:04 Climb 265 kn Penalty - overspeed under FL100.
But the route details show altitude was already 11128 ft 30 seconds earlier at 00:11:34.
http://www.cbfsim.co.uk/cbfsim/g-cbfs/C ... 124450#MAP

I've asked for the flight to be reviewed and posted the evidence.
Could be some odd timing issue in the client (v2.0.10b). Hopefully they will find the problem and tighten it up.

DM