Three-Dimensional Airspace Analysis Programs (3DAAP) : User Manual: Program Installation and Menu Commands

Three-Dimensional Airspace Analysis Programs
(3DAAP)
User Manual:
Program Installation and Menu Commands
AutoCAD Map 3D 2005
March 2005
Prepared under a grant from the State of Florida Department

of Transportation Aviation Office to the Hillsborough County
Aviation Authority.
Prepared by:
FAA Technical Center Airway Facility
Tower Integration Laboratory &
Planning Technology, Inc.
3DAAP PROGRAM - AutoCAD Map 3D
TABLE OF CONTENTS
Installation ..... .......... ........... ...................... ........... .......... ........... .......... ........... .......... iii
3DAAP Operational Preface ...................... ........... .......... ........... .......... ........... .......... iii
Menu Item Selections:

AirSpace -> RW Data Files -> Runway Data ........... .......... ........... .......... ........... .......... 1
AirSpace -> RW Data Files -> Edit Data ...... ........... .......... ........... .......... ........... .......... 7
AirSpace -> Part 77 Model -> Model ........... ........... .......... ........... .......... ........... .......... 8
AirSpace -> Part 77 Model -> Cut Model..... ........... .......... ........... .......... ........... .......... 9
AirSpace -> Part 77 Model -> Remove Non-Critical .......... ........... .......... ........... .......... 10
AirSpace -> Shadow -> 2D Shadow ........... ........... .......... ........... .......... ........... .......... 11
AirSpace -> Shadow -> 2D & 3D Shadow ... ........... .......... ........... .......... ........... .......... 12
AirSpace -> Analysis/Conflict Setup -> Place LOS Surfaces ........... .......... .......................13
AirSpace -> Analysis/Conflict Setup -> Place Pt to Pt LOS Surfaces .......... ........... .......... 14
AirSpace -> Analysis/Conflict Setup -> Place Pt to Pt RCL Surfaces.......... ........... .......... 16
AirSpace -> Analysis/Conflict Setup -> Place Conflict Objects ........ .......... ........... .......... 17
AirSpace -> Analysis/Conflict Setup -> Place Multi Conflict Objects.......... ........... .......... 18
AirSpace -> Analysis/Conflict Setup -> Make Tree XYZ File .......... .......... ........... .......... 20
AirSpace -> Analysis/Conflict Setup -> Tree Conflict .......... ........... .......... ........... .......... 21
AirSpace -> Analysis/Conflict Setup -> Spot Conflict.......... ........... .......... ........... .......... 22
AirSpace -> Profile Tools -> Airspace Only Profile .......... ........... .......... ........... .......... 23
AirSpace -> Profile Tools -> Setup Multiple Profiles .......... ........... .......... ........... .......... 25
AirSpace -> Profile Tools -> Single Profile ........... .......... ........... .......... ........... .......... 26
AirSpace -> Profile Tools -> Multiple Profiles......... .......... ........... .......... ........... .......... 28
AirSpace -> Misc Surfaces -> Radar ........... ........... .......... ........... .......... ........... .......... 29
AirSpace -> Misc Surfaces -> 100_1Srf ...... ........... .......... ........... .......... ........... .......... 30
AirSpace -> 3D View ........... ...................... ........... .......... ........... .......... ........... .......... 31
AirSpace -> Surf Prep ........... ...................... ........... .......... ........... .......... ........... .......... 32
AirSpace -> Set Project......... ...................... ........... .......... ........... .......... ........... .......... 33
AirSpace -> Building/Mapping Tools -> 3D Building to Elev .......... .......... ........... .......... 34
AirSpace -> Building/Mapping Tools -> 3D Building to Surface .......... ........... .......... 35
AirSpace -> Symbols ........... ...................... ........... .......... ........... .......... ........... .......... 36
Analysis -> FAR Part 77 -> Airspace Model Conflict Test ........... .......... ........... .......... 37
Analysis -> Terminal Instrument Procedures -> TERPS Conflict Test......... ........... .......... 39
Analysis -> FAA Electronic Underground Cable -> Create Buffer Offset ........... .......... 43
Analysis -> FAA Electronic Underground Cable ->Underground Cable Vicinity Test .........44
Analysis -> Airport Traffic Control Towers -> ATCT Conflict Test .......... ........... .......... 45
Analysis -> Airport Surface Detection Equipment -> ASDE Conflict Test ........... .......... 46
Analysis -> Approach Lighting Systems -> Insert xxx.......... ........... .......... ........... .......... 47
Analysis -> Approach Lighting Systems -> ALS Conflict Test ......... .......... ........... .......... 48
Analysis -> Visual Approach Slope Indicators -> Insert xxx ........... .......... ........... .......... 49
3DAAP PROCESS IMPLEMENTATION --i

Analysis -> Visual Approach Slope Indicators -> VASI Conflict Test ......... ........... .......... 50
Analysis -> Precision Approach Path Indicators -> Insert PAPI .......... ........... .......... 51
Analysis -> Precision Approach Path Indicators -> PAPI Conflict Test ........... .......... 52
Analysis -> VHF Omnidirectional Range Station -> VORS Vicinity Test ........... .......... 53
Analysis -> VHF Omnidirectional Range Station -> Insert 0.5 Degree Surface .......... 54
Analysis -> VHF Omnidirectional Range Station -> VORS Conflict Test ........... .......... 55
Analysis -> VHF Omnidirectional Range Station -> Width Test .......... ........... .......... 56
Analysis -> Distance Measuring Equipment -> DME Vicinity Test .......... ........... .......... 57
Analysis -> Distance Measuring Equipment -> Insert 0.5 Degree Surface ........... .......... 58
Analysis -> Distance Measuring Equipment -> DME Conflict Test .......... ........... .......... 59
Analysis -> Non-Directional Beacons -> NDB Utility Line Vicinity Test ........... .......... 60
Analysis -> Non-Directional Beacons -> NDB Vicinity Test ........... .......... ........... .......... 61
Analysis -> Instrument Landing Systems -> Localizer Buffer Non-Crane ........... .......... 62
Analysis -> Instrument Landing Systems -> Localizer Buffer Crane .......... ........... .......... 63
Analysis -> Instrument Landing Systems -> Glide Slope Non-Crane .......... ........... .......... 64
Analysis -> Instrument Landing Systems -> Glide Slope Crane ........ .......... ........... .......... 65
Analysis -> Instrument Landing Systems -> Markers Vicinity Test .......... ........... .......... 66
Analysis -> Low Level Wind Shear Alert System -> LLWAS Conflict Test ........... .......... 67
Analysis -> Low Level Wind Shear Alert System -> LLWAS Vicinity Test ........... .......... 68
Analysis -> Low Level Wind Shear Alert System -> LLWAS 10 Degree Width Test ......... 69
Analysis -> Low Level Wind Shear Alert System -> Electrical Noise Vicinity Test .......... 70
Analysis -> AWOS/ASOS -> AWOS/ASOS Conflict Test ........... .......... ........... .......... 71
Analysis -> AWOS/ASOS -> Electrical Noise Vicinity Test ........... .......... ........... .......... 72
Analysis -> AWOS/ASOS -> Light Source Vicinity Test ..... ........... .......... ........... .......... 73
Analysis -> Wind Speed/Direction Equipment -> WS/DE Vicinity Test ........... .......... 74
Analysis -> Wind Speed/Direction Equipment -> WS/DE 10 Degree Width Test .......... 75
Analysis -> Remote Hydrothermometer -> RHYDRO Vicinity Test .......... ........... .......... 76
Analysis -> Runway Visual Range -> Light Source Vicinity Test .......... ........... .......... 77
Analysis -> Communications Facilities -> CF Conflict Test ........... .......... ........... .......... 78
Analysis -> Communications Facilities -> Insert 1.0 Degree Surface .......... ........... .......... 79
Analysis -> Communications Facilities -> CF Vicinity Test 1 ........... .......... ........... .......... 80
Analysis -> Communications Facilities -> CF Vicinity Test 2 ........... .......... ........... .......... 81
Analysis -> Airport Surveillance Radars -> ASR Conflict Test......... .......... ........... .......... 82
Analysis -> Airport Surveillance Radars -> Insert 0.25 Degree Surface....... ........... .......... 83
Analysis -> Airport Surveillance Radars -> ASR Vicinity Test 1 .......... ........... .......... 84
Analysis -> Airport Surveillance Radars -> ASR Vicinity Test 2 .......... ........... .......... 85
Analysis -> Radio Communications Links -> RCL Conflict Test .......... ........... .......... 86
Analysis -> Weather Surveillance Radar -> Insert Flat Surface......... .......... ........... .......... 87
Analysis -> Weather Surveillance Radar -> Insert 0.25 Degree Surface ........... .......... 88
Analysis -> Weather Surveillance Radar -> WSR Conflict Test........ .......... ........... .......... 89
Analysis -> Weather Surveillance Radar -> WSR Width Test........... .......... ........... .......... 90
--ii 3DAAP PROCES S IMPLEMENTATION

INSTALLATION
The installation of the software is an easy process. This software will run on any Windows based
system that has the AutoCAD Map 3D software installed and properly configured.
The installation process operates like any normal Windows program installation and is broken down
by the following steps.
Install program from website in the C Drive.
The next step in setting up 3DAAP is adding the 3DAAP menus that now reside in the
\3DAAP\SUPPORT\Map2005 directory.
Begin by starting AutoCAD. Once it is loaded, go to the "TOOLS" pull down menu under
"Customize Menus" and load the 3DAAP menu.
Then insert the "Airspace" and "Analysis" menus at the top.
The AutoCAD Preferences will now have to be set for support directories for 3DAAP to operate
properly.
Under the "TOOLS" pull down menu go to "Options" and add the following to the Preferences,
support files search path \3DAAP and \3DAAP\support\Map2005.
3DAAP OPERATIONAL PREFACE
The following operational notes should be kept in mind when utilizing the 3DAAP program for the
most efficient use.
h When the program prompts the user for any locations for any of the applications, the
input can either be a pick point on the drawing base or an input of an "X,Y"
coordinate.
h All of the commands will work only on three-dimensional objects that are constructed
with three sided AutoCAD 3DFACE surfaces. Refer to the SURFPREP command for
more information.
h When doing a conflict report with a building object, the user must use one of the
conflict object placement commands to place vertical lines or ASTICKS@ to represent
the surfaces or walls of a building or structure.
h If any airspace analysis applications fail for any reason, try utilizing the command
"SURFPREP". This command will verify and assure the integrity of all the faces in
your drawing session. It will also turn all four sided faces into valid three sided faces.
3DAAP PROCESS IMPLEMENTATION --iii

h Please refer to Chapter 2 of the standards manual for specific NAVAID test
requirements associated with this software.
--iv 3DAAP PROCES S IMPLEMENTATION

