                              ===================
                                 S U M M A R Y
                              ===================

    This file contains information on the use of Simon Hradecky's utilities 
   (SCENEDIT, ATPUTIL, et al) to insert the new Denver International Airport 
                       facilities into ATP scenery files. 

            =======================================================
            A S S U M P T I O N S    A N D    C O N V E N T I O N S
            =======================================================

1. ATP program files are in C:\ATP directory.
2. USA scenery files are in C:\ATP\IPS subdirectory.
3. Default ATP scenery files (F1 and F1.sp?) are in C:\ATP.
4. You have SCENEDIT, preferably v. 3.03 or higher.
5. SCENERY.DAT is in C:\ATP and you have changed it to specify the location of
   your ATP scenery files -- ATP Default, USA East/West, GB, whatever.
6. You've received your USA West scenery update.
7. You've copied the scenery files you're going to modify to another location 
   and/or directory -- just in case Murphy finds out what you're trying to do 
   and wants to help.
8. Configuration of new runways and navaids is contained in file DENDIA.TXT.

We're going to: 

   - Install a runway (17R-35L) .
   - Install runway lights and markings for 17R and 35L.
   - Install IAQD ILS on 35L.
   - Install marker beacons for IAQD ILS.
   - Install new VORs.

To clarify the relationship between the old and new airports, the old, current
airport is Stapleton.  The new airport, 12 nm ENE of Stapleton, is Denver 
International Airport.  The local media use the acronym DIA in references to 
Denver International.  DIA isn't recognized by FAA, but it speeds the written 
and spoken word a bit.  So, the old airport is Stapleton, the new one is DIA.
Current estimated operational date is early March.  A more realistic date is
probably late, late March or early to mid April.

   ==========================================================================
   I N S T A L L I N G    R U N W A Y S ,    L I G H T S ,    M A R K I N G S
   ==========================================================================

Here goes:

   - From C:\ATP prompt, type SCENEDIT, press <Enter>.  ATP Scenery Editor 
     window appears. Menu options are: "Info, NavAids, Elevation, and Runways".
   - Click left on "Info".  Drop down window opens.
   - Click left on "Scenery", select the scenery to be modified.  
   - Press <Enter>.
   - Click left on "Runways".
   - Click left on "Create Runway".  Runway entry window opens.  Pointer is 
     in "Position North" entry position.
   - Press <F3> to edit entry.
   - Press "+" on the num key pad.  "Lat/Lon Coordinates" window opens.
   - Refer to runway elements for 17R-35L in DENDIA.TXT.  Enter following 
     coordinate data from DENDIA.TXT:

       Latitude:   39   50   30.     (30" is 0.5 * 60")
       Longitude: 104   39   18.  W  (18" is 0.3 * 60")

       CAUTION:  Be sure to type a "." (period) after the 30" and the 18" 
       above.  Otherwise, you will be entering 3.0" and 1.8".

   - Press <Enter> to return to "Runway" entry form.
   - Cells "North" and "East" now contain Lat/Lon coordinates converted to ATP 
     North/East coordinates.
   - Click left on "Runway Direction" highlight.
   - Type "170.<Enter>".  You've entered the magnetic direction of 17R.
   - Type "17<Enter>".
   - Type "R<Enter>".  Pointer moves to "Runway Length" highlight.
   - Type "12000<Enter>".
   - Type "150<Enter>" (Dimension).
   - Type "0<Enter>".
   - Type "0<Enter>".

Careful.  Don't press <Enter> until instructed to do so or you may drop out 
of the "Edit" mode and return to the "Runway" entry form; previous entries 
will be lost. You won't break anything; you'll just lose your previous entries.

Not all of the runway, VASI, approach lights, and runway markers actually 
installed at the airport are available for ATP scenery files.  There are enough,
however, to come pretty close.  The lines from "Runway Lights:" through the 
row following "Opp.Dir" contain a series of switches for the several types 
of visual aids.  Double-click on the "Runway Lights:" highlight, then "VASI:"
highlight, etc. to view options available.  Toggle the switches on and off by 
clicking left.

As contained in DENDIA.TXT, the visual aids actually installed on this runway 
are:

    Rwy             Visual Aids
--------------------------------------------
    17R    HIRL   CL   MALSR    TDZ   PAPI-L
    35L    HIRL   CL   ALSF-II  TDZ   PAPI-L

Turn on the following switches for a close approximation:

     Runway Lights: Sidelines       center TD-Zone
     Opp. dir:      Sidelines       center TD-Zone
     VASI: VASI 16         Opp.Dir: VASI 16
     App. Lights: MALSF    Opp.Dir:        ALSF-2

     Markers: Threshold TD-zone fixed-dist TDZ-end
                             Sidelines light-grey
     Opp.Dir: Threshold TD-zone fixed-dist TDZ-end
              
If you prefer another combination of lights and markings, go for it.  What 
FAA doesn't know won't hurt 'em.

OK, after you've entered the coordinates and sizes, turned on the approach
lights and runway markings, the "Runway" entry form should look like this.

          ---------------------------------------------
                             Runway
          ---------------------------------------------
          Position North: 16724.8078   East: 11015.3296
          Runway Direction:   170.00   Identifier: 17R

          Runway Length (ft):  12000   Dimension:  150
          Length Holding:    0   Hold. opp. Dir.:    0

          Runway Lights: Sidelines       center TD-zone
          Opp. dir.:     Sidelines       center TD-zone
          VASI: VASI 16         Opp.Dir: VASI 16
          App. Lights: MALSF    Opp.Dir:        ALSF-2

          Markers: Threshold TD-zone fixed-dist TDZ-end
                                  Sidelines light-grey
          Opp.Dir: Threshold TD-zone fixed-dist TDZ-end
          ---------------------------------------------

You're now ready to save the runway data to the scenery files.  First, however,
PrintScreen the form.  You may need it to find the runway when you return to
ATP.  To save, press <Enter><Enter>.  HD light comes on, you're back in the 
original Scenery Editor menu window, the new runway data has been placed in the 
scenery files, and you've built a runway -- a 12,000' concrete runway.  Right, 
it would be a good idea to check and see if data entered is actually in the 
scenery files.

   - To verify the changes, click left on "Runways".
   - Click left on "Edit Runway".
   - In "North" highlight, enter "16725".
   - In "East" highlight, enter "11015".
   - In "Runway ID:" highlight, enter "17", then "R".
   - Press <Enter> again.
   - The data you entered is displayed for edit.

The runway is no longer 12,000' long.  ATP has shortened it by two feet, added 
it to the width.  It's now 11998' long, 152' wide.  OK, sobeit.  If you 
change anything, resave by pressing <Enter><Enter>.  

It wouldn't hurt to take a look in ATP, see if the runway is really there.  
Press <Esc> then "Y<Enter>" to exit the Scenery Editor.  

Start ATP, press "<F7> 1", select the scenery you're editing (West or ATP 
default).  Press "<F7> 3", and enter the N/E coordinates from the SCENEDIT 
PrintScreen you made of the runway elements:

     N 16724.8078       E 11015.3296  

Press <Esc><Esc> to return to 3D window.  Now, enter helicopter mode.  SL 
calls it "Slew Mode".  It's "<Alt>S" in either case.  Find the runway and check
it out.  Left, right, up, down arrows do pretty much what you think they should 
do.  "Q" goes up.  "A" comes down.  Check your documentation for the other 
movement keys.  Use "Dusk" and "Night" from "<F3> 2" menu to see if you're 
satisfied with the lights and runway markings.  If lights are OK, use "<F3> 2",
select "Day".  Return to 3D window with <Esc>.

When you have it like you want it, stay in ATP.  We have a few things to
do before going on to the next section, i.e., installing an ILS.  We need the 
N/E coordinates for location of localizer and glide slope transmitters.  

Start by activating the map window, <Shift><ScrollLock>.  Use <Shift> + or - 
(num key pad) to set map range to 100'.  Use <F9>, Status Report, to check 
range selected.  Range is in the lower right corner of the <F9> window.  Press 
<Esc> to leave the Status Report, return to 3D window.  Climb to about 5400' 
or 5500'("Q" in slew mode, "5" in number key pad to stop the climb or any other 
slew motion).  Turn till your heading is 350^ (1 and 3 in number key pad to 
turn -- 5 to stop turning).  Slew around till you're in final approach position, 
200' - 300' off the south end of the runway, aligned on the centerline 
extension.  

Now, start forward slowly, take a good look at the runway markings.  

   - At the near end of the runway, there are four parallel bars on each
     side of the runway.  They're 150' long.  They're the Threshold Marker.

   - Next comes the runway name -- 35 L with the L centered below the 35.

   - The Touchdown Zone Marker comes next.  It's the three parallel bars on
     each side of the runway.  They're 75' long.

   - 500' beyond the start of the Touchdown Zone Marker is the first Fixed
     Distance Marking.  It's the single, wide solid bar on each side of the 
     runway.  Bars are 150' long, 30' wide.  The south end of the Fixed 
     Distance Marker is (you guessed it) a fixed distance from the approach 
     end of the runway -- 1,000'.  Count on it.

OK, with that information, we can establish the location of the glide slope 
and localizer transmitters.  Think of their functions as one of projecting
planes of radio energy in two different axes.  

   - The glide slope is a plane inclined at about 3^ (some are less, some are 
     more -- seldom/never less than 2.8^ nor more than 3.2^) to the horizontal.  
     It intersects the runway at a point about 200' beyond the north end of 
     the Fixed Distance Marking.  

   - The localizer is a vertical plane aligned with the center of the runway 
     and located on the extended center line of the runway.  Transmitter is
     approximately 200' off the north end of the runway.

Descend to the runway with "A".  Position yourself at the north end of the 
Fixed Distance Marker, on the runway centerline.  Still on a heading of 350^, 
move north a distance equal to a bit more than the width of the runway.  Stop.  
Write down the N/E coordinates displayed in the upper left corner of the 
screen.  They should be close to: 

     N-16719.4600     E-11014.3200.  

This is point at which the plane of the 3^ glide slope intersects the runway.
We'll install the glide slope antenna here.  Now, in real life, there are no
glide slope antennas installed on runway centerlines near the fixed distance
marker.  They're off to the side of the runways.  If there were GS antennas on
the runway they would only last until the first aircraft landed.  And the pilot 
would be awfully, awfully mad.  Our runway, however, being a virtual runway, 
will have a virtual GS antenna installed -- it's a bit easier to position, 
isn't at all dangerous, and won't make anyone mad.

Now, continue on down the runway till you near its north end.  Slew yourself to 
the end of the runway, between the 17R Threshold Markers, still 350^ heading, 
exactly on the runway centerline.  Move forward (north) a distance equal to 
slightly more than the runway width.  Stop.  Write down the N/E coordinates.  
They should approximate:

     N-16731.9800     E-11016.6800.  

We'll put the localizer transmitter here.  It projects a vertical reference 
plane along the extended centerline of the runway, in both directions.

This is all we need for ILS positioning, but, to make it easier to come back
here the next time you enter ATP, press <F2>.  Press "7", Create Mode, enter
DENNEW.  Press "9" to save DENNEW as the startup mode the next time you open
ATP.

OK, now you can leave ATP and continue with the job of modifying the selected
scenery to provide an ILS for runway 35L.

                        ==============================
                        I N S T A L L I N G    I L S s
                        ==============================

Start SCENEDIT.  Highlight is on NavAids.  

   - Click left on "Info".
   - Click left on "Scenery".
   - Select scenery in which you will install the IAQD ILS.
   - Click left on "Navaids".
   - Arrow highlight down to "New ILS".
   - Press <Enter> to access the ILS entry form.  Refer to ILS tables in 
     DENDIA.TXT.
   - Highlight is on "Name".  Enter "IAQD".
   - Enter "108.5", the frequency.
   - Press "Y", then <Enter> for DME capability.
   - Enter "28".  This is normal range for ILSs used in ATP scenery.  Increase
     it at your peril.  Yes, it's nice to pick up an ILS at about the same 
     time you start your letdown, follow the glide slope and centerline down 
     from FL 370, but it's certain that eventually you will experience 
     interference from nearby ILSs on the same frequency.  Leave it at 28 or 30,
     save yourself some future grief.
   - Enter the localizer coordinates from your notes obtained while you were
     helicoptering around DIA.  Figures should be those you wrote down, close 
     to:

          N 16731.9800   E 11016.6800

   - Enter "350." in "Direction" cell.
   - Enter the glide slope coordinates obtained from last step in previous
     section.  Your figures, close to:
          
          N 16719.4600  E 11014.3200

   - Enter "3." in Angle cell.
   - Enter:

       ".2" for Inner Marker Distance.
       ".5" for Middle Marker Distance.
       "4.5" for Outer Marker Distance.

   - Use "Left or Right" for "Presence of ILS:" cell.  Note:  if and when you 
     install the ILS for runway 17R (IACX), this cell for IACX must be changed 
     to "Reciprocal".  Reason:  IACX and IAQD share the same frequency: 108.5.
     To avoid a backcourse ILS, in which left/right indications are reversed, 
     "Reciprocal" in this cell for IACX will provide normal left/right ILS 
     readings in the cockpit.

When you've finished entering the above, and before saving the changes, this
is what the completed form should look like:

          ----------------------------------------------------
                               ATP - ILS
          ----------------------------------------------------
          Name:  IAQD     Frequency:  108.50     DME:     Yes
                          Range:          28
          Localizer
          Position North:  16731.9800     East:   11016.6800
                   Direction:  350.00
          Glidepath
          Position North:  16719.4600     East:   11014.3200
                   Angle:      3.0000

          Inner Marker  Distance (nm):     0.2
          Middle Marker Distance (nm):     0.5
          Outer Marker  Distance (nm):     4.5
          Presence of ILS:       Left or Right
          ----------------------------------------------------

Save the data by pressing <Enter>.  Be patient.  Occasionally, it takes up to a
minute or so to save the data to scenery files.  When the HD light goes out, 
the highlight will return to your menu screen and you're ready to take a look 
at the form, see if everything came out all right.  Click left on "NavAids", 
arrow highlight to "View" or "Edit", press <Enter>, type "IAQD <Enter><Enter>" 
to access the ILS form again.

Well, it's a little different isn't it?  Marker distances especially.  Don't 
sweat it.  It's probably as close as you're going to get.  Something about 
fitting one coordinate system (Distance) to another coordinate system (ATP N/S 
grid).  Pilots aren't supposed to understand this stuff anyway.  

Press <Esc> a time or two, leave SCENEDIT.  Enter ATP.  You should be in the 
same place you left it, previous access.  Tune in 108.5, run a couple of ILSs, 
see if your installation is satisfactory.  Altitudes at OM are in the ILS table 
in DENDIA.TXT.  When you have it finished, we can install a VOR.

                        ==============================
                        I N S T A L L I N G    V O R s
                        ==============================

OK, here's the situation.  There will be three VORs at the new airport:  DEN 
(Denver), DVV (Mile High), and FQF (Falcon).  

   - USA West already has these VORs in the scenery files.  Location of DEN in
     West scenery, however, is the old airport: Stapleton.  DVV and FQF are 
     OK -- they are in the locations necessary to provide VOR support for the 
     new airport.  

   - ATP default scenery (the F1 series) has DEN at the current, Stapleton
     location, of course.  F1 does not contain DVV and FQF.

   - When you decide to move your operations from Stapleton to DIA, you have 
     two choices regarding DEN.

        1. Change the DEN coordinates in current scenery files (F1 and/or West),
           with SCENEDIT, to reflect the new location.  Save with <Enter>
           <Enter>, and you're in business.

                          OR

        2. Delete the old, current DEN, at Stapleton, by blanking out the 
           "Name" field in SCENEDIT's "ATP - VOR" edit window.  Save with 
           <Enter><Enter>.  That removes DEN from the scenery.  Then enter 
           DEN with the new elements and you're in business.  Fewer steps in
           1 than 2.

   - You do NOT repeat NOT want to set up a new DEN VOR, at DIA (using the 
     "New VOR" option in the NavAids menu), while the old one is still in the 
     scenery files at Stapleton -- unless you enjoy restoring from backup files
     (if you backed them up) or re-installing from original diskettes (if you 
     didn't).  

   - To complete the move, add DVV and FQF to the F1 files and you're set for 
     the 21st century.

Following is a description of how to enter the DVV VOR in the F1 scenery.  FQF
can be entered using the same process.  VOR coordinates are in DENDIA.TXT file.

   - Start SCENEDIT.  Highlight will be on "NavAids", opening screen.
   - Click left on "Scenery".
   - Select "ATP Standard" or name you assigned to ATP default scenery.
   - Click left on "NavAids".
   - Arrow down to "New VOR", press <Enter>.
   - Enter "DVV".
   - Enter "114.7".
   - Press "Y <Enter>".
   - Enter "132".  This is normal range for an ATP VOR used in the high 
     altitude route structure.  Highlight moves to "Position North:" cell.  
   - Press <F3> to edit entry.
   - Press "+", num key pad.  This accesses the LatLon menu.
   - Refer to table on VOR elements in DENDIA.TXT.  Enter:
    
       Latitude:    39    53    42.      (42" is .7 * 60" = 42")
       Longitude:  104    37    30.  W   (30" is .5 * 60" = 30")

       Again, be sure to type a "." after the 42 and 30.  Otherwise you'll
       be entering 4.2 and 3.0.

   - Press <Enter>.
   - Click left on "Altitude (ft):".
   - Since this VOR's name is Mile High, try "5280" as the "Altitude (ft)".
     Close enough.
   - Enter "20.5" as North Deviation.  It should work for all the VORs at DIA.

Before saving the data, see if it agrees with the following:

               ------------------------------------------------
                                  ATP - VOR
               ------------------------------------------------
               Name:   DVV      Frequency: 114.70   DME:    Yes
                                Range:        132

               Position North:  16745.8424    East:  11028.9796
                      Altitude (ft):  5280

               North Deviation:   20.5000
               ------------------------------------------------

   - If it's OK, press <Enter> to save.  May take a while, may not.

Stay in SCENEDIT, take a look at what the actual data on DVV looks like.

   - Click left on "NavAids".
   - Arrow down to "Edit", press <Enter>.
   - Enter "DVV".
   - Have a look.  Didn't change much.  Altitude's a little different, that's 
     about it.

Press <Esc><Esc>, then "Y <Enter>".  You've installed DVV at DIA.  Repeat for
FQF and you've installed both VORs in the ATP default scenery (F1).

      ===================================================================
      I N T E G R A T I N G    D I A    I N T O    A T P    F L I G H T S
      ===================================================================

To make DIA useable, add at least one East/West runway with ILSs in each 
direction. Also, add IACX to 17R.  Obviously, if you don't need more facilities
than that, there's no point in installing them -- except for the desire for 
realism.  So, if you want them all, fine.  If not, that's also OK.

Anyway, after you have finished DIA's runways, lights, markings, ILSs, and 
VORs to your satisfaction, you can fly in there and practice some ILSs and 
(when you obtain copies of procedures) profile descents, holding patterns, 
all that fun stuff.  

Then, there will come the time that you'd like to use DIA in CFA and FA 
flights.  For that you'll have to use ATPUTIL.  You'll need to redefine some 
*.bin files, the AIRPORT.ATP and AIRWAY.ATP files, modify some nodes and the 
hi alt airways to and from DIA.  It's enough to keep you off the streets and 
out of game arcades for a few days, at least.  Just open Simon Hradecky's 
ATPUTIL.DOC -- this assumes you have registered his v. 3.0 programs and files, 
of course.  Read all about it, set it all up.

CAUTION:  The advice given up front, about possibility of Murphy finding out
what you're working on and participating in the effort, is still good.  Put
copies of the important files* in another directory so you can recreate the ATP
environment if something goes wrong.  If something CAN go wrong, it WILL go 
wrong etc., etc., etc.  You know how that goes.

                                         JP Pool
                                         73016,1574	
                                         5 February 1994


-----------------------------------

* What's an important file?  It's ANY file that you thought was unimportant 
  and didn't safeguard when you discover that it IS important and you SHOULD 
  have safeguarded it.  
