Balanced vs. Unbalanced Field Length Explained

Short answer: Under 14 CFR 121.189(c), accelerate-stop distance must not exceed the runway length plus any stopway, and takeoff distance must not exceed the runway length plus any clearway capped at one-half the runway length. Takeoff run must not be greater than the length of the runway under 14 CFR 121.189(c)(3). When stopways or clearways are present, or when declared distances under AIM 4-3-6 differ, Accelerate-Stop Distance Available (ASDA) and Takeoff Distance Available (TODA) provide different lengths for stopping and continuing takeoff.

Balanced vs. Unbalanced Field Length at a Glance

When you prepare for a technical airline interview or review transport category performance, matching aircraft performance requirements against airport declared distances is governed by specific operating limitations under 14 CFR 121.189 and AIM 4-3-6.

If an airport does not have a clearway or a stopway, and no runway safety area subtractions exist, the physical runway length governs declared distances. Under AIM 4-3-6, Takeoff Run Available (TORA), Takeoff Distance Available (TODA), and Accelerate-Stop Distance Available (ASDA) are equal in that baseline configuration.

When an airport publishes a clearway or a stopway in the Chart Supplement, or subtracts runway length to meet safety area standards, the available stopping distance no longer equals the available takeoff distance. Declared distances treat these runway performance requirements independently.

Comparison of Declared Distance and Takeoff Limitations

Performance Feature Runway Without Stopway or Clearway Runway With Stopway or Clearway
Applicable declared distances (AIM 4-3-6) TORA, TODA, and ASDA equal physical runway length TODA includes clearway. ASDA includes stopway
Accelerate-stop distance limit (14 CFR 121.189(c)(1)) Must not exceed length of the runway Must not exceed length of the runway plus length of stopway
Takeoff distance limit (14 CFR 121.189(c)(2)) Must not exceed length of the runway Must not exceed runway length plus clearway (clearway capped at one-half runway length)
Takeoff run limit (14 CFR 121.189(c)(3)) Must not be greater than length of the runway Must not be greater than length of the runway

The Four Declared Distances in AIM 4-3-6

To understand why runway declared distances differ, you first need the exact FAA definitions. According to AIM 4-3-6 (and mirrored in AIP ENR 1.1), declared distances represent the maximum distances available and suitable for meeting takeoff and landing performance requirements.

The airport operator calculates these figures by taking the physical length of the paved runway, adding any clearway or stopway, and subtracting any length needed to achieve standard Runway Safety Areas (RSA), Runway Object Free Areas (ROFA), or Runway Protection Zones (RPZ). All 14 CFR Part 139 airports report declared distances for each runway in the Chart Supplement.

If a runway does not have published declared distances, you may assume the declared distances equal the physical length of the runway, unless a displaced landing threshold shortens the Landing Distance Available. When declared distances are published, AIM 4-3-6 states that pilots must use the declared distances determined by the airport operator and never attempt to calculate them independently by adding stopways or clearways to the physical runway length.

  • Takeoff Run Available (TORA): The runway length declared available and suitable for the ground run of an airplane taking off. It is typically the physical runway length, though it can be shorter if a portion of the pavement is needed to satisfy runway protection zone requirements.
  • Takeoff Distance Available (TODA): The TORA plus the length of any remaining runway or clearway beyond the far end of the TORA. Any available clearway length is already included in the published TODA figure in the Chart Supplement.
  • Accelerate-Stop Distance Available (ASDA): The runway plus stopway length declared available and suitable for the acceleration and deceleration of an airplane aborting a takeoff. It can be longer than the physical runway if a stopway is designated, or shorter if pavement is used to meet Runway Safety Area requirements.
  • Landing Distance Available (LDA): The runway length declared available and suitable for a landing airplane, which may be reduced by a displaced threshold or Runway Safety Area subtractions at the far end.

How 14 CFR 25.109 Defines Accelerate-Stop Distance

In a transport category airplane certificated under Part 25, your stopping requirement is governed by 14 CFR 25.109. The regulation requires manufacturers to determine the accelerate-stop distance on a dry runway as the greater of two scenarios: an engine failure rejected takeoff, or an all-engines-operating rejected takeoff.

In the engine-failure case under 14 CFR 25.109(a)(1), the airplane accelerates from a standing start with all engines operating to the engine failure speed, VEF. The critical engine fails at VEF, the airplane continues accelerating to the highest speed reached during the rejected takeoff assuming the pilot takes the first action to reject at V1, and then comes to a full stop. In the all-engines case under 14 CFR 25.109(a)(2), the airplane accelerates with all engines operating to the highest speed reached assuming the first action to reject occurs at V1, and comes to a full stop with all engines still operating.

