|
Clarification on purpose of the Feature status REMOVE The Remove feature status should be assigned to features if Field Operations personnel want to recommend that a feature on the field plot sheet (that still exists) be removed and not included on the revised AOC. This is similar to underlining a feature on the field plot sheet in green ink. Field Operations should not assign the feature status Disabled Full to features of this type.Why this clarification? Compilers routinely assign the Disabled Full feature status to active features that are deemed not necessary for the chart (due to clutter, etc.). The Disabled Full feature status is reserved for Applications Branch personnel and is assigned when it is determined that the feature WILL NOT be included on the chart. QC personnel review these features. If Field operations assigns the Disabled feature status to selected features the QC person cannot discern whether the decision to exclude a feature from consideration was made by the field personnel or the compiler (without an Obstruction Comparison Report). Note: Field Operations Personnel are required to assign the feature status Disabled for AOC only and Disabled for ANA only when necessary. |
|
Policy Statement for Airport Elevation FAA Procedure Development personnel (AVN) are having problems with elevation data (ANA only airports-not Part 77 airports) collected at airports that have non-specially prepared runways (non-SPHS) having a higher elevation than the specially prepared (SPHS) runway(s). The policy at this time is that only SPHS runways are surveyed at ANA only airports. The problem with this way of conducting business is that the procedure specialist needs the airport high point of all useable runways to create a procedure to that airport, including non-SPHS runways. We are changing the policy for ANA airports as of June 18, 1999. ANA only surveys: If the Airport Elevation (highest elevation on usable runways) is on a non-SPHS runway, the non-SPHS will be surveyed and the Airport Elevation location determined.
The policy for surveying SPHS and non-SPHS runways for compilation of an Airport Obstruction Chart has not changed. |
Subject: Required Runway/Stopway data on NON-SPHS runways
Henceforth, when an obstruction survey is performed on a runway with
a non-SPHS, the required Runway/Stopway data will be the same as for a
SPHS runway. The required data is listed in Table 2.1 (p 2.2) of the
FAA 405 (4th Ed.) under the heading SPHS RWY.
The NGS deliverable (uddf) will be modified to correctly report the
appropriate information when the above mentioned condition exists.
If
Runway Type set to Unpaved
&
Class "OIS" (Primary) is not NULL ** anything but NULL **
Then
generate uddf reflecting above policy (as if SPHS runway)
Requirements Branch will note this policy in the Project Instructions
when the condition exist.
Example: Clovis Municipal Airport (CVN oc5144).
The 4th Edition FAA 405 does not clearly address the condition
mentioned above. The 3rd Edition FAA 405 was much more specific (see
section 2.2.1.1). Future ammendment/revisions to the FAA 405 should
clarify the required Runway/Stopway data when an obstruction survey is
performed on an non-SPHS runway.
|
Subject: Convention for reporting Runway Widths
11.11 SURVEY WORK - GENERAL
D. WIDTHS -
Measure runway widths with a tape measure to the nearest foot (0.1 ft) and
submit the actual dimension measured on the runway end sketch. For loading
the width in the Exchange File format, use the following rounding convention:
if the runway width is under 100 feet, round to the nearest 5 feet.
If the runway width is over 100 feet, round the width to the nearest
10 feet. If the rounded width is different from the published width, contact
NGS for further advice.
|