Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.
Summary | 75 Summary12 Airport operators can play an important role in developing PBN procedures for their airport. Airport operators can be valuable to each step of the PBN implementation process, from the initial request through the design and evaluation, implementation, documentation, deploy- ment, and post-implementation assessment. Airport operators have knowledge of the local airspace, aircraft operators and airport characteristics, and relationships with the local community. Their support of the PBN design process can ensure some level of compatibility with these local needs, balanced with the objectives of the air transportation system they operate within. Areas for potential airport contribution to the PBN implementation process include: ⢠Understanding the limitations of the current flight procedures and their impacts on the airport, air- craft operators, and local community and specifying objectives for design of PBN procedures based on those limitations. ⢠Providing airport data, information and operating characteristics, such as preferred runway con- figurations, preferred routes, airport survey data, and airport fleet mix characteristics to support the design of the PBN procedures. ⢠Supporting the characterization of the baseline operations of the airport and local airspace, for the design and benefits assessment of the PBN procedures. ⢠Supporting evaluation of PBN procedures in the design and post-implementation phases by identi- fying noise-sensitive areas around the airport, specifying allowable noise thresholds for those areas, assessing the impact of the procedures on those areas, and proposing design changes to satisfy the constraints. ⢠Reviewing published procedures to ensure they comply with airport and community requirements and constraints. ⢠Maintaining relationships with relevant FAA personnel involved in the design of PBN procedures, such as the Traffic Management Unit of the local TRACON, ATCT, and the representative of the governing service center. ⢠Communicating with groups representing the local community and other stakeholders in order to explain the plans for and potential impacts of proposed PBN procedures, understand the concerns of the stakeholders, support translating these concerns into design objectives and constraints for the PBN procedures, and obtain feedback from the community in the post-implementation phase regarding the impact on PBN procedures. In addition to areas of potential contribution, areas of process vulnerability include: ⢠Not sufficiently accounting for the needs and considerations of the airport, community, aircraft operators, and other local stakeholders when establishing the objectives and constraints for the procedure design process. For example, noise-sensitive areas proximate to the airport that might limit the available routing alternatives.
76 | UNDERSTANDING THE AIRPORTâS ROLE IN PERFORMANCE-BASED NAVIGATION ⢠Changes to the proposed procedures that might occur through successive design iterations imple- mented in order to better accommodate the needs of other stakeholders or satisfy other design criteria. Such changes might introduce conflicts with local needs and considerations, even if they were initially accounted for in the problem definition process. ⢠Not being able to satisfy the needs of all community members or other local stakeholders in the final design of the flight procedures, due to other severe design constraints or compromises that must be made to satisfy other design criteria. ⢠Inadequate outreach to community, government, and other local stakeholders as part of the proce- dure design process to communicate design objectives, considerations, trade-offs, and propositions in order to obtain understanding. This includes CatExs to proposed procedures, which obviate the EA or EIS processes and their associated public outreach requirements. ⢠Not communicating the purpose and impacts of the procedure design initiative in terms under- standable or relevant to the community in order to obtain their understanding. ⢠Differences between the performances of the PBN procedures anticipated during the design phase and realized in post-implementation, such as unintended noise impacts. This may be due to differences in the modeling of aircraft for the design phase and the actual flight performance of aircraft in implementation, or the natural variability in the flight performances of aircraft due to, for example, atmospheric conditions, aircraft weight, and other parameters.