Reset, restart, disable or uninstall ChasePlane in MSFS safely, preserve camera profiles, remove integration files and fix stubborn leftovers.
To reset or remove ChasePlane in Microsoft Flight Simulator, first close MSFS and quit ChasePlane from the Windows notification area. Restart the app for a soft reset; disable its automatic launch for a temporary stop; or uninstall the desktop app through Windows Settings, then remove only its separate MSFS integration package if one remains.
These instructions apply to MSFS 2020 and MSFS 2024 on Windows. ChasePlane is a separate Windows application, not simply a Community-folder mod; our breakdown of the desktop app and simulator-side component explains that distinction. Console users do not have a ChasePlane desktop application to remove.
Which ChasePlane action should I use?
Restart ChasePlane for a temporary fault, disable it when testing a conflict, reset it when settings or views are corrupted, and uninstall it when you no longer want the utility.
| Action | Use it when | Effect on profiles |
|---|---|---|
| Restart | The app is frozen, disconnected or ignoring controls | Profiles remain intact |
| Disable | You want to test MSFS without ChasePlane | Profiles remain intact |
| Reset a profile | One aircraft or camera set behaves incorrectly | Only the selected profile is affected |
| Full reset | Settings remain broken after restarting | Preferences and profiles may be erased |
| Uninstall | You want to remove the application | User data may remain unless removed separately |
How do I restart ChasePlane when it is frozen?
A proper ChasePlane restart requires quitting its background process, not merely closing or minimising the main window.
- Close the ChasePlane window. Check the Windows notification area and use its Quit or Exit command if the icon remains there.
- Open Task Manager if it is unresponsive. Find the ChasePlane process and select End task. Do not end unrelated MSFS or SimConnect processes.
- Start ChasePlane again. If it still will not connect, close both applications, start MSFS, and then open ChasePlane once the simulator is running.
- Restart Windows only if necessary. This can release a process or file which remained locked after Task Manager closed it.
Restarting does not reset camera positions, aircraft profiles or preferences. It is the safest first step when ChasePlane stops responding during a flight.
How can I reset ChasePlane without losing every view?
Reset only the affected aircraft profile or camera preset before wiping ChasePlane's complete configuration.
- Back up or export useful profiles. Use ChasePlane's profile export or backup feature where available, and record any important keyboard or controller assignments.
- Reset the smallest affected item. Delete or restore defaults for the troublesome camera, aircraft profile or control assignment rather than resetting the entire application.
- Test with one aircraft. This separates a damaged aircraft-specific profile from a global ChasePlane problem.
- Use a full data reset only as a last resort. Close ChasePlane completely, then rename its app-specific user-data folder rather than immediately deleting it. ChasePlane data may be stored beneath
%APPDATA%or%LOCALAPPDATA%, depending on the build and installation method.
Only rename a folder clearly belonging to ChasePlane. Do not remove an entire publisher folder because it may contain settings for other products. Reopening ChasePlane should create fresh data; if that does not solve the fault, close it and restore the renamed folder. A full reset may also clear sign-in details, and synchronised profiles may return after signing in again.
How do I temporarily disable ChasePlane in MSFS?
Quit ChasePlane and prevent it from starting automatically; uninstalling is unnecessary when you only need a clean comparison with the default MSFS camera.
- Exit ChasePlane from its notification-area icon. Confirm in Task Manager that its process has stopped.
- Turn off automatic launch. Disable any start-with-Windows or start-with-simulator option exposed by ChasePlane or the application used to install it.
- Check Windows Startup apps. Disable ChasePlane there if an entry exists.
- Leave the integration package alone initially. An inactive helper package normally does not justify deleting files. Remove or disable it only when testing a package conflict or when it keeps relaunching the application.
If ChasePlane is disabled but a camera control still behaves incorrectly, inspect MSFS Controls Options for duplicate camera bindings. Quitting an external camera utility does not erase assignments saved in an MSFS controller preset.
How do I completely uninstall ChasePlane?
A complete ChasePlane uninstall removes the Windows application, its simulator integration package and, if desired, its retained user settings.
- Export anything you want to retain. Save camera profiles before removing the application.
- Close MSFS and ChasePlane. Verify through Task Manager that ChasePlane is no longer running.
- Uninstall the Windows application. In Windows Settings, open Apps and then Installed apps, locate ChasePlane and choose Uninstall. If it is not listed, use the same library application or installer that originally managed it.
- Remove the MSFS integration package. Check the active Community folder or add-on management tool for a package clearly identified as ChasePlane. Disable a linked package at its source rather than deleting only its symbolic link.
- Remove retained settings only for a clean wipe. Delete the ChasePlane-specific data you previously backed up or renamed. Keep it if you expect to reinstall and want your profiles back.
- Start MSFS and test the default camera. There is no need to delete the entire Community folder, clear scenery caches or reinstall Microsoft Flight Simulator.
Do not uninstall or delete SimConnect components. ChasePlane uses the simulator's connection interface, but other add-ons may use it as well.
Why does ChasePlane still launch or affect MSFS after uninstalling?
Persistent ChasePlane behaviour usually comes from a surviving background process, an automatic-start entry, a duplicate integration package or an MSFS control binding.
- End any remaining ChasePlane process and restart Windows.
- Check Windows Startup apps and the utility that installed ChasePlane.
- Look for more than one integration-package copy, especially if MSFS 2020 and MSFS 2024 use different active package locations.
- Remove duplicate camera assignments from the active MSFS controller preset.
- Confirm that another camera or motion utility is not producing the same effect.
Before reinstalling, follow the checks for duplicate integration packages and a clean ChasePlane setup. Reinstall only one desktop copy and one appropriate simulator-side package.
Can I use MSFS cameras after removing ChasePlane?
MSFS cockpit views and the Drone Camera continue to work after ChasePlane is removed, although ChasePlane-specific profiles and shortcuts will no longer operate.
Reassign any camera controls that ChasePlane previously captured, then save a fresh MSFS controller preset. If you want similar functionality without reinstalling it, compare the available free camera and replay alternatives for MSFS.