TORA – Takeoff Run Available: An In-Depth Glossary for Aviation Professionals

TORA (Takeoff Run Available): Definition and Core Concepts

Takeoff Run Available (TORA) is a declared runway distance fundamental to the safe and regulatory-compliant operation of aircraft during takeoff. According to ICAO Annex 14 and FAA AIM 2-3-3, TORA is defined as the length of runway declared available and suitable by the airport operator for the ground run of an aircraft during takeoff, beginning at the designated takeoff threshold and extending to the end of the runway surface. Notably, TORA does not include any stopway or clearway—these are excluded to ensure calculation precision for the actual paved surface on which the aircraft accelerates.

TORA is published in official sources such as national Aeronautical Information Publications (AIP), airport charts, and digital databases. Airport authorities establish this figure in accordance with regulations, considering runway geometry, local operational needs, and environmental constraints. For pilots, dispatchers, and performance engineers, TORA is the critical reference for evaluating safe takeoff given aircraft weight, weather, and any temporary runway restrictions.

TORA serves as the upper limit for the takeoff ground roll distance in all approved performance charts, flight management systems, and planning tools. Exceeding TORA is a regulatory violation and a safety risk. All takeoff performance calculations must be based strictly on the current TORA, including any temporary reductions due to NOTAMs or construction.

TORA in Airport Planning and Runway Design

TORA is a cornerstone of airport planning and influences both the design and operational capacity of runways. In airport master planning, the required runway length (and thus TORA) is determined based on the most demanding aircraft expected, prevailing weather, and airport elevation. Planners ensure the TORA is sufficient for all design aircraft under a variety of scenarios, analyzing runway geometry, threshold location, and the presence of any stopway or clearway.

In compliance with ICAO Annex 14 and national rules (such as FAA Part 139), each runway end must have a declared TORA published in the AIP. TORA is one of the four principal declared distances, along with Takeoff Distance Available (TODA), Accelerate-Stop Distance Available (ASDA), and Landing Distance Available (LDA). Proper calculation and publication of TORA is critical for safety and for maximizing airport capacity without compromising compliance.

TORA also affects the design of runway safety areas, obstacle limitation surfaces, and runway protection zones. The start and end points of TORA must be clear of obstacles, and safety margins must comply with ICAO and FAA standards. TORA impacts the planning of adjacent land uses, the boundaries of runway protection zones, and overlay districts. In short, TORA is a key data point in every facet of airport planning and design.

TORA in Flight Operations: Application and Performance Calculations

In daily flight operations, TORA is the operational reference for all takeoff ground run calculations. Before departure, pilots and dispatchers must ensure the aircraft’s required takeoff run is less than or equal to the published TORA, after accounting for any temporary reductions.

Modern flight planning software and onboard flight management systems rely on accurate TORA values. For intersection departures, the available TORA is reduced by the distance from the runway threshold to the intersection—a calculation that must be precise and reflected in performance planning. If a NOTAM reduces the runway, the operative TORA changes, and all calculations must use the new value.

Regulations require that only the published or currently operative TORA may be used for takeoff ground roll calculations. Pilots cannot use stopways or clearways for this purpose. Strict adherence is crucial for regulatory compliance and safety. Flight operations audits routinely check for correct TORA use, and errors may result in operational violations or safety incidents.

Declared Distances: TORA, TODA, ASDA, LDA—Comparative Analysis

The “declared distances” system underpins regulatory compliance and operational planning at every airport. Each distance serves a distinct purpose, defined in ICAO Annex 14 and FAA regulations.

Aircraft operators must use these distances as defined, referencing them in all performance and dispatch calculations. Regulatory audits and investigations routinely check for compliance.

TORA Determination, Calculation, and Adjustments

Airport operators determine the TORA for each runway end, subject to approval by the relevant aviation authority. TORA is based on the physical runway length between the takeoff threshold and the end of the paved surface, excluding any stopway or clearway.

Temporary conditions (runway repairs, obstacles, contamination) may reduce TORA. The airport operator issues NOTAMs and updates databases to reflect these changes. Flight crews and dispatchers must check NOTAMs before every departure and use the reduced TORA for calculations.

For intersection departures, subtract the distance from threshold to intersection from the published TORA to determine the available takeoff run. Runway surface condition does not change the declared TORA, though it may require increased takeoff distance per performance charts.

Workflow for determining TORA:

1. Identify intended runway end and direction.
2. Check latest AIP, charts, or database for published TORA.
3. Review NOTAMs for reductions or restrictions.
4. Subtract distance for intersection departures as needed.
5. Use resultant TORA in all performance calculations.
6. Verify all software and paper calculations are based on this TORA.

Regulatory Framework and Compliance for TORA

