Abstract

Predictions of the noise environment due to aircraft noise near airports are needed for a wide variety of planning and regulatory purposes. Several different computer programs, some very elaborate, have been developed to provide these predictions. In application, given the same nominal airport input data, these programs may produce contours that are quite different in size and shape. Differences in modeling algorithms and aircraft noise and profile data are usually responsible for most of these differences. The following factors which should be examined in evaluating aircraft noise programs will be discussed: (1) the basic program structure and modeling assumptions, (2) the algorithms governing the prediction of noise levels for ground‐to‐ground propagation and transition from air‐ to‐ground to ground‐to‐ground propagation modes, (3) the stored aircraft noise level and profile data, (4) flexibility in program output formats, (5) program operating complexity and convenience and, (6) overall program operating costs. Examples of contour differences arising from differing modeling assumptions and propagation algorithms will be presented.Predictions of the noise environment due to aircraft noise near airports are needed for a wide variety of planning and regulatory purposes. Several different computer programs, some very elaborate, have been developed to provide these predictions. In application, given the same nominal airport input data, these programs may produce contours that are quite different in size and shape. Differences in modeling algorithms and aircraft noise and profile data are usually responsible for most of these differences. The following factors which should be examined in evaluating aircraft noise programs will be discussed: (1) the basic program structure and modeling assumptions, (2) the algorithms governing the prediction of noise levels for ground‐to‐ground propagation and transition from air‐ to‐ground to ground‐to‐ground propagation modes, (3) the stored aircraft noise level and profile data, (4) flexibility in program output formats, (5) program operating complexity and convenience and, (6) overall program operati...

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.