Presentation is loading. Please wait.

Presentation is loading. Please wait.

Presented to:FAA field personnel By:AOSC Date:February 17, 2006 Presented to:FAA field personnel By:AOSC Date:February 17, 2006 Federal Aviation Administration.

Similar presentations


Presentation on theme: "Presented to:FAA field personnel By:AOSC Date:February 17, 2006 Presented to:FAA field personnel By:AOSC Date:February 17, 2006 Federal Aviation Administration."— Presentation transcript:

1 Presented to:FAA field personnel By:AOSC Date:February 17, 2006 Presented to:FAA field personnel By:AOSC Date:February 17, 2006 Federal Aviation Administration Airport Obstructions Standards Committee FAA Broadcast On Precision Obstacle Free Zone (POFZ) Implementation FAA Broadcast On Precision Obstacle Free Zone (POFZ) Implementation

2 Federal Aviation Administration 2 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 Agenda Introduction Broadcast Objectives AOSC Background Overview of POFZ POFZ Examples ARC-1 Memo to RAPTs Frequently Asked Questions Questions & Answers Introduction Broadcast Objectives AOSC Background Overview of POFZ POFZ Examples ARC-1 Memo to RAPTs Frequently Asked Questions Questions & Answers

3 Federal Aviation Administration 3 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 Broadcast Objectives Develop common understanding of POFZ requirements Provide clarifying guidance to regional teams Discuss associated implementation issues Develop common understanding of POFZ requirements Provide clarifying guidance to regional teams Discuss associated implementation issues

4 Federal Aviation Administration 4 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 AOSC Background Chartered May 2003 The AOSC works across FAA lines of business to transform outdated, inconsistent obstruction standards practices to future policy that optimally balances operational safety, effectiveness, and economic benefit Chartered May 2003 The AOSC works across FAA lines of business to transform outdated, inconsistent obstruction standards practices to future policy that optimally balances operational safety, effectiveness, and economic benefit

5 Federal Aviation Administration 5 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 AOSC Steering Group Reports to Deputy Administrator, ADA-1 AOSC Steering Group Membership –Ruth Leverenz, ARC-1 –Catherine Lang, ARP-1 –Russ Chew, ATO-1 –Nick Sabatini, AVS-1 Reports to Deputy Administrator, ADA-1 AOSC Steering Group Membership –Ruth Leverenz, ARC-1 –Catherine Lang, ARP-1 –Russ Chew, ATO-1 –Nick Sabatini, AVS-1

6 Federal Aviation Administration 6 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 AOSC Decision Documents DD01 - POFA and Runway Separation, dated 12/18/03 DD02 - 40:1 Departure Surface, dated 9/13/04 DD03 - Atlanta End-Around Taxiway (Departure Only), dated 7/12/04 DD04 - Runway / Parallel Taxiway Separation Standards, dated 03/21/05 DD05 - Airport Traffic Control Tower Interim Siting Guidance, dated 06/08/05 DD06 - Dallas / Fort Worth (DFW) End-Around Taxiway System, dated 06/08/05 www.aosc.faa.gov DD01 - POFA and Runway Separation, dated 12/18/03 DD02 - 40:1 Departure Surface, dated 9/13/04 DD03 - Atlanta End-Around Taxiway (Departure Only), dated 7/12/04 DD04 - Runway / Parallel Taxiway Separation Standards, dated 03/21/05 DD05 - Airport Traffic Control Tower Interim Siting Guidance, dated 06/08/05 DD06 - Dallas / Fort Worth (DFW) End-Around Taxiway System, dated 06/08/05 www.aosc.faa.gov

7 Federal Aviation Administration 7 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 POFZ Introduction POFZ protects the area of short final area during very low ceilings (<250’ feet) and or visibilities (<3/4 Sm or < 4000’ RVR) P O F Z Final Approach “W” Surface TERPS 34:1 area 400’ 200’ 2 4

8 Federal Aviation Administration 8 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 POFZ Applicability  The requirement to clear the POFZ applies when an aircraft on a vertically guided final approach is within 2 nautical miles of the runway threshold and the reported ceiling is below 250 feet and/or visibility less than ¾ SM (or runway visual range below 4,000 feet).

