Procedure Guide

Please note

Different procedures are used depending on the operator. The following explanations are therefore only exemplary.

Flight Planning

• Performance planning via Simbrief is recommended to use the default E170 or E175 profile. The weights have been adapted to these profiles.

• Direct route import into the MCDU is possible via 2 ways:

World Map menu

1. Export your flightplan as msfs flightplan file (.FLT) (i.e. Simbrief, SimtoolkitPro, etc.).

2. In MSFS World Map menu import your flightplan file (LOAD/SAVE->LOAD FROM THIS PC).

3. The route will automatically be added to the E-Jets MCDU upon flight initialization.

Simbrief MCDU import

1. Create a flightplan in Simbrief.

2. Start your flight at the correct departure airport. It will automatically be inserted as origin in the MCDU RTE page.

3. On RTE page enter the destination and flight ID matching with your simbrief flightplan. The flight ID in simbrief is called Flight Number and can be found in the OFP. It is not the callsign!

4. Click on SEND (LSK L4) and wait until you see the (SENT) promt indicating your flightplan got fetched correctly. If not, the scratchpad will show you the reason.

5. Click on DLK FPL to open the datalink flightplan list. You should now see the fetched flight plan.

6. Click on APPLY ACTIVE to insert the flightplan route into MCDU. Remember that it will not import any departure or arrival route, only the enroute waypoints.

We also have a video guide available:

Power Up

1. BATTERIES ............................................... ON

2. GPU AVAIL ................................................. IN

3. APU .................................... ON, then START

4. NAV LIGHT ............................................... ON

5. LOGO LIGHT ......................... AS REQUIRED

6. EMER LIGHT ..................................... ARMED

Pushback

• Default MSFS Option: works fine

• Toolbar Pushback: works fine

• GSX Pro: works but requires custom profile.

Startup

• To avoid power interruptions it is recommended to wait 30 s after the %N2 stabilizes before shutting the APU down or GPU disconnection, or to use the Electrical Synoptic Page to follow the power transfer.

1. FSTN BELTS SIGN .................................... ON

2. BEACON .................................................... ON

3. ENGINE 1 / 2 ...................................... START

After Startup

1. APU ........................................ AS REQUIRED

2. ELEC PUMP A............................................ ON

3. TAXI LIGHTS ............................................. ON

4. FLAPS ....................................................... SET

Taxi

• The E-Jets tend to start rolling on idle thrust when releasing parking brake. Increased weight reduces that effect.

• In order to allow thermal stabilization of the engines, operate them at or near IDLE for at least 2 minutes before selecting high trust settings. Taxi time at or near IDLE can be included in the warm up period.

• Single Engine Taxi is allowed.

• VTAXI (Dry Straight): 30 kt

• VTAXI (Dry Turn): 10 kt

• VTAXI (Wet Straight): 10 kt

• VTAXI (Wet Turn): 5 kt

During initial roll it might be neccessary to counteract engine thrust pitch up moment by some nose down input on elevator to increase nose wheel steering effectiveness.

Before Takeoff

• T/O config button must be pressed until you hear an aural feedback to check aircraft configuration.

• TOGA Button on Throttle lever must be pressed before takeoff by latest to set the autoflight system into takeoff mode. Most operators do that prior startup.

1. APU ........................................ AS REQUIRED

2. STROBE LIGHT ........................................ ON

3. INSP LIGHT .............................................. ON

4. LANDING LIGHT ..................................... ON

5. T/O CONFIG ................................. CHECKED

Stab Trim

ALL WEIGHTS
FLAP	CG POSITION (% MAC)
7	9	11	13	15	17	19	21	23	25	27
1	6.0	6.0	5.5	5.0	5.0	4.5	4.0	3.5	3.0	3.0	2.5
UP	UP	UP	UP	UP	UP	UP	UP	UP	UP	UP
2	6.0	6.0	5.5	5.0	4.5	4.0	3.5	3.5	3.0	2.5	2.0
UP	UP	UP	UP	UP	UP	UP	UP	UP	UP	UP
4	6.0	5.5	5.0	4.5	4.0	3.5	3.0	2.5	2.0	1.5	1.0
UP	UP	UP	UP	UP	UP	UP	UP	UP	UP	UP

Takeoff

• Ensure takeoff mode has been armed (FMAs on PFD).

• Arm Autothrottle by pressing the corresponding button on glareshield panel.

• Adjust thrust to 40% N1. When engines stabilize at 40% N1, advance thrust levers to TO/GA detent. Autothrottle will take over at 50% N1.

• Minimum airspeed at positive rate: V2 + 10

Climb

VNAV is not implemented yet.

• Use FLCH during climb

• Target speed: 250 - 270 kt IAS

Enroute

• Autothrottle will disconnect if throttles are being used by user input. Exception: Airspeed is less than 60 kts.

Descent

VNAV is not implemented yet.

• Use FPA mode for descend and plan to the according values. Add additional distance for speed reduction if necessary.

Required distance = (Current Altitude - Target altitude) / Slope equivalent

• 3 degree slope: 320ft per nm

  • Example: (30.000ft - 3.000ft) / 320ft/nm = 84nm

• 3.5 degree slope: 375ft per nm

  • Example: (30.000ft - 3.000ft) / 375ft/nm = 72nm

• 4.0 degree slope: 425ft per nm

  • Example: (30.000ft - 3.000ft) / 425ft/nm = 64nm

Approach

ILS Auto Tune

Since v0.9.9 we implemented the Auto Tune feature. It will automatically set up the ILS frequency and course if

• ILS approach is selected in MCDU and

• Aircraft is within 150nm from destination

If you change the approach type in MCDU while autotune is active:

• ILS approach but different runway: frequency and course will get updated automatically

• other than ILS approach: autotune gets deactivated

If ILS frequency or course gets overwritten by user input autotune gets disconnected.

You can toggle it on/off in any MCDU NAV page:

• Click on MCDU radio button

• Click on LSK next to any standby frequency to enter NAV page

• Toggle Auto Tune mode via LSK 5R

ILS Auto Preview

Since v0.9.9 we implemented the Auto Preview feature. When in FMS source mode, PREV will automatically be activated and set to NAV1/2 (depending on AP source) with ILS frequency and course if

• ILS approach is selected in MCDU and

• Aircraft is within 150nm from destination

When in FMS source mode and auto tune is active it will automatically change nav source to V/L (NAV1 or 2) when

• LOC is armed and

• Localizer needle starts to move

You can arm LOC and GS by pressing APP when FMS source is still active and LOC1/2 is visible in preview. Once the auto tuning mode switches the nav source to V/L it will start to capture the LOC (and GS later on).

When in FMS source mode and APP is pressed without PREV active on NAV1/2 nothing will happen.

ILS Manual Intercept

• The aircraft currently uses the default approach logic provided by MSFS (yes we will change that!). Best practice to intercept an ILS for now if you don't use Auto Tune/Preview procedure:

  • Approach the localizer with a 30 degree angle in HDG mode

  • Once localizer needle (PFD) starts moving, press APP button on glareshield panel

Landing

• As in the real aircraft the Speed Retard Mode will activate 30ft above ground. However the speed reduction is quite slow resulting in a long flare. Best practice for landing:

  • At MA/DA disconnect AT

  • At 50 ft raise the nose slightly

  • At 30 ft reduce throttle to idle and raise the nose to make the end of the runway not move up or down (usually 6-7 degrees nose up pitch)

  • When nose gear is on ground, apply reverse thrust

  • At 80 kts set reverse idle

  • At 60 kts reverse is stowed