presented to:faa field personnel by:aosc date:february 17, 2006 presented to:faa field personnel...

26
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

Upload: vivien-young

Post on 31-Dec-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 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

Presented to: FAA field personnel

By: AOSC

Date: February 17, 2006

Presented to: FAA field personnel

By: AOSC

Date: February 17, 2006

Federal AviationAdministrationAirport Obstructions

Standards CommitteeAirport Obstructions Standards Committee

FAA Broadcast On

Precision Obstacle Free Zone (POFZ)

Implementation

FAA Broadcast On

Precision Obstacle Free Zone (POFZ)

Implementation

Page 2: 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

Federal AviationAdministration

2Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

AgendaAgenda

• 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

Page 3: 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

Federal AviationAdministration

3Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

Broadcast ObjectivesBroadcast 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

Page 4: 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

Federal AviationAdministration

4Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

AOSC BackgroundAOSC 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

Page 5: 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

Federal AviationAdministration

5Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

AOSC Steering GroupAOSC 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

Page 6: 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

Federal AviationAdministration

6Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

AOSC Decision DocumentsAOSC 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

Page 7: 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

Federal AviationAdministration

7Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

POFZ IntroductionPOFZ Introduction

POFZ protects the area of short final area during very low ceilings (<250’ feet) and or visibilities (<3/4 Sm or < 4000’ RVR)

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

TERPS34:1 area

400’

400’

200’2

4

Page 8: 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

Federal AviationAdministration

8Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

POFZ ApplicabilityPOFZ 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).

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).

Page 9: 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

Federal AviationAdministration

9Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

POFZ Applicability (Cont’d)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).

Page 10: 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

Federal AviationAdministration

10Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

POFZ CompliancePOFZ 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”.

Page 11: 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

Federal AviationAdministration

11Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

POFZ ExamplesPOFZ Examples

Page 12: 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

Federal AviationAdministration

12Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

P O F Z

T E R

P S

Page 13: 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

Federal AviationAdministration

13Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

PO

FZ

TERPS

Page 14: 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

Federal AviationAdministration

14Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

POFZ

TERP

S

Page 15: 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

Federal AviationAdministration

15Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

POFZ

TE

RP

S

Page 16: 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

Federal AviationAdministration

16Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

PO

FZ

TERPS

ILS Critical

Page 17: 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

Federal AviationAdministration

17Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

•T

POFZ

TER

PS

PO

FZ

TERPS

POFZ

TER

PS

Page 18: 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

Federal AviationAdministration

18Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

ARC-1 Memo to RAPTs (12/16/05)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

Page 19: 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

Federal AviationAdministration

19Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

ARC-1 Memo to RAPTs (12/16/05) Cont.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.

Page 20: 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

Federal AviationAdministration

20Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

POFZ Reference MaterialPOFZ 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)

Page 21: 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

Federal AviationAdministration

21Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

Frequently Asked QuestionsFrequently 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.

Page 22: 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

Federal AviationAdministration

22Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

Frequently Asked QuestionsFrequently 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.

Page 23: 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

Federal AviationAdministration

23Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

Frequently Asked QuestionsFrequently 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.

Page 24: 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

Federal AviationAdministration

24Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

Frequently Asked QuestionsFrequently 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.

Page 25: 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

Federal AviationAdministration

25Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

Frequently Asked QuestionsFrequently 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

Page 26: 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

Federal AviationAdministration

26Precision Obstacle Free Zone (POFZ) ImplementationFebruary 17, 2006

Additional Questions & Answers

Additional Questions & Answers