BACKGROUND

Runway incursions are persistent hazards in airport operations as evidenced by their consistent occurrence. While much study has been conducted on runway incursions, data collection and mitigation efforts have focused on towered airports. Thus, the risk of collisions due to runway incursions in non-towered environments is not well known despite runway incursions occurring in such environments.   

Airport practitioners at non-towered airports face obstacles in collecting data related to runway incursions. Without the data, it is challenging, if not impossible, to assess these risks. Airport practitioners at non-towered airports have limited familiarity with data-collection methodologies, associated risk frameworks, and the needs of stakeholders. Research is needed to assess the risks of runway incursions so that non-towered airport operators, regulators, and consultants can evaluate these risks while fostering the development of innovative tools and mitigation strategies more accurately.

OBJECTIVES

The objectives of this research are to (1) develop a guide; (2) produce spreadsheet templates that enable airport operators to assess the safety risk for runway incursions at non-towered airports (Special Note A); and (3) create an introductory video. The guide will include at a minimum the following:  

• Methodology for identifying data sources to assess runway incursion risks (Special Note B);
• Recommended practices for selecting critical data fields in runway incursion analytics;
• Methodology for correlating and analyzing collected data to evaluate runway incursion risks;
• Evaluation of existing runway incursion assessment strategies at towered airports that may be adapted for non-towered airports;
• References to key standards and industry resources (e.g., Federal Aviation Administration (FAA) Advisory Circular AC 90-66C, relevant ACRP reports);
• Common internal and external stakeholders at non-towered airports, including their roles and responsibilities;
• Case study plan and rationale (Special Note C);
• Ready-to-use spreadsheet template with a sample dataset from a non-towered airport;
• Summary of existing technologies for on-airfield data collection;
• Single-pilot site validation for airfield data collection and integration into the spreadsheet template (Special Note D);
• Introductory video demonstrating use of the spreadsheet template and risk assessment toolkit; and
• Slide deck for executive communication and stakeholder buy-in.

The introductory video should run 4–5 minutes and focus on two key elements: (1) how to use the spreadsheet template and (2) implementing runway risk assessment for at least one non-towered airport.

RESEARCH PLAN

The ACRP is seeking the insights of proposers on how best to achieve the research objectives. Proposers are expected to describe research plans that can realistically be accomplished within the constraints of available funds and subaward time. Proposals must present the proposers' current thinking in sufficient detail to demonstrate their understanding of the issues and the soundness of their approach to meeting the research objectives. The work proposed must be divided into tasks and proposers must describe the work proposed in detail.

The research plan shall comprise the appropriate interim deliverables for ACRP review and approval, including

• Literature review and data collection plan;
• Interim report that provides a description and analysis of each research task completed to date;
  • An annotated outline of the guide
  • Potential problem statement(s) based on research gaps
• Case study plan and rationale; and
• Data collection techniques and technologies for assessing risk of runway incursions.

Note: For each problem statement approved by the panel, the research team will use the ACRP problem statement process (https://trb.org/ACRP/problemstatements.aspx) to submit the problem statement on behalf of the project panel. The development and submission of problem statements should occur as soon as possible, taking into account the ACRP problem statement annual submission deadline of early April.

 Note: The interim report should be of sufficient detail and clarity to allow the panel to confirm successful accomplishment of the technical aspects of the research plan performed to date.

 The research plan shall include the following checkpoints with the ACRP panel:

• Kick-off web meeting to be held within 1 month of the Notice to Proceed; 
• Web meeting to discuss and approve the literature review and data collection report;
• One face-to-face interim deliverable review meeting;
• Web-enabled teleconferences tied to the panel review and ACRP approval of other interim deliverables as deemed appropriate;
• Web meeting to review pilot results and the spreadsheet template; and
• Web meeting to review the video.

 Final deliverables shall include: 

• Guide;
• Slide deck for executive communication and stakeholder buy-in;
• Runway risk assessment spreadsheet template;
• Four to five minute video;
• A technical memo titled “Implementation of Research Findings and Products” (see Item IV);
• Key Findings form (see Item V); and
• A conduct of research report documenting the entire research effort, results, and analysis (see Item VI).

Note: Following receipt of the draft final deliverables, there should be 3 months for ACRP review and comments and for the research team’s preparation of the final deliverables. For budgeting purposes, proposers should assume that ACRP will provide access to web-enabled teleconference services. ACRP will pay panel members’ travel costs for the face-to-face interim meeting. Proposers should assume that the meeting will be held in Washington, DC.

SPECIAL NOTES

A.  For the purposes of this study, non-towered airports are defined as airports that don’t have control towers or have part-time control towers.

B.  Proposers should provide their initial thinking on potential commercial and open-source data sources for collecting runway incursion data at non-towered airports.

C. Proposers should provide their initial thinking on possible case studies across non-towered and part-time controlled airports.

D. Proposers should provide their initial thinking on potential data capture sources, for e.g., video, automatic dependent surveillance-broadcast (ADSB), common traffic advisory frequency (CTAF), radar, and electronic flight bag (EFB). 

< < < IMPORTANT > > >

I. The brochure Information and Instructions for Preparing Proposals for the Transportation Research Board’s Cooperative Research Programs includes extensive guidance on the preparation of acceptable proposals for submission to CRP. Revisions to these instructions are highlighted in yellow within that document.

II. Proposals will be rejected if any of the proposed research team members work for organizations represented on the project panel. The panel roster for this project can be found at < https://www.mytrb.org/OnlineDirectory/Committee/Details/7404>. Proposers may not contact panel members directly; this roster is provided solely for the purpose of avoiding potential conflicts of interest.

III. The text of the final deliverable is expected to be publication ready when it is submitted. It is strongly recommended that the research team include the expertise of a technical editor as early in the project timeline as possible. See Appendix F of the Procedural Manual for Subawardees Conducting Research in the Transportation Research Board’s Cooperative Research Program for technical editing standards expected in final deliverables.

IV. The required technical memorandum titled, “Implementation of Research Findings and Products” should provide: (a) recommended tactics to facilitate implementation; (b) possible institutions/partners and their potential implementation role; (c) potential impediments to successful implementation; (d) metrics to measure extent of product use and benefit; (e) related FAA guidance; and (f) appendices as needed. An annotated template for the memorandum is found here: https://onlinepubs.trb.org/onlinepubs/acrp/ACRP_Implementation_TechMemo_Template_2019.pdf.

V. The Key Findings form can be found here: https://survey.alchemer.com/s3/8448606/Key-Findings-Submission-Form. Proposers will be asked to provide: (a) the value of the research product; (b) key data; and (c) interesting findings that can be used to help promote and market the product(s).

VI. The summary of the problem statement(s) objective(s) should be included in the interim report and conduct of research report, along with the decision(s) of the panel about each problem statement.

VII. The National Academies have an ethical and legal obligation to provide proper attribution whenever material from other sources is included in its reports, online postings, and other publications and products. TRB will review all Cooperative Research Programs draft final deliverables using the software iThenticate for potential plagiarism. If plagiarized text appears in the draft final deliverable, the research team will be required to make revisions and the opportunity to submit future proposals may be affected.