Previous Home Site Map Contact Next
Wasmer Consulting BaseOps User's Guide Editing Flight Profiles
A flight profile describes the operational characteristics (height, power setting, airspeed, etc.) of an aircraft as it flies along a flight track.
In BaseOps, flight profiles are defined as a sequence of one or more flight profile segments: sections of a flight track where the operational characteristics are either constant or vary linearly. Each segment begins with a profile point: a location where the operational characteristics are specified. The location of profile points along a flight track is specified by the linear track distance, measured from the start of the track.
Flight profiles are used by the NMap, AAM, and RNM noise models. Unless one of these models is selected, the parts of the BaseOps user interface dealing with flight profiles will be hidden. See Noise Models.
Name - A short (10 characters maximum) name that uniquely and unambiguously identifies the flight profile.
Long Name - A one-line (80 characters maximum) name for the flight 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 flight profile. There is no restriction on the length of notes. Press the Enter key to insert additional lines.
The operation counts specify the average number of times per calendar day that the flight 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 is set to three for this BaseOps case.
Flight Track - The flight track associated with this flight profile. Select the track from the dropdown list. Press the Add Flight Track button to add a new track. Press the Go To Flight Track button to edit the selected track. See Editing Flight Tracks for more information.
The length of the selected flight track is displayed.
Displacement - The takeoff and/or landing runway displacements associated with this flight profile. The displacements that are requested (takeoff, landing, or both) will depend on the flight track type (arrival, departure, etc.).
The takeoff displacement is the distance, measured from the beginning of the runway, to the point where the aircraft begins its takeoff roll. For all flight track types except for arrival, the takeoff displacement is the origin from which flight profile cumulative track distances are measured.
The landing displacement is the distance, measured from the beginning of the runway, to the point where the aircraft touches down. For arrival flight tracks, the landing displacement is the origin from which flight profile cumulative track distances are measured.
You can change the units used to specify runway displacements: see Setting the Case's Physical Units.
A/C Category - The aircraft category is used to group flight profiles into broad categories. Specifying the category is not strictly necessary. However, doing so is useful for organizational and documentation purposes.
The categories are defined in the A/C Category group: see Using Groups. If desired, you can add additional categories.
Aircraft - The aircraft associated with this flight profile. Only those aircraft applicable to the selected noise model(s) are displayed: see Noise Models.
Engine - The aircraft engine associated with this flight profile. The available engines will depend on the selected aircraft.
Power Units - The units used to specify engine power settings for this flight profile. The available units will depend on the selected aircraft and engine.
Some aircraft perform a static runup of their engines before beginning a takeoff roll. The runup is the duration of this static runup.
The runup is displayed only for certain aircraft when operating on departure and interfacility flight tracks. For interfacility tracks, the runup is not displayed if the initial airspeed is greater than zero. This allows interfacility tracks to be used in a manner similar to INM's overflight tracks.
You can change the units used to specify times: see Setting the Case's Physical Units.
The aircraft's power setting when conducting the static runup is specified in the first row of the flight profile segments table.
A flight profile's segments are specified using a table, where each table row represents the profile point of a segment. The following table columns are defined. Note that only those columns applicable to the flight profile's aircraft will be displayed.
Distance - The location of this profile point, specified as a linear distance along the flight track, measured from the runway displacement.
You can change the units used to specify track distances: see Setting the Case's Physical Units.
Height - The aircraft height at this profile point. Type the height, then select whether the height is above ground level (AGL) or above mean sea level (MSL).
You can change the units used to specify heights: see Setting the Case's Physical Units.
Power - The aircraft engine power setting at this profile point. Type the numeric power level, then choose the operation power description (for example, "Takeoff"). For some operation power descriptions (for example, "Afterburner"), the numeric power level is fixed and cannot be changed.
Power settings are applicable only to NMap and AAM fixed-wing aircraft. The operation power description is applicable only to NMap aircraft.
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 flight profile's aircraft and engine. If the aircraft conducts a static runup prior to beginning its takeoff roll, the available operation power descriptions in the first row of the flight profile segments table (where the runup power is set) will be those for static operations.
Information about the Noisefile record that corresponds to each flyover operation power description is displayed below the segment table.
The Range column specifies the range of power levels for which NMap 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 NMap is run.
The Interpolation and OPC columns specify the Noisefile interpolation method and operational power code, respectively.
Aircraft Configuration - The state of the aircraft's landing gear, flaps, etc. at this profile point. The aircraft configuration is applicable only to fixed-wing AAM aircraft.
Airspeed - The aircraft airspeed at this profile point, in knots. Airspeeds are not applicable to rotary-wing NMap aircraft.
Yaw Angle -
Angle of Attack -
Roll Angle -
Thrust Vector Angle -
Nacelle Tilt Angle - The aircraft orientation angles, in degrees. These are applicable only to AAM and RNM aircraft. The angles displayed will vary, depending on the aircraft type (RNM rotary-wing, AAM fixed-wing, etc.).
The sign conventions for the applicable orientation angles are displayed below the profile segments tables.
The angle of attack and the yaw angle are technically applicable to non-helicopter AAM aircraft. However, for these aircraft, accurate values of these parameters are difficult to obtain, and their values rarely depart significantly from zero. Therefore, by default, zero is assumed for these parameters, and the corresponding columns are hidden in the profile segments table.
If you have specialized needs, you can choose to display and edit these parameters. See AAM Advanced Options for more information.
Left Dispersion Width -
Right Dispersion Width - The AAM noise model supports the concept of flight dispersion. This allows you to model aircraft operations that have a lateral Gaussian probability distribution with respect to a flight track.
To activate flight dispersion, enter non-zero dispersion widths for each flight profile segment. The widths define ±3 standard deviations. Since separate left and right widths are defined, the Gaussian distribution is not necessarily symmetrical with respect to the flight track.
When specifying dispersion widths, left and right are with respect to the direction the aircraft is flying. That is, they are left (port) and right (starboard) from the pilot's point of view.
You can change the units used to specify flight dispersion widths: see Setting the Case's Physical Units.
Notes - Miscellaneous information about this profile segment. There is no restriction on the text that can be typed into this box. The notes are not used by the noise models; they are for your use to record any information you believe is relevant.
The triangle icon indicates the selected flight profile segment. To select another segment, either click somewhere on that segment's row, or navigate to that segment using the Tab key.
To add a new segment, either press the Add Segment button , or press Ctrl + A. The new segment will be added directly below the selected segment. Alternatively, using the Add mouse tool , click on the location along the flight track where the new profile point should be added. See The Add Mouse Tool for more information.
To delete the selected segment, either press the Delete Segment button , or press Ctrl + Del.
To move the selected segment up or down in the table, press the Move Up and Move Down buttons and , or press Ctrl + U and Ctrl + D.
When you add a new segment, BaseOps simply duplicates the selected segment. If desired, you can use the quick-add feature, which lets you efficiently add a segment while simultaneously specifying its properties. To add a segment, type a quick-add command into the text box, then press the Add Segment button or the Enter key.
The quick-add commands are somewhat cryptic, but once learned, they allow you to add segments 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.
Using the Select and Edit map tool, you can graphically edit a flight profile's segments. See The Select and Edit Mouse Tool for more information.
Press the Show Profile Height Graph button to view a graphical representation of the profile's height as a function of track distance.
BaseOps ships with a library of standard flight profiles for many aircraft. These default profiles are useful if you are unable to obtain the actual flight profile flown by an aircraft at the site you are modeling.
To load a standard profile from the library, press the Load Standard Profile button. A dialog box appears, listing the available standard profiles that apply to your profile's aircraft, engine, and flight track type.
Select the desired profile, then press OK. The following properties in your flight profile will be updated to match the library profile.
If desired, you can save your own flight profiles to the standard profile library. To save the current profile, press the Save as Standard Profile button. A dialog box appears, asking for the name that this profile will be known by in the library.
Your user library of standard flight profiles is stored in the file Standard Flight Profile Library - User.baseops, which is located in the BaseOps home directory. This is a regular BaseOps case file. If desired, you can load this case into BaseOps and edit it. If you choose to do so, note these points.
Make sure each profile's Long Name contains a description of the profile (even if the description is simply something generic like "Standard Departure" or "Standard Arrival"). The long name is the text that is displayed to the user when displaying a list of standard profiles to choose from.
Make sure that the profile's flight track is set to either Arrival or Departure, depending on whether the profile is for arrivals or departures.
The height of all flight profile segments should be specified using AGL, not MSL.
The BaseOps library (as opposed to the user library) of standard flight profiles is stored in the file Standard Flight Profile Library - BaseOps.baseops. Only BaseOps' developers should edit this file, as it will be overwritten whenever a new version of BaseOps is installed.
Previous Home Site Map Contact NextCopyright © 1996-2017, Wasmer Consulting