MENU SELECTIONS
MENU: AirSpace -> RW Data Files -> Runway Data

Description: Create an Airport Runway Data File.
This command will create an airport runway data file for use with the MODEL and CUTMODEL
commands. It contains all of the relevant information regarding the individual runways and their
associated airspace surfaces. It also contains the established airport elevation, number of runways and
allows the user to enter station and elevation data for the runway centerline. This station and
elevation data allows the user to pinpoint specific points along the runway to better depict the actual
airspace surfaces at a particular airport. Any intersections that occur between runways are also
defined by this station and elevation information. A process for determining the station and elevation
for intersecting runways will be described later. The process for using this command is as follows.
Select the command from the pull-down menu as indicated above. A file selection dialog box will
appear as follows.
3DAAP IMPLEMENTATION PROCESS --1

MENU: AirSpace -> RW Data Files -> Runway Data (Continued):
Enter the file name of the airport data file that you want to create. You can also select an existing one
from the list of files. If you select an existing file, a dialog box will appear warning you that this file
already exists. When it appears, select whether or not you want to replace the existing one. Be careful
of your file selections, because you can accidentally erase a valuable data file if you do not pay
attention to your selection. Do not enter a file name extension. All runway data files have an
extension of ".RW". Once you have specified a file name, another dialog box will appear as shown
here.
Enter the airport title and

established airport
elevation. Then select
from the pull-down list
the number of runways
that are to be defined in
this file. You can switch
between the areas of data
entry by using either the
TAB key or by selecting
the area with your mouse
or digitizer.
Once you have done so, select the OK button to proceed. A dialog box will appear as follows.
--2 3DAAP PROCESS IMPLEMENTATION

This is the dialog box for entering the specific data for the starting end of the current runway. It is
important to note, that for multiple runway scenarios that intersect with each other, enter the data for
the runway that intersects with more of the other runways first. This assures that the calculation of the
runway boundaries will work correctly. If you do not follow this rule, errors may occur.
On the dialog box there is a pull-down list of default runway setups based upon standard approach
types. You can quickly set all of your approach settings with one selection by using these defaults.
Otherwise, you can enter values for non-standard approach surfaces. Be sure to enter the correct
radius offset for the conical surface area.
Before using this command, you should have previously prepared the following information:
Established Airport Elevation: FAA Advisory Circular 150/5070-6A, Airport Master Plans, defines
the Airport Elevation as "the highest point of the usable landing area, to the nearest tenth of a foot."
[Source FAA A/C 150/5070-6A, Chp. 9, Section 2(4)(a)]
Runway Endpoint Coordinates: Calculate the relative coordinates of the runway endpoints (along
the centerline) for each runway end. These coordinates may be calculated using either an established
airport grid, a state plane grid, or other known reference. The units for this coordinate system is in
feet. Latitude and longitude must be converted to this format before they can be utilized. If no other
grid information is available, an existing AutoCAD drawing of the airport may be used. Simply use
the AutoCAD ID command for each endpoint and write down the X and Y coordinates. By using the
same coordinates as your AutoCAD drawing, the resulting airspace model can be combined with the
airport drawing utilizing the AutoCAD INSERT command.
Station and Elevation Data for the Runway Centerline: Calculate the station and elevation along
the runway centerline for all changes in elevation or any runway intersections. To do this in
AutoCAD, first use the LINE command to draw the runway center lines in 2D. Enter the X,Y
coordinates for each runway centerline for all points that the user needs to specify elevations at. Make
sure that you do not enter any elevation data for these construction lines. Once the lines are all drawn,
use the DISTANCE command to measure the distance from the start point of each runway to all of
the points or intersections that occur for a particular runway. Use the object snap feature to select the
exact points on the center lines. Start with the closest point or intersection to the start of the runway.
Write down each distance as you measure it for a particular runway. Do this from the closest point
out to the farthest point in sequential order. You do not have to measure the end point of the runway
since that is already known. Repeat this procedure for each runway centerline until you have all of the
station information for each runway.

Now go back to your notes and assign the appropriate elevation value to each station. Be sure to
enter the exact same elevation for any runway intersections as this is very important for the
construction of the airspace model. Also set your AutoCAD units to the maximum precision for
readout of the distances as possible. Refer to your AutoCAD manual on that procedure. Set the
decimal precision to eight. An example of a two runway airport might look like this:
Runway 18-36
Distance from start Point: Elevation:
1109.37845633 108.45
3456.78894564 113.75
6783.48290466 116.01 (Intersection with other Runway)
7122.39728374 117.83
Runway 10-28
Distance from start point: Elevation:
4563.94720378 111.34
5422.94738328 116.01 (Intersection with other Runway)
6534.73639373 118.13
Use this station and elevation data in the dialog box that is described later.
Radius of Horizontal Surface: FAR Part 77.25 defines the Horizontal Surface as a horizontal plane
150 feet above the established airport elevation. The perimeter of this surface is constructed by arcs
of specified radii from the center of each end of the primary surface of each runway, connected by
lines tangent to these arcs. The radius of each arc is: (1) 5,000 feet for all runways designated as
utility or visual; or (2) 10,000 feet for all other runways. It is permissible to have both radius values
within the same airport data file. This would allow for multiple runway scenarios with differing
horizontal surface radius values to be a part of the same airspace model.
Approach Slope Information: The approach slope dimensions should be defined for each runway
end. FAA Advisory Circular 150/5300-13, Airport Design, defines the Approach Surface Dimensions
as shown in the table on the next page.

Note: Pick one of the approach defaults and check the numbers. If not correct, pick another
until the numbers are correct, or enter the correct numbers.
Approach Slope Dimension Table

When you have finished entering the data for the starting end of the runway, select the OK
button to continue. A dialog box for entering the information about the opposite end of the
runway will appear. Enter the necessary information to define the approach and location for
that end of the runway. Once you have entered the data, select the OK button to continue. The
station and elevation dialog box will then appear as follows.
This is where the user enters the station and elevation data as described earlier. Be sure to enter the
station and elevation in order. Start with the station that is closest to the start of the runway and
continue entering data in that sequence. The process for entering this data for each station and
elevation combination is simple. Enter the station first, then the elevation. Then select the OK button
when finished. The dialog box will appear again with the values set to A0". Repeat this process until
all of the station and elevation data for a particular runway is complete. When you are finished select
the OK button with the values set to A0" to end the sequence.
This process will repeat for the number of runways that the user defines at the beginning dialog box.
When you have finished entering all of the runway information for all of the runways, the process is
complete. You now have an airport data file that can be used to create an airspace model with either
the MODEL or CUTMODEL commands.

MENU: AirSpace -> RW Data Files -> Edit Data
Description: Edit a Airport Runway Data File.
This command will allow the user to edit or append to an existing airport runway data file for
use with the MODEL and CUTMODEL commands. The user can add additional runways to
the file or delete existing ones that are already in the file. Existing station and elevation data
can be reentered as needed along with any other values that are already in the data file. The
process for using this command is as follows. Select the command from the pull-down menu as
indicated above. The process that follows is exactly as described in the RWDATA command.
The user selects a runway data file from the file selection dialog box. The file is then read in
and the sequence is followed as in the RWDATA command. Any of the values that are
displayed can be altered as needed. To add additional runways to the data file, select the
number of total runways in the appropriate dialog box. It will cycle through the data until it
reaches the end of the current data and the user can then enter additional runway information.
Station and elevation data can be changed for existing runways by reentering the station and
elevation information again from the beginning for each runway that is to be altered. Once the
data entry has been completed, the old file will be deleted and the new one takes its place. It
might be wise to make a backup of the existing file before editing it, just in case you make a
mistake. If you select the CANCEL button at anytime, it will exit the function without altering
the existing file.

MENU: AirSpace -> Part 77 Model -> Model
Description: Create a Three Dimensional Airspace Model (Un-Clipped).
This command will allow the user to create a three dimensional FAR Part 77.25 Airspace model.
Intersections for all of the airspace surfaces will not be calculated with this command. If you want to
have all of the surface intersections calculated and clipped, then use the CUTMODEL command. For
a quick creation of an airspace model though, this command will suffice. The process for using this
command is as follows. Select the command from the pull-down menu as indicated above. A file
selection dialog box will appear listing the available airport data files that were created with the
RWDATA command. Select the desired file. The rest of the procedure is completely automatic. It
can take several minutes to create a model depending on its complexity, but most will be created in
under two minutes. All of the airspace surfaces are on specific layers. They follow guidelines specified
by FAA drawing standards. They are listed as follows:
LAYER NAME DESCRIPTION

7 Conflict Object Entities
10 Primary Surface
11 Transitional Surface - Primary
12 Inner Approach Surface
13 Transitional Surface - Inner Approach
14 Outer Approach Surface
15 Transitional Surface - Outer Approach
16 Horizontal Plane Surface
17 Conical Surface
18 Part 77 Contour Lines
These layers are numbered so that translation of drawing entities between AutoCAD and
MicroStation can be easily implemented. Of course, once the model is created, you may rename the
layers to any name that you want. However, once the layer names have been changed, the main
conflict report command will not operate properly.

MENU: AirSpace -> Part 77 Model -> Cut Model
Description: Create a Three Dimensional Airspace Model (Clipped).
This command will allow the user to create a three dimensional FAR Part 77.25 Airspace model.
Intersections for all of the airspace surfaces will be calculated with this command. This creates a
model that has all of the surface intersections calculated and clipped. The process for using this
command is as follows. Select the command from the pull-down menu as indicated above. A file
selection dialog box will appear listing the available airport data files that were created with the
RWDATA command. Select the desired file. The rest of the procedure is completely automatic. Due
to the complexity of calculating all of the different possibilities of intersecting airspace surfaces, this
process can take up to several hours to complete. In most instances though, it will take anywhere
from 15 minutes to one hour to complete. There are 37 different calculation steps in this process
between different surfaces and an activity prompt displays the current status of the process. You can
cancel the process at anytime by entering a CONTROL-C key combination on your keyboard. Once
the process is complete you can then choose to use a command to remove all of the non-critical
surfaces from the model. That command is described next.

