Adding EOSIDs to JeeHell FMGS A320
Engine Out Standard Instrument Departures (EOSIDs) are special procedures designed by airlines to ensure the safe conduct of a flight should an engine fail during takeoff (at or past V1) or shortly after takeoff. As they are airline specific they are not included in the standard navigation database (Navigraph or similar).
As part of the MCDU preparation the secondary flight plan will typically be programmed to include the EOSID for the departure runway and an approach to a suitable runway for an immediate return to the field. This would allow the pilots to switch to the secondary flight plan should an engine fail very early in the flight and keep them clear of obstacles while climbing out on a single engine. A hold is usually included at the end of the procedure to give the pilots time to work on addressing issues and running through checklists.
When information about an EOSID is available it can be manually entered in the secondary flight plan but this is rather tedious and might not always represent the actual procedure (e.g. flying a specific heading to intercept a radial to a VOR or performing a direct turn to a fix). As the JeeHell FMGS software used in our A320 home cockpit supports including additional data into the navigation database (via a file aptly named “additional.txt”) I have started a project to create EOSIDs for the airports I frequently visit.
|ICAO Airport Codes
|EDDB, EDDL, EDDS
Note: airport codes in bold indicate the latest additions (if none, then only corrections were made).
Latest version: v016
Date: February 11, 2024
Copy the “additional.txt” file to the “\Navdata\Navdata1” folder and rebuild the database as usual.
You should now have, for the supported airports and departure runways, an additional SID in the Departure list of the flight plan, named “EOxxy” (where “xxy” is the runway identifier, eg. 28 or 25L). the EOSID will be found towards the end of the list of SIDs, right before the NO SID option.
Note: if you already use your own “additional.txt” file you can simply merge the content of the two files in a text editor.
Note: the screenshots above show the primary flight plan. This is for illustration only as the EOSID would typically be used for the secondary flight plan.
I believe the SimSmart Performance Calculator provides information about Engine Out procedures but I haven’t looked into it.
Engine Out procedures could also be found in the now discontinued TOPCAT but it seems that the information is rather old and unreliable.