Runway Length Requirement Calculator

Runway length requirements depend on aircraft weight, density altitude, wind component, slope, and surface condition. This calculator takes your aircraft's published POH takeoff or landing ground roll at a reference condition and applies the FAA-recommended density altitude correction (approximately 10% increase per 1,000 ft of density altitude above the POH reference) plus an optional safety margin. Always consult your specific aircraft's POH performance charts for authoritative figures. This tool is for planning and educational use only.

Published POH takeoff or landing ground roll at standard conditions
Density altitude at which the POH figure was obtained (often sea level)
Use the density altitude calculator to find this value
FAA recommends 1.25 minimum; enter 1.0 for no margin
1,680.00 ft
2,100.00 ft
4,000.00 ft

Runway length correction formula (FAA rule of thumb)

DA_increase = actual_DA - POH_reference_DA
correction_factor = 1 + (DA_increase / 1,000) x 0.10
corrected_distance = POH_ground_roll x correction_factor
final_distance = corrected_distance x safety_factor

The 10% per 1,000 ft rule is a FAA-endorsed approximation from the Pilot's Handbook of Aeronautical Knowledge. For precise calculations, always use the actual performance charts in the aircraft POH, entering the correct pressure altitude and temperature columns.

When to be especially careful

  • High elevation airports: density altitude at an 8,000 ft airport on a 30 degree Celsius day can exceed 12,000 ft.
  • Soft or wet grass surfaces increase ground roll by 15-45% compared to dry hard surface.
  • Downhill runway reduces takeoff distance but adds to landing roll; always compute both.
  • Weight: below-maximum-gross-weight performance is significantly better; check your actual weight.
  • Obstacle clearance: if trees, terrain or structures are within the departure path, use the 50-ft obstacle distance, not ground roll.

Runway length requirement calculator: frequently asked questions

How does density altitude affect runway length required?

Higher density altitude means lower air density, which reduces engine power and aerodynamic lift. As a result, the aircraft needs more speed and therefore more runway distance to reach flying speed. A commonly used FAA rule of thumb is that takeoff distance increases approximately 10% for every 1,000 ft increase in density altitude above the POH baseline.

What is the 50-foot obstacle clearance distance?

Published takeoff and landing distances in FAA-format POHs are usually given in two forms: ground roll (the distance to lift off or stop on the runway surface) and total distance over a 50-foot obstacle. The obstacle distance includes the climb out or approach path needed to clear a 50-foot obstacle at the runway end. Always use the appropriate value for your actual runway conditions.

What correction factor should I apply for temperature?

The FAA recommends using density altitude, not just elevation, to correct POH performance charts. The POH charts already account for altitude and temperature if you enter both correctly. If you only have the sea-level ground roll figure, the simplified correction is to increase distance by 10% per 1,000 ft of density altitude. This calculator applies that adjustment.

Should I use a safety margin on top of the calculated distance?

Yes. The FAA recommends applying a 1.25 safety factor (25% additional distance) to account for pilot technique variability, surface conditions, and other real-world factors. Some operators apply 1.5 (50%) for additional safety, particularly for off-airport operations or student pilots.

Does runway slope affect required distance?

Yes. An upslope runway increases takeoff distance (you are climbing during the roll) and decreases landing distance. A downslope runway decreases takeoff distance but increases landing distance. The FAA POH typically provides slope correction factors. As a rule of thumb, each 1% of upslope increases takeoff distance by approximately 10%.

Official sources

Reviewed by the CalculatorHub team, edited by James Graham, 14 June 2026. See our methodology.