Structural engineering and detailing for airport programmes.

Building inside a running airport

An airport programme is rarely the hardest structure on its own drawing board. What makes it hard is that almost nothing can be built at the pace a normal site would allow, because the airport underneath it never stops operating.

• Work happens in windows, not days. Airside structures are often only accessible during night possessions or scheduled closures, so a package has to be sequenced to what a shift can actually complete before the apron reopens.
• Airside access is controlled. Security zoning and airside permitting govern who can be on a stand or apron and when, and that constraint reaches back into how a package is programmed and issued.
• Terminal roofs carry the geometry. Long-span roof structures over check-in halls, piers and concourses are rarely orthogonal, and the steel has to be detailed to a geometry that was modeled, not assumed.
• Baggage and jet bridge interfaces arrive late. Baggage handling systems and passenger boarding bridges are specified by their own suppliers, on their own programme, and the structural package has to absorb their loads and fixings without a redesign.
• Every discipline touches the same steel. Mechanical, fire, security and IT systems all fix back to the same structure, so the coordination load on an airport package is larger than the structure itself would suggest.

The structures an airport programme covers

An airport is a site, not a structure. A single programme usually runs several kinds of building at once, and each is governed by something different even though they share a fence line and a permitting regime.

• Terminals and concourses — long-span roofs over check-in, security and departure halls, with mezzanines and retail decks hung below them, and floor structures carrying crowd loading and queue equipment rather than a uniform office live load.
• Piers, satellites and gate structures — repetitive bays that reward being detailed once and repeated properly, with passenger boarding bridge supports and baggage runs cutting through the same zone.
• Passenger transfer equipment — escalators, travelators, lifts and link bridges, each arriving as a supplier package with its own pit dimensions, fixing loads and dynamic requirements the structure has to accept without a redesign.
• Car parks and forecourt structures — multi-storey car parks in precast or composite construction, canopies and drop-off decks. Charging installations added later bring plant, cable containment and a revised fire loading assumption onto a deck detailed before any of it existed.
• Airside support buildings — hangars, maintenance facilities, ground support equipment stores, fire stations and energy centres: long-span or heavily serviced, built under the same access restrictions as the terminal.
• Structures inside the movement area — apron slabs and pits, drainage chambers, culverts, service ducts, blast screens and the bases for masts and gantries, where the pavement design belongs to the civil engineer and the reinforcement, cover, joint and fixing detail belongs to the structural set.

The packages an airport programme needs

Most airport packages combine a long-span steel roof with heavily loaded concrete below it, all coordinated against systems that are still being specified.

• Steel detailing for terminal and pier roof structures, canopies, airbridge support steel and plant decks, issued with the fabrication data the shop runs on.
• Rebar and concrete detailing for apron slabs, pile caps and foundations under piers and jet bridges, where loading is heavy and access for a correction is limited.
• BIM modeling and coordination across structure, architecture, mechanical and the baggage and security systems that fix back to the same frame.
• Drafting and CAD production for the controlled issue set, sequenced to match the possession calendar rather than a single fixed handover date.

Standards and authority requirements

An airport package sits under two layers of standard at once: the structural code of the country of construction, and the aviation authority's own design and safety requirements.

Structurally, that is AISC 360 and AISC 303 in North America, the Eurocodes with the relevant National Annex across Europe, BS EN Eurocodes with the UK National Annex, or AS 4100 and AS 3600 in Australia. Authority-side, the recurring references are ICAO Annex 14 for aerodrome design, the FAA Advisory Circular 150/5300 series in the United States, and national civil aviation authority standards elsewhere, which govern clearances, obstacle limitation surfaces and the separation a structure has to keep from the movement area.

Those authority constraints are agreed at intake, alongside the governing structural code, and configured into the checks rather than applied by convention on the day a drawing is issued.

Airfield pavement design itself runs to the FAA AC 150/5320 series or the ICAO Aerodrome Design Manual and normally stays with the civil designer. What reaches a structural drawing is the reinforcement, joint, cover and fixing detail of the slabs, pits and buried structures inside the movement area, plus the clearances those documents fix. Information management runs to ISO 19650 inside the operator's own common data environment, with numbering and distribution set by the programme, and the drawing production itself is controlled to ISO 9001 — which matters more than usual here, because the same package is often reviewed by the operator, the airline and the aviation authority in parallel, and every one of them expects to be looking at the same revision.

Where the programme breaks, and what we check

Airport packages fail in a small number of predictable places, and those are where the automated checks concentrate.

• Late supplier data. Baggage handling and jet bridge loads and fixings are checked against the current supplier issue every time it changes, and the affected steel is flagged rather than silently carried forward.
• Clash between disciplines. Mechanical, security and IT fixings onto the same structure are reconciled between the structural, architectural and services models before issue, not discovered on the apron.
• Obstacle limitation surfaces. Roof and plant heights are checked against the clearances the aerodrome design sets, so a plant upgrade late in the programme does not quietly breach a surface it was never checked against.
• Possession readiness. Packages are sequenced and issued against the possession calendar, so a crew arriving for a night window has a complete, checked issue waiting for them rather than a partial one.

The check record is issued with the package, and a senior engineer reviews and signs it before it goes out.

Delivering against possessions

An airport programme does not forgive a late issue the way other sectors sometimes can, because a missed possession is not a missed day, it is a missed window that may not come round again for weeks. The repetitive production behind each package is AI-driven, so a re-issue triggered by a late baggage or jet bridge revision is turned around in the time it takes to check it, not redraw it.

What does not change is accountability. BuildTwin is the delivery partner for the whole structural scope, one delivery lead, one register, one programme, working to your possession calendar and inside your common data environment, so a night window is met with a complete package rather than a partial one and an explanation.