In both dry runway scenarios, 14 CFR 25.109(a) adds a distance equivalent to 2 seconds at V1 onto the total stopping distance. Under 14 CFR 25.109(g), the landing gear must remain extended throughout the entire accelerate-stop distance.

Wet runway calculations change the stopping physics and the rules on reverse thrust. Under 14 CFR 25.109(b), the wet accelerate-stop distance is the greater of the dry runway distance or the wet distance computed using wet VEF and wet V1 values. Under 14 CFR 25.109(f), the effects of available reverse thrust shall not be included as an additional means of deceleration on a dry runway, but may be included on a wet runway using recommended procedures if they are safe, reliable, consistent, and do not require exceptional skill.

How 14 CFR 25.113 Defines Takeoff Distance and Takeoff Run

The go side of the takeoff equation is defined in 14 CFR 25.111 and 14 CFR 25.113. The airplane accelerates on the ground to VEF where the critical engine is made inoperative, rotates at a speed not less than VR, and accelerates to V2 before reaching 35 feet.

When you check whether a runway is long enough, 14 CFR 25.113(a) states that the takeoff distance on a dry runway is the greater of two measurements. The first is the horizontal distance along the takeoff path with one engine inoperative from the start of the takeoff to the point where the airplane is 35 feet above the takeoff surface. The second is 115 percent of the horizontal distance from the start of takeoff to 35 feet with all engines operating.

On a wet runway, 14 CFR 25.113(b) defines the takeoff distance as the greater of the dry runway takeoff distance, or the horizontal distance on a wet runway to the point where the airplane is 15 feet above the takeoff surface, achieved in a manner that still ensures V2 is reached before 35 feet.

Clearways split takeoff distance and takeoff run into two separate numbers. Under 14 CFR 25.113(c), if the takeoff distance does not include a clearway, the takeoff run is equal to the takeoff distance. If the takeoff distance includes a clearway, the takeoff run on a dry runway is the greater of the one-engine-inoperative distance or 115 percent of the all-engines-operating distance from the start of takeoff to a point equidistant between the liftoff point (where VLOF is reached) and the point where the airplane is 35 feet above the takeoff surface. On a wet runway with a clearway, the takeoff run is the greater of the wet distance to 15 feet or 115 percent of the all-engines dry distance to the midpoint between VLOF and 35 feet.

How Stopways and Clearways Alter Operating Limits Under 14 CFR 121.189

For airline operations under Part 121, 14 CFR 121.189 sets the legal takeoff weight limits for turbine-engine-powered airplanes. Under 14 CFR 121.189(c) (applicable to airplanes certificated after August 29, 1959), no person may take off at a weight greater than the Airplane Flight Manual weight that shows compliance with three distance rules.

First, under 14 CFR 121.189(c)(1), the accelerate-stop distance must not exceed the length of the runway plus the length of any stopway (ASDA). Second, under 14 CFR 121.189(c)(2), the takeoff distance must not exceed the length of the runway plus the length of any clearway (TODA), except that the length of any clearway included must not be greater than one-half the length of the runway. Third, under 14 CFR 121.189(c)(3), the takeoff run must not be greater than the length of the runway (TORA).

When an airport provides a clearway or a stopway, the declared distances published under AIM 4-3-6 differ from the physical runway length. Under AIM 4-3-6, TODA includes any clearway beyond the far end of TORA for satisfying takeoff distance requirements, while ASDA includes any designated stopway for decelerating an aborting airplane. If an airport provides a clearway or a stopway, or reduces declared distances for safety areas, available stopping distance and available takeoff distance are not equal.

If a stopway has surface characteristics substantially different from the runway, 14 CFR 25.109(h) requires the takeoff data to include operational correction factors for the accelerate-stop distance that account for those surface traits and seasonal weather variations such as temperature, rain, snow, and ice.

Beyond the runway end, 14 CFR 121.189(d)(2) requires a net takeoff flight path that clears all obstacles either by a height of at least 35 feet vertically, or by at least 200 feet horizontally within the airport boundaries and at least 300 feet horizontally after passing the boundaries. In computing these paths under 14 CFR 121.189(e) and (f), operators must correct for runway gradient, elevation, ambient temperature, wind component, and runway surface condition (dry or wet), while assuming the airplane is not banked before reaching 50 feet and banked no more than 15 degrees thereafter.

