E-JETS-FANFLIGHT COMPANION
FOR MICROSOFT FLIGHT SIMULATOR 2024FLIGHTSIM STUDIO E-JETS
FLIGHTSIM STUDIO E-JETSE170E175E190E195
E-JETS / FLIGHT COMPANION / CONFLICTING FSS INSTRUCTIONSGuide overview
FLIGHT MANAGEMENT / SOURCE CONFLICTS

Conflicting FSS instructions

Some FSS pages contain highlighted statements that the Welcome page does not explain. The conflicts below are between published FSS pages, not conclusions drawn from the highlight colour.

FSS says Version 1.0 is released. The Service Update 1 article and its changelog describe FIX INFO and Vertical Direct-To as added in 1.1.0, and the changelog calls Step Climb a feature overhaul. The roadmap still lists all three as “In Progress”; its disclaimer says it shows only selected work. The NAV page still says FIX INFO is not implemented. FSS does not explain these mismatches. Check the MCDU pages and prompts in your installed build before relying on a feature. FSS E-Jets [1] · Service Update 1 article and changelog [2] · roadmap [71] · NAV page [84].

Route-import instructions use different prompts. The Preflight Setup [85] and SimBrief Import [86] pages offer DLK PFL and CO ROUTE. The Procedure Guide [9] describes SEND-based SimBrief import, as do the RTE [87] and DATALINK [88] pages. RTE labels the list DLK FPL and says CO ROUTE is not implemented; DATALINK describes SEND and APPLY ACTIVE/ACCEPT. FSS had documented the CO ROUTE format in its 0.10.48 release notice. In a 6–7 November support thread, one user on 1.1.0 could not find DLK FPL after sending a SimBrief plan from the EFB. Replies first asked whether the SimBrief username or user ID had been entered as COMPANY ADDRESS under NAV → DATALINK → ADDRESS → FLIGHTPLAN. Another user then suggested CO ROUTE `EGPFEGLL001`. The original poster later said it seemed to be working but did not say which action fixed it. That is one unresolved report, not a verified workaround or a confirmed cause. Check the company address as well as the prompt your aircraft shows, and verify the MOD route before activating it. FSS #news, 10 September 2026 [89] · Community-support thread, 6–7 November 2026 [90].

On the thrust lever quadrant page [51], OVRD is described as allowing thrust-lever movement without disconnecting A/T. The same page says throttle movement above 60 kt disconnects A/T. The EFB settings page [91] lists an Overridable Autothrottle option but does not explain how it interacts with the 60 kt condition. FSS does not state whether OVRD changes that condition. Watch the FMA after moving the levers.

The Speed Control page [50] says phase target speeds are set on PERF INIT 1/3. The current PERF page [24] lists other 1/3 fields and puts speed-mode choices on 3/3. FSS does not explain whether the targets are separate fields or whether one page is outdated. Check the labels and displayed target in your installed aircraft.

FSS describes the MCDU route request both from RTE → SEND and from DATALINK → FLT PLAN → SEND REQST followed by ACCEPT or APPLY ACTIVE. These are separate page paths. The documentation does not say whether they use identical request handling; check the prompts and verify that the intended route appears in MOD. RTE [87] · DATALINK [88].

The DATALINK page says ATS/ACARS request pages on DLK MAIN MENU are display-only. The 1.0.0 release notice lists Hoppie CPDLC; Service Update 1 says BeyondATC and SayIntentions provide PDC, CPDLC and ATIS through the MCDU after provider selection in EFB settings. The documentation does not explain how the Hoppie feature or the newer providers map to the display-only request pages. Check the service and responses available in your installed build. DATALINK [88] · FSS #news, version 1.0.0 [78] · Service Update 1 [2].