Previous Home Site Map Contact Next
Wasmer Consulting BaseOps User's Guide Editing Airspace Profiles
An airspace profile describes the operational characteristics (engine power setting, altitude profile, frequency of operations, etc.) of an aircraft operating in a either a military operations area (MOA) or a military training route (MTR).
Airspace profiles are used by the MRNMap noise model. Unless that model is selected, the parts of the BaseOps user interface dealing with airspace profiles will be hidden. See Noise Models.
To work with airspace profiles, choose Airspace Profiles from the object type selector dropdown list. Airspace profiles can be added, duplicated, and deleted as described in Working with the List Pane.
Name - A short (10 characters maximum) name that uniquely and unambiguously identifies the airspace profile.
Long Name - A one-line (80 characters maximum) name for the airspace profile. The long name can be more descriptive than the short name. It is optional: if you do not supply a long name, the short name will be used in its place when necessary.
Notes - Miscellaneous information about the airspace profile. There is no restriction on the length of notes. Press the Enter key to insert additional lines.
Area or Route - The MOA or MTR associated with the airspace profile. This defines the geographic region where the aircraft operates.
Select the MOA or MTR from the dropdown list. Press the Add button to add a new MOA or MTR. Press the Go To button to edit the selected MOA or MTR.
Standoff - The distance from the boundary of a MOA where an aircraft begins to turn while operating in that MOA. In the turning zone, the frequency of aircraft operations linearly decreases, reaching zero at the MOA's boundary.
The standoff distance is only applicable to MOAs, and is hidden when an MTR is selected.
You can change the units used to specify the standoff distance: see Setting the Case's Physical Units.
Annual Ops - The average number of times per year that the airspace profile is flown during the day, evening, and night. Note that day, evening, and night are precisely defined periods: see Operations. The evening period will be displayed only if the number of daily periods for this BaseOps case is three.
The number of monthly operations is calculated by dividing the annual operations by 12. The number of daily operations is calculated by dividing the monthly operations by the average flying days per month: see Operations.
Air Time - The length of time that the aircraft operates in a MOA as part of a single operation. The MOA's average daily usage time for the airspace profile is calculated by multiplying the air time by the number of daily operations.
Air time is only applicable to MOAs, and is hidden when an MTR is selected.
You can change the units used to specify air times: see Setting the Case's Physical Units.
Aircraft - The aircraft associated with this airspace profile.
Engine - The aircraft engine associated with this airspace profile. The available engines will depend on the selected aircraft.
Power - The aircraft engine power setting used by the aircraft when operating as part of this airspace profile. Type the numeric power level, choose the operation power description (for example, "Normal Rated Thrust"), and choose the units used to specify the power level (for example, "% NC"). Note that for some operation power descriptions (for example, "Afterburner"), the numeric power level is fixed and cannot be changed.
The operation power description is used to select which Noisefile interpolation curve to use. Expert users can select the interpolation curve directly by selecting either "Variable" or "Parallel" in place of the operation power description.
The available operation power descriptions will depend on the airspace profile's aircraft and engine. As an aid to the user, information about the Noisefile record that corresponds to each operation power description is displayed.
The Range column specifies the range of power levels for which MRNMap can extrapolate the measured Noisefile noise data. You can enter power settings outside of this range (and are encouraged to do so to accurately record real-world flight parameters). Power levels are clipped to the extrapolation range when MRNMap is run.
The Interpolation and OPC columns specify the Noisefile interpolation method and operational power code, respectively.
Airspeed - The aircraft's airspeed when operating as part of this airspace profile.
Each airspace profile has a distribution of heights at which the aircraft operates as part of that profile. The distribution is defined by a set of one or more altitude bands (delimited by floor and ceiling heights), along with the relative amount of time spent in each band.
The altitude bands are specified using a table, where each table row represents one band. The following table columns are defined.
Ceiling - The minimum and maximum flight levels of this altitude band. Type the height, then select whether the height is above ground level (AGL) or above mean sea level (MSL).
At least one band must be specified, and each band's ceiling must be at least as high as its floor. Otherwise, no restrictions are placed on the band heights. Bands with a zero height range are allowed: i.e., the floor can equal the ceiling. Bands can be listed in any order, and the height range of different bands can overlap. Uses as many bands as needed to model the distribution of heights at which the aircraft flies.
You can change the units used to specify heights: see Setting the Case's Physical Units.
Relative Utilization - The relative amount of time the aircraft spends in this altitude band. The utilization numbers are unitless. MRNMap compares the utilization numbers for each band to determine the relative amount of time the aircraft spends in each band.
For example, assume you have two altitude bands, with relative utilization numbers of 10 and 30, respectively. In this case, MRNMap would model the aircraft flying 25% of the time in the first band and 75% of the time in the second.
The triangle icon indicates the selected altitude band. To select another band, either click somewhere on that band's row, or navigate to that band using the Tab key.
To add a new band, either press the Add Altitude Band button , or press Ctrl + A. The new band will be added directly below the selected one.
To delete the selected band, either press the Delete Altitude Band button , or press Ctrl + Del.
To move the selected band up or down in the table, press the Move Up and Move Down buttons and , or press Ctrl + U and Ctrl + D. This capability is provided solely for your own organizational purposes; MRNMap attributes no meaning to the order in which bands are listed.
When you add a new altitude band, BaseOps simply duplicates the selected one. If desired, you can use the quick-add feature, which lets you efficiently add an altitude band while simultaneously specifying its properties. To add a band, type a quick-add command into the text box, then press the Add Altitude Band button or the Enter key.
The quick-add commands are somewhat cryptic, but once learned, they allow you to add bands very quickly. Frequent users will find it worthwhile spending a few minutes learning the quick-add commands. To display a list of the quick-add commands that you can use, either press the Quick-Add Hints button , or press Ctrl + H.
Previous Home Site Map Contact NextCopyright © 1996-2017, Wasmer Consulting