Fix GSX Pro's 'no supported aircraft available' error in MSFS by checking aircraft profiles, Community links, Couatl and add-on variants.
GSX Pro reports no supported aircraft are available when Couatl cannot match the aircraft loaded in Microsoft Flight Simulator to a usable GSX definition. Fully load the flight, update GSX and Couatl, test without custom profiles, then correct the aircraft folder match or repair the GSX Community-package link.
What does the GSX Pro error mean?
The wording means aircraft detection failed; it does not normally mean that the airport or parking stand is unsupported. GSX must identify the active aircraft and associate it with built-in configuration data or a valid gsx.cfg profile before it can position stairs, loaders, passengers and catering vehicles.
If the message appears inside the simulator, Couatl has usually failed to identify the live user aircraft. If it appears in the GSX Profile Manager, the utility has not found a compatible installed aircraft package under the selected simulator installation.
How do I fix no supported aircraft in GSX Pro?
- Load completely into the cockpit. Do not open GSX from the main menu, hangar or loading screen. Enter a flight, wait for the aircraft and toolbar panels to finish loading, then open GSX. After changing aircraft through Developer Mode, return to the main menu and load a fresh flight.
- Test a standard airliner. Load one of the simulator's standard airliners at a parking stand. If that aircraft works, GSX itself is running and the fault belongs to the original add-on, variant, livery or profile.
- Update and repair GSX. Close Microsoft Flight Simulator, run the supported GSX updater, and confirm that it targets the correct simulator installation. Check that its package link points to the Community folder the simulator actually uses. Our GSX installation and repair checks cover outdated Couatl files and broken Community links.
- Temporarily remove the user profile. Move the folder for the affected aircraft out of
%APPDATA%\Virtuali\Airplanes\, then restart Couatl or reload the simulator. A stale user profile can override working GSX data, particularly after an aircraft developer changes a model or internal folder name. - Check the profile structure. A typical user profile should end up as
%APPDATA%\Virtuali\Airplanes\AIRCRAFT_FOLDER\gsx.cfg. Avoid an extra nested folder, and do not use the friendly aircraft name from the MSFS selection screen unless it is also the required internal folder name. See our aircraft-profile placement and matching instructions before reinstalling the file. - Match the exact aircraft variant. Profiles made for another engine type, fuselage length or developer's version may not match even when the aircraft has the same marketing name. Test the base aircraft and its default livery; if those work, inspect the failing livery or variant rather than reinstalling all of GSX.
- Restart Couatl after every profile change. Editing or replacing
gsx.cfgdoes not always refresh the active aircraft immediately. Use the available Couatl restart option, or close and reopen the simulator if recognition remains stale.
Is the aircraft profile or GSX installation at fault?
A controlled test with more than one aircraft usually separates a profile problem from a damaged GSX installation.
| Test result | Likely cause | Next action |
|---|---|---|
| Every aircraft fails | Outdated GSX or Couatl, wrong simulator target, or broken package link | Update and repair the GSX installation |
| Only one add-on fails | Missing, incompatible or incorrectly named aircraft profile | Remove the user profile, then install one for the exact variant |
| Only one livery fails | The livery uses a separate or incorrectly registered SimObject | Test the default livery and update or replace the livery package |
| Removing the user profile fixes it | The custom gsx.cfg was stale or malformed | Keep the built-in definition or rebuild the profile |
| GSX identifies the aircraft but services are unavailable | Parking, door, engine or service conditions are not satisfied | Stop troubleshooting aircraft detection and check operating conditions |
If all aircraft still fail after an update and clean-profile test, work through the Couatl, toolbar and package-conflict checks for MSFS 2024. The same core checks also help distinguish an installation fault from an aircraft-specific problem.
Does the aircraft need a custom GSX profile?
Not every aircraft needs a downloaded profile, but an add-on without suitable built-in data may require one to define its doors, cargo holds and service positions. An airport profile is different and cannot make an unrecognised aircraft supported.
A custom profile also cannot repair a stopped Couatl process or a missing GSX package link. Fix the installation first, confirm that another aircraft works, and only then add or edit the affected aircraft's profile.
Can the parking position cause this message?
A bad parking position can block individual services, but it should not prevent GSX from identifying the aircraft itself. Starting on a runway, away from an airport or at an unsuitable stand may produce service or parking warnings after recognition.
Once GSX displays the correct aircraft but boarding, stairs or pushback remain unavailable, use the parking and service-availability checks in our GSX Pro usage guide rather than repeatedly reinstalling the aircraft profile.