Lately, the FSE Abuse department has been contacting more and more people for unrealistic flight log entries. A couple of recent examples: Flying a light aircraft with a normal 500-mile range from California to Hawaii, or landing a large aircraft with a reported fuel burn of just 5 or 10 gallons per hour when the "expected" rate should have been 100GPH or more.

Although there are some automated tools in place to send a flight-cancelled message, the various FSE clients do not catch everything. It is considered a matter of abuse when the acts are done intentionally, such as "well, I just loaded some fuel bladders for that long flight because you could do that in the real world". This is considered abuse because none of that fuel was paid for, cheating someone out of fuel payments. (note: this is NOT an invitation to just start sending money around and then taking advantage of whatever the clients might not catch.)

Reminder: FSE Terms of Service do not permit "well the system let me do it, so it must be ok" excuses. The applicable parts of the ToS are as follows:

While many of the rules contained within the Terms of Service are enforced through automated procedural methods (i.e. the "game code"), there are several other aspects of the rules that rely on member integrity. This is because FSE is a very open-ended system designed to allow simulation pilots the ability to fly the way they want to fly and use the FSE framework for various business methods. Violations of these rules, especially the "integrity rules" will be handled on a case-by-case basis

FSE Game World Rules:
1. You will not use features within the Flight Simulator program to circumvent the controls within the FSE system. This includes, but is not limited to: moving an aircraft from one location to another without actually flying the plane; adding fuel to your aircraft through the simulator's fuel level control screens; not consuming the proper amount of fuel during a flight; altering the elapsed time of the flight.

Although FSE Staff strives for an "educate first" policy, some recently active members are no longer quite as active due to either their abrasive responses or their unwillingness to accept the above "integrity" rules. We will continue to monitor flight logs for these abuses, and we will continue to contact individuals who need to make corrections. It's entirely possible that the whole event was unintended due to a misconfigured .cfg file... or it's a blatant act of abuse... or somewhere in the middle. If the trend continues to keep rising, we will look for ways to programatically cancel flights that exceed any of the expected flight envelopes.