Balanced Field Length Calculator

The Balanced Field Length Calculator computes the runway length required for balanced accelerate-stop and accelerate-go performance given aircraft, weight, thrust, and conditions.

Balanced Field Length Calculator Explained

Balanced field length ties together two competing paths at the decision speed. If the critical engine fails at that speed and you reject the takeoff, the aircraft must stop within the available distance. If you continue, it must reach liftoff and pass the screen height within the same distance. When those distances match, the field is balanced.

The calculator models both paths. The first is accelerate–stop, which covers ground roll to the decision speed, pilot reaction, and braking to a full stop. The second is accelerate–go, which covers the initial acceleration, the engine failure, continued acceleration on one engine, liftoff, and the climb to screen height. The result is the runway length at which the two distances are equal.

This balance depends on thrust, weight, drag, rolling resistance, and runway conditions. It also depends on air density, which changes with temperature and elevation. Small changes in these variables can shift the balance point by hundreds of feet or meters.

How to Use Balanced Field Length (Step by Step)

You can use balanced field length when planning takeoff performance or learning how the physics works. The concept links the decision speed and runway length with a safety margin. Follow these steps to frame the problem before opening the tool.

• Define the aircraft configuration: flaps, anti-ice, and any performance penalties.
• Collect environment data: pressure altitude, outside air temperature, wind, and runway slope.
• Note the runway surface condition: dry, wet, or contaminated, and the braking action report.
• Set the target screening height: 35 ft for most turbines, 50 ft for many pistons.
• Choose an initial guess for decision speed and weight to test sensitivity.

Balanced field length is not just a number. It is a relationship. By changing one variable at a time, you will see how the runway requirement grows or shrinks. That makes tradeoffs clearer and safer.

Formulas for Balanced Field Length

Our model uses classical mechanics with practical adjustments. We split the calculation into two distances and set them equal. This gives you a transparent view of the physics and the variables that matter. Units must be consistent throughout to get a valid result.

• Accelerate–stop distance, ASD: ASD ≈ s_accel(0→V1) + V1·t_react + V1²/(2·a_brake), where s_accel ≈ V1²/(2·a_to). Here a_to ≈ (T − D − μ_r·W)/m, and a_brake ≈ μ_b·g + D/m with g the gravitational acceleration.
• Accelerate–go distance, AGD: AGD ≈ s_accel(0→V1) + s_transition + s_accel_OEI(V1→Vlof) + s_liftoff + s_climb_to_screen. A simple form uses s_accel_OEI ≈ (Vlof² − V1²)/(2·a_OEI), and s_climb_to_screen ≈ h_screen / tan(γ_OEI), where γ_OEI ≈ (T_OEI − D)/W.
• Balanced condition: Balanced Field Length, BFL, occurs when ASD = AGD. Solve for V1 or for runway length; then set BFL = that common distance.
• Drag and rolling resistance: D ≈ 0.5·ρ·V²·S·C_D + μ_r·(W − L), with L the lift term during the ground roll. Rolling terms increase with contamination and slope.
• Density effects: ρ scales with pressure altitude and temperature; thrust T also drops with hot and high conditions. This reduces acceleration and increases both distances.

In practice, you iterate on the decision speed to balance the two distances. Many certified methods also include margins and corrections for engine spool-down, pilot technique, and system delays. The calculator exposes these elements, so you can see how each assumption moves the result.

What You Need to Use the Balanced Field Length Calculator

Before you open the Calculator, gather a short list of inputs. These make the physics model complete and keep your units consistent. The better the inputs, the more useful the result.

• Aircraft weight and configuration (flap setting, bleed/anti‑ice status, assumed temperature or derate).
• Available thrust or thrust-to-weight curve at the given pressure altitude and temperature.
• Runway condition and slope (dry/wet/contaminated, gradient in %), and declared distances (TORA/ASDA/TODA).
• Local weather: pressure altitude, temperature, wind component, and, if needed, runway condition code.
• Target screen height and decision speed bounds (minimum and maximum acceptable V1).

Make sure your units match the model (for example, knots and feet or meters and meters per second). Edge cases include very short runways, severe tailwinds, high elevations, and contaminated surfaces. In those cases, a solution may not exist, or the balanced speed may hit regulatory limits. The tool will flag those conditions.

How to Use the Balanced Field Length Calculator (Steps)

Here’s a concise overview before we dive into the key points:

1. Open the Calculator and select your unit system (SI or US customary).
2. Enter aircraft weight, configuration, and any derate or assumed temperature.
3. Input pressure altitude, outside air temperature, wind, runway slope, and condition.
4. Set bounds for the decision speed and the screen height appropriate to your aircraft.
5. Run the calculation to compute ASD and AGD across the speed range.
6. Review the plotted intersection or the reported balanced result and check declared distances.

These points provide quick orientation—use them alongside the full explanations in this page.

Real-World Examples

