How to Determine Your Airport's Critical Aircraft

What “critical aircraft” means

The critical aircraft — the FAA’s term, used interchangeably with design aircraft — is the most demanding aircraft, or composite of aircraft, that makes regular use of a runway or the airport, and for which the facility is designed. It is the single reference from which the geometric design standards are selected.

The critical aircraft is not always one airframe. It can be a single aircraft type when one obvious airframe dominates, or it can be a composite assembled from the most demanding characteristics observed across several aircraft. A composite takes the worst-case value of each design parameter independently — for example, the approach speed from one type, the wingspan from another, and the undercarriage geometry from a third — so the resulting design envelope safely covers the whole regular-use fleet even though no single airplane hits every limit at once.

The 500-operation regular-use threshold

An aircraft counts toward the critical-aircraft determination only if it makes regular use of the facility. The FAA defines regular use as at least 500 annual operations of an aircraft — or of a group of aircraft with similar characteristics — at the runway or airport in question.

Three rules govern how those 500 operations are counted:

• One operation = one takeoff or one landing. A single arrival is one operation; a single departure is another.
• Count itinerant operations; exclude touch-and-go operations. Touch-and-go training cycles do not count toward the 500-operation regular-use threshold.
• Cumulate aircraft with similar characteristics. Individual types rarely reach 500 on their own, so airplanes with similar design-driving characteristics are grouped and their operations summed — for example, a family of comparable business jets is cumulated to test the threshold together rather than discarded one model at a time.

AvPlot follows this convention exactly: 500-operation regular use excluding touch-and-go, with cumulative grouping of similar-characteristics aircraft, and a 2× TFMSC normalization applied to the operations data source so that counts drawn from the FAA Traffic Flow Management System Counts reflect both halves of each operation pair.

How the critical aircraft drives the design code

Once you have identified the critical aircraft (or built the composite), you read its physical characteristics off the airframe data and translate them into a design code. Two codes come out of this step: the Runway Design Code (RDC) and the Taxiway Design Group (TDG).

Aircraft Approach Category (AAC)

The AAC is a letter (A through E) derived from the aircraft’s approach speed — 1.3 × Vstall in the landing configuration, i.e. V_ref. The category boundaries are fixed per the AC:

• A — less than 91 kt
• B — 91 to 120 kt
• C — 121 to 140 kt
• D — 141 to 165 kt
• E — 166 kt and above

Airplane Design Group (ADG)

The ADG is a Roman numeral (I through VI) taken from the larger of wingspan or tail height. The wingspan boundaries are fixed per the AC:

• I — less than 49 ft
• II — 49 to 79 ft
• III — 79 to 118 ft
• IV — 118 to 171 ft
• V — 171 to 214 ft
• VI — 214 ft and above

Taxiway Design Group (TDG)

The TDG is derived from the aircraft’s undercarriage geometry — the main gear width (MGW) and the cockpit-to-main-gear distance (CMG). The TDG drives taxiway width, taxiway shoulder, and fillet geometry, and is classified per AC 150/5300-13B Change 1, Table 1-4. Unlike the AAC and ADG, it speaks to how the airplane tracks through turns rather than how fast or how wide it is.

The Runway Design Code and the cascade

The Runway Design Code (RDC) combines the AAC, the ADG, and the approach visibility minimums for the runway end. The RDC then keys into nearly every dimensional standard in AC 150/5300-13B — runway width, RSA, ROFA, RPZ, runway-to-taxiway and taxiway-to-taxiway separation, and more. That is why the critical aircraft matters so much: it is the single input from which the entire design standard set cascades.

Determining it in practice

For an existing facility, the workflow runs in five steps:

1. Pull operations data. Source counts from the FAA Traffic Flow Management System Counts (TFMSC), applying the 2× normalization AvPlot uses so that the data reflects both takeoff and landing halves of each operation.
2. Group and test the threshold. Cumulate aircraft with similar characteristics and test each group against the 500-annual-operation regular-use threshold, excluding touch-and-go operations.
3. Identify the critical aircraft. Among the airframes that pass the regular-use test, take the most demanding aircraft — or assemble the composite from the most demanding individual characteristics across the qualifying fleet.
4. Read off the codes. Translate the critical aircraft into its AAC, ADG, and TDG using the boundaries above.
5. Carry the design code into the standards. Use the resulting RDC and TDG to select runway, safety-area, RPZ, separation, and taxiway dimensions from AC 150/5300-13B.

For a planned facility — a new runway, an extension, or an upgrade — the governing input is the forecast critical aircraft: the aircraft expected to make regular use of the facility in the design year, not just the one using it today. The same 500-operation regular-use logic applies, projected forward against the activity forecast.

This article is a reference summary for planning use, not a substitute for the governing FAA text. Citations refer to AC 150/5000-17 (Critical Aircraft and Regular Use Determination) and AC 150/5300-13B (Airport Design), Change 1, dated August 16, 2024. Operations counts and thresholds are illustrative of the method; always verify the critical-aircraft determination against current activity data and the governing ACs before issuing a design product. See the full airport planning glossary or the AvPlot toolkit.