Two aircraft of the same type depart from the same threshold, at the same weight, three minutes apart. The first passes over the housing estate while climbing steeply, with landing gear extended, at low speed. The second passes lower at the same point but is already clean and will be significantly higher fifteen kilometers further on. Neither has been quieter than the other—they’ve just displaced the noise elsewhere. The question remains: where, who is protected, who isn’t, and who pays in fuel.
What is displaced, and what is not removed
The noise level received by a resident depends on three factors, and a departure procedure only controls two of them. The first is the acoustic power emitted. On a jet engine, the noise from the jet mixing varies as a very high power of the ejection velocity—the so-called eighth-power law—so a modest reduction in thrust disproportionately reduces the noise source. On high-bypass engines, the fan contributes more, but the principle holds: the engine speed controls the noise level much faster than proportionally.
The second factor is the oblique distance between the source and the ear. A point source in free field loses about six decibels for each doubling of distance, plus atmospheric absorption (which affects high frequencies most) and lateral attenuation (which depends on the angle at which the aircraft is viewed and what lies between it and the ground). The third factor is directivity: a jet engine does not radiate equally forward and aft, which is why a resident hears the aircraft longer after passing than before.
Of these three factors, the procedure affects engine speed and geometry. This is where the difference between the two profile families lies, and it’s also where the most common reasoning trap occurs: gaining altitude only pays off if the aircraft is near the vertical of the listener. From a distance, at a shallow angle, an extra hundred meters changes the oblique distance hardly at all.
The noise you hear from an aircraft depends on how loud it is, how far away it is, and the direction it’s pointing. The departure procedure can only change the first two: by reducing engine noise or by making the aircraft climb higher (and thus farther away). But extra height only helps if you’re directly below the plane—farther away, the difference is tiny.
An Airbus A320 departing from Paris Charles de Gaulle on a 3,000-meter runway at 15°C. At 800 feet (thrust reduction altitude), the “close” profile accelerates immediately, reaching 250 knots by 1,500 feet. The “distant” profile stays at 180 knots until 3,000 feet, gaining 100 meters of altitude over the first 2 km—but at 5 km, the “close” profile is 200 meters higher and quieter.
A word on airframe noise, often incorrectly cited here. Flaps and slats generate it, but at takeoff power, it’s masked by the engines, and the landing gear is already retracted. Keeping the takeoff configuration longer costs fuel, not decibels. All the acoustic advantage of the profile that retains its flaps comes from the altitude gained, never from its drag.
Two configuration schedules, one physics
The two NADP standardized profiles are based on the same framework: a thrust reduction altitude, an acceleration altitude, and a procedure end altitude. The international framework sets a minimum for thrust reduction—around eight hundred feet above the aerodrome elevation—and ends the procedure at about three thousand feet, beyond which the climb becomes a normal climb. Many operators raise this minimum for margin or standardization reasons: their documentation is the law, not the generic value.
What distinguishes the two profiles is a single decision: where to place the acceleration altitude. Setting it at the thrust reduction minimum gives the so-called distant profile; delaying it to the end of the procedure gives the so-called close profile. Everything else—climb speed, gradient, flap retraction timing, time spent at climb power—follows mechanically.
NADP 1: Altitude first
At the thrust reduction altitude, the crew transitions to climb power but does not change the configuration or speed: flaps remain in the takeoff position, and speed is maintained at the takeoff safety speed plus ten to twenty knots. All excess thrust then goes into the climb rate, as nothing is diverted to accelerate. This is the maximum gradient the aircraft can sustain with all engines, and it holds until the end of the procedure, where acceleration and flap retraction finally occur.
The result is clear at short distances: the aircraft is higher over the first few kilometers, thus farther in oblique distance, and quieter where altitude differences still matter. In return, it remains slow, in an extended configuration, with poor glide ratio.
NADP 2: Speed and glide ratio first
Same thrust reduction altitude, but acceleration begins immediately: excess thrust first goes into kinetic energy, flaps retract as per the schedule, and the aircraft completes the procedure clean, at climb speed. The path during acceleration is almost flat, and this is precisely what is visible from the ground at short distances.
What follows is less visible but equally real. A clean aircraft has a much better glide ratio; at the same climb power, it climbs faster and, above all, climbs faster with less thrust. The distant resident therefore receives an aircraft that is both higher and quieter at the source. The energy did not disappear during acceleration: it changed form, then was converted into altitude when the aircraft became efficient. The choice between the two profiles is not a choice between more or less noise; it’s a choice about when the energy is absorbed.
Where the crossover point lies
The two noise level curves cross somewhere. Exactly where, no one can say without calculation: it depends on the type, weight, thrust setting, temperature, terrain, and ground composition between the aircraft and the listener. The certification noise measurement points give the scale of the problem: the lateral point is a few hundred meters from the runway centerline, and the flyover point is a few kilometers from brake release. The crossover typically falls beyond the first and in the region of the second, where the suburbs begin rather than the immediate vicinity.
| Item | NADP 1 (close-in noise) | NADP 2 (distant noise) |
|---|---|---|
| Acceleration height | end of procedure | thrust reduction height |
| Initial climb configuration | take-off flaps held | retracted on schedule |
| Vitesse tenue | safety speed plus a small increment | clean climb speed |
| Gradient over the first few kilometres | maximal | reduced during acceleration |
| Residents who benefit | immediate vicinity of the runway | built-up areas beyond the crossover |
| Lift-to-drag ratio during the procedure | degraded over the whole length | degraded over a short segment |
| Fuel burn on departure | the higher of the two | the lower of the two |
| Sensitivity to an imposed level-off | high: the aircraft stays slow and configured | low: it is already clean |
What the close profile costs
The energy cost of the close profile is not found in a table: it is the product of excess drag and the distance covered in the extended configuration. Every meter flown with flaps extended is paid for at the rate of degraded glide ratio, and the close profile multiplies these meters, as it retains the configuration until the end of the procedure instead of abandoning it at the thrust reduction altitude. It’s the area between two drag curves.
At the scale of a flight, the difference is not measured in tons or minutes: it is counted with each departure, across an entire fleet, every day. This cumulative impact is what matters to an operator, and that’s why the decision is not made in the cockpit. Add to this a rarely mentioned effect: the additional fuel is burned low, in the atmospheric boundary layer, where nitrogen oxides affect local air quality. Protecting the immediate resident’s ears therefore costs some of their air, making the choice between the two profiles an environmental trade-off, not just an acoustic option.
When the noise reduction profile takes a back seat
A noise reduction procedure is never prioritized over safety, and the list of situations that suspend it is longer than one might think. It starts before takeoff: in wet snow conditions, deicing imposes an effectiveness window, engine anti-icing consumes power, and the available performance becomes the constraint that dictates the profile.
An engine failure changes everything: the noise reduction profile is abandoned, the clean trajectory and the go-around path take precedence, and the acceleration altitude to be maintained is no longer that of the noise procedure but the one that ensures obstacle clearance. Wind shear, turbulence, icing in climb, level-off, or speed reductions imposed by ATC produce the same effect.
| Situation | What then governs | Effect on the profile |
|---|---|---|
| Contaminated runway | take-off performance and flight path control | profile subordinate to the performance calculation |
| Engine failure after the decision | net flight path and obstacle clearance | noise procedure abandoned |
| Nearby terrain or obstacle | acceleration height determined by obstacles | acceleration height raised, profile imposed |
| Level-off imposed by ATC | compliance with the clearance | early clean-up, procedure interrupted |
| Wind shear or turbulence | configuration and manoeuvring speed | profile abandoned at the crew’s discretion |
The trap. The numbering is not universal. An operator may name its profiles differently than the international framework, and an aerodrome publication may prescribe one by description rather than by number. An crew may then conscientiously apply the distant profile while believing they are applying the close profile. The second trap is more insidious: the acceleration altitude entered into the flight management system does not distinguish on its own between the all-engine acceleration altitude and the obstacle protection altitude in case of engine failure. Entering one for the other goes unnoticed until something happens.
What to verify in your own documentation
Three questions suffice, and none are resolved in flight. Which profile does the operations manual prescribe by default, and in what terms—mandatory, recommended, or left to the captain’s discretion? Are the two altitudes expressed as height above the aerodrome or as altitude, and what exactly does the flight management system do with the entered value? Finally, what abandonment criteria are written in black and white, and are they stated in the departure briefing rather than assumed to be known?

The right reflex. State the two altitudes aloud during the briefing, with their reference—thrust reduction altitude, acceleration altitude, and the value retained in case of engine failure if it differs—then compare them with what is actually displayed in the computer. This is the only check that catches both input errors, confusion between the two profiles, and the substitution of an obstacle altitude for a noise altitude.
There remains a gray area that the cockpit cannot fill: the crossover point is published nowhere. A crew applying the local instruction does not know if it effectively protects the targeted population—that demonstration is the responsibility of the aerodrome manager and the balanced approach that frames noise-related restrictions, where noise reduction procedures come only after source reduction and urban planning control. For those preparing a type rating or line training, the question asked in the simulator is almost never “which profile”: it’s “what do you abandon first, and to what signal”. Discussions on these local instructions continue on the FL330 forum.
Finally, this text describes a mechanism, not an applicable instruction: the applicable regulatory text, the aerodrome’s aeronautical information publication, and the operator’s approved documentation take precedence in all cases over what is written here.

Leave a Reply
You must be logged in to post a comment.