A twin‑engine jet at sea level, standard day, dry runway, zero slope, and a 7,500 ft TORA is departing at 65,000 kg. Thrust is set to full rated with no derate. The model computes ASD and AGD across decision speeds from 120 to 145 kt and finds the balance at V1 = 134 kt. At that speed, ASD = AGD = 6,210 ft, giving 1,290 ft of remaining runway, and a climb gradient to clear the 35 ft screen is satisfied. What this means: the runway is suitable with margin, and reducing weight or adding a derate would still meet requirements.

The same aircraft at 5,500 ft pressure altitude on a 30 °C day with a 1% uphill slope faces a 6,500 ft TORA. With wet runway and anti‑ice on, thrust falls and rolling resistance rises. The model’s iteration shows the balanced point at V1 = 136 kt, where ASD = AGD ≈ 6,740 ft, exceeding ASDA and TORA. Even reducing V1 to the minimum allowed does not balance within the available distance. What this means: the takeoff is not feasible as planned; you must reduce weight, change to a cooler time, accept a headwind, or choose another runway.

Accuracy & Limitations

The calculator follows sound physics and uses clear variables. It is ideal for education, scenario testing, and early planning. However, certified performance comes from the Aircraft Flight Manual or approved software. Those sources include proprietary data, correction factors, and certification margins that a generic model cannot fully reproduce.

• Regulatory definitions set specific screen heights, speed schedules, and correction factors.
• Engine thrust lapse and drag vary with configuration and manufacturer data beyond simple curves.
• Braking and tire behavior change with temperature, anti‑skid logic, and contamination depth.
• Obstacle clearance requires detailed terrain and procedure data, not just a screen height.
• Declared distances (TORA, TODA, ASDA) and stopway/clearway availability limit the usable result.

Use this tool to understand trends, units, and sensitivities. For real-world dispatch, always base decisions on AFM tables, performance bulletins, and approved calculations for your aircraft and runway.

Units and Symbols

Balanced field length calculations mix speeds, forces, and distances. Consistent units are essential so the variables interact correctly and the result makes sense. The table below lists common symbols and their typical units.

Pick one unit system and stay with it. For example, if you enter weight in pounds and thrust in lbf, then keep distances in feet and speeds in knots. Mixed units will produce the wrong result even if the inputs look reasonable.

Common Issues & Fixes

Most issues come from inputs or unit mismatches. The physics is straightforward, but small mistakes can skew the result. Here are quick checks if the number looks off.

• If the balanced length is shorter on a hot day than on a cold day, recheck temperature units.
• If ASD and AGD do not intersect, your V1 bounds may be too narrow or the runway is too short.
• Large differences between dry and wet results often point to an incorrect braking coefficient.
• Declared distance limits (ASDA/TORA) can block feasible balances; verify airport data.

When in doubt, reduce the model to a simpler case: sea level, standard day, dry runway. Verify the trend with weight and temperature. Then add complexity one variable at a time.

FAQ about Balanced Field Length Calculator

What is balanced field length in simple terms?

It is the runway length where the distance to stop after an engine failure equals the distance to continue the takeoff and climb to the screen height.

Is this calculator approved for flight planning?

No. Use it for learning and early estimates. For dispatch or legal compliance, rely on AFM data and approved performance software for your aircraft.

How does V1 affect the result?

Raising V1 reduces accelerate–stop distance but increases accelerate–go distance. Lowering V1 does the opposite. The balanced point is where the two distances meet.

What if my runway is wet or contaminated?

Braking effectiveness drops and rolling resistance rises, which increases both distances. The calculator models this with different coefficients and warns if no balanced solution exists within declared distances.

Key Terms in Balanced Field Length

Balanced Field Length

The runway length where accelerate–stop distance equals accelerate–go distance for an engine failure at the decision speed.

Decision Speed (V1)

The speed by which the pilot must decide to reject or continue the takeoff after a critical engine failure.

Accelerate–Stop Distance (ASD)

The ground distance to accelerate from standstill to the decision speed and then stop, including reaction time and braking.

Accelerate–Go Distance (AGD)

The distance to accelerate to the decision speed, lose one engine, continue the takeoff on remaining power, lift off, and reach the screen height.

Screen Height

A fixed height above the runway, often 35 ft for turbines and 50 ft for many pistons, used to standardize takeoff performance.

Density Altitude

An effective altitude that combines pressure altitude and temperature, directly affecting thrust and aerodynamic forces.

Declared Distances

Airport-published runway lengths used for performance: TORA (takeoff run available), TODA (takeoff distance available), and ASDA (accelerate–stop distance available).

Runway Condition Code

A standardized index describing runway contamination and braking action, used to adjust performance for wet or contaminated surfaces.

References

Here’s a concise overview before we dive into the key points:

• eCFR: 14 CFR §25.109 Accelerate-stop distance
• eCFR: 14 CFR §25.113 Takeoff distance and takeoff run
• SKYbrary: Balanced Field Length
• EASA CS-25 Subpart B: Takeoff Speeds and Distances
• FAA AC 25-7D: Flight Test Guide for Transport Category Airplanes
• Airbus Flight Operations Briefing Notes: Aircraft Performance

These points provide quick orientation—use them alongside the full explanations in this page.