MENU: AirSpace -> Part 77 Model -> Remove Non-Critical:
Description: Remove Non-Critical Surfaces from a Clipped Airspace Model.
This command will allow the user to remove non-critical surfaces from an airspace model that
was created with the CUTMODEL command. This creates a single cohesive airspace model
which contains only the most critical surfaces for analysis purposes. The process for using this
command is as follows. Select the command from the pull-down menu as indicated above. This
procedure is completely automatic. Due to the process of calculating all of the different
possibilities of overlapping airspace surfaces, this process is a lengthy one, even for a small
airspace model. It is recommended that the user initiates this command overnight. Since this
command only needs to be run once per model, letting it run overnight is an advantageous way
of creating the final model without having to have any user inactiveness on the computer. An
activity prompt displays the current status of the process. You can cancel the process at
anytime by entering a CONTROL-C key combination on your keyboard.
Once the process is complete, save your drawing to insure that the model is stored on your
disk. One step that the user will have to complete manually is the removal of horizontal plane
surfaces that overlap the physical runway pavement area. Since there are not any surfaces
created for the area around the immediate runway, this command cannot remove those
surfaces that are over the runway. The process for manually removing those surfaces is to first
set the current layer in AutoCAD to 16 (The horizontal plane layer). Then freeze all of the
other layers. After that, zoom to extents. You can then easily see the surfaces that remain that
are over the physical runway. You can turn on layer 10 to see the runways for reference if you
want. Then erase the surfaces that overlap the runways with the AutoCAD ERASE command.
Next thaw layer 11 and set to that layer. Freeze all layers and repeat the process of erasing the
surfaces that are in the runway primary areas. Turn all of the layers back on and the process
will be complete. You can use the 3DVIEW command or the AutoCAD VPOINT command to
view the model from a different perspective. You can also use the AutoCAD SHADE command
to render the model to see the surfaces in full color. The REMOVE command will work
properly for the majority of runway scenarios. However, because the REMOVE command has
been purposely simplified for time saving reasons, there may be some surfaces in very complex
models which will have to be manually removed. The SHADE command will help with this
process.

MENU: AirSpace -> Shadow -> 2D Shadow:
Description: Create a 2D Shadow Boundary from 3D Objects.
This command will draw a 2D polyline boundary of the area of shadow or obstruction that a 3D
object or objects blocks from the view of a particular viewpoint. This is useful in determining areas
that are blocked from the view of the control tower, for instance. The process for using this command
is as follows. Select the command from the pull-down menu as indicated above. The following
prompt will be displayed.
Select Obstruction Surfaces: (Window or Crossing)
Select the 3D objects that you want to process. When you have selected all of the desired surfaces,
hit the <Enter> key. The following prompt will be displayed.
Select Eye View Icon/<Place Icon>:
If you have not yet placed an eye view icon, which is a block that visually references the view point,
hit the <Enter> key. Otherwise select the eye view icon that is already in your drawing. It may be
necessary to zoom in close enough to your icon to see it well enough to select it. If you hit <Enter>
you will be prompted:
Select Eye Point:
Select the desired location of the eye point icon. Afterwards you will be prompted:
Enter Eye Point Elevation:
Enter the elevation of the eye point. You will then be prompted:
Enter Ground Elevation for Shadow:
Enter the ground elevation for the shadow boundary to be cast to usually ground elevation in that
area. The boundary will then be calculated and drawn. If there are multiple boundaries to be
calculated due to objects that do not overlap, then multiple boundaries will be calculated and drawn.
An activity prompt will be displayed while this process is underway and completed.
Note: The ground elevation for the shadow should be at least as low as the lowest point of the
object from which the shadow is cast.

MENU: AirSpace -> Shadow -> 2D & 3D Shadow:
Description: Create a 2D Shadow Boundary and Project 3D Surfaces from 3D Objects.
This command will draw a 2D polyline boundary of the area of shadow or obstruction that a 3D
object or objects blocks from the view of a particular viewpoint. It also draws the 3D surfaces from
the object to the boundary. This is useful in determining elevations along the shadow area that are
blocked from the view of the control tower. These 3D surfaces can be used with the CONFLICT,
TREE or SPOT commands for determining points of penetration. The process for using this
command is as follows. Select the command from the pull-down menu as indicated above. The
following prompt will appear:
Select Obstruction Surfaces: (Window or Crossing)
Select the 3D surfaces that you want to process. When you have selected all of the desired surfaces,
hit the <Enter> key. The following prompt will be displayed.
Select Eye View Icon/<Place Icon>:
As described in the SHADOW command, either place a new eye view icon or select an existing one.
You will then be prompted:
Enter Ground Elevation for Shadow:
Enter the ground elevation for the shadow boundary to be cast to. The boundary will then be
calculated and drawn. 3D surfaces that represent the three dimensional boundary between the
obstruction object and the 2D shadow boundary will also be drawn. If there are multiple boundaries
to be calculated due to objects that do not overlap, then multiple boundaries and surfaces will be
calculated and drawn. An activity prompt will be displayed while this process is underway. You will
be prompted when the process is complete.
Note: The ground elevation for the shadow should be at least as low as the lowest point of the
object from which the shadow is cast.

MENU: AirSpace -> Analysis/Conflict Setup -> Place LOS Surfaces:
Description: Create Line of Sight 3D Obstruction Surfaces from a View Point.
This command will allow the user to draw 3D surfaces that extend from a view point, usually the
control tower, to points along the ground or other objects in the drawing. These surfaces represent
areas that restrict the line of sight from the view point. The process for using this command is as
follows. Select the command from the pull-down menu as indicated above. The following prompt will
appear:
Select Eye Point:
Select the point on-screen where the line of sight surfaces are to be projected from. This can represent
a control tower or similar structures. The following prompt will appear:
Enter Eye Point Elevation/<0.00>:
Enter the elevation for the view point. Or hit <Enter> to accept the last entered value. The first value
with the first use of the command is always zero. Any value that is entered afterwards will be the
default until it is changed. The following prompt will appear:
Select First Vector Point:
Select the point that the first corner of the obstruction surface will be projected to. The following
prompt will appear:
Enter Elevation/<0.00>:
Enter the elevation for the selected point. The following prompt will appear:
Select Next Vector Point/<Exit>:
Select the next point. The following prompt will appear:
A 3D surface will then be drawn. These steps will repeat until you hit <Enter> to exit.

MENU: AirSpace -> Analysis/Conflict Setup -> Place Pt to Pt LOS Surfaces:
Description: Create Line of Sight 3D Obstruction Surfaces between two points.
This command will allow the user to draw 3D surfaces that extend from a view point, usually the
control tower, to points that represent other structures or towers within an airport. These surfaces
represent areas that restrict the line of sight from the view point to the selected point. The process
for using this command is as follows. Select the command from the pull-down menu as indicated
above. The following prompt will appear:
Select LOS Surface Start Point:
Select LOS Surface End Point:
Select the point that the obstruction surface will be projected to. The following prompt will appear:
Enter the elevation for the selected point. The following prompt will appear:
Surface Type/<NONE>:
Enter the description code for the surface that is being drawn. The list of codes are described as
follows:
NONE .......... No Description will be attached to entity.

GENERIC ..... ........... General Purpose Surface
ATCT. .......... ........... Airport Traffic Control Towers
ASDE. .......... ........... Airport Surface Detection Equipment
ALS.... .......... ........... Approach Lighting Systems
VASI.. .......... ........... Visual Approach Slope Indicators
PAPI .. .......... ........... Precision Approach Path Indicators
VORS .......... ........... VHF Omnidirectional Range Station
DME .. .......... ........... Distance Measuring Equipment

MENU: AirSpace -> Analysis/Conflict Setup -> Place Pt to Pt LOS Surfaces: (Continued)
ILS ..... .......... ........... Instrument Landing Systems

LLWAS......... ........... Low Level Wind Shear Alert System
AWOSASOS. ........... AWOS/ASOS
CF ...... .......... ........... Communication Facilities
ASR ... .......... ........... Airport Surveillance Radars
RCL ... .......... ........... Radio Communications Links
Enter the appropriate surface type description code that relates to the particular analysis involved.
You will then be prompted:
Enter Surface Width/<1.0>:
Enter the width of the surface to be drawn. The default is 1.0. Once you have entered the width the
surface will be drawn. The following prompt will appear:
Select Next LOS Surface End Point:
Select the next point as needed. The surfaces will be drawn from point to point as selected. These
steps will repeat until you hit <Enter> to exit.
Note: If the placement of sticks for the representation of a building wall are spaced every two feet,
the one foot width of this surface may not catch the sticks of the wall. Please be aware of the
spacing for the sticks representing a building wall and the width of these surfaces.

MENU: AirSpace -> Analysis/Conflict Setup -> Place Pt to Pt RCL Surfaces:
Description: Create RCL Line of Sight 3D Obstruction Surfaces between two points.
This command will allow the user to draw 3D RCL surfaces as defined by FAA screening criteria that
extend from a view point, usually the control tower, to points that represent other structures or
towers within an airport. These surfaces represent areas that restrict the line of sight from the view
point to the selected point. The final group of surfaces that are drawn with this command resemble
half of a cylinder turned on its side. The process for using this command is as follows. Select the
command from the pull-down menu as indicated above. The following prompt will appear:
Select RCL Surface Start Point:
Select RCL Surface End Point:
Select the point that the RCL obstruction surfaces will be projected to. The following prompt will
appear:
Enter Elevation/<0.00>: To always assure the proper operation of the RCL conflict
routine, the conflict object should be
Enter the elevation for the selected point. The RCL surfaces will then be drawn between the two
points as selected. These steps will repeat until you hit <Enter> to exit.
Note: Since the RCL surface has a radius of 500 feet, if an elevation of the RCL point is zero, the
elevation of the RCL surface at that point will be minus 500 feet. To always assure the proper
operation of the RCL routine, the conflict object should be set with a base elevation of minus 501
feet.

MENU: AirSpace -> Analysis/Conflict Setup -> Place Conflict Objects:
Description: Place 3D Objects for use with the various conflict calculations.
This command will allow the user to place vertical lines that represent points that are to be tested if
they penetrate a particular airspace surface or other type of 3D surface. Several commands that
calculate conflicts with various surfaces use these lines to produce conflict reports. Along with the
lines and surfaces that are drawn, an ID is attached to the line so that the conflict processes can
identify a penetration by this ID number. The ID number is also placed next to each line as text for
visual reference. The process for using this command is as follows. Select the command from the pull-
down menu as indicated above. The following prompt will appear:
Select Obstruction Point:
Select a location on-screen that represents the desired point of obstruction to be tested. The following
prompt will appear:
Enter Base Elevation/<0.00>:
Enter the bottom elevation of the obstruction. The following prompt will appear:
Enter Height/<1.00>:
Enter the height of the obstruction AGL. The following prompt will appear:
Description/<NONE>:
Enter a description for the obstruction. The description length is only 12 characters. You can hit the
<Enter> key to accept the default. This description is listed in the report that is generated from the
conflict processes. The following prompt will appear:
Select Next Obstruction Point/<Exit>:
This process will repeat until you hit <Enter> to exit.
Note: The text height for the ID point will utilize the text height set in AutoCAD for the drawing
session.

