Bad result for arriving to early at destination

[Florian Wassmann]

Thank you for your good discussion about this topic.

A fine for arrive ahead of scheduled time would be a better solution. In my daily work, I know that there were only a very marginal number of guest
who complain about a early arrival.

In case of canceling the rule of a bad result for arriving ahead of scheduled time, cheating should be prevented by FSP. Otherwise it would be
possible to use a enter a long long flighttime for a short trip, for getting better results anyway. But how to do it?
My Suggestion would be, to implement a (very simple !!!) calculator for the normal flight times between the choosen airports with the choosen
aircraft. The maximum speed could be read from Aircraft.cfg. It should not be complicated. The easiest way could be to take 90% of maximum speed and
calculate the flighttime of the direct way. Now add some minutes due to the normal non-direct flight path. Afterwards the value should be increased by
15 minutes for approach and start.

For example 500 kts for 1000 nm means about 2:00 flight time. For the non-direct path, we should add some minutes -> 2:05. And last but not least - 15
minutes for landing and starting -> 2:20. In real life a flight from Hanover to Mallorca with an Airbus A 320 normaly takes between 1:55 to 2:30. Not
a bad calculation I think.

But back to FSP. If you reach your final destination ahead of this time - nothing will happen in your results - but happy passengers. Depending of
being later than 110%, 125%,... of the calculated flighttime, passengers could be more and more angry. Nevertheless we just have the busy controllers,
but this is nothing else than in real life

I agree with you, that for future flights I may should calculate the influence of the weather conditions in a better way to find the best time.

best regards



Post Edited ( 09-19-08 01:02 )