1 / 14

Airport 20 to 1 Approach Surface

Airport 20 to 1 Approach Surface. Oklahoma Airport Operators Association, (OAOA)/ American Association of Airport Engineers, (AAAE) Annual Conference Ron Sanders Southwest Regional Flight Procedures Team March 10, 2015. 20:1 Approach Penetrations.

chumani-walker
Télécharger la présentation

Airport 20 to 1 Approach Surface

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Airport 20 to 1 Approach Surface Oklahoma Airport Operators Association, (OAOA)/ American Association of Airport Engineers, (AAAE) Annual Conference Ron Sanders Southwest Regional Flight Procedures Team March 10, 2015

  2. 20:1 Approach Penetrations • Criteria developed by Flight Standards in the late 1990s • Requires clear 20:1 Visual Approach surface for night minimums • All terminal procedures are currently reviewed every two years, as required by AFS policy. • During that periodic review, or other amendments, the TERPS Specialist in AeroNav Products may identify obstacles that penetrate the 20:1 visual surface.

  3. 20:1 Penetrations (continued) • Background: During Oct 2012, Flight Standards Division AFS-400 required immediate NOTAM action resulting in “Not Authorized (NA) at night when 20:1 identified. • Current Policy: Effective Jan 6, 2014, refined policy considered “Risk” factor of the identified penetrations and allowing a validation period (30 days). • Validation: To verify if the obstacle exists or has been removed, and/or if the obstacle is lighted.

  4. 20 to 1 Approach Surface (TERPS)

  5. 20 to 1 Penetrations Identified by : • Geographic Information System (GIS) tool - Mandatory biennial reviews / OKC ANP - During instrument procedure amdts Reported by: ∙Various offices: Regional FPT, ANP, GDOT, FC •Result in loss of night time capability • Daytime visibility restricted to 1 SM

  6. Identification of 20 to 1 Penetrations Typical scenario: • During biennial review of airport’s procedure(s) OKC development branch identifies non-validated penetrations. - - Specialist’s findings are forwarded to Flight Procedures Team (FPT), assigning each penetration with risk assessment of high, medium or low. - - FPT adds GoogleEarth overlay to the file (.kml)

  7. 20 to 1 penetrations (cont) - - Within 3-business days, file is forwarded to airport requiring sponsor to validate each penetration ASAP, but no more than 30-days / ADO copied • Airport owner/sponsor must provide a written report and copy ADO • No response received within prescribed timeframe will result in IAP visibility minima and night capability as required.

  8. Airport Owner / Sponsor Response • If 20 to 1 penetrations determined invalid - - FPT will notify applicable offices to update airport’s data file(s); no action required to restrict or modify subject IAP. • If 20 to 1 penetrations determined valid: - - Submit written compliance plan Mitigation - - Remove, light or lower - - VGSI can be used as mitigation when approved by Flight Standards

  9. Possible Mitigation Actions • Visual Glideslope Indicator (VGSI) - Apt Mgr submits Form seeking AFS approval • Apply ILS / LOC / LPV / LP Full-Scale Deflection - Calculation, conducted by Aero Nav Products when trying to mitigate 20:1 penetration vs restricting night mins • Restrict only CAT C/D approach category minimums vs restricting CAT A/B/C/D • If penetrations are outside CAT A/B area

  10. Thank you Questions?

  11. Contact Info • Ron Sanders • Central Flight Procedures Team • 817-321-7615, ron.a.sanders@faa.gov

More Related