MENU: AirSpace -> Analysis/Conflict Setup -> Place Multi Conflict Objects:
Description: Place Multiple 3D Objects between two points for use with various conflict
calculations.
This command will allow the user to place multiple vertical lines that represent points that are to be
tested if they penetrate a particular airspace surface or other type of 3D surface. Several commands
that calculate conflicts with various surfaces use these lines to produce conflict reports. Along with
the lines and surfaces that are drawn, an ID is attached to the line so that the conflict processes can
identify a penetration by this ID number. The ID number is also placed next to each line as text for
visual reference. The primary difference between this command and the previous one is that this one
calculates the position of additional conflict objects that lie between two selected points. An example
of this might be a wall of a structure. Rather than place many conflict objects along a wall by manually
calculating the positions and height of each stick at 1.0 foot intervals along the wall, this command
does it automatically. The process for using this command is as follows. Select the command from the
pull-down menu as indicated above. The following prompt will appear:
Select Obstruction Start Point:
Select a location on-screen that represents the beginning point of the obstruction objects to be drawn.
The following prompt will appear:
Enter the bottom elevation of the obstruction. The following prompt will appear:
Enter the height of the obstruction AGL. The following prompt will appear:
Select Obstruction End Point:
Select a location that represents the end point of the obstruction objects to be drawn. The following
prompt will appear:
Enter the bottom elevation of the end point obstruction. The following prompt will appear:
Enter the height of the end point obstruction AGL. The following prompt will appear:
Description/<NONE>:
MENU: AirSpace -> Analysis/Conflict Setup -> Place Multi Conflict Objects:

(Continued):
Enter a description for the obstruction. The description length is only 12 characters. You can hit the
<Enter> key to accept the default. This description is listed in the report that is generated from the
conflict processes. The following prompt will appear:
Enter Object Interval Distance/<0.50>:
Enter the interval distance between the conflict objects that are to be drawn. The conflict objects will
then be drawn as specified. This process will repeat until you hit <Enter> to exit.

MENU: AirSpace -> Analysis/Conflict Setup -> Make Tree XYZ File:
Description: Create a Tree Location Data File for use with the TREE command.
This file contains X and Y coordinate data along with the top and bottom elevation data for each tree.
The process for using this command is as follows. Select the command from the pull-down menu as
indicated above. A file name dialog box will appear. Enter the name of the tree location XYZ file to
be created. After you enter the file name the following prompt will appear:
Select Tree Location:
Select a point on-screen for the location of a tree. You could use this command while digitizing from
a existing drawing or aerial photograph for a quicker way of translating the locations of the trees to
the XYZ data file. You can also enter the point coordinates manually. The following prompt will
appear:
Enter the elevation of the bottom of the tree. The following prompt will appear:
Enter Tree Height/<10.00>:
Enter the elevation of the top of the tree. A vertical line will be drawn that represents the three
dimensional location of the center of the tree. Surfaces will be drawn around the line to represent the
tree. The following prompt will appear:
Select Next Tree Location/<Exit>:
Repeat the process to place more trees or hit <Enter> to exit. The XYZ file will then be written to
disk. An example of the file format is listed below:
X Y Top Elevation Base Elevation

8699.8431 556.3515 47.4500 12.3000

MENU: AirSpace -> Analysis/Conflict Setup -> Tree Conflict:
Description: Calculate and Report on Tree Conflicts with Airspace Surfaces.
This command will process a data file created with the MAKEXYZ command. This calculates
penetration points between trees and airspace surfaces. It also allows the user to enter a rate of
growth factor to determine future conflicts for tree maintenance. The process for using this command
is as follows. Select the command from the pull-down menu as indicated above. A file dialog box will
appear with a list of the available XYZ data files that represent tree locations. These files are created
with the MAKEXYZ command. After a file is selected another file dialog box will appear. Enter the
file name of the file that will be created for the generated report if conflicts are found. After you enter
the file name, the following prompt will appear:
Enter Feet of Growth Per Year/<0.00>:
If you want to calculate future growth for trees, enter a value for the estimated growth per year for
the trees in the selected file. If you do not want to predict future growth, then hit the <Enter> key. If
you did enter a growth rate, the following prompt will appear:
Enter Number of Years of Growth:
Enter the number of years of growth that you want to calculate. The file will then be processed to see
if any penetration occurs. If conflicts are found then a report is generated and written to disk. An
example of the file format is listed below:
TREE PENETRATION OF AIRSPACE SURFACES REPORT

GENERATED FROM [ C:\3DAAP\TEST.XYZ ].
FEET OF GROWTH PER YEAR = [ 2.00 ]
NUMBER OF YEARS OF GROWTH = [ 1 ]
====================================================================
Tree Tree Penetration Point Surface or Layer Name
ID No X Coordinate Y Coordinate Elevation of Penetration Surface
====================================================================
1 8699.843 556.352 239.100 Horizontal Plane

MENU: AirSpace -> Analysis/Conflict Setup -> Spot Conflict:
Description: Calculate Individual Point Conflicts with Surfaces.
This command will allow the user to select a point on-screen and obtain the spot elevation for the
point of penetration of a surface. It places a small circle at the 3D coordinate of penetration for visual
reference. The process for using this command is as follows. Select the command from the pull-down
menu as indicated above. The following prompt will appear:
Select Point to Inquiry:
Select the location of the point to be tested. You may also enter the coordinates manually. The
Enter Point Base Elevation/<100.0>:
Enter the base or bottom elevation of the point to be tested. This value represents items such as the
bottom of an antenna tower or other similar structure. The following prompt will appear:
Enter Point Top Elevation/<200.0>:
Enter the top elevation of the point to be tested. This value represents the top of the structure or item.
The intersection point of that point and any surface that it penetrates (if found) will be displayed as
follows:
Penetration of surface on layer [ 42 ].

Intersection at [ 15502.7506, -37371.1125, 919.9384 ].
Penetration above surface [ 499.834 ] below surface [ 123.4 ].
Select Point to Inquiry:
The point of penetration and the layer name or surface description (depending on what surface is
found) is listed. Repeat the process until you hit <Enter> to exit.

MENU: AirSpace -> Profile Tools -> Airspace Only Profile:
Description: Draw a Profile View of Airspace and Object Surfaces with Grid.
This command will allow the user to draw a profile view of a cross section of the airspace model and
associated 3D objects that are in the range of the profile section. A grid is drawn to better reference
the profile view. The vertical scale, horizontal increment and vertical increment can be user specified.
The process for using this command is as follows. Select the command from the pull-down menu as
indicated above. The following prompt will appear:
Select Profile Line/<Draw Profile>:
If an existing profile centerline has been drawn, then select that line. Otherwise, hit <Enter> to draw
a profile centerline. This line represents a cross section that is used to draw a profile view of the
surfaces that it intersects. If you are drawing a profile line, the following prompt will appear:
Select Start Point:
Select the start point of the profile line. After you select a point, the following prompt will appear:
Select End Point:
Select the end point of the profile line. A line will be drawn that represents where the cross section for
the profile view will be cut. After the line is drawn, the airspace surface layers will be turned off to
better facilitate viewing of the objects that will be selected in the next step. The following prompt will
appear:
Select objects to project into profile:
Select the objects that you want to project into the profile view. These are the 3DFACE surfaces
created with the 3DBLDG, MAKEXYZ, TREE or the CONFOBJ command. Use a window
selection method to insure that all surfaces are selected. You do not have to select any surfaces if you
so desire. After you select the surfaces, the airspace layers will be turned back on. The following
prompt will appear:
Vertical Scale/<10.00>:
Enter the appropriate vertical scale factor for the profile view. Or hit the <Enter> key to accept the
default. The following prompt will appear:
Minimum elevation on profile = [ 0.00 ].

Bottom of Grid Elevation/<-10.00>:

MENU: AirSpace -> Profile Tools -> Airspace Only Profile (Continued):
Enter the elevation that you want the bottom of the grid of the profile view to be drawn at. This
defaults to 10 feet below the lowest elevation of any of the sections found. Hit the <Enter> key to
accept the default. The following prompt will appear:
Horizontal Grid Spacing/<2000.00>:
Enter the grid spacing for the horizontal lines on the grid. The following prompt will appear:
Vertical Grid Spacing/<100.00>:
Enter the grid spacing for the vertical lines on the grid. The following prompt will appear:
Select Profile Grid Insertion Point:
Select the location for the bottom left corner of the profile grid. After you select the point, the profile
view will be drawn. The process will then be complete.

MENU: AirSpace -> Profile Tools -> Setup Multiple Profiles:
Description: Create Multiple Profile Baselines.
This command will allow the user to draw profile centerlines that are used in the various profile
generation commands. The process for using this command is as follows. Select the command from
the pull-down menu as indicated above. The following prompt will appear:
Select Start Point:
Select the starting location of the profile centerline. You may also enter the coordinates manually.
The following prompt will appear:
Select End Point:
Select the end point of the profile line. The centerline profile segment will then be drawn between the
two points. This process will repeat until you hit <Enter> to exit.

MENU: AirSpace -> Profile Tools -> Single Profile:
Description: Draw a Profile View of any Surfaces with Grid.
This command will allow the user to draw a profile view of a cross section of all 3D objects and
3DFACE surfaces that are in the range of the profile centerline section. A grid is drawn to better
reference the profile view. The vertical scale, horizontal increment and vertical increment can be user
specified. The process for using this command is as follows. Select the command from the pull-down
menu as indicated above. The following prompt will appear:
Select Profile Line/<Draw Profile>:
If an existing profile centerline has been drawn, then select that line. Otherwise, hit <Enter> to draw a
profile centerline. This line represents a cross section that is used to draw a profile view of the
surfaces that it intersects. If you are drawing a profile line, the following prompt will appear:
Select Start Point:
Select the start point of the profile line. After you select a point, the following prompt will appear:
Select End Point:
Select the end point of the profile line. A line will be drawn that represents where the cross section for
the profile view will be cut. After the line is drawn, the airspace surface layers will be turned off to
better facilitate viewing of the objects that will be selected in the next step. The following prompt will
appear:
Minimum elevation on profile = [ 0.00 ].

Bottom of Grid Elevation/<-10.00>:
Enter the elevation that you want the bottom of the grid of the profile view to be drawn at. This
defaults to 10 feet below the lowest elevation of any of the sections found. Hit the <Enter> key to
accept the default. The following prompt will appear:

MENU: AirSpace -> Profile Tools -> Single Profile (Continued):
Select the location for the bottom left corner of the profile grid. After you select the point, the profile
view will be drawn. The process will then be complete. NOTE: The bottom elevation of the grid is
labeled on the bottom left side of the drawn profile.

