Runway PCN evaluation for London Luton Airport

Runway PCN evaluation for London Luton Airport

Fjori was commissioned by London Luton Airport Operations Limited in November 2017 to carry out a runway PCN evaluation and determination of residual life, such that the airport can plan for its next runway strengthening and/or resurfacing. The runway pavements at LTN range from 12 to 58 years old. The original 1959 concrete runway has been overlaid with asphalt numerous times, resulting in a relatively thick pavement. The evaluation was carried out to DMG27 using intrusive testing and evaluation of material stiffnesses using Indirect Tensile Stiffness Measurement. Lead times for access to the runway were such that it was not possible to include for HWD testing. Therefore, to take advantage of shorter mobilization times an intrusive testing specification was developed to meet the needs of limited lead times and access. Fjori also carried out an assessment of recent years’ friction testing data to determine post-rubber removal rates of deterioration in friction. This allowed Fjori to advise on maintenance options aligned with the timing for the reinstatement of friction. Fjori provided maintenance options at three horizons: Immediate, Short-Term rehabilitation (1-5 years life) and LongTerm rehabilitation (up to 20 years structural life).

Reference available on request

Key Project Details

• Single runway airport with limited nighttime availability for surveys

• Use of Heavy Weight Deflectometer testing not possible due to short lead times

• Visual inspection of existing repairs to establish residual life of repairs themselves

• Visual overview of AGL luminaire condition

• Existing data evaluation, including friction data

• Development of PCN evaluation strategy using data limited due to available access opportunities

• ACN/PCN capability assessment, based on existing and forecast aircraft fleet at LTN

• Use of FAARFIELD and DMG27 modeling for pavement designs

• All maintenance option designs are ICAO/EASA compliant

Share this case study