Taxiway Design Modifications: What Triggers a Redesign?
An existing taxiway can be perfectly serviceable and still need a redesign — not because it is worn out, but because the standard, the fleet, or the safety expectation moved. For a consultant scoping a taxiway improvement, the first question is not “how do we lay it out?” but “what is forcing the change, and how far does that force reach?” This article walks the triggers that put a taxiway on the redesign list under AC 150/5300-13B Change 1, and how each one scopes the work. It is a companion to taxiway design, which covers the underlying standards.
The five triggers
Most taxiway redesigns trace to one of five causes. They are not mutually exclusive — a single project often combines a fleet change with a safety fix — but naming the trigger tells you which standards table to open and how wide the work spreads.
| Trigger | What it changes |
|---|---|
| New design aircraft | ADG and/or TDG shift → separation, width, and fillet geometry |
| Runway-incursion risk | Intersection geometry, direct-access removal, hot-spot mitigation |
| Separation shortfall | Centerline-to-centerline or centerline-to-object distances below standard |
| Pavement rehabilitation | Reconstruction that obligates current-standard geometry |
| Capacity / circulation | New exits, bypass or parallel taxiways to relieve delay |
Trigger 1 — a new design aircraft
The most common driver. When the critical aircraft for a taxiway changes — a larger type starts regular use, or a forecast brings one — both design groups can move, and they drive different things:
- A higher ADG (a wider wingspan band) raises the separation requirements: runway-centerline-to-taxiway, taxiway-to-taxiway, and taxiway/taxilane-to-object. If the existing separation no longer meets the new ADG standard, the taxiway may have to move.
- A higher TDG (a larger gear-geometry band) raises the pavement width, taxiway edge safety margin, shoulder width, and fillet geometry at every intersection the aircraft uses.
The scoping discipline is to read each off the right table: separation against the ADG, cross-section and fillets against the TDG. A redesign that bumps width for the new TDG but leaves an out-of-standard separation has solved half the problem.
Trigger 2 — runway-incursion risk
A large share of modern taxiway redesigns are safety-driven, not fleet-driven. The AC’s taxiway-geometry guidance is built around preventing runway incursions, and it flags specific layouts for correction even when the taxiway is otherwise fine:
- Direct access from an apron to a runway — a taxiway that lets an aircraft taxi straight onto a runway without a turn removes a decision point. The fix is to offset or interrupt the path so the pilot must consciously turn.
- Wide expanses of pavement at intersections, which blur where the aircraft should be — resolved with defined taxiway routes and pavement-edge markings.
- Complex or high-energy intersections — three-or-more runway/taxiway nodes meeting at one point. The guidance favors keeping intersections simple (the “three-node” idea: limit how many paths converge) and avoiding crossings near the high-energy middle of a runway.
- Acute-angle runway entrances that give a poor view of the runway environment.
- Published airport hot spots — locations the FAA and operators have flagged for confusion; geometry redesign is a primary mitigation.
These triggers scope differently from a fleet change: they are about the shape of the junction, not the size of the aircraft, and they often justify a redesign on their own.
Trigger 3 — a separation shortfall
Sometimes the fleet has not changed but a survey or an ALP update reveals that an existing separation is simply below the current standard for the runway’s design code — a legacy taxiway built to an older AC. A nonstandard separation is not automatically rebuilt overnight; it is documented and dispositioned, and a redesign is scoped when a project, a funding cycle, or a safety case makes correcting it practical. The key is that the shortfall is measured against the current ADG-keyed standard, pulled fresh, not carried over from the prior plan.
Trigger 4 — pavement rehabilitation
This trigger surprises people: a taxiway can land on the redesign list because it is being reconstructed. When pavement is rehabilitated to the point of reconstruction — especially with federal funding — the work is generally expected to bring the geometry up to current design standards, not simply repave the old footprint. A mill-and-overlay may not trigger it; a full-depth reconstruction usually does. So a project that began as a pavement-condition fix can grow to include realigned geometry, corrected fillets, or relocated centerlines. Scoping this early avoids a mid-design surprise.
Trigger 5 — capacity and circulation
Finally, a taxiway may be redesigned to move traffic better: adding high-speed (acute-angle) exits to clear a runway faster, building a parallel or bypass taxiway to remove back-taxiing, or reconfiguring a holding bay. These come out of a capacity analysis rather than a standards violation, and they are usually the lower-cost capacity fixes weighed before any new runway.
Scoping a redesign — the order of questions
- Name the trigger. Fleet, safety, separation, pavement, or capacity — it determines which tables and which reach.
- Re-establish the design aircraft and read both its ADG and TDG fresh.
- Pull the standards — separation by ADG, cross-section and fillets by TDG — from the current AC, not the prior drawing.
- Check the safety geometry — direct access, intersection complexity, hot spots — independent of aircraft size.
- Bound the project — confirm whether a reconstruction scope pulls in current-standard compliance for adjacent geometry.
Done in that order, the redesign scope follows from the trigger instead of expanding mid-design: you change what the cause requires, verify it against the current standards, and document why each move was needed.
This article is a reference summary for planning use, not a substitute for the governing FAA text. Citations refer to AC 150/5300-13B Change 1 (Airport Design) — Table 4-1 (separation), Table 4-2 (taxiway width), Appendix J (fillets), and its runway-incursion-mitigation geometry provisions — and AC 150/5320-6 (pavement design). Always verify dimensions and the scope-of-compliance trigger against the current governing documents and your FAA Airports District Office before issuing a design product. See the full airport planning glossary or the AvPlot toolkit.