MENU: AirSpace -> Profile Tools -> Multiple Profiles:
Description: Draw Multiple Profile Views of any Surfaces with Grid.
This command will allow the user to draw multiple profile views of any cross section centerlines of all
3D objects and 3DFACE surfaces that are in the range of the profile centerline sections. A grid is
drawn to better reference the profile view. The vertical scale, horizontal increment and vertical
increment can be user specified. The process for using this command is as follows. Select the
Select Profile Lines:
Select any existing profile centerlines to create profile views from. After selecting the profile
centerlines that you want to use, the following prompt will appear:
Select the location for the bottom left corner for all of the profile grids to be drawn. The profile grids
are drawn from the bottom up. After you select the point, the profile views will be drawn. The
process will then be complete. NOTE: The bottom elevation of the grid is labeled on the bottom left
side of the drawn profiles.

MENU: AirSpace -> Misc Surfaces -> Radar:
Description: Draw a Radar Projection Airspace Surface.
This command will draw a 3D surface that represents the area that would be required to check for
obstructions for an Airport Surveillance Radar (ASR). The process for using this command is as
appear:
Select Insertion Point:
Select the center point of the radar surface area. After you select the insertion point the following
prompt will appear:
Enter Elevation:
Enter the elevation (ground elevation) for the insertion point of the radar surface. After you enter the
elevation, the radar surface will be drawn. The process will then be complete.

MENU: AirSpace -> Misc Surfaces -> 100_1Srf:
Description: Draw a 100:1 Airspace Surface.
This command will draw a circular airspace surface with a rise of 100:1 feet from the center point.
This surface is described in FAR Part 77.13 Section (a)(1) (i). The process for using this command is
as follows. Select the command from the pull-down menu as indicated above. The following prompt
will appear:
Select Insertion Point:
Select the center point of the 100:1 surface. After you select the insertion point the following prompt
will appear:
Enter Elevation:
Enter the elevation (ground elevation) for the insertion point for the 100:1 surface. After you enter
the elevation, the 100:1 surface will be drawn. The process will then be complete.

MENU: AirSpace -> 3D View:
Description: Position Perspective View.
This command will allow the user to position the display for a particular perspective view. The
indicated above. The following prompt will appear:
Select Target Point:
Select the point that you want to view. The following prompt will appear:
Enter Target Elevation:
Enter the elevation of the target point. The following prompt will appear:
Select Eye Point:
Select the point that you want to view from. The following prompt will appear:
Enter Eye Elevation:
Enter the elevation of the eye point. The display will then adjust to show a perspective view of your
model from the eye point looking at the target point. To set the display back to normal, type in PLAN
and hit the <Enter> key. This would be used for visually checking the line of sight from the control
tower point to points located around the airfield.

MENU: AirSpace -> Surf Prep:
Description: Create 3 Sided Surfaces From All 4 Sided Surfaces.
This command is to convert any four sided 3DFACE surfaces into the required three sided 3DFACE
surfaces. The 3DAAP software requires three sided surfaces for the programming to work. This
prevents errors in calculating surface intersections that can arise when using four sided surfaces. The
indicated above. The following prompts will appear.
Converting Surfaces to Three Sided.

Their are [ 587 ] Surfaces to Process.
Processing Surface [ 573 ].
The number of surfaces that are to be processed will be shown when the process starts. Any four
sided surface will be converted into a three sided counter-clockwise orientated 3DFACE surface. The
process will be completed when the counter reaches the total number of surfaces.

MENU: AirSpace -> Set Project:
Description: Set the Current Project Name.
Each time the 3DAAP software is loaded for use, the user is asked for a project name. This project
name represents the overall project reference name. This project name is used to create the
appropriate sub-directory on your hard drive that will contain all project specific files that are used or
created by this software. All analysis conflict files will then be placed under this project sub-directory
location. The directory structure for all projects is as follows:
\3DAAP\ ....... ........... ...................... (Software Location)

\3DAAP\PROJECTS\ ..................... (Central Path to All Projects)
JFK\............. (Sample Projects)
OIA\
LASVEGAS\

MENU: AirSpace -> Building/Mapping Tools -> 3D Building to Elev
Description: Create Fixed Height 3D Buildings or Structures from Polylines.
This command will draw a representation of a 3D building or structure using a polyline for the
outline. These buildings can then be used in the various profile generation commands to show in the
profile view or for creating shadow diagramming analysis. The process for using this command is as
appear:
Select Building Outlines/<Exit>:
Select all of the polyline entities that represent the outline of a building or structure. Use the
AutoCAD PLINE or 3DPOLY command to draw these. Once you have selected the polylines, the
Enter Building Height:
Enter the height of the building or structure. After you enter the height, the walls will be drawn. You
can use the 3DVIEW or the AutoCAD VPOINT command to view the buildings better. If the
polylines are already at an elevation, for instance rooflines obtained from three-dimensional
photogrammetry, you can enter a negative elevation to create the walls from the rooflines down to the
ground.

MENU: AirSpace -> Building/Mapping Tools -> 3D Building to Surface
Description: Create Variable Height 3D Buildings or Structures from Polylines that are
Projected to Ground Surfaces.
This command will draw 3DFACE surfaces from a building or structure polyline outline down to any
digital terrain model surfaces that are in the same drawing. This is useful in converting digitized aerial
photography drawings into 3D quickly and accurately. It will also draw a flat roof over the entire area
of the polyline outline if needed. These 3D buildings can then be used in the various profile generation
commands to show in the profile views. The process for using this command is as follows. Select the
Calculating lowest surface elevation....

Lowest surface elevation = [ 23.34 ].
Select Building Outlines/<Exit>:
Select objects:
Select all of the polyline entities that represent the outline of a building or structure. Use the
AutoCAD PLINE or 3DPOLY command to draw these. Make sure that the polylines that are used
in this process are at their accurate elevations. Once you have selected the polylines, the following
prompt will appear:
Processing segment [ 2 ] of polyline [ 1 ].
The surfaces will begin to be calculated and drawn. Once all of the polylines selected have been
processed, the following prompt will appear:
Draw roof? No/<Yes>:
Enter Yes to draw the roof. Otherwise enter No to exit the command. You can use the 3DVIEW or
the AutoCAD VPOINT command to view the buildings better.

MENU: AirSpace -> Symbols
Description: NAVAID and Aircraft 2D and 3D Symbol Library.
This menu selection allows the user to select from a library of 2D and 3D symbols and aircraft for
insertion into your drawing. The listing of NAVAIDS available are depicted in Appendix C of the
standards manual. The process for using this command is as follows. Select the command from the
pull-down menu as indicated above. Then select the desired library that contains the specific symbol
or aircraft to be inserted. Then select the particular symbol as described below. All navigational aids
are to be inserted at the specific runway end point for proper alignment. All aircraft are inserted by
their particular nosewheel location.
NAVAID symbols are to be used for 2D siting only. Aircraft 3D symbols are to be used with 3D
viewing and obstruction shadow diagramming.
NOTE: There may be instances when a navigational aid symbol may need to be mirrored after an
insertion and rotation. If this is required, set the AutoCAD variable "MIRRTEXT" to "0" then
mirror the symbol as required and delete the old object. Then set the variable "MIRRTEXT@ back
to "1". Example:
Mirrtext 0
Mirror the symbol
Delete old symbol
Mirrtext 1

MENU: Analysis -> FAR Part 77 -> Airspace Model Conflict Test
Description: Calculate and Report on Object Conflicts with Airspace Surfaces.
This command processes the objects placed with the conflict object placement commands for conflicts
or penetrations of the various analysis criteria surfaces. A report in the form of an ASCII file is
created for the user. The report includes the location of penetration using the station and offset from a
user selected runway centerline. It also identifies what surface is penetrated along with the elevation
of the point of penetration. The process for using this command is as follows. Select the command
from the pull-down menu as indicated above. The layers that contain the airspace surfaces will be
turned off. This is to allow the user to see the runway center lines for easier selection at the next
prompt. The following prompt will appear:
Select Runway Centerline to Offset Obstructions from/<Exit>:
Select the runway centerline that you want the station and offset for all points of penetration to be
calculated from. Extended entity data has been attached to these center lines that contain information
about the particular runway. That data will be displayed as follows:
Airport [ Orlando Executive ] at Elev [ 112.10 ] with [ 2 ] RW's

Starting RW [ 10 ] Ending RW [ 28 ] Proceed? No/<Yes>:
This provides the user the information about the runway selected. If it is the correct runway, hit the
<Enter> key to proceed. Otherwise, type in NO to select another runway. The airspace surface layers
will then be turned back on. The following prompt will appear:
Select Airspace Surfaces: (Window or Crossing)
Select the airspace surfaces that you want to process the conflict objects against. You can select all of
the surfaces at once for an easier selection, but it will take longer to process. Once again, the layers
that contain the airspace surfaces will be turned off. The following prompt will appear:
Select Obstruction Objects:

MENU: Analysis -> FAR Part 77 -> Airspace Model Conflict Test (Continued)
Select the obstruction objects to be processed with a window selection method. The layers will be
turned back on and an activity prompt will be displayed indicating the status of the process. The
process can take anywhere from several seconds to several minutes depending on the number of items
to be processed. When the process is complete you will be prompted if conflicts were found. A report
will be generated and written to disk under the project file name. A report will only be generated if
the objects are directly under an airspace surface. If the objects do not conflict with a surface, the
report will only provide station and offset information for the object. An example of that file would
look like the following:
PENETRATION ANALYSIS REPORT
AIRPORT NAME = [ SAMPLE ONE RUNWAY SETUP ]
AIRPORT ELEV = [ 89.10 ]
NUMBER OF RUNWAYS = [ 1 ]
DESIGNATED RUNWAY END NAMES = Start [ 10 ] End [ 28 ]
RUNWAY CENTERLINE START POINT = [ 350.4779, 3417.8744, 91.2000]
RUNWAY CENTERLINE END POINT = [ 2695.0544, -4094.2029, 85.4000]
RUNWAY LENGTH = [ 7869.46 ]
RUNWAY CENTERLINE FORESIGHT ANGLE = [ 287 ]
==================================================================
I.D. Conflict Station Station Offset Description Surface Penetrated
Num. Elev MSL From SP From EP (- Left) (Or Layer Name)
==================================================================
1 1017.61 47357.86 39488.40 783.03 Pole Outer App.
2 811.62 39118.42 31248.96 1962.25 Sign Outer App.
Two report files are created with this command. The file name extensions are .CNF and .CND. The
.CNF file is the one described above. The .CND file is similar except that it portrays the base
elevation, the top elevation and the penetration amount.

MENU: Analysis -> Terminal Instrument Procedures -> TERPS Conflict Test
Description: Calculate and Report on Adjusted Decision Height and New Visibility
Requirements for ILS Surfaces
Note: This command will only work if the airport has its TERPS surfaces properly constructed in 3D
wireframe depictions within AutoCAD.
The TERPCON command processes an object for the potential impact to the decision height and
visibility requirements for a particular runway's ILS approach surface. If there is an impact, the
routine will report a new decision height and associated visibility requirement. A report in the form of
an ASCII file is created for the user to use. An example of the report is included at the end of this
section. This command will also graphically depict the distance and offset of the analyzed object.
Before starting the command you will have to insert the runways specific TERP surfaces. Then the
indicated above. All layers will be shut off except for the Terp Construction Surfaces. Select the
surfaces utilizing the AutoCAD crossing selection set option and hit <Enter>. There should always
be two surfaces that you selected. Then all layers will be frozen except for the ILS surface. You will
then be prompted to select all outer transitional surfaces. Utilize the selection process as described
previously and hit <Enter>. the following dialog box will be displayed which will prompt you for an
output file name.

(Continued):
Type a filename of your choice. The information needed to complete the analysis will be required. The
following prompts are what the program will need:
Enter Airport Name/<>:
Enter Airport Elevation/<0.00>:
Enter Runway End Designation/<>:
Runway End Point/<0.000000,0.000000>:
This should exactly match the insertion point of the TERP 3D wireframe surfaces.
Enter Runway End Point Elevation/<0.00>:
Enter Runway End Point Latitude/<>:
Enter Runway End Point Longitude/<>:
Enter Runway Length/<0.00>:
Enter Runway True Bearing as Azimuth Angle/<0.000000>:
Enter Touchdown Zone Elevation/<0.00>:
Enter GPI to Threshold Distance/<0.00>:
Obtained from TERP construction effort or from the appendix.
Select Obstruction Location/<0.000000,0.000000>:
Enter Obstruction Latitude/<>:
Enter Obstruction Longitude/<>:
Enter Top of Obstacle Elevation MSL/<0.00>:
Enter Obstacle Height AGL/<0.00>:

(Continued):
If there is a penetration then Conflicts Found will be in the command prompt with the associated
output file created. An example of the output file is shown below.
TERP ILS ANALYSIS REPORT
AIRPORT NAME = [ Miami Intl. Airport ]
AIRPORT ELEV = [ 9.30 ]
RUNWAY END DESIGNATION = [ 09L ]
RUNWAY END POINT = [ 0.0000, 0.0000, 9.3000]
RUNWAY END LATITUDE = [ 20 00 00 ]
RUNWAY END LONGITUDE = [ 80 00 00 ]
RUNWAY LENGTH = [ 9754.23 ]
RUNWAY TRUE BEARING = [ 90.000000 ]
TOUCHDOWN ZONE ELEVATION = [ 9.30 ]
GPI TO THRESHOLD DISTANCE = [ 900.00 ]
OBSTACLE LOCATION = [ -7981.0989, 4221.9891, 0.0000]
OBSTACLE LATITUDE = [ 20 09 00 ]
OBSTACLE LONGITUDE = [ 80 01 00 ]
OBSTACLE HEIGHT MSL = [ 500.00 ]
OBSTACLE HEIGHT AGL = [ 490.70 ]
DECISION HEIGHT REPORT
======================
DISTANCE FROM RUNWAY END POINT = [ 7981.10 ]

(Continued):
OFFSET FROM RUNWAY END POINT = [ 4221.99 ]
COMPUTED NEW DECISION HEIGHT = [ 272.10 ]
HEIGHT ABOVE THRESHOLD = [ 262.80 ]
VISIBILITY REPORT
=================
VISIBILITY NOT LESS THAN 1 MILE.

MENU: Analysis -> FAA Electronic Underground Cable -> Create Buffer Offset
Description: Create Buffer Zone for Underground Cable Test.
This command will create a polyline offset buffer that defines the area around a structure or building
that will be used in the electronic underground cable vicinity test. You must have an existing polyline
in your drawing to use as the structure or building outline. The process for using this command is as
appear:
Enter Buffer Offset/<50.0>:
Enter the offset distance for creating the buffer offset. The default for the test is the FAA criteria of
50.0 feet. The following prompt will appear:
Select Buffer to Offset/<Exit>:
Select the buffer outline to offset. The following prompt will appear:
Select side to offset:
Select a point to indicate which side to offset the buffer on. The offset buffer will then be drawn.

MENU: Analysis -> FAA Electronic Underground Cable -> Underground Cable Vicinity
Test
Description: Locates any electronic underground cables within buffer.
This command tests for electronic underground cables that are within a user defined buffer around a
structure or building. The process for using this command is as follows. Select the command from the
pull-down menu as indicated above. The following prompt will appear:
Select Buffer Outline/<Exit>:
Select a polyline that represents the buffer area to be tested. If any cables are found, then the user will
be notified. You will then have the option to create a graphic of the area. A dialog box appears that
asks the user to enter a filename for the drawing file to be saved of the buffer area. If you do not
want to create a drawing, press the CANCEL button on the dialog box.

MENU: Analysis -> Airport Traffic Control Towers -> ATCT Conflict Test
Description: Calculate and Report on Object Conflicts with ATCT Surfaces.
This command processes the objects placed with the various conflict object placement commands for
conflicts or penetrations of ATCT surfaces. A report in the form of an ASCII file is created for the
user. The report includes the identification reference number of the conflict object, the X, Y, Z
coordinates of the penetration and the layer name of the surface penetrated. The process for using this
command is as follows. Select the item as shown above on the pull-down menu. The following
prompt will appear:
Select [ ATCT ] Conflict Surfaces:
As indicated, select the surfaces that are to be tested for potential conflicts. After you do that, the
Select [ ATCT ] Obstruction Objects:
Select the conflict objects to be tested. These are the conflict objects placed with the Place Conflict
Object or Place Multi Conflict Object commands. Once you have selected the objects, the
Example: Processing Item [ 12 ] with [ 1 ] to go.
This indicates that the processing of each object is taking place. If conflicts are found then it displays
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.att ] and [ \3daap\projects\jfk\jfk.atd] created.
If no conflicts are found then it displays the following:
No conflicts found!
[ \3daap\projects\jfk\jfk.att ] and [ \3daap\projects\jfk\jfk.atd] deleted.
The filenames shown above are examples of the reports that are generated with this command. The
filenames are based upon the current project name and the current conflict test that is being used. The
.ATT filename extension represents the ATCT ASCII text file report that is generated if conflicts are
found. The .ATD filename extension represents the ATCT ASCII comma delimited format file that
represents the same results which can then be imported into a database application as needed.

MENU: Analysis -> Airport Surface Detection Equipment -> ASDE Conflict Test
Description: Calculate and Report on Object Conflicts with ASDE Surfaces.
conflicts or penetrations of ASDE surfaces. A report in the form of an ASCII file is created for the
prompt will appear:
Select [ ASDE ] Conflict Surfaces:
Select [ ASDE ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.ast ] and [ \3daap\projects\jfk\jfk.asd] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.ast ] and [ \3daap\projects\jfk\jfk.asd] deleted.
.AST filename extension represents the ASDE ASCII text file report that is generated if conflicts are
found. The .ASD filename extension represents the ASDE ASCII comma delimited format file that

MENU: Analysis -> Approach Lighting Systems -> Insert xxx
Description: Insert Various ALS Lighting Surfaces
These are a series of FAA defined surfaces that are used in the completion of the analysis tests that
are conducted with this software. The items that can be inserted are listed as follows:
ALSF-2 Approach Lighting System

MALS Approach Lighting System
MALSF Approach Lighting System
MALSR Approach Lighting System
ODALS Approach Lighting System
When a surface type is selected the user is asked for an insertion point and then an elevation
for the insertion point. After that the user defines the clockwise angle of insertion rotation with 0.0
degrees pointing up or to the North. The surfaces will then be inserted into the drawing.

MENU: Analysis -> Approach Lighting Systems -> ALS Conflict Test
Description: Calculate and Report on Object Conflicts with ALS Surfaces.
conflicts or penetrations of ALS surfaces. A report in the form of an ASCII file is created for the
prompt will appear:
Select [ ALS ] Conflict Surfaces:
Select [ ALS ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.alt ] and [ \3daap\projects\jfk\jfk.ald] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.alt ] and [ \3daap\projects\jfk\jfk.ald] deleted.
.ALT filename extension represents the ALS ASCII text file report that is generated if conflicts are
found. The .ALD filename extension represents the ALS ASCII comma delimited format file that

MENU: Analysis -> Visual Approach Slope Indicators -> Insert xxx
Description: Insert Various VASI Surfaces
These are a series of FAA defined surfaces that are used in the completion of the analysis tests that
are conducted for Visual Approach Slope Indicators. Please refer to Appendix C of the standards
document for VASI references. The items that can be inserted are listed as follows:
VASI-2 Downwind Bar

VASI-2 Upwind Bar
VASI-3 Downwind Bar
VASI-3 Middle Bar
VASI-3 Upwind Bar
When a surface type is selected the user is asked for an insertion point and then an elevation for the
insertion point. After that the user defines the clockwise angle of insertion rotation with 0.0 degrees
pointing up or North. The surfaces will then be inserted into the drawing.

MENU: Analysis -> Visual Approach Slope Indicators -> VASI Conflict Test
Description: Calculate and Report on Object Conflicts with VASI Surfaces.
conflicts or penetrations of VASI surfaces. A report in the form of an ASCII file is created for the
prompt will appear:
Select [ VASI ] Conflict Surfaces:
Select [ VASI ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.vat ] and [ \3daap\projects\jfk\jfk.vad] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.vat ] and [ \3daap\projects\jfk\jfk.vad] deleted.
.VAT filename extension represents the VASI ASCII text file report that is generated if conflicts are
found. The .VAD filename extension represents the VASI ASCII comma delimited format file that

MENU: Analysis -> Precision Approach Path Indicators -> Insert PAPI
Description: Insert PAPI Surfaces
This command inserts a single set of FAA defined Precision Approach Path Indicator surfaces that
are used in the completion of the analysis tests. When the command is selected the user is asked for
an insertion point and then an elevation for the insertion point. After that the user defines the
clockwise angle of insertion rotation with 0.0 degrees pointing up or North. The surfaces will then be
inserted into the drawing.
Note: Please refer to Appendix C of the standards document for the PAPI references.

MENU: Analysis -> Precision Approach Path Indicators -> PAPI Conflict Test
Description: Calculate and Report on Object Conflicts with PAPI Surfaces.
conflicts or penetrations of PAPI surfaces. A report in the form of an ASCII file is created for the
prompt will appear:
Select [ PAPI ] Conflict Surfaces:
Select [ PAPI ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.pat ] and [ \3daap\projects\jfk\jfk.pad] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.pat ] and [ \3daap\projects\jfk\jfk.pad] deleted.
.PAT filename extension represents the PAPI ASCII text file report that is generated if conflicts are
found. The .PAD filename extension represents the PAPI ASCII comma delimited format file that