Worked Example: Calculating Usable Clearway and Unbalanced Limits

In a technical interview, a panel pilot may give you a set of runway dimensions and ask how much clearway or stopway you can legally credit under Part 121. Here is our own step-by-step calculation showing how 14 CFR 121.189(c) and AIM 4-3-6 apply to a hypothetical runway.

Suppose an airport has a physical paved runway length of 8,000 feet, a physical clearway of 5,000 feet beyond the departure end, and a designated stopway of 1,000 feet. Assume full standard Runway Safety Areas exist, so no pavement subtractions apply.

Step 1: Determine TORA. Under AIM 4-3-6 and 14 CFR 121.189(c)(3), the Takeoff Run Available and maximum permissible takeoff run equal the physical length of the runway, which is 8,000 feet.

Step 2: Determine ASDA. Under AIM 4-3-6 and 14 CFR 121.189(c)(1), the accelerate-stop distance cannot exceed the runway length plus any stopway. By our calculation from 14 CFR 121.189(c)(1), 8,000 feet of runway plus 1,000 feet of stopway gives a usable ASDA of 9,000 feet.

Step 3: Determine maximum usable TODA under Part 121. The physical clearway is 5,000 feet, which would make the raw sum of runway plus clearway 13,000 feet. However, 14 CFR 121.189(c)(2) states that the length of any clearway included in takeoff distance calculations must not be greater than one-half the length of the runway. By our calculation from 14 CFR 121.189(c)(2), one-half of the 8,000-foot runway is 4,000 feet. Therefore, you can only credit 4,000 feet of the clearway, capping your usable TODA for Part 121 performance at 12,000 feet while your takeoff run (up to the midpoint between VLOF and 35 feet on a dry runway under 14 CFR 25.113(c)(1)) must still finish within the 8,000-foot TORA.

Geographical Constraints, Intersection Takeoffs, and Safety Areas

A runway does not need a clearway or stopway to have unequal declared distances. As detailed in AIM 4-3-6 (and mirrored in AIP ENR 1.1), declared distances account for standard Runway Safety Areas (RSA), Runway Object Free Areas (ROFA), and Runway Protection Zones (RPZ) at geographically constrained airports.

Under AIM 4-3-6, declared distances represent the maximum distances available and suitable for meeting takeoff and landing performance requirements. When an airport lacks sufficient space beyond the runway ends to meet safety area design standards, declared distances like ASDA or LDA may be reduced below the physical runway length. When ASDA is reduced to satisfy safety area requirements while TODA remains the full physical runway length, TODA is longer than ASDA.

AIM 4-3-6 notes an important operational detail about these unmarked limits: while you must use the published declared distances (such as a reduced ASDA or LDA) during preflight performance planning to accept the runway, an aircraft is not prohibited from physically rolling beyond an unmarked declared distance limit during an actual takeoff, aborted takeoff, landing, or taxi operation, provided the runway surface is marked as usable runway.

Intersection takeoffs also change your available distances. Under AIM 4-3-10, pilots who depart from an intersection must assess the resulting length reduction to both the published runway length and the published declared distances. If you ask the control tower for the remaining length from an intersection, AIM 4-3-10 states that controllers will issue the measured distance from the intersection to the physical runway end rounded down to the nearest 50 feet, but controllers are not able to inform you of the distance from the intersection to the end of any published declared distances.

Preflight Checklist for Evaluating Declared Distances

Use this step-by-step checklist written by our team to verify your runway distance limits before accepting a runway or intersection clearance, and to explain your preflight workflow clearly during a simulator or technical briefing.

  • Check the Chart Supplement for the departure runway end to verify TORA, TODA, ASDA, and LDA, rather than relying on the single runway length printed on the airport diagram (AIM 4-3-6).
  • Compare TORA, TODA, and ASDA to verify whether declared distances equal physical runway length or differ due to clearways, stopways, or RSA/RPZ subtractions.
  • Verify runway surface condition (dry, wet, or Runway Condition Codes 1 through 6 under AIM 4-3-9) and confirm whether grooved or porous friction course (PFC) wet data is approved in the Airplane Flight Manual (14 CFR 121.189(e)).
  • If an intersection takeoff is planned or offered by ATC, verify that your takeoff run, takeoff distance, and accelerate-stop distance fall within the reduced declared distances for that specific intersection, remembering that tower controllers only report physical length rounded down to the nearest 50 feet (AIM 4-3-10).
  • Confirm that the net takeoff flight path clears all obstacles by at least 35 feet vertically, or 200 feet horizontally within airport boundaries and 300 feet horizontally outside boundaries, with no banking below 50 feet and at most 15 degrees of bank above 50 feet (14 CFR 121.189(d) and (f)).

