Frequently Asked Questions

Interruption vs Invalidation

Jobs in FSCharter are subject to certain constraints so that all users share a fair environment. The FSCharter client and server both continuously validate these constraints.

If any of the constraints are no longer satisfied then three different outcomes are possible:

• Simulator paused: This allows you to remedy the situation immediately (adjust fuel, payload, etc.) and then unpause the simulator and continue the flight

• Flight interrupted (locally): The FSCharter client stops tracking your flight, which is still valid on the FSCharter server. Premium users can click Start Over and resume the flight assuming the constraint that triggered the interruption is no longer active. Corrective actions (e.g. position) will happen as part of the flight resume procedure

• Job invalidation (centrally): If the server finds one of its constraints are broken it will invalidate the flight directly on the server, which is unrecoverable

Here is an overview how each rule is handled:

The simulator will be automatically paused when:

• The fuel level of the aircraft is higher than expected.

• The payload of the aircraft is too low

The flight will be locally Interrupted (not invalidated) when:

• Position manipulation is detected due to 'slewing'.

• Position manipulation is detected due to change of location via the menu or the map.

• The main menu is accessed in MSFS.

The flight will be irreversibly invalidated when:

• The ground speed of the aircraft is too high

• The vertical speed is too high

• The aircraft has flown much further than its listed range

• The takeoff point is too far from the boarding point

• The aircraft has landed at an airport that is not known to FSCharter

• The simulator has reported that the aircraft has crashed

• FSCharter detects a crash due to an extremely hard landing

• The flight has been paused for too long

• The route has been removed buy the manager

• The pilot has deleted their FSCharter account

Does FSCharter modify my aircraft or simulator?

No. The plugin positions your aircraft, reads fuel levels, sets payload, and records flight data, but it does not modify aircraft files or simulator settings in any way.

Could the plugin cause MSFS crashes (CTDs)?

Highly unlikely. The FSCharter plugin runs out of process and communicates with the simulator via SimConnect, meaning it does not inject or alter simulator code.If you suspect a conflict, test with a default aircraft and no other add-ons. You can submit your logs through a Support ticket for further analysis.

What if I can’t set payload to the expected values?

Some aircraft limit or reject programmatic changes, or round values to the nearest supported increment. The plugin accepts values within a tolerance range, but you can also set them manually if required by changing the aircraft-specific settings. See Troubleshooting for guidance.

My aircraft tilts upwards when boarding

This usually indicates that the automatic payload distribution has exceeded per-station limits.
To resolve this:

1. Disable automatic Payload in Aircraft-specific options.

2. Redistribute the payload manually using your aircraft’s loading tools, or reduce the total payload.

My flight was interrupted - what now?

• Local interruption (sim crash or PC issue):
  The plugin stops tracking, but premium users can use Start Over to resume from the last recorded point.

• Remote interruption (service issue):
  The simulator flight may continue recording locally and will be reconciled automatically once the FSCharter service is available again.

What counts as valid fuel and payload during flight?

• Fuel: Must remain at or below the expected value throughout the flight.

• Payload: Must remain at or above the expected value throughout the flight.

Can I use slew mode or time acceleration?

No. Slewing is not permitted, and time acceleration beyond the aircraft’s type-dependent ground-speed limits is flagged and may invalidate the flight.

Where are logs stored?

• X-Plane: Log.txt and Output/logs/FSCharter.log

• SimConnect Plugin: See the Support section for instructions on retrieving logs.

How often does the plugin sample data?

The plugin samples simulator data every 0.5 seconds to maintain accurate tracking.