Hello,Could someone tell me if the EOSID / Custom SIDs section of the FMS is modelled in PMDG's MD-11.I understand they are not part of the standard Navigraph (EAG) database, however I have them all from my company and is it possible to load them into the database so they will display correctly in the FMS?I guess a work around is just to create them as normal SIDs and add them to the database allowing for the selection of the EOSID on the sec flightplan page..Anyway just curious from someone who knows more about the specific programming of the sim and these FMS procedures what is the best way to accomplish the goal of having custom and engine out sids available in the PMDG MD-11.FCOM "CUSTOM SID SELECTION/ENTRYLSK 5L on the SID page provides a CSTM SIDS * for selection if custom SIDs are available. If pushed, all the custom SIDs for that airport will be displayed.Page operation using Customer SIDs/Transitions is the same as that previously described for standard SIDs.Switching between Standard and Custom SIDs/Transitions is accomplished by pushing LSK 5L. The SID page will only allow selection of one procedure type,either custom or standard or vice versa. The selections already made by the pilot will be retained for display and insertion until another selection is made. Thefollowing screen reflects the result of having selected Custom SIDs after a standard procedure was already chosen.By selecting a custom SID from the menu, the following screen will be displayed.ENGINE OUTThe FMS has an engine out operating mode that includes performance predictions designed around the loss of one engine and incorporates emergency engineout (EO) SID routing (if available). The EOSID routing is incorporated into the NAV database at the airline request and may not exist for every departurerunway. If EOSID routing exists for a selected departure runway, it is available when the runway is selected.If more than one engine is lost, both PROF and FMS SPD modes are disengaged, predictions are replaced with dashes, and MULTIPLE ENGINE OUT is displayedin the scratchpad.When the FCC detects an engine loss or the pilot pushes the ENG OUT function key on the MCDU, a _CONFIRM ENG OUT CLEAR_ prompt is displayedin line 6 for pilot selection.CAUTIONIF THE ENG OUT KEY HAS BEEN PUSHED, THE PILOT MUST SELECT EITHER *CONFIRM OR CLEAR*. FAILING TO DO SO LEAVES ENGINE OUT ARMED AND REMOVES THE ALTERNATE FLIGHT PLAN FROM THE MAP AND PLAN MODES.NOTEThe engine out mode cancels time constraints and the DECEL mode.ENGINE OUT TAKEOFF / INITIAL CLIMBThe FMS engine out mode predicts engine out performance and incorporates EOSID routing (if available for the departure runway). If available, EOSID routing is available when the runway is selected. If an EOSID is available and the aircraft has not passed the diversion point of the planned SID and the EOSID, the _CONFIRM ENG OUT CLEAR_ prompt is displayed on the ACT F-PLN page on the data line before the diversion point.The engine out speed target is the speed obtained at the time of engine loss (between V2 and V2 + 10) until the EO ACCEL altitude. At the EO ACCEL altitude,the aircraft levels off and accelerates to V3. At V3 it continues to climb until reaching the all engine ACSTEPENGINE OUT SID AND ROUTE (NOT ACTIVE)If the NAV data base contains an EOSID for the selected runway, it will be automatically selected when the departure runway is selected on the SID page. Ifavailable, the EOSID may be displayed by pushing the ENG OUT key or will be displayed when the FCC detects an engine failure before passing the EOSID diversion waypoint.The EOSID selection is displayed on a modified FPLN page as illustrated below. Before confirmation the proposed EOSID is also displayed on the ND.The departure continues to ELX, the EOSID diversion waypoint, then direct to LAIRD and EBENS in preparation for landing on RW 27R at KORD. A --- F-PLNDISCONTINUITy --- is strung between the end of the EOSID and the EOSID diversion point followed by the original flight plan route.Confirming the engine out condition enters the EOSID into the F-PLN and starts two engine performance computations. To land at KORD using FMS guidance,a new destination must be entered in order to get proper approach and runway selection for the return flight. (Of course the pilot may choose to manually flythe aircraft without employing FMS functions).Once the F-PLN has incorporated the EOSID, subsequent EOSID clearing will not restore the original FPLN.However, the prudent pilot should have copied the F-PLN into the SECONDARY F-PLN before evaluating the effect of an EO situation.If the EO condition occurs after the EOSID diversion waypoint, the PERF page will be displayed and the EOSID is no longer available for pilot selection.Mark

Not modelled that I am aware of. The method to add custom SIDs would be to modify the sidstar procedures file for that location. This is not difficult, an excellent tutorial is available from Terry Yingling at his planepath.com site.Engine out terminal (SID routing) procedures are not availabel either, but the performance features are in there.If the procuedures that you have are available for public dissemination, and they are in use via a LOA with local ATC, I'd like to incorporate them into the sidstar procedures that I publish for US locations. What locations do you have?