9 Federal Aviation Administration 9 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 POFZ Applicability (Cont’d)  The POFZ is considered clear even if the wing of the aircraft holding on a taxiway waiting for runway clearance penetrates the POFZ; however, neither the fuselage nor the tail may infringe on the POFZ.  If the POFZ is not clear, the MINIMUM authorized height above touchdown (HAT) and visibility is 250 feet and ¾ statute mile (SM).  The POFZ is considered clear even if the wing of the aircraft holding on a taxiway waiting for runway clearance penetrates the POFZ; however, neither the fuselage nor the tail may infringe on the POFZ.  If the POFZ is not clear, the MINIMUM authorized height above touchdown (HAT) and visibility is 250 feet and ¾ statute mile (SM).

10 Federal Aviation Administration 10 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 POFZ Compliance In the approved AOSC Decision Document #01, the requirement was set for the POFZ guidance to be applied uniformly to all airports nationally by January 1, 2007 It was further noted that “any airport that fails to meet the POFZ guidance by that date will not have its procedures approved at their next subsequent biennial review”. In the approved AOSC Decision Document #01, the requirement was set for the POFZ guidance to be applied uniformly to all airports nationally by January 1, 2007 It was further noted that “any airport that fails to meet the POFZ guidance by that date will not have its procedures approved at their next subsequent biennial review”.

11 Federal Aviation Administration 11 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 POFZ Examples

12 Federal Aviation Administration 12 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 P O F Z T E R P S

13 Federal Aviation Administration 13 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 P O F Z T E R P S

14 Federal Aviation Administration 14 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 P O F Z T E R P S

15 Federal Aviation Administration 15 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 P O F Z TERPS

16 Federal Aviation Administration 16 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 POFZ TERPS ILS Critical

17 Federal Aviation Administration 17 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 T POFZ TERPS POFZ TERPS POFZ TERPS

18 Federal Aviation Administration 18 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 ARC-1 Memo to RAPTs (12/16/05) Less than a year remains before the POFZ implementation deadline Help is needed to ensure that implementation strategies are developed and the necessary actions are taken at any affected airports. –Implementation oversight by the Region is critical to successful implementation –Regional Airspace Procedures Team (RAPT) support is needed Less than a year remains before the POFZ implementation deadline Help is needed to ensure that implementation strategies are developed and the necessary actions are taken at any affected airports. –Implementation oversight by the Region is critical to successful implementation –Regional Airspace Procedures Team (RAPT) support is needed

19 Federal Aviation Administration 19 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 ARC-1 Memo to RAPTs (12/16/05) Cont. Specifically, the AOSC requested (by February 28, 2006) the RAPT to: –Review the requirements outlined in AOSC Decision Document #01 (attached) to keep the POFZ clear under the specified conditions and determine the appropriate method of compliance for each runway end with a current or near-term planned precision approach. –Identify the locations where additional markings/signage are needed and a target date for completion Follow-up by the RAPT toward the end of 2006 may also be needed to ensure that the necessary actions are completed by the January 1, 2007 deadline. Specifically, the AOSC requested (by February 28, 2006) the RAPT to: –Review the requirements outlined in AOSC Decision Document #01 (attached) to keep the POFZ clear under the specified conditions and determine the appropriate method of compliance for each runway end with a current or near-term planned precision approach. –Identify the locations where additional markings/signage are needed and a target date for completion Follow-up by the RAPT toward the end of 2006 may also be needed to ensure that the necessary actions are completed by the January 1, 2007 deadline.

20 Federal Aviation Administration 20 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 POFZ Reference Material AOSC Decision Document #01 Advisory Circular 150/5340-18D “Standards for Airport Sign Systems” Advisory Circular 150/5340-1J, “Standards for Airport Markings” Airport Certification Program Policy and Guidance, Policy #88 FAA Order 7110.65R, “Air Traffic Control” (Section 3-7-6) FAA Order 7210.3R, “Facility Operation and Administration” (Section 10-1-12) ATO training briefing Aeronautical Information Manual (Section 5-4-20b) AOSC Decision Document #01 Advisory Circular 150/5340-18D “Standards for Airport Sign Systems” Advisory Circular 150/5340-1J, “Standards for Airport Markings” Airport Certification Program Policy and Guidance, Policy #88 FAA Order 7110.65R, “Air Traffic Control” (Section 3-7-6) FAA Order 7210.3R, “Facility Operation and Administration” (Section 10-1-12) ATO training briefing Aeronautical Information Manual (Section 5-4-20b)