TORA is regulated globally by ICAO Annex 14 and, in the US, by FAA AIM 2-3-3 and Order 8260.19. National AIPs, chart supplements, and digital products must reflect the current, approved TORA for each runway end.

Only TORA may be used for takeoff ground run calculations. Performance software and FMS are designed to accept only valid, published TORA values, and regulatory audits check for proper use.

Incorrect use of TORA—such as using outdated data, not applying NOTAM reductions, or miscalculating intersection departures—can result in violations, incidents, or accidents. Operators must regularly audit databases and train staff on correct TORA application.

TORA in Land Use, Environmental Planning, and Community Impact

TORA plays a major role beyond operations and regulation. It is a primary factor in establishing runway protection zones (RPZs) and airport overlay districts—areas that must remain clear of incompatible land uses and hazards.

Airport planners use TORA to draw these zones in Airport Land Use Compatibility Plans (ALUCPs). Shortening TORA, due to obstacles or environmental constraints, can reduce airport capacity and economic viability. New development near the runway end may require a TORA reduction, triggering operational limitations and community engagement.

TORA also affects noise maps, safety studies, and environmental impact assessments, and any change in TORA may require public disclosure or new studies under environmental regulations.

TORA in Aviation Databases and Performance Software

Accurate, up-to-date TORA values are essential in aviation databases and software. Airlines and operators use products like Jeppesen, LIDO, or ATR FOS/SPS, integrating TORA from the AIP and updating for NOTAMs or airport changes.

Performance software uses TORA as a primary input for calculating limiting weights, reference speeds, and required distances for various takeoff configurations. When a NOTAM reduces runway length, the software allows users to input the new TORA, ensuring calculations are valid for current conditions.

Database management is critical. Errors or omissions in TORA values can compromise safety and compliance. Rigorous data management, including automated NOTAM feeds and regular audits, is standard for professional operators.

TORA: Practical Examples and Use Cases

• Standard Takeoff Calculation:
  A Boeing 737 is departing Runway 27. Published TORA is 3,200 m, TODA is 3,500 m (300 m clearway), ASDA is 3,300 m (100 m stopway). The pilot must use the TORA (3,200 m) for the takeoff ground roll, regardless of longer TODA/ASDA. If construction reduces TORA by 400 m, the new operative TORA is 2,800 m.

• Intersection Departure:
  A Gulfstream G650 departs from Taxiway Alpha, 1,000 feet from the threshold of Runway 15. Published TORA is 8,000 feet. For this intersection departure, available TORA is 7,000 feet.

• Software Implementation:
  A dispatcher loads the current airport database into ATR SPS. For each departure, the dispatcher checks the runway, NOTAMs, and selects the correct intersection. The software displays the correct TORA, allowing manual input if NOTAMs have reduced it.

• Land Use Planning:
  An airport updates its ALUCP. Using the declared TORA, planners delineate RPZs and ensure new development doesn’t encroach. Any reduction in TORA due to obstacles triggers boundary updates and community consultation.

Notes, Best Practices, and Safety Considerations

• Always Use Current Data: Source TORA from the latest charts, AIP, and NOTAMs.
• NOTAMs Override: Temporary restrictions override published values. Always use operative TORA.
• Intersection Departures: Subtract distance from threshold to intersection for TORA.
• Database Integrity: Regularly update and cross-check software databases.
• Training/Auditing: Train staff and audit usage for correct TORA application.
• Regulatory Compliance: Follow definitions and limits strictly.
• Land Use Planning: TORA affects RPZs and land use boundaries—update with any changes.

Glossary of Related Terms

• TORA (Takeoff Run Available): Runway length available for ground run, excluding stopway/clearway.
• TODA (Takeoff Distance Available): TORA plus clearway.
• ASDA (Accelerate-Stop Distance Available): TORA plus stopway.
• LDA (Landing Distance Available): Runway length available for landing, may be less than full runway.
• NOTAM (Notice to Air Missions): Official notice with timely operational information.
• AIP (Aeronautical Information Publication): Primary source for aeronautical data.
• ALUCP (Airport Land Use Compatibility Plan): Governs land development around airports.

Quick Reference Table: Declared Distances

Summary

TORA (Takeoff Run Available) is a foundational parameter in aviation, defined as the length of runway declared available for the ground run of an aircraft during takeoff, excluding stopway and clearway. Its precise determination, publication, and application are essential for safe, efficient, and compliant flight operations. TORA influences airport planning, runway design, operational performance calculations, and land use compatibility, and is strictly regulated by ICAO, FAA, and other authorities worldwide. Aviation professionals must ensure the use of current, correct TORA values for every operation, maintaining the highest standards of safety and compliance.