How to Explain Balanced vs. Unbalanced Field in a Pilot Interview

When an interviewer asks you to explain takeoff performance limitations, keep your answer structured around the competing distances and the regulations that govern them.

Explain how declared distances in AIM 4-3-6 (TORA, TODA, and ASDA) separate the ground run, the airborne climb to 35 feet (or 15 feet wet under 14 CFR 25.113), and the stopping margin (which includes the 2-second distance at V1 under 14 CFR 25.109).

Finish by tying the definitions to your operational limits under 14 CFR 121.189(c): the takeoff run stays on the runway, the accelerate-stop distance stays within the runway plus stopway, and the takeoff distance stays within the runway plus a clearway of no more than half the runway length.

Practice example

Walk me through how declared distances and the presence of a clearway or stopway change your takeoff performance limits under Part 121.

Example answer, written by us. It is not a real applicant's story. Under AIM 4-3-6 and 14 CFR 121.189, takeoff performance is evaluated against our declared distances: TORA, TODA, and ASDA. On a standard runway with no clearway, stopway, or safety area reductions, these distances equal the physical runway length. When a clearway is published, it increases our Takeoff Distance Available beyond the runway, though 14 CFR 121.189(c)(2) caps usable clearway credit at one-half of the runway length, and our takeoff run under 14 CFR 25.113 must still finish within the physical runway. When a designated stopway is published, it increases our Accelerate-Stop Distance Available for decelerating an aborted takeoff under 14 CFR 121.189(c)(1). Evaluating TODA, TORA, and ASDA allows us to meet 14 CFR 25.109 accelerate-stop rules and 14 CFR 25.113 screen heights of 35 feet dry or 15 feet wet while complying with Part 121 takeoff operating limitations.

This response connects declared distances in AIM 4-3-6 directly to 14 CFR 121.189 operating limits. Citing the one-half runway clearway cap and the 35-foot dry versus 15-foot wet screen heights proves solid command of Part 25 and Part 121 performance rules.

Practice this on Fourstripe. Pick your airline and a captain runs the interview out loud: TMAAT, about-you, technical and scenario questions, with real follow-ups. You get a scored report on every answer. 7-day trial, then from $149 a week. Start a practice interview

Frequently asked questions

What is the difference between TODA and ASDA?

Under AIM 4-3-6, Takeoff Distance Available (TODA) is the Takeoff Run Available (TORA) plus any remaining runway or clearway beyond the far end of the TORA. Accelerate-Stop Distance Available (ASDA) is the runway plus any designated stopway length declared available and suitable for accelerating and decelerating an airplane aborting a takeoff.

How much clearway can be used in Part 121 takeoff calculations?

Under 14 CFR 121.189(c)(2), the takeoff distance may include a clearway, but the length of any clearway included must not be greater than one-half the length of the runway. In addition, 14 CFR 121.189(c)(3) requires that the takeoff run itself must not exceed the physical length of the runway.

Does accelerate-stop distance include reverse thrust?

Under 14 CFR 25.109(f), the effects of available reverse thrust shall not be included as an additional means of deceleration when determining accelerate-stop distance on a dry runway. However, reverse thrust may be included on a wet runway using recommended procedures if it is safe, reliable, consistent, and does not require exceptional skill.

Why is ASDA sometimes shorter than the physical length of the runway?

According to AIM 4-3-6, an airport operator may subtract length from the physical runway when declaring ASDA in order to obtain a standard Runway Safety Area (RSA), Runway Object Free Area (ROFA), or Runway Protection Zone (RPZ) beyond the far end of the runway. While you must use this shorter declared ASDA for preflight performance compliance, you are permitted to roll beyond the unmarked end of the ASDA onto the remaining usable runway during an actual aborted takeoff.

What is the screen height for takeoff distance on a dry vs. wet runway?

Under 14 CFR 25.113(a), dry runway takeoff distance is measured to 35 feet above the takeoff surface (the greater of the one-engine-inoperative distance to 35 feet or 115 percent of the all-engines-operating distance to 35 feet). Under 14 CFR 25.113(b), wet runway takeoff distance is the greater of the dry takeoff distance or the wet horizontal distance to 15 feet above the takeoff surface, provided V2 is still achieved before reaching 35 feet.

Sources