Introduction to EOSID

Engine out takeoff guidance has a number of names as adopted by industry, some of the common names include:

1. Engine Out Departure Procedures

2. Engine Out Contingency Procedures

3. Engine Out Escape Paths

4. Engine Out SIDs

The name selected is optional but it must reflect the approved kind of operation of the aircraft. Items 1, 2 and 3 can make reference to both VMC and IMC operations and must have the appropriate guidance for the operation type. Item 4, as the name suggests is based on IMC operations. Although not a requirement of CAO 20.7.1B, the majority of the aircraft that operate to this CAO are IFR approved. For IFR approved aircraft an EOSID must cover takeoffs in both VMC and IMC. From this point forward engine out takeoff guidance will be referred to as an EOSID.

Standard Instrument Departures (SIDs) or departure procedures (DPs) are designed in accordance with U.S. Standards for Terminal Instrument Procedures (TERPS) or ICAO Pans-Ops. These are based on normal all-engine operations and assume that the aircraft are capable of maintaining a climb profile. These departure procedures are normally published as specific routes to be followed or as omni-directional departures, together with procedure design gradients and details of significant obstacles. They are normally established for each runway where instrument departures are expected to be used and they define a departure procedure for the various categories of aircraft used.

In the event of an engine failure, continued adherence to departure procedures may not be possible as SIDs or DPs do not necessarily assure that engine-out obstacle clearance requirements are met. An engine failure during takeoff is a non-normal condition, and therefore, takes precedence over noise abatement, air traffic, SID’s, DPs, and other normal operating considerations. The fundamental difference between SIDs and EOSIDs is that SIDs provides the minimum performance considerations to meet the departure requirements assuming an all engine operation whereas EOSIDs are based upon engine out performance in relation to obstacle clearance. EOSIDs can be in the form of a straight departure and or a series of turns.

Note: Development of Engine Out Takeoff Procedures is the responsibility of the operator.

--o0o--

Source:

CAAP 235-4(0): Engine Out SID (EOSID) and Engine Out Missed Approach Procedures