Collecting, Applying, and Maintaining Pavement Condition Data at Airports

Many airports have developed pavement management programs; however, there are challenges related to the collection and use of pavement condition data. Data is being collected in accordance with American Society for Testing and Materials (ASTM) D5340 and in a number of different methods and levels: network-level evaluation, project evaluation, and maintenance and repair. The collection of pavement condition data and the reporting of Pavement Condition Index (PCI) are time-consuming and expensive. Obstacles such as aircraft operations that limit the ability to collect the data may be addressed by evolving technologies. The data is used in a number of applications, including determining maintenance and repair; however, the industry is not realizing the full value of the data being collected. Also, the data is frequently not reported in a manner that is easily usable by airports in creating their operational, maintenance and capital plans. Airports need better guidance to determine the best methods to use in the collection, interpretation, application, and maintenance of pavement condition data. The objective of this research is to develop guidelines for airports that identify evidence-based best practices in collecting and using airfield pavement condition data. As part of the pavement management process this data is used to determine the PCI and how it impacts operations, maintenance, and capital improvement programs (see Note); therefore, the resource document shall have three main components: (1) data collection and interpretation, (2) data application, and (3) data maintenance. The guidelines should include, at a minimum: An introductory section that describes the importance of pavement condition data for the pavement management process; Guidance on how decision makers can use the rigid and flexible pavement condition data to make the most efficient use of funding and personnel resources; Description of a process to integrate the pavement condition data into an airport’s operating budget and capital improvement program; Methods to capture the data including automated data collection technologies and the advantages and disadvantages of each methodology; Case study examples of successful practices and lessons learned of the collection and use of pavement condition data at a variety of airport types and sizes; Consideration of adaptable landside and highway pavement applications and processes for using PCI; Opportunities and challenges for collaboration and information sharing for those generating, interpreting, and using the pavement condition data; Integration of the data into geographic information system (GIS); Identification and discussion of performance measurements outside the ASTM D5340 standard that could benefit the pavement management process, e.g., longitudinal profiles, deflection measurements; Exploration of the impact of new technologies on the future revisions of data collection standards and processes, e.g., ASTM D5340, Federal Aviation Administration (FAA) ACs. The work proposed must be divided into tasks and proposers must describe the work proposed in each task in detail. The research plan should include appropriate interim deliverables that will require Airport Cooperative Research Program (ACRP) approval, including at a minimum: (1) an annotated list of literature review references; (2) a select listing of airports that have collected and implemented pavement condition data representative of different types and sizes of airports including at least 5 case studies; (3) a draft table of contents with an annotated summary of each section of the resource document; (4) a decision tree or equivalent implementation method to direct airports of different types and sizes to appropriate practices for pavement condition data collection, use and maintenance; and (5) an interim report that describes work done in early tasks with an updated work plan for remaining tasks, including a draft sample of several chapters of the resource document and the case studies. The research plan should build in other appropriate checkpoints with the ACRP panel, including at a minimum (1) a kick-off teleconference meeting to be held within 1 month of the Notice to Proceed; (2) one face-to-face interim report meeting to review the results of the interim report; and (3) web-enabled teleconferences tied to the panel review and ACRP approval of other interim deliverables deemed appropriate. The final deliverables will include: (1) the guidelines that meet the requirements as stated in the objective; (2) presentation templates that can be used to educate board members, operations, maintenance, and planning & engineering staff on PCI data and how it can be used in airport decision making; and (3) A stand-alone technical memorandum titled “Implementation of Research Findings and Products”.


  • English


  • Status: Proposed
  • Contract Numbers:

    Project 09-17

  • Sponsor Organizations:

    Airport Cooperative Research Program

    Transportation Research Board
    500 Fifth Street, NW
    Washington, DC    20001

    Federal Aviation Administration

    800 Independence Avenue, SW
    Washington, DC  United States  20591
  • Project Managers:

    Schatz, Theresia

  • Start Date: 20170204
  • Expected Completion Date: 20180504
  • Actual Completion Date: 0
  • Source Data: RiP Project 41437

Subject/Index Terms

Filing Info

  • Accession Number: 01625541
  • Record Type: Research project
  • Source Agency: Transportation Research Board
  • Contract Numbers: Project 09-17
  • Files: TRB, RiP
  • Created Date: Feb 4 2017 1:00AM