what to do?
Engine out SIDs (EOSIDs)
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.
Civil Aviation Regulations 1988, Reg 235, Takeoff and Landing of Aircraft etc.
Civil Aviation Order Part 20, Section 20.7.1B, Issue 5, Aeroplane Weight and Performance Limitations — Specified Aeroplanes Above 5700 kg — All Operations (Turbine and Piston and Engined)
Civil Aviation Order Part 40, Section 40.2.1, Issue 4 Instrument Ratings. Getting to Grips with aircraft Performance, Airbus Publication Boeing Performance Training - Operations Course notes Boeing Jet Transport Methods, Document D61420, Seventh Edition dated May 1989 Boeing FMS RNAV Workshop February 9,2000
Code of Federal Regulations Title 14, Aeronautics and Space Part 25—Airworthiness Standards – Transport Category Airplanes.
Code of Federal Regulations Title 14, Aeronautics and Space Part 77—Objects Affecting Navigable Airspace.
Code of Federal Regulations Title 14, Aeronautics and Space Part 121—Operating Requirements, Domestic, Flag, and supplemental Operations.
Boeing Document D6-39067-3 RNP Capability of FMC equipped 737, Generation 3 Joint Aviation Requirements for Large Aeroplanes JAR-25
ICAO Procedures for Air Navigation Services, DOC 8 168 Volume II, 4th Edition, Construction of Visual and instrument Flight Procedures.
FAA Order 8260.3, United States Standard for Terminal Instrument Procedures (TERPS), current edition.
FAA Order 8260. 48 Area Navigation (RNAV) Approach Construction Criteria
FAA Order 8260.44A Civil Utilisation of Area Navigation (RNAV) Departure Procedures
FAA Order 8260.40B Flight Management System (FMS) Instrument Procedures Development
FAA Advisory Circular 120- OBS-11, Airport Obstacle Analysis, Draft Copy Issue
RTCA DO-236A, Minimum Aviation System Performance Standards: Required Navigation Performance for Area Navigation, dated September 13,2000
RTCA DO-201A Standards for Aeronautical Information, dated April 19, 2000 ARINC Specification 424-17 Navigation System Data Base, published August 31, 2004 Collins FMS Newsletter Business and Regional Systems July 1998 Volume 1, Issue 2 FAA Notice N8400.80 Special Instrument approach and Engine Out Missed approach Procedures.
CAAP 235-4(0) Guidelines for the Consideration and Design of: Engine Out SID (EOSID) and Engine Out Missed Approach Procedures, Nov 2006
The rules and operators obligations under FAA, JAR etc are fairly obvious.
CAAP 235 is about as concise a answer as you can get...