# Search And Rescue A possible career activity that users will face in Microsoft Flight Simulator 2024 is to fly some kind of **search and rescue** mission. In these activities you have to take an aircraft (plane or helicopter) and fly off in search of missing people in arid deserts or dense forests. Users will have to scour the wilderness and scan every nook and cranny for signs of distress, then use their piloting expertise to land and recover people safely. If you wish your aircraft to be used on this kind of activity you will need a **preset** that has been appropriately set up as part of the [Modular SimObject,](../modular-simobjects/modular-simobjects/) as explained below. {{< image-center src="images/5_Content_Config/Careers/Search_Rescue/rescue_1_example.png" alt="Example Of An Aircraft Flying A Search And Rescue Activity" >}}   For more information on the various other career activities and how to prepare your aircraft, please see here: - [Career Activities](career-activities/)     ### Search And Rescue Constraints When it comes to setting up aircraft for the available search and rescue activities, there are a few requirements that must be fulfilled, depending on the aircraft being used. The following constraints are applicable to all aircraft types:   - The aircraft will need to have the `navigation_graph_pilot.cfg` (as explained [here](general-career-information/spawn-pilot-transversal/)). - The aircraft will need to have the `ApronWithoutCovers.flt` file (as explained [below](#flt_files)). - The `operating_status` must be either "*in\_service*" or "*experimental*". - The aircraft *cannot* be flagged as [military](../cfg-files/aircraft.cfg/#military). - The aircraft *cannot* be flagged as [premium](../cfg-files/aircraft.cfg/#premium). - The aircraft `ui_max_range` must be greater than 1. - Correct navigation graph set up as explained in [Navigation Graph Setup](search-and-rescue/#nav-graph) section, below.   There are also some additional constraints depending on the type of aircraft being set up for search and rescue.   - For **planes**, the following constraints will also be applied: - The `targeted_specializations` must include the `SAR-PLN` dressing code. - The `object_class` must be "*Airplane*". - The aircraft complexity must also be **simple**, as explained here: [Note On Aircraft Complexity](general-career-information/career-additional-information/#complexity). - The aircraft can *only* have **[big wheels](general-career-information/career-additional-information/#big-wheels)**, for landing gear. - There must be a navigation graph called `navigation_graph_rescue.cfg` with the following nodes: `RTC_SAR_VICTIM_ENTRANCE`, `RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE`, and SIT. This is explained in more detail below. This aircraft does not have an associated [Cabin Code](general-career-information/career-additional-information/#cabin-codes).   - For **rotorcraft**, the following constraints will also be applied: - If the rotorcraft is to be used on **hoist** missions, then the `targeted_specializations` must include the `SAR-ROI` dressing code, otherwise it should be the `SAR-ROT` dressing code (if the craft is compatible with both mission types, then both dressing codes should be included). - The `object_class` must be either "*helicopter*" or "*tiltrotor*". - The `engine_type` must be either "*Piston*" or "*Helo-Turbine*" - The landing gear *must* be either *wheels* or *skids*. - There must be a navigation graph called `navigation_graph_rescue.cfg` (for regular search and rescue missions) or `navigation_graph_hoist_rescue.cfg` (for hoist rescue activities). The details of the nodes that are required by these graph files are given below. - If the rotorcraft is to be used on **Hoist Rescue Missions**, the model will need a `RESCUE_ROPE_ATTACH` helper node in one of the {{< glossterm >}}gltf{{< /glossterm >}} files. This node should be placed on the part of the hoist apparatus where the rope should be spawned, and should be present on *at least* LOD0 and LOD1. {{< image-center src="images/5_Content_Config/Careers/Search_Rescue/rescue_7_model_node.png" alt="Example Of The Position For The RESCUE_ROPE_ATTACH Model Helper Node" >}} Following the constraints given here will give the aircraft the `SAR_Cabin` type. See here for more information: [Note On Cabin Codes](general-career-information/career-additional-information/#cabin-codes)     ### Mission Flow - Planes The flow for performing **search and rescue** flights using a *plane* is as follows: {{< image-center src="images/5_Content_Config/Careers/Guidelines/career_flowchart_11_sarplane.png" alt="Mission Flow Chart" >}} This flow will also require the aircraft to be setup for - and follow - the [General Career Mode Requirements](general-career-information/general-career-mode-requirements/).     ### Mission Flow - Rotorcraft The flow for performing ****search and rescue**** flights using a *rotorcraft* is as follows: {{< image-center src="images/5_Content_Config/Careers/Guidelines/career_flowchart_11_sarrotor.png" alt="Mission Flow Chart" >}} This flow will also require the aircraft to be setup for - and follow - the [General Career Mode Requirements](general-career-information/general-career-mode-requirements/).     ### Mission Flow - Rotorcraft (Hoist) The flow for performing ****search and rescue**** flights using a *rotorcraft* with a *hoist* is as follows: {{< image-center src="images/5_Content_Config/Careers/Guidelines/career_flowchart_11_sarhoist.png" alt="Mission Flow Chart" >}} This flow will also require the aircraft to be setup for - and follow - the [General Career Mode Requirements](general-career-information/general-career-mode-requirements/).     ### SimVars (Rotorcraft Only) The following SImVars will be used when performing the search and rescue missions using **rotorcraft**, and as such the aircraft will need to be modeled and set up correctly to use them (see [Doors, Hatches, And Canopies](../../models-and-textures/modeling/aircraft/airframe/doors-hatches-and-canopies/) for more information):   {{< table-wrapper >}} | SimVar | Description | |--------------------------|---------------------------------------------------------------------------------------| | `INTERACTIVE POINT GOAL` | Used to open/close the back door of the rotorcraft to permit the entry of the victim. | | `INTERACTIVE POINT OPEN` | Used to check the status of the rear door. | {{< /table-wrapper >}}     ### Navigation Graph Setup Once the aircraft model has been prepared for search and rescue activities and the [Modular SimObject](../modular-simobjects/modular-simobjects/) has been created with a **preset** that uses the adapted model parts and respects the constraints, the next thing to do would be to add in the required `navigation_graph.cfg` files. One thing that all these navigation graphs have in common is the need to set up **mass stations** and **station loads** for weight distribution. These things are explained in detail here: [Weight Distribution](commercial-passengers/#weight).     #### Plane Search And Rescue The navigation graph for planes to participate in search and rescue missions needs to be called `navigation_graph_rescue.cfg`. Within this file you will need the following nodes: {{< image-center src="images/5_Content_Config/Careers/Search_Rescue/rescue_2_nodes_plane.png" alt="Placement Of The NavGraph Nodes For A Plane Rescue Activity" >}}   - ##### RTC\_SAR\_VICTIM\_ENTRANCE This is the node where a person to be rescued will be spawned. It should be [projected on the ground](../cfg-files/navigation_graph.cfg/#projectOnGround), around 5-6m from the aircraft, and the node [heading](../cfg-files/navigation_graph.cfg/#pbh) should be pointed towards the aircraft entrance. You can place this node multiple times, to have multiple people being rescued, but note that for each of these nodes you place, you will need a corresponding `RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE` node and - inside the aircraft - a `SIT` node as well.   - ##### RTC\_SAR\_VICTIM\_AIRCRAFT\_ENTRANCE This is the node where a rescued person will enter the aircraft. It should be [projected on the ground](../cfg-files/navigation_graph.cfg/#projectOnGround), close to the aircraft entrance, and the node [heading](../cfg-files/navigation_graph.cfg/#pbh) should be pointed towards the aircraft entrance as well. You should have the same number of these as you do `RTC_SAR_VICTIM_ENTRANCE` nodes. Once placed, you will need to connect the nodes using an [edge](../cfg-files/navigation_graph.cfg/#edges%20(Main%20Graph)).   - ##### SEAT\_PASSENGER (SIT) Additionally, for every `RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE` there needs to be a `SIT` node in the aircraft, positioned at the feet of the seats where passengers can sit. This node is not normally created in the `navigation_graph_rescue.cfg`, but should exist in the navigation graph of the rescued passenger seat **logic object**, as explained here: - [The Passenger Navigation Graph](commercial-passengers/#nav-graph) Note that these seats should be included in the file section related to [Weight Distribution](commercial-passengers/#weight).     #### Rotorcraft Search And Rescue The navigation graph for rotorcraft to participate in search and rescue missions needs to be called `navigation_graph_rescue.cfg`. Within this file you will need the following *exterior* nodes: {{< image-center src="images/5_Content_Config/Careers/Search_Rescue/rescue_3_nodes_helicopter.png" alt="Position Of The Exterior Nodes For Helicopter Rescue Activities" >}}   - ##### RTC\_SAR\_VICTIM\_ENTRANCE This is the node where a person to be rescued will be spawned, awaiting rescue, as the start of the {{< glossterm >}}rtc{{< /glossterm >}} animation. There should be **five** of these circling the aircraft, and they should all have [projectOnGround](../cfg-files/navigation_graph.cfg/#projectOnGround) set to *true*, and [isExit](../cfg-files/navigation_graph.cfg/#isExit) set to *false*. All of these nodes will need to be connected via an [edge](../cfg-files/navigation_graph.cfg/#edges%20(Main%20Graph)), as shown in the image above, such that they surround the aircraft, and link to the double-tagged node "`RTC_SAR_VICTIM_ENTRANCE, RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE`". For the single node that starts a distance from the aircraft, [projectOnGround](../cfg-files/navigation_graph.cfg/#projectOnGround) should be set to *true*, [isExit](../cfg-files/navigation_graph.cfg/#isExit) should be set to *false*, and it should also have the [heading](../cfg-files/navigation_graph.cfg/#pbh) pointed towards the aircraft entrance. This node needs an [edge](../cfg-files/navigation_graph.cfg/#edges%20(Main%20Graph)) connected to single-tagged `RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE` node.   - ##### RTC\_SAR\_VICTIM\_AIRCRAFT\_ENTRANCE This is the node where the rescued person will enter the aircraft at the end of the {{< glossterm >}}rtc{{< /glossterm >}} animation. It should be [projected on the ground](../cfg-files/navigation_graph.cfg/#projectOnGround), close to the aircraft entrance, and the node [heading](../cfg-files/navigation_graph.cfg/#pbh) should be pointed towards the aircraft entrance as well. Once placed, you will need to connect the node to the corresponding `RTC_SAR_VICTIM_ENTRANCE` using an [edge](../cfg-files/navigation_graph.cfg/#edges%20(Main%20Graph)).   - ##### RTC\_SAR\_VICTIM\_ENTRANCE + RTC\_SAR\_VICTIM\_AIRCRAFT\_ENTRANCE This is a **double-tagged** node that is connected to `RTC_SAR_VICTIM_ENTRANCE` nodes near the entrance of the aircraft where the rescued person will enter the aircraft at the end of the {{< glossterm >}}rtc{{< /glossterm >}} animation. The tag setup in the CFG file will look like this for this node: ``` cpp tag=RTC_SAR_VICTIM_ENTRANCE,RTC_SAR_VICTIM_AIRCRAFT_ENTRANCE ``` With this node, [projectOnGround](../cfg-files/navigation_graph.cfg/#projectOnGround) should be set to *true*, and it needs an [edge](../cfg-files/navigation_graph.cfg/#edges%20(Main%20Graph)) to connect it to a unique `RTC_SAR_VICTIM_ENTRANCE` node.   - ##### RTC\_SAR\_RESCUER\_ENTRANCE This is the node that defines where the rescuer will spawn into the world at the start of the rescue mission, as a short {{< glossterm >}}rtc{{< /glossterm >}} animation plays. The node [heading](../cfg-files/navigation_graph.cfg/#pbh) should be pointed towards the aircraft entrance. You can only have *one* of these nodes and it requires a corresponding `RTC_SAR_AIRCRAFT_ENTRANCE` node and - inside the aircraft - a `RESCUER_SEAT` node as well.   - ##### RTC\_SAR\_AIRCRAFT\_ENTRANCE This is the node where the rescuer will enter the aircraft at the end of the {{< glossterm >}}rtc{{< /glossterm >}} animation. It should be [projected on the ground](../cfg-files/navigation_graph.cfg/#projectOnGround), close to the aircraft entrance, and the node [heading](../cfg-files/navigation_graph.cfg/#pbh) should be pointed towards the aircraft entrance as well. Once placed, you will need to connect the node to the corresponding `RTC_SAR_RESCUER_ENTRANCE` using an [edge](../cfg-files/navigation_graph.cfg/#edges%20(Main%20Graph)).   For the *interior* of the rotorcraft, the `navigation_graph_rescue.cfg` will need the following additional nodes (there should only be *one* of each of these): {{< image-center src="images/5_Content_Config/Careers/Search_Rescue/rescue_4_nodes_helicopter.png" alt="Position Of The Interior Nodes For Helicopter Rescue Activities" >}}   - ##### DOOR This node is where the rescuer will position themselves to help the person being rescued into the rotorcraft.    - ##### RESCUER\_SEAT This is the node that defines where the rescue worker will kneel while in the rotorcraft.   - ##### VICTIM\_SEAT This is the node that defines where the person being rescued will kneel while in the rotorcraft.      #### Rotorcraft Hoist Search And Rescue The navigation graph for rotorcraft to participate in search and rescue missions where a hoist is required needs to be called `navigation_graph_hoist_rescue.cfg`. Within this file you will need the following *exterior* nodes: {{< image-center src="images/5_Content_Config/Careers/Search_Rescue/rescue_5_nodes_hoist.png" alt="Position Of The Exterior Nodes For Helicopter Hoist Activities" >}}   - ##### RTC\_SAR\_HOISTOPERATOR\_ENTRANCE This is the node that defines where the hoist operator will spawn into the world at the start of the rescue mission, as a short {{< glossterm >}}rtc{{< /glossterm >}} animation plays. The node [heading](../cfg-files/navigation_graph.cfg/#pbh) should be pointed towards the aircraft entrance. You can only have *one* of these nodes and it requires a corresponding `RTC_SAR_AIRCRAFT_ENTRANCE` node and - inside the aircraft - a `HOISTOPERATOR_SEAT` node as well.   - ##### RTC\_SAR\_RESCUER\_ENTRANCE This is the node that defines where the rescuer will spawn into the world at the start of the rescue mission, as a short {{< glossterm >}}rtc{{< /glossterm >}} animation plays. The node [heading](../cfg-files/navigation_graph.cfg/#pbh) should be pointed towards the aircraft entrance. You can only have *one* of these nodes and it requires a corresponding `RTC_SAR_AIRCRAFT_ENTRANCE` node and - inside the aircraft - a `RESCUER_SEAT` node as well.   - ##### RTC\_SAR\_AIRCRAFT\_ENTRANCE This is the node where the rescuer and hoist operator will enter the aircraft at the end of the {{< glossterm >}}rtc{{< /glossterm >}} animation. It should be [projected on the ground](../cfg-files/navigation_graph.cfg/#projectOnGround), close to the aircraft entrance, and the node [heading](../cfg-files/navigation_graph.cfg/#pbh) should be pointed towards the aircraft entrance as well. Once placed, you will need to connect the node to the both the `RTC_SAR_HOISTOPERATOR_ENTRANCE` and `RTC_SAR_RESCUER_ENTRANCE` nodes using [edges](../cfg-files/navigation_graph.cfg/#edges%20(Main%20Graph)).   For the *interior* of the rotorcraft, the `navigation_graph_hoist_rescue.cfg` will need the following additional nodes (there should only be *one* of each of these): {{< image-center src="images/5_Content_Config/Careers/Search_Rescue/rescue_6_nodes_hoist.png" alt="Position Of The Interior Nodes For Helicopter Hoist Activities" >}}   - ##### DOOR This node is where: - the rescuer worker will leave the aircraft. - the hoist operator will position themselves to operate the hoist. - the person being rescued and rescue worker will enter the aircraft. This node must have an [interactiveObject](../cfg-files/navigation_graph.cfg/#interactiveObject) associated with it called `Hoist_Test`. This object is included in the simulation and simply needs to be spawned by the node (the simulation will position it automatically according to the position of the `RESCUE_ROPE_ATTACH` helper node of the model) .   - ##### HOISTOPERATOR\_SEAT This is the node that defines where the hoist operator will kneel while in the rotorcraft.   - ##### RESCUER\_SEAT This is the node that defines where the rescue worker will kneel while in the rotorcraft.   - ##### VICTIM\_SEAT This is the node that defines where the person being rescued will kneel while in the rotorcraft.     ### FLT Files For both **planes** and **rotorcraft**, the pilot will start by going through the usual [Preflight checks](general-career-information/preflight/), and so these aircraft will need to have the `Apron.flt` setup in the activity preset as follows:   - Section `[SimVars.0]` must have the parameter `SimOnGround` set to `true`. - All *defined* `[Covers]` need to be set to `true` (see [here](general-career-information/general-career-mode-requirements/#general-flt-file-requirements) for more information). - Section `[Controls.0]` must have the parameter `ParkingBrake` set to 100.00 (if the aircraft has a parking brake). - Aircraft electrics and engines must be turned off. - The aircraft flight parameters (trim, flaps, etc...) should be set for a **cold** and **idle** aircraft.   An additional FLT file is required - the `ApronWithoutCovers.flt` file - for those occasions when the user may skip the preflight phase and there is an RTC event, or when something causes a [Back On Track](../flt-files/back-on-track/) event after preflight. This file should be set up like a regular apron FLT file, however you should ensure that these changes are made:   - All *defined* `[Covers]` need to be set to `false` (see [here](general-career-information/general-career-mode-requirements/#general-flt-file-requirements) for more information).   Finally, **rotorcraft** will require the `Hover.flt`, with the following setup:   - Section `[SimVars.0]` must have the parameter `SimOnGround` set to `false`. - All *defined* `[Covers]` need to be set to `false` (see [here](general-career-information/general-career-mode-requirements/#general-flt-file-requirements) for more information). - The helicopter configuration in the FLT file must be setup such that the helicopter is in a safe "hover" state, ie: electrical systems and engine(s) should be **on** and set appropriately, the rotor brake should be **off**, flight parameters should be set such the rotorcraft is stationary in the air, etc...