First, open the "ExampleFlightNormal" flight in Prepar3D.

Important:- Select Vehicle/Failures in the menu and deactivate the "Oil Leak" in the category "Engines".
(If you forget this, the mission will end exactly like the "normal flight", because after 4-5 minutes the oil will leak out as fast as possible).- Select Options/General in the menu, click on "Realism" and make sure that the item "Detect crashes and damage" is activated in the upper right corner.
(If this is not set correctly now, the mission will always start with collision detection disabled. You can't change this later).

Select Scenario/Save from the menu and search for the flight "ExampleFlightNormal" in the list.

Click on it and you will see that the default file name (Maule M7 260C EC-527...) changes to "ExampleFlightNormal".

We will save the flight under a different name:
Change the "File Name" to:
ExampleFlight

Change the Description to:
"Example Flight where an oil leak occurs. This is a mission. (Beispiel Flug, bei dem ein Öl Leck auftritt. Dies ist eine Mission.)"

Leave the checkmark at "Default", this mission will be the default flight.
Confirm with "OK".

Now quit the Prepar3D.

Open the SimDirector

If you have marked the flight as default, SimDirector will start directly with this flight.
(If not, you have to load this flight in SimDirector first:
Click on "File", "Open" in the upper left corner and search for the flight "ExampleFlight.fxml").

At this point a short explanation of the SimDirector display:
- The top area (red) has basic controls to load/save a mission, adjust the display, rotate/move objects, etc.
- In the middle (orange) is the main area. On the left above the main area you can switch the display with the tabs "Prepar3D" and "Visualization".
- The left area (blue) has several functions. With the tabs below you switch the single functions.
- The area on the right (green) shows the settings of a currently selected object, in this example the UserOwnship1.
Let's just get started, you'll soon be able to handle the display.

Click on "Run Validation" (1), you will notice that "ScenarioMetaData" (2) is missing. Double click this line and confirm the request with "Yes" (3). Click on the tab "Visualization" (4)

You see 3 objects: UserOwnship1 (your plane), UserAvatar1 (The pilot in the plane) and ScenarioMetadata1.

Switch to the tab "Prepar3D" (1) and zoom in on the plane (by turning the mouse wheel).

Now we set an Area: Switch the left pane to "Catalog" (2), click on "Areas" (3) at the top and search for "RectangleArea" (4) in the window below. Click on it and drag the area into the Prepar3D window in front of the aircraft while holding down the mouse button.

1) The area is set, but much too big, so adjust the size in the window on the right: Length 50, With 10, Height 50.

2) At "DrawStyle" change from "Filled" to "Outlined". The area will be transparent, but still visible for testing in the flight simulator. As soon as the mission is finished and working, change it to "None" and the area will be invisible.

3) Give the area a meaningful name: Click at "ObjectName" in the field and write "StartTimer".

4) Make sure that "Pitch" and "Bank" are both set to "0", otherwise the Ares will hang crooked (marked red).

1) The area must be positioned correctly, so click on "Rotate" and turn the area at the green circle to the right angle to the runway (Heading ca 73). Red and blue circles change pitch and bank, so leave them unchanged. Then click on "Rotate*" again to deactivate the mode.

2) If the area needs to be moved, click on the orange drop and drag the area to the desired position with the mouse button pressed.

The area is positioned, now you have to define what should happen when the plane rolls into the area. Switch to "Visualization" (1), find the "Triggers" (2) in the upper right window under "Category", click on it and find the "ProximityTrigger" (3) in the window below. Hold down the mouse button and drag the trigger into the visualization window.

Enter a meaningful name in the right window under "ObjectName", e.g. "StartTimer".

The trigger needs a reference so that it knows when it has to fire. So double click under "OnEnterFilter", "Available" the line "UserOwnship1". UserOwnship1 moves to the top of the "Referenced" field.

In Visualization window you see a connection between ProximityTrigger and UserOwnship1 (1).

Scroll down in the right window to the "Areas" (2). Here you have to tell the trigger when to fire. Double click on the Available area "StartTimer" (3).

"StartTimer" has moved to the top and the trigger has connected to the area in the visualization window.
Make sure that you see a green dot next to the trigger. This means that the trigger is activated. When you click on the green dot, it turns red, so it is inactive and the trigger will do nothing when the plane rolls into the area. Therefore, switch the trigger to active (green).

