Invalidated Flights
To ensure that FSCharter remains a fair environment for all players certain constraints are added to jobs. If these constraints are broken then the flight will be invalidated, the job will be cancelled and the aircraft will be returned to the departure airport.
Invalidation Criteria
Invalidation Message | Description |
|---|---|
The aircraft's fuel consumed can not decrease in-flight | The amount of fuel that the aircraft reports as consumed can not decrease in-flight. This can trigger if the level of fuel is manually updated in-flight |
The aircraft can not consume more fuel than it has in the tank | The aircraft can not report that it has consumed more fuel than has been allocated for the current flight |
The aircraft has crashed | The plugin has declared the current aircraft as crashed |
The route was deleted by a manager | The route that the current job is for has been deleted by a manager and is no longer valid |
The flight was invalidated during disembarkation due to a server error | This means that something has gone wrong on our side, sorry about that! Please file a bug report |
This flight has been inactive for too long | The simulator has been paused longer than the allowed duration whilst an active flight is in progress |
You have not landed at a known airport | If you land at an airport that is not in the FSCharter database then the flight will be invalidated. There are plans to fix this in an upcoming release but for now the best way to ensure that FSCharter recognises the airport that you are flying to is to check if the airport exists in the Marketplace or the Operations Cockpit |
The user was deleted | The user flying the job has deleted their account |
The aircraft is travelling much faster than its maximum speed. This may be due to the use of time compression, which FSCharter does not support | This invalidation is triggered when the distance between two ground points is too great for the reported timestamps. FSCharter uses ground speed to calculate invalidation speed and therefore may be influenced by a strong tailwind. Because of this, a healthy margin has been added to allow for realistic tailwinds |
The aircraft has flown significantly further than its maximum range | All aircraft in FSCharter have a published range that is based on average payload for the real-world aircraft. If the aircraft travels significantly further than this published range then the flight will be invalidated due to suspected fuel consumption manipulation. Although some aircraft may be capable of flying significantly further than their published range when empty it is recommended that any long-haul relocation flights are broken into multiple smaller jobs to avoid this invalidation from triggering erroneously |
The aircraft is climbing at an unrealistic rate | In an attempt to prevent slewing, aircraft can not ascend and/or descend at unrealistic rates |
The timestamp can not be in the future | When a flight departs the plugin sends a timestamp that anchors the simulator time to the server time. Every time the plugin sends a location update to FSCharter it includes a timestamp. If time acceleration is used or other means of manipulating this timestamp are detected then the server will invalidate the flight |
Reverting Invalidations
Unfortunately it isn't possible to directly reinstate a job once it's been invalidated. Invalidation of the flight triggers a lot of cleaning up that propagates through the system. Passengers and cargo have to be returned to the origin airport, demand has to be updated, aircraft have to be moved back to the original location, the aircraft and job are released back to the marketplace, fuel has to be adjusted and refunded. None of this would be able to happen if that job was held open to potentially be re-instated.