MENU: Analysis -> VHF Omnidirectional Range Station -> VORS Vicinity Test
Description: Checks for Conflict Objects within VORS Criteria.
This command tests for the presence of conflict objects within the VORS vicinity test defined radius.
The process for using this command is as follows. Select the item as shown above on the pull-down
menu. The following prompt will appear:
Select VORS Location:
Select the center point of the area to be checked for conflict objects. It is the center point of the
radius used for this particular test. The following prompt will appear:
Enter VORS elevation:
Enter the elevation of the center point just selected. The display will resize itself to fit the area being
tested and a circle will be drawn to show the area. This circle is only drawn on screen and can be
removed by a simple redraw of the drawing. If no conflict objects are found, the user is informed of
that fact. If conflict objects are found, the user is asked to create a drawing of the area being tested. If
a drawing is wanted, then enter a filename for the drawing and press the OK button. Otherwise, hit
the Cancel button to exit.

MENU: Analysis -> VHF Omnidirectional Range Station -> Insert 0.5 Degree Surface
Description: VORS 0.5 Degree Surface Insertion
This command inserts a single set of FAA defined VORS 0.5 degree surfaces that are used in the
completion of the analysis tests that are conducted. When the command is selected the user is asked
for an insertion point and then an elevation for the insertion point. The surfaces will then be inserted
into the drawing.

MENU: Analysis -> VHF Omnidirectional Range Station -> VORS Conflict Test
Description: Calculate and Report on Object Conflicts with VORS Surfaces.
conflicts or penetrations of VORS surfaces. A report in the form of an ASCII file is created for the
prompt will appear:
Select [ VORS ] Conflict Surfaces:
Select [ VORS ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.vot ] and [ \3daap\projects\jfk\jfk.vod] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.vot ] and [ \3daap\projects\jfk\jfk.vod] deleted.
.VOT filename extension represents the VORS ASCII text file report that is generated if conflicts are
found. The .VOD filename extension represents the VORS ASCII comma delimited format file that

MENU: Analysis -> VHF Omnidirectional Range Station -> Width Test
Description: Tests for VORS Width Criteria.
This command tests for the angle between two points that the user selects. These points locate the
positions of the end points of the extents of a structures penetration through a particular surface or
surfaces. The process for using this command is as follows. Select the item as shown above on the
pull-down menu. The following prompt will appear:
Select VORS Location:
Select the location of the VORS. The following prompt will appear:
Select First Width Point:
Select the start point of the points of conflict that are to be tested. The following prompt will appear:
Select Second Width Point:
Select the end point of the extents of the penetration being tested. If the width is within the allowed
distances, the following prompt will appear:
Enter VOR Radio Frequency in MHz.
Structure Width = [ 33.0] Allowed Width = [ 45.0 ].

Width of structure is within tolerance allowed. Test passed!
If the width is greater than allowed, the following prompt will appear:

Width of structure is greater than allowed. Test Failed.
The process is now complete.

MENU: Analysis -> Distance Measuring Equipment -> DME Vicinity Test
Description: Checks for Conflict Objects within DME Criteria.
This command tests for the presence of conflict objects within the DME vicinity test defined radius.
Select DME Location:
Enter DME elevation:

MENU: Analysis -> Distance Measuring Equipment -> Insert 0.5 Degree Surface
Description: DME 0.5 Degree Surface Insertion
This command inserts a single set of FAA defined DME 0.5 degree surfaces that are used in the
completion of the analysis tests that are conducted. When the command is selected the user is asked
into the drawing.

MENU: Analysis -> Distance Measuring Equipment -> DME Conflict Test
Description: Calculate and Report on Object Conflicts with DME Surfaces.
conflicts or penetrations of DME surfaces. A report in the form of an ASCII file is created for the
prompt will appear:
Select [ DME ] Conflict Surfaces:
Select [ DME ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.dmt ] and [ \3daap\projects\jfk\jfk.dmd] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.dmt ] and [ \3daap\projects\jfk\jfk.dmd] deleted.
.DMT filename extension represents the DME ASCII text file report that is generated if conflicts are
found. The .DMD filename extension represents the DME ASCII comma delimited format file that

MENU: Analysis -> Non-Directional Beacons -> NDB Utility Line Vicinity Test
Description: Checks for Conflict Objects within NDB Utility Line Criteria.
This command tests for the presence of conflict objects within the NDB Utility Line vicinity test
defined radius. The process for using this command is as follows. Select the item as shown above on
the pull-down menu. The following prompt will appear:
Select NDB Location:
Enter NDB elevation:

MENU: Analysis -> Non-Directional Beacons -> NDB Vicinity Test
Description: Checks for Conflict Objects within NDB Antenna Height Criteria.
This command tests for the presence of conflict objects within the NDB vicinity test defined radius.
Select NDB Location:
Enter NDB base elevation:
Enter the elevation of the center point just selected. The following prompt will appear:
Enter NDB antenna height:
Enter the height of the NDB antenna. The display will resize itself to fit the area being tested and a
circle will be drawn to show the area. This circle is only drawn on screen and can be removed by a
simple redraw of the drawing. If no conflict objects are found that fail the height restrictions for this
test, the user is informed of that fact. If conflict objects are found, the user is asked to create a
drawing of the area being tested. If a drawing is wanted, then enter a filename for the drawing and
press the OK button. Otherwise, hit the Cancel button to exit.

MENU: Analysis -> Instrument Landing Systems -> Localizer Buffer Non-Crane
Description: Draws the ILS Buffer for this Criteria
This command draws a polyline that represents the buffer area that the ILS Localizer Buffer uses to
test for a Non-Crane structure. The process for using this command is as follows. Select the item as
shown above on the pull-down menu. The following prompt will appear:
Select Localizer Location:
Select the location point of the localizer. The following prompt will appear:
Select Runway Start Point:
Select the start point of the runway that is nearest the localizer location. The following prompt will
appear:
Select Runway End Point:
Select the runway end point. It is the opposite point from the start point. Once these points have been
selected, the buffer area will be drawn. A drawing of the area can then be created.

MENU: Analysis -> Instrument Landing Systems -> Localizer Buffer Crane
Description: Draws the ILS Buffer for this Criteria
This command draws a polyline that represents the buffer area that the ILS Localizer Buffer uses to
test for a Crane type structure. The process for using this command is as follows. Select the item as
Select Localizer Location:
Select the location point of the localizer. The following prompt will appear:
Select the start point of the runway that is nearest the localizer location. The following prompt will
appear:

MENU: Analysis -> Instrument Landing Systems -> Glide Slope Non-Crane
Description: Draws the ILS Glide Slope Buffer for this Criteria
This command draws a polyline that represents the buffer area that the ILS Glide Slope Buffer uses to
test for a Non-Crane structure. The process for using this command is as follows. Select the item as
Select Glide Slope Location:
Select the location point of the glide slope antenna. The following prompt will appear:
Select the start point of the runway that is nearest the glide slope location. The following
prompt will appear:
Select the runway end point. It is the opposite point from the start point. Once these points
have been selected, the buffer area will be drawn. A drawing of the area can then be created.

MENU: Analysis -> Instrument Landing Systems -> Glide Slope Crane
Description: Draws the ILS Glide Slope Buffer for this Criteria
This command draws a polyline that represents the buffer area that the ILS Glide Slope Buffer uses to
test for a Crane type structure. The process for using this command is as follows. Select the item as
Select Glide Slope Location:
Select the location point of the glide slope antenna. The following prompt will appear:
Select the start point of the runway that is nearest the glide slope location. The following prompt will
appear:

MENU: Analysis -> Instrument Landing Systems -> Markers Vicinity Test
Description: Checks for Conflict Objects within ILS Markers Criteria.
This command tests for the presence of conflict objects within the Markers vicinity test defined
radius. The process for using this command is as follows. Select the item as shown above on the pull-
down menu. The following prompt will appear:
Select Marker Location:
Enter Marker elevation:

MENU: Analysis -> Low Level Wind Shear Alert System -> LLWAS Conflict Test
Description: Calculate and Report on Object Conflicts with LLWAS Surfaces.
conflicts or penetrations of LLWAS surfaces identified in the next few pages. A report in the form of
an ASCII file is created for the user. The report includes the identification reference number of the
conflict object, the X, Y, Z coordinates of the penetration and the layer name of the surface
penetrated. The process for using this command is as follows. Select the item as shown above on the
Select [ LLWAS ] Conflict Surfaces:
Select [ LLWAS ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.llt ] and [ \3daap\projects\jfk\jfk.lld] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.llt ] and [ \3daap\projects\jfk\jfk.lld] deleted.
.LLT filename extension represents the LLWAS ASCII text file report that is generated if conflicts
are found. The .LLD filename extension represents the LLWAS ASCII comma delimited format file
that represents the same results which can then be imported into a database application as needed.

MENU: Analysis -> Low Level Wind Shear Alert System -> LLWAS Vicinity Test
Description: Checks for Conflict Objects within LLWAS Criteria.
This command tests for the presence of conflict objects within the LLWAS vicinity test defined
Select LLWAS Location:
Enter LLWAS elevation:

MENU: Analysis -> Low Level Wind Shear Alert System -> LLWAS 10 Degree Width
Test
Description: Tests for LLWAS Width Criteria.
positions of the end points of the extents of a structure=s penetration through a particular surface or
Select the location of the LLWAS. The following prompt will appear:



MENU: Analysis -> Low Level Wind Shear Alert System -> Electrical Noise Vicinity
Test
Description: Checks for Conflict Objects within LLWAS Electrical Noise Criteria.
This command tests for the presence of conflict objects within the LLWAS Electrical Noise vicinity
test defined radius. The process for using this command is as follows. Select the item as shown above
on the pull-down menu. The following prompt will appear:
Enter LLWAS elevation:

MENU: Analysis -> AWOS/ASOS -> AWOS/ASOS Conflict Test
Description: Calculate and Report on Object Conflicts with AWOS/ASOS Surfaces.
conflicts or penetrations of AWOS/ASOS surfaces. A report in the form of an ASCII file is created
for the user. The report includes the identification reference number of the conflict object, the X, Y, Z
prompt will appear:
Select [ AWOS ] Conflict Surfaces:
Select [ AWOS ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.awt ] and [ \3daap\projects\jfk\jfk.awd] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.awt ] and [ \3daap\projects\jfk\jfk.awd] deleted.
.AWT filename extension represents the AWOS/ASOS ASCII text file report that is generated if
conflicts are found. The .AWD filename extension represents the AWOS/ASOS ASCII comma
delimited format file that represents the same results which can then be imported into a database
application as needed.

MENU: Analysis -> AWOS/ASOS -> Electrical Noise Vicinity Test
Description: Checks for Conflict Objects within AWOS/ASOS Electrical Noise Criteria.
This command tests for the presence of conflict objects within the AWOS/ASOS Electrical Noise
vicinity test defined radius. The process for using this command is as follows. Select the item as
Select AWOS/ASOS Location:
Enter AWOS/ASOS elevation:

MENU: Analysis -> AWOS/ASOS -> Light Source Vicinity Test
Description: Checks for Conflict Objects within AWOS/ASOS Light Source Criteria.
This command tests for the presence of conflict objects within the AWOS/ASOS Light Source
vicinity test defined radius. The process for using this command is as follows. Select the item as
Select AWOS/ASOS Location:
Enter AWOS/ASOS elevation:

MENU: Analysis -> Wind Speed/Direction Equipment -> WS/DE Vicinity Test
Description: Checks for Conflict Objects within WSDE Criteria.
This command tests for the presence of conflict objects within the WSDE vicinity test defined radius.
Select WSDE Location:
Enter WSDE elevation:

MENU: Analysis -> Wind Speed/Direction Equipment -> WS/DE 10 Degree Width Test
Description: Tests for WSDE Width Criteria.
Select WSDE Location:
Select the location of the WSDE. The following prompt will appear:



MENU: Analysis -> Remote Hydrothermometer -> RHYDRO Vicinity Test
Description: Checks for Conflict Objects within RHYDRO Criteria.
This command tests for the presence of conflict objects within the RHYDRO vicinity test defined
Select RHYDRO Location:
Enter RHYDRO elevation:

MENU: Analysis -> Runway Visual Range -> Light Source Vicinity Test
Description: Checks for Conflict Objects within RVR Light Source Criteria.
This command tests for the presence of conflict objects within the RVR Light Source vicinity test
defined radius. The process for using this command is as follows. Select the item as shown above on
the pull-down menu. The following prompt will appear:
Select RVR Location:
Enter RVR elevation:

MENU: Analysis -> Communications Facilities -> CF Conflict Test
Description: Calculate and Report on Object Conflicts with CF Surfaces.
conflicts or penetrations of CF surfaces. A report in the form of an ASCII file is created for the user.
The report includes the identification reference number of the conflict object, the X, Y, Z coordinates
of the penetration and the layer name of the surface penetrated. The process for using this command
is as follows. Select the item as shown above on the pull-down menu. The following prompt will
appear:
Select [ CF ] Conflict Surfaces:
Select [ CF ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.cft ] and [ \3daap\projects\jfk\jfk.cfd] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.cft ] and [ \3daap\projects\jfk\jfk.cfd] deleted.
.CFT filename extension represents the CF ASCII text file report that is generated if conflicts are
found. The .CFTD filename extension represents the CF ASCII comma delimited format file that

MENU: Analysis -> Communications Facilities -> Insert 1.0 Degree Surface
Description: CF 1.0 Degree Surface Insertion
This command inserts a single set of FAA defined Communication Facility 1.0 degree surfaces that
are used in the completion of the analysis tests. When the command is selected the user is asked for
an insertion point and then an elevation for the insertion point. The surfaces will then be inserted into
the drawing.

MENU: Analysis -> Communications Facilities -> CF Vicinity Test 1
Description: Checks for Conflict Objects within CF Test 1 Criteria.
This command tests for the presence of conflict objects within the CF Test 1 vicinity test defined
Select CF Location:
Enter CF elevation:

MENU: Analysis -> Communications Facilities -> CF Vicinity Test 2
Description: Checks for Conflict Objects within CF Test 2 Criteria.
This command tests for the presence of conflict objects within the CF Test 2 vicinity test defined
Select CF Location:
Enter CF elevation:

MENU: Analysis -> Airport Surveillance Radars -> ASR Conflict Test
Description: Calculate and Report on Object Conflicts with ASR Surfaces.
conflicts or penetrations of ASR surfaces. A report in the form of an ASCII file is created for the
prompt will appear:
Select [ ASR ] Conflict Surfaces:
Select [ ASR ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.art ] and [ \3daap\projects\jfk\jfk.ard] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.art ] and [ \3daap\projects\jfk\jfk.ard] deleted.
.ART filename extension represents the ASR ASCII text file report that is generated if conflicts are
found. The .ARD filename extension represents the ASR ASCII comma delimited format file that

MENU: Analysis -> Airport Surveillance Radars -> Insert 0.25 Degree Surface
Description: ASR 0.25 Degree Surface Insertion
This command inserts a single set of FAA defined Airport Surveillance Radar 0.25 degree surfaces
that are used in the completion of the analysis tests that are conducted with this software. When the
command is selected the user is asked for an insertion point and then an elevation for the insertion
point. The surfaces will then be inserted into the drawing.

MENU: Analysis -> Airport Surveillance Radars -> ASR Vicinity Test 1
Description: Checks for Conflict Objects within ASR Test 1 Criteria.
This command tests for the presence of conflict objects within the ASR Test 1 vicinity test defined
Select ASR Location:
Enter ASR elevation:

MENU: Analysis -> Airport Surveillance Radars -> ASR Vicinity Test 2
Description: Checks for Conflict Objects within ASR Test 2 Criteria.
This command tests for the presence of conflict objects within the ASR Test 2 vicinity test defined
Select ASR Location:
Enter ASR elevation:

MENU: Analysis -> Radio Communications Links -> RCL Conflict Test
Description: Calculate and Report on Object Conflicts with RCL Surfaces.
conflicts or penetrations of RCL surfaces placed with the Create Pt to Pt RCL Surfaces. A report in
the form of an ASCII file is created for the user. The report includes the identification reference
number of the conflict object, the X, Y, Z coordinates of the penetration and the layer name of the
surface penetrated. The process for using this command is as follows. Select the item as shown above
on the pull-down menu. The following prompt will appear:
Select [ RCL ] Conflict Surfaces:
Select [ RCL ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.rct ] and [ \3daap\projects\jfk\jfk.rcd] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.rct ] and [ \3daap\projects\jfk\jfk.rcd] deleted.
.RCT filename extension represents the RCL ASCII text file report that is generated if conflicts are
found. The .RCD filename extension represents the RCL ASCII comma delimited format file that

MENU: Analysis -> Weather Surveillance Radar -> Insert Flat Surface
Description: WSR 0.0 Degree Surface Insertion
This command inserts a single set of FAA defined Weather Surveillance Radar 0.0 degree surfaces
that are used in the completion of the analysis tests. When the command is selected the user is asked
into the drawing.

MENU: Analysis -> Weather Surveillance Radar -> Insert 0.25 Degree Surface
Description: WSR 0.25 Degree Surface Insertion
This command inserts a single set of FAA defined Weather Surveillance Radar 0.25 degree surfaces
that are used in the completion of the analysis tests. When the command is selected the user is asked
into the drawing.

MENU: Analysis -> Weather Surveillance Radar -> WSR Conflict Test
Description: Calculate and Report on Object Conflicts with WSR Surfaces.
conflicts or penetrations of WSR surfaces. A report in the form of an ASCII file is created for the
prompt will appear:
Select [ WSR ] Conflict Surfaces:
Select [ WSR ] Obstruction Objects:
the following:
Conflicts found!
[ \3daap\projects\jfk\jfk.wst ] and [ \3daap\projects\jfk\jfk.wsd] created.
No conflicts found!
[ \3daap\projects\jfk\jfk.wst ] and [ \3daap\projects\jfk\jfk.wsd] deleted.
.WST filename extension represents the WSR ASCII text file report that is generated if conflicts are
found. The .WSD filename extension represents the WSR ASCII comma delimited format file that

MENU: Analysis -> Weather Surveillance Radar -> WSR Width Test
Description: Tests for WSR Width Criteria.
Select WSR Location:
Select the location of the WSR. The following prompt will appear:



Three-Dimensional Airspace Analysis Programs (3DAAP) : User Manual: Program Installation and Menu Commands

Uploaded by

Copyright:

Available Formats

Three-Dimensional Airspace Analysis Programs (3DAAP) : User Manual: Program Installation and Menu Commands

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Three-Dimensional Airspace Analysis Programs (3DAAP) : User Manual: Program Installation and Menu Commands

Uploaded by

Copyright:

Available Formats

Three-Dimensional Airspace Analysis Programs

Prepared under a grant from the State of Florida Department

Menu Item Selections:

3DAAP PROCESS IMPLEMENTATION --i

--ii 3DAAP PROCES S IMPLEMENTATION

Install program from website in the C Drive.

Then insert the "Airspace" and "Analysis" menus at the top.

3DAAP OPERATIONAL PREFACE

3DAAP PROCESS IMPLEMENTATION --iii

--iv 3DAAP PROCES S IMPLEMENTATION

MENU: AirSpace -> RW Data Files -> Runway Data

3DAAP IMPLEMENTATION PROCESS --1

Enter the airport title and

--2 3DAAP PROCESS IMPLEMENTATION

3DAAP IMPLEMENTATION PROCESS --3

Distance from start Point: Elevation:

Distance from start point: Elevation:

--4 3DAAP PROCESS IMPLEMENTATION

Approach Slope Dimension Table

3DAAP IMPLEMENTATION PROCESS --5

--6 3DAAP PROCESS IMPLEMENTATION

3DAAP IMPLEMENTATION PROCESS --7

LAYER NAME DESCRIPTION

--8 3DAAP PROCESS IMPLEMENTATION

3DAAP IMPLEMENTATION PROCESS --9

--10 3DAAP PROCESS IMPLEMENTATION

Select Obstruction Surfaces: (Window or Crossing)

Select Eye View Icon/<Place Icon>:

Select Eye Point:

Enter Eye Point Elevation:

Enter Ground Elevation for Shadow:

3DAAP IMPLEMENTATION PROCESS --11

Select Obstruction Surfaces: (Window or Crossing)

Select Eye View Icon/<Place Icon>:

Enter Ground Elevation for Shadow:

--12 3DAAP PROCESS IMPLEMENTATION

Select Eye Point:

Enter Eye Point Elevation/<0.00>:

Select First Vector Point:

Select Next Vector Point/<Exit>:

Select the next point. The following prompt will appear:

3DAAP IMPLEMENTATION PROCESS --13

Select LOS Surface Start Point:

Select LOS Surface End Point:

NONE .......... No Description will be attached to entity.

--14 3DAAP PROCESS IMPLEMENTATION

ILS ..... .......... ........... Instrument Landing Systems

Enter Surface Width/<1.0>:

Select Next LOS Surface End Point:

3DAAP IMPLEMENTATION PROCESS --15

Select RCL Surface Start Point:

Select RCL Surface End Point:

--16 3DAAP PROCESS IMPLEMENTATION

Select Obstruction Point:

Enter Base Elevation/<0.00>:

Select Next Obstruction Point/<Exit>:

This process will repeat until you hit <Enter> to exit.

3DAAP IMPLEMENTATION PROCESS --17