Now click on "Run Validation" and you will see that the mission has an error: The trigger is missing an action it should take when the plane rolls into the area.

Search for "Actions" in the upper left window under "Category" and click on it. In the window below find the "DelayAction" and drag it into the visualization window with the mouse button held down.

Give the action a meaningful name in the right window under "ObjectName", e.g. "4.5min. to OilLeak".

In the field "DelaySeconds" type 270 (4,5min. = 4x60sec. + 30sec. = 270sec.).

Now click on the ProximityTrigger in the visualization window. In the window on the right scroll down and look for the item "OnEnterAction".

Under "Available" double click on the action "4,5min. to OilLeack", this action moves to the top.

In the visualization window you see that the trigger is connected to the DelayAction.

The trigger fires when the aircraft rolls into the area and activates the DelayAction, which runs for 270 seconds. After this time, the action must trigger the oil leak.

So we need another Action:

Search in the window on the left under "Categorie" / "Actions", the "FailureAction", and drag it into the visualization window with the mouse button held down.

Give the FailureAction the name "OilLeak".
Scroll down and double-click the "UserOwnship1" under "ObjectReference", which moves to the top.
(In P3dV4 and up to P3dV5.0 this reference does not exist, the UserOwnship1 is used automatically. That's why old missions from P3dV5.1 and in P3dV6 don't work if a Failure Action is used).

Scroll all the way up again and look for "Oil Leak" under the "System" heading.

Unfortunately, the P3d makers introduced a new, dark color scheme in P3dV6 and forgot to adjust this menu. That's why there is white writing, on a white background, so it's not readable. But if you move the mouse over the menu, the current item becomes blue and thus readable.

Oil leak is selected, now you have to determine how big the leak is. So set 95 under "HealtPercent".

100 = no leak, 0 = largest possible leak (oil leaked in 20 seconds).

The DelayAction must be linked to the FailureAction.

So click on the DelayAction in the visualization window and double click on the "Oil Leak Action" in the right window under "OnCompleteActions".
This is how it should look now:

One important object is still missing:

In the left window, under "Category", find the item "Scenario". In the window below, drag and drop the "RealismOverrides" into the visualization window.

Here you set the "amount" of autogen, scenery details and water effect for this mission (0-7).

This is important if you give your mission to other users and plan to land in the terrain. You may have Autogen set to 2, so you can land on open ground. If the other user has autogen set to max (7), the planned landing area will be overgrown with trees and bushes.

You also determine whether changes to the flight are allowed. So things like aircraft type, aircraft load, weather settings, airport selection and flight planner.
Without "RealismOverrides" everything is basically locked.

Set the following:- FlyingTips: Enable (This will tell you, for example, if the mixture is not sufficiently leaned).
- CrashBehavior: ResetFlight (This will automatically restart the flight in case of a crash).
- FlightRealism: Relaxed (With this you allow the user to deactivate the collision detection).
- WorldRealism: Relaxed (Allows the user to activate automatic rudder)
- UnlimitedFuel: Limited (Fuel is limited to the current amount of fuel.)
- AircraftLabels: Enable (Aircraft identifier is displayed.)
- AvatarNoCollision: Disable

Done! Save the flight (disk icon in the upper left corner) and exit SimDirector with the "x" in the upper right corner.

Now start the Prepar3D and test the mission.

Once the oil leak occurs, you have about 10 minutes until the engine fails.

There are now 4 files in the save directory:
- ExampleFlight.fxml: The saved flight, in it the settings for the aircraft, switch settings, window positions, etc.
- ExampleFlight.graph: This file is new since P3dV6 (not present in P3dV4 and P3dV5), it stores how triggers, areas, actions are placed in the SimDirector visualization window. In large missions, areas and triggers often overlap, for a better overview you can move them individually to other places. You can safely delete this file, it has no influence on the flight or the mission.
- ExampleFlight.wx: Here the weather data are stored.
- ExampleFlight.xml: This is where the mission data is stored, i.e. how the triggers, areas and actions are set and linked.

If you don't want to rebuild all this, but you are curious about the result, you can download this zip and copy the contained 3 files into your storage directory.

ExampleFlight.zip