BaseOps User's Guide, Chapter 19: Defining Aircraft Substitutions

When creating a BaseOps case, you may need aircraft that are not present in the standard aircraft library. To handle this situation, BaseOps allows you to define aircraft substitutions, which associate new aircraft names with equivalent proxy aircraft that are in the library.

Once the substitutions are defined, the new aircraft can be used throughout the BaseOps case. However, when the noise models are run, the substitution aircraft are used.

To define aircraft substitutions, choose Aircraft Substitutions from the object type selector dropdown list. Substitutions can be added, duplicated, and deleted as described in Working with the List Pane.

To edit an aircraft substitution, first select it in the object list, then edit its properties in the text pane.

Aircraft substitutions have the following properties.

• New Aircraft Name - The name of the new, non-BaseOps aircraft you are defining. While there is no limit on the name's length, you should keep it as short as possible.

• Substitution Aircraft - The name of the standard library aircraft that will act as a substitute for the new aircraft.

• Notes - Miscellaneous information about the aircraft substitution. There is no restriction on the length of notes. Press the Enter key to insert additional lines.