EFATO profile/routing
Thanks for the comments on Straight Ahead/Runway Heading ; here's another one for you ...
Each operator (airline) has a published profile/routing - for every runway that they use - that pilots are expected to follow in the event of suffering an engine failure at take-off, this is designed to guarantee (?) the required separation from terrain and obstacles. Under JAR-OPS this has to have a 'termination' ie, an end-point, usually a holding racetrack (which may or may not be a published procedure).
Q: Does a controller's training or briefing include any information on what this may entail, ie what some/many operators train/expect crews to do in the unlikely event? For example, there is a 'standard' Engine Failure Procedure employed by many operators that says something like "Climb straight ahead to 1500ft aal or so and then turn back to the Missed Approach or Intermediate Approach holding fix for the runway in use; this might be overhead the airfield or above the final approach track. We are supposed to obtain ATC clearance before making this turn (or ask for radar vectors) - but in a non-radar environment we have to fly the procedure and turn back towards traffic that is on the approach or going around! Gulp!