Previous Home Site Map Contact Next
Wasmer Consulting BaseOps User's Guide Editing Runways
Runways serve an important purpose in BaseOps: they are anchors for flight tracks. The location and orientation of a flight track depends on the location and heading, respectively, of the track's runway.
Runways 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 runways will be hidden. See Noise Models.
BaseOps can import runways from DAFIF. See Importing Information from DAFIF.
Runways have the following properties.
Name - A short (10 characters maximum) name that uniquely and unambiguously identifies the runway.
Long Name - A one-line (80 characters maximum) name for the runway. 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 runway. There is no restriction on the length of notes. Press the Enter key to insert additional lines.
Start Location -
End Location - The location of the runway centerline at the beginning and end of the runway, not counting any overrun areas.
You can change the coordinate system used to specify locations: see Setting the Case Coordinate System.
Using the Select and Edit map tool, you can drag a runway endpoint to another location on the map. See The Select and Edit Mouse Tool for more information.
Displaced runway thresholds are incorporated into flight profiles. See the discussion of the displacement parameter in Editing Flight Profiles.
It is critical that runway locations be entered accurately and with sufficient precision. Since a flight track's initial direction is determined by its runway, a small error in the runway's heading will result in substantial location errors in the portions of the flight track that are far from the runway.
Start Elevation -
End Elevation - The elevations, with respect to mean sea level, of the runway centerline at the beginning and end of the runway, not counting any overrun areas.
You can manually enter the elevations, or else choose to use the elevation of the case reference point: see Reference Point.
You can change the units used to specify the elevations: see Setting the Case's Physical Units.
Width - The width of the runway. The width is not used when calculating noise levels, but BaseOps uses it when drawing runways on maps.
Heading - The length and heading of the runway, calculated from the endpoint locations.
You can double-check a runway's endpoints by comparing the calculated length and heading with published values (from, say, a FLIP chart).
Press the Reverse button to swap the runway endpoints and modify the runway name so that it refers to the opposite runway (for example, changing 23L to 05R). The name is not changed if it does not follow standard runway naming conventions (two digits referring to the heading, optionally followed by 'L', 'C', or 'R').
After adding a runway, you can easily add the opposite runway to the BaseOps case by following these steps.
Press the Duplicate button on the list pane to create a copy of the first runway.
Press the Reverse button to change the copy into the opposite runway.
Previous Home Site Map Contact NextCopyright © 1996-2017, Wasmer Consulting