21 Federal Aviation Administration 21 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 Frequently Asked Questions Does POFZ apply to GPS WAAS approaches? –The POFZ applies to any approach with ceiling below 250 feet and/or visibility below 3/4 of a statute mile or below 4,000 RVR. Does POFZ apply at military airports? –The POFZ applies at joint-use facilities. How do we determine the 250 foot ceiling requirement? –The reportable values from appropriate weather sources should be used to determine ceiling height. Does POFZ apply to GPS WAAS approaches? –The POFZ applies to any approach with ceiling below 250 feet and/or visibility below 3/4 of a statute mile or below 4,000 RVR. Does POFZ apply at military airports? –The POFZ applies at joint-use facilities. How do we determine the 250 foot ceiling requirement? –The reportable values from appropriate weather sources should be used to determine ceiling height.

22 Federal Aviation Administration 22 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 Frequently Asked Questions How do we apply POFZ at non-towered airports or towers that have limited hours? –Pilots will be notified of POFZ requirements at all airports (including non-towered airports) through the Aeronautical Information Manual (AIM). Hold lines should be placed at the most conservative location to protect both the POFZ and the ILS critical area. Pilots are required to understand and comply with these markings. How do we apply POFZ at non-towered airports or towers that have limited hours? –Pilots will be notified of POFZ requirements at all airports (including non-towered airports) through the Aeronautical Information Manual (AIM). Hold lines should be placed at the most conservative location to protect both the POFZ and the ILS critical area. Pilots are required to understand and comply with these markings.

23 Federal Aviation Administration 23 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 Frequently Asked Questions Who will fund modifications to the airport environment (marking, signage, concrete)? –ARP, working with the sponsor, should be developing funding plans for the necessary modifications. However any extensive work requiring multi-year funding should be reported though the RAPT to the AOSC. Who will fund modifications to the airport environment (marking, signage, concrete)? –ARP, working with the sponsor, should be developing funding plans for the necessary modifications. However any extensive work requiring multi-year funding should be reported though the RAPT to the AOSC.

24 Federal Aviation Administration 24 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 Frequently Asked Questions Can the implementation date be deferred? –Any requests for deferral will be considered at the AOSC executive steering group level). –Every effort needs to be made to meet the deadline and each RAPT should report implementation concerns as soon as possible. If an airport is not able to comply by 1/1/07, is it an option to increase the published minima to 250 feet and ¾ statute mile? –Yes, that is an option. Can the implementation date be deferred? –Any requests for deferral will be considered at the AOSC executive steering group level). –Every effort needs to be made to meet the deadline and each RAPT should report implementation concerns as soon as possible. If an airport is not able to comply by 1/1/07, is it an option to increase the published minima to 250 feet and ¾ statute mile? –Yes, that is an option.

25 Federal Aviation Administration 25 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 Frequently Asked Questions Are vehicles allowed to penetrate the POFZ when the POFZ is active? –The POFZ should be protected from all obstacles. The only exception is a wing of a taxiing aircraft. This can be enforced by a hold sign on a road or other agreement with the airport operator Are vehicles allowed to penetrate the POFZ when the POFZ is active? –The POFZ should be protected from all obstacles. The only exception is a wing of a taxiing aircraft. This can be enforced by a hold sign on a road or other agreement with the airport operator

26 Federal Aviation Administration 26 Precision Obstacle Free Zone (POFZ) Implementation February 17, 2006 Additional Questions & Answers


Download ppt "Presented to:FAA field personnel By:AOSC Date:February 17, 2006 Presented to:FAA field personnel By:AOSC Date:February 17, 2006 Federal Aviation Administration."

Similar presentations


Ads by Google