Los Angeles ARTCC on VATSIM - Standard Operating Procedures and Letters of Agreement

Sector File Certification

POC: Facility Advisory Board	Date: 2003-05-12
Code: ZLA	Version: 1.01

3. DISTRIBUTION.

This SOP is intended for use by individuals developing sector files intended for use within ZLA.

4. BACKGROUND.

Certification of sector files in ZLA occurs under the specifications set forth in this document. Sector files authors intending to develop sector files for use within ZLA should pay special attention to the requirements set forth in this SOP. Sector file developers should apply these standards to their sector files before submitting them for certification and publication. Further, any sector file submitted to ZLA for review before certification MUST meet these guidelines before certification will be possible.

General Requirements

Sector files submitted for certification within ZLA must meet the following general requirements.

Sector file structure must maintain 100% compliance with the original Pro Controller sector file specification. In addition, sector files should conform to the extended features in ASRC.

Consistency of information and assurance of the use of current information:.

Careful attention should be used in applying updates to sector file information. Sector file creators must ensure that information contained in any sector file intended for use within ZLA is based on the most current and accurate information available from approved resources as defined in this document.

Sector file developers should be aware that much of the data which exists in the simulated environment, especially the environment of an un-patched MSFS2002 client, is some what inconsistent with real world navigational information. As such, some consideration must be given to the fact that there are people in our simulated environment who will be relying on this inaccurate or out dated information as compared to that information which is available from the latest charts and resources. Sector file authors should apply this knowledge by making some reasonable effort to divulge information where such inconsistencies exist by including representative information and notes pertaining to such inconsistencies, as necessary, within the sector file itself. In this way sector file users will be aware of such inconsistencies and therefore have the best chance possible of being well prepared to handle aircraft operations efficiently in all circumstances.

The following is the list of approved resources for obtaining information for use in sector files.

National Imagery and Mapping Agency (NIMA) Digital Aeronautical Flight Information File (DAFIF). The DAFIF can be found at: https://164.214.2.110/products/digitalaero/index.cfm.

National Oceanic and Atmospheric Administration (NOAA) Coastline information files. The NOAA can be found at: http://seaserver.nos.noaa.gov/projects/shoreline/shoreline.html.
NOAA Coastline data is downloaded from the main NOAA Coastline Extractor site at: http://rimmer.ngdc.noaa.gov/coast/getcoast.html

For the purposes of aiding in end user readability, sources known to be derived from the DAFIF information, such as those published for the current AIRAC cycle, may also be used.

ASCII or plain text shall be the markup languages used for all sector files. No other markup languages (I.E. MS Word document or HTML) may be used for sector files.

Sector Files intended for use in ZLA shall be distributed for free and unrestricted public use. Sector Files shall not be copyrighted, licensed, privately held or intended only for private use. Further, information which is copyrighted, privately owned or not intended for free and unrestricted public use, redistribution, dissemination or modification shall not be included in any sector file intended for use in ZLA. No copyright information or statement which implies ownership, license rights or restrictions on usage, or the like, shall be included in any sector file intended for use in ZLA.

Comments included at the top of the file shall be limited to no more that 15 lines of information. Text included in this area shall be limited to the following information:

Sector file name and the ARTCC, TRACON or facility name it was developed for.

Name of development software used in creation of the file, if any.

Date and time of creation and/or version number. I.E. 1.0 23:10:14 19-Mar-03

Name (s) of the individual (s) who have built or contributed to the file.

Any special instructions as necessary such as "Do not manually edit the comment lines in this file!"

In addition to following the PRO CONTROLLER and ASRC specifications for formatting, the INFO section shall meet the following content requirements:

First Line - NAME - This shall be the name of the sector file following these specifications -

For example:

The ARTCC NAME might be "ZLA"

The FACILITY NAME might be "Los Angeles Tower"

The VERSION might be "1.0"

The DATE will be in the format: dd/mm/yyyy

The result might be:

ZLA/Los Angeles Tower 1.0 01/01/2003

Second Line - Default Call sign - This shall be the default call sign as used by a controller when logging into a control position as appropriate for the facility type being depicted in the sector file. For example: LAX_TWR would be the default call sign for the LAX_TWR sector file. One exception to this requirement should be noted. For Center or ARTCC level sector files, the observer call sign of LAX_OBS should be used as the default call sign within the sector file.

Third Line - Default Weather Station - This shall be the ICAO of the largest major airport in the area -OR- the ICAO of the facility itself for facility level sector files; if the facility supports AWOS.

Center of screen latitude - this shall be the latitude of an identifiable feature geographically located at the point mostly closely identifiable as the center of the area or facility which the file represents. For very large areas the largest major airport or facility in that area should be used.

Center of screen longitude - this shall be the longitude of an identifiable feature geographically located at the point mostly closely identifiable as the center of the area or facility which the file represents. For very large areas the largest major airport or facility in that area should be used.

Number of NM between 1 deg of latitude. - For ZLA this number shall be equal to sixty (60).

Number of NM between 1 deg of longitude. - For ZLA this number shall be equal to fifty one (51).

Magnetic Variation - For ZLA this number shall be equal to negative thirteen point seven five (-13.75).

Scaling Factor (Optional) - This number shall be one (1).

Comments shall be associated with all entries in a sector file. Each element of the file shall have a descriptive comment associated with it. It may not be practical to have an individual comment for each line entry of a given element (I.E. GEO INFO, SIDS or STARS) For these areas it will be acceptable for a single comment to proceed a group of entries in a referenced section, and for that comment to be used as the descriptor for that section of entries. Realize though that it is the purpose of this requirement that each entry or section of entries should be well defined and described so that there is no mystery as to the purpose of an entry or group of entries within a sector file. One example of proper commenting is:

[AIRPORT]

KLAX 120.950 N033.56.33.146 W118.24.29.073 B ;- Los Angeles International

When including fixes for use as ground labels, taxiway markers, or feature identifiers care should be taken to ensure that the labels are no more than four digits in length. Also, labels used for such purposes should not duplicate any fix or airport name.

Facility Specific Requirements

In addition to the general requirements, sector files must also meet one or more of the following facility specific requirements depending on the area or facility the file represents.

CENTER or ARTCC LEVEL SECTOR FILE REQUIREMENTS:

Required content

The following elements shall be represented, in any Center or ARTCC level sector file intended for use within ZLA.

AIRPORTS - ALL all class B, C, D, E, and select G airports within ZLA. Center or ARTCC level files should also include select facilities within 300 miles of ZLA airspace including all class Bravo and Charlie facilities as well as other select facilities.

RUNWAYS class Bravo, Charlie and select Class Delta Facilities underlying Class Bravo and Charlie airspace.

VOR - In addition to the VOR's this section shall also include the NDB's because the NDB section is used for MVA's.

NDB - This section shall include MVA's as well as class Bravo and Charlie airspace floor and ceiling information. Each of these shall be segregated into their own "area" within the file by using comments to indicate the section for each MVA or class of airspace.

For example: ;SBA MVA's

;LAS CLASS B Airspace floors/ceilings

MVA's shall be denoted using the following format:

The MVA shall be used in what would normally be the name field position of the NDB record.

The capital letter M shall be used in place of the frequency in what would normally be the frequency field in the NDB record.

The Latitudinal coordinates where the MVA indicator should appear.

The Longitudinal coordinates where the MVA indicator should appear.

An example of this is:

25 M N033.52.00.000 W117.55.00.000

Charlie and Bravo airspace floors and ceilings shall be denoted using the following format:

A period shall be used in place of the name of the NDB.

The airspace qualifier followed by the airspace floor, a period and then the airspace ceiling shall be used in place of the frequency in what would normally be the frequency field.

The Latitudinal coordinates where the airspace indicator should appear.

The Longitudinal coordinates where the airspace indicator should appear.

An example of this is:

. B70.100 N034.04.58.707 W118.54.12.573

FIXES - This area should include all fixes within the boundaries of the ARTCC air space, as well as those fixes outside of the ARTCC but within 300 miles of the ARTCC boundaries. FIXES are an integral part of the ASRC routing function and, as such, there is a necessity for as much accurate fix information as practical to be present in the sector file.

STAR - This section shall include Standard Arrivals as well as information pertaining to the graphical representation of other airspace specific features including but not limited to:

Arrival Gates

Airspace boundaries

Special attention should be paid to the requirements for applying the use of colors for elements in this area of the sector file as detailed in part two of this section "Use of Colors for Center level or ARTCC sector files".

SID - This section shall include Standard Departures as well as information pertaining to the graphical representation of other airspace specific features including but not limited to:

Departure Gates

Airspace Boundaries

MOA's

Special attention should be paid to the requirements for applying the use of colors for elements in this area of the sector file as detailed in part two of this section "Use of Colors for Center level or ARTCC sector files".

LOW AIRWAY - This section shall include low airways (Victor Airways) within the ARTCC. Airways which do not exist solely within ZLA airspace should be included if they begin, end or traverse any portion of ZLA airspace. The portion of any airway which exists outside of ZLA airspace may be included as necessary in order to properly display the features of that airway which are necessary in order to represent the airway within ZLA airspace. In any case no airway should be represented beyond 100 miles of the boundary of the ARTCC. Each entry shall represent a single leg of an airway. Where appropriate an entry may represent a single leg of two or more merged airways. The naming convention for these airways shall be.

Where the segment represents a single airway and a single MEA, use the name of the airway and then in brackets the altitude for the MEA.

For Example: V8[30]

Where the segment represents a two or more airways and a single MEA, use the name of the airway a dash the number of the merged airway and then in brackets the altitude for the MEA.

For Example: V8-21[30]

Where the segment represents two or more airways and two MEA's, use the name of the airway a dash the number of the first merged airway a dash the number of the next merged airway, etc., until all of the merged airways are represented. Then in brackets the altitude and direction of the first MEA a dash and the altitude and direction of the second MEA.

For Example: V16-370-372[120W-80E]

HIGH AIRWAY - This section shall include all high jet airways within the ARTCC. Jet airways which do not exist solely within ZLA airspace should be included if they begin, end or traverse any portion of ZLA airspace. The portion of any jet airways which exists outside of ZLA airspace may be included as necessary in order to properly display the features of that jet airway which are necessary in order to represent the jet airway within ZLA airspace. In any case no jet airway should be represented beyond 100 miles of the boundary of the ARTCC. Each entry shall represent a single leg of a jet airway. Where appropriate an entry may represent a single leg of two or more merged jet airways. The naming convention for these jet airways shall be.

Where the segment represents a single jet airway, use the name of the jet airway alone.

For Example: J1

Where the segment represents a two or more jet airways, use the name of the first jet airway, a dash, the number of the first merged jet airway, a dash, the number of the next merged jet airway, etc., until all of the merged jet airways are represented.

For Example: J4-10-64-93-104-127-123

ARTCC - These entries represent each of the individual TRACON boundaries in the ZLA sector. The boundaries of each area shall be represented. The areas which shall be represented include, but are not limited to:

Bakersfield Approach BFL_APP

Burbank Approach BUR_APP

Las Vegas Approach LAS_APP

Los Angeles Approach - LAX_APP

Los Angeles Feeder Approach - LAX_F_APP

NTD_APP

Ontario Approach - ONT_APP

Palm Springs Approach - PSP_APP

San Diego Approach - SAN_APP

Santa Barbara Approach - SBA_APP

Santa Ana Approach - SNA_APP

Yuma Approach - YUM_APP

Edwards Approach - EDW_APP

ARTCC Low - This section shall be used to represent the MVA boundaries. Each entry shall represent an individual line segment for an MVA boundary. Each entry shall be named according to the MVA which is represents according to the following naming convention:

The name shall include the three letter identifier for the area that the MVA is in, an underscore and the word MVA.

An example of this is: L35_MVA

ARTCC High - This section shall be used to represent the CENTER boundaries. Each entry shall represent an individual line segment for a CENTER boundary. Each entry shall be named according to the following naming convention:

The name shall include the three letter identifier for the center or ARTCC area, an underscore and the three letter acronym CTR.

An example of this is: LAX_CTR.

GEO -

The geo section represents to following information:

Coastline data extending from just South East of the ARTCC. boundary to just North West of the ARTCC boundary.

Warning Areas and Restricted airspace boundaries.

Representations of key lakes and large bodies of water.

Representations of islands off of the coast and within the ZLA. ARTCC boundaries, within 75 miles of the shoreline.

The FAX_BEAVER APPROACH boundaries.

Class B and C facility Taxiway and Terminal Maps.

The following per-element color application standards shall be complied with for entries in this section. Colors shall be defined as detailed in section 2 "Use of Colors for Center level or ARTCC sector files".

Coastline data and island representations - COAST-C

Lakes and inland bodies of water - LAKE-C

Warning areas and restricted airspace boundaries - WARN-C

Test ranges - WARN-C

Neighboring sector boundaries - CTR-C1

Outer boundaries - CTR-C1

Representations of class B airspace - BRVO-C

Representations of class C airspace - CHRLI-C

Taxiways, parking areas, aircraft movement areas - TWAY-C

Runways - RWAY-C

Helipads - RWAY-C

Extended Runway Centerlines - CTRLN-C

Displaced thresholds and Position and hold points - HOLD-C

Hold short points - HOLD-C

Terminals, buildings, hangars and other structures - BUILD-C

Fuel - FUEL-C

Use of Colors for Center level or ARTCC sector files

The following colors shall be defined in all Center level or ARTCC sector files using a #define entry at the top of the file.

#define AGATE-C 16711680
#define AQUA 16776960
#define BLACK 0
#define BLUE 16711680
#define BRVO-C 8388608
#define BUILD-C 106
#define CTR-C1 55552
#define CTR-C2 38144
#define CHRLI-C 4194432
#define COAST-C 16384
#define DGATE-C 16711935
#define FIXES-C 44444
#define FUCHSIA 16711935
#define FUEL-C 32896
#define GRAY 8421504
#define GREEN 32768
#define HOLD-C 32896
#define LAKE-C 4210688
#define LIME 65280 #define MAROON 128
#define MOA-C 5865472
#define OLIVE 32896
#define PURPLE 8388736
#define RADAR-C 44444
#define RED 128
#define RWAY-C 5592405
#define SILVER 12632256
#define TEAL 8421376
#define TRACON-C 32896
#define TWAY-C 4210688
#define WARN-C 3757312
#define WHITE 16777215
#define CTRLN-C 21845
#define YELLOW 65535
#define ZLAHI-C 4144959
#define ZLALO-C 5592405
#define RESTR-C 128

For Airspace boundaries defined in the SIDS/STARS section it is possible to apply color selections. For this reason the following per-element color application standards shall be complied with for airspace defined in these sections:

CLASS B AIRSPACE Boundaries- BRVO-C

CLASS C AIRSPACE Boundaries- CHRLI-C

APPROACH/DEPARTURE Airspace Boundaries - TRACON-C

Restricted / Military Airspace Boundaries - RESTR-C

Arrival gate Boundaries - AGATE-C

Departure gate Boundaries - DGATE-C

Center Airspace Boundaries - CTR-C2

HIGH ARTCC Airspace Boundaries - ZLAHI-C

LOW ARTCC Airspace Boundaries - ZLALO-C

TRACON (APPROACH/DEPARTURE) LEVEL SECTOR FILE REQUIREMENTS:

Required content

The following elements shall be represented, in any TRACON level sector file intended for use within ZLA.

AIRPORT - ALL all class B, C, D, E, and select G airports within the TRACON as well as facilities within 60 miles of the TRACON boundaries.

RUNWAY - Include runways for all class B, C and Military facilities within the APP/DEP control area.

VOR - In addition to the VOR's this section shall also include the NDB's because the NDB section is used for MVA's.

NDB - This section shall include MVA's as well as class Bravo and Charlie airspace floor and ceiling information. Each of these shall be segregated into their own "area" within the file by using comments to indicate the section for each MVA or class of airspace.

For example: ;SBA MVA's

;LAS CLASS B Airspace floors/ceilings

MVA's shall be denoted using the following format:

The MVA shall be used in what would normally be the name field position of the NDB record.

The capital letter M shall be used in place of the frequency in what would normally be the frequency field in the NDB record.

The Latitudinal coordinates where the MVA indicator should appear.

The Longitudinal coordinates where the MVA indicator should appear.

An example of this is:

25 M N033.52.00.000 W117.55.00.000

Charlie and Bravo airspace floors and ceilings shall be denoted using the following format:

A period shall be used in place of the name of the NDB.

The airspace qualifier followed by the airspace floor, a period and then the airspace ceiling shall be used in place of the frequency in what would normally be the frequency field.

The Latitudinal coordinates where the airspace indicator should appear.

The Longitudinal coordinates where the airspace indicator should appear.

An example of this is:

. B70.100 N034.04.58.707 W118.54.12.573

FIXES - This area should include all fixes within the boundaries of the TRACON air space, as well as those fixes outside of the TRACON but within 60 miles of the TRACON boundaries. FIXES are an integral part of the ASRC routing function and, as such, there is a necessity for as much accurate fix information as practical to be present in the sector file.

STAR - This section shall include Standard Arrivals as well as information pertaining to the graphical representation of other airspace specific features including but not limited to:

Arrival Gates

Airspace boundaries

Special attention should be paid to the requirements for applying the use of colors for elements in this area of the sector file as detailed in part two of this section "Use of Colors for Center level or ARTCC sector files".

SID - This section shall include Standard Departures as well as information pertaining to the graphical representation of other airspace specific features including but not limited to:

Departure Gates

Airspace Boundaries

MOA's

Special attention should be paid to the requirements for applying the use of colors for elements in this area of the sector file as detailed in part two of this section "Use of Colors for Center level or ARTCC sector files".

LOW AIRWAY - This section shall include low airways (Victor Airways) within the TRACON and within a fifteen mile radius of the TRACON. The portion of any airway which exists outside of TRACON airspace may be included as necessary in order to properly display the features of that airway which are necessary in order to represent the airway within the TRACON airspace. In any case no airway should be represented beyond 15 miles of the boundary of the TRACON. Each entry shall represent a single leg of an airway. Where appropriate an entry may represent a single leg of two or more merged airways. The naming convention for these airways shall be.

Where the segment represents a single airway and a single MEA, use the name of the airway and then in brackets the altitude for the MEA.

For Example: V8[30]

Where the segment represents a two or more airways and a single MEA, use the name of the airway a dash the number of the merged airway and then in brackets the altitude for the MEA.

For Example: V8-21[30]

Where the segment represents two or more airways and two MEA's, use the name of the airway a dash the number of the first merged airway a dash the number of the next merged airway, etc., until all of the merged airways are represented. Then in brackets the altitude and direction of the first MEA a dash and the altitude and direction of the second MEA.

For Example: V16-370-372[120W-80E]

HIGH AIRWAY - This section shall include all high jet airways within the TRACON. Jet airways which do not exist solely within the TRACON airspace should be included if they begin, end or traverse any portion of the TRACON airspace. The portion of any jet airways which exists outside of the TRACON airspace may be included as necessary in order to properly display the features of that jet airway which are necessary in order to represent the jet airway within the TRACON airspace. In any case no jet airway should be represented beyond 15 miles of the boundary of the TRACON. Each entry shall represent a single leg of a jet airway. Where appropriate an entry may represent a single leg of two or more merged jet airways. The naming convention for these jet airways shall be.

Where the segment represents a single jet airway, use the name of the jet airway alone.

For Example: J1

Where the segment represents a two or more jet airways, use the name of the first jet airway, a dash, the number of the first merged jet airway, a dash, the number of the next merged jet airway, etc., until all of the merged jet airways are represented.

For Example: J4-10-64-93-104-127-123

ARTCC - These entries represent the TRACON boundaries. These entries shall not be used to represent airspace classifications or class B and C airspace boundaries within the TRACON. Areas that may be represented in this section, other than the TRACON boundaries, include as necessary:

Restricted airspace boundaries

Test Range airspace boundaries

ARTCC Low - This section shall be used to represent the MVA boundaries. Each entry shall represent an individual line segment for an MVA boundary. Each entry shall be named according to the MVA which is represents according to the following naming convention:

The name shall include the three letter identifier for the area that the MVA is in, an underscore and the word MVA.

An example of this is: L35_MVA

ARTCC High - This section shall be used to represent CENTER boundaries immediately above or adjacent to the TRACON. Center boundaries to which the TRACON does not hand off to nor receive handoffs from need not be represented. Each entry shall represent an individual line segment for a CENTER boundary. Each entry shall be named according to the following naming convention:

The name shall include the three letter identifier for the center or ARTCC area, an underscore and the three letter acronym CTR.

An example of this is: LAX_CTR.

GEO -

The geo section represents to following information:

Coastline data within the boundaries of the TRACON.

Warning Areas and Restricted airspace boundaries.

Representations of key lakes and large bodies of water within the TRACON boundaries.

Representations of islands off of the coast and within the TRACON boundaries or within 60 miles of the TRACON boundary.

Class B and C facility Taxiway and Terminal Maps for all class B and C facilities within the TRACON.

The following per-element color application standards shall be complied with for entries in this section. Colors shall be defined as detailed in section 2 "Use of Colors for TRACON (Approach and Departure) level sector files."

Coastline data and island representations - COAST-C

Lakes and inland bodies of water - LAKE-C

Warning areas and restricted airspace boundaries - WARN-C

1. PURPOSE.

2. ROLES AND RESPONSIBILITIES.

3. DISTRIBUTION.

4. BACKGROUND.

General Requirements

Facility Specific Requirements

CENTER or ARTCC LEVEL SECTOR FILE REQUIREMENTS:

TRACON (APPROACH/DEPARTURE) LEVEL SECTOR FILE REQUIREMENTS: