<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<REGINFO_RIN_DATA xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" RUN_DATE="2026-04-06-04:00" xsi:noNamespaceSchemaLocation="https://www.reginfo.gov/public/xml/REGINFO_XML_Ver10262011.xsd">
    <RIN_INFO>
        <RIN>2120-AK31</RIN>
        <PUBLICATION>
            <PUBLICATION_ID>201410</PUBLICATION_ID>
            <PUBLICATION_TITLE>The Regulatory Plan and the Unified Agenda of Federal Regulatory and Deregulatory Actions</PUBLICATION_TITLE>
        </PUBLICATION>
        <AGENCY>
            <CODE>2120</CODE>
            <NAME>Federal Aviation Administration</NAME>
            <ACRONYM>FAA</ACRONYM>
        </AGENCY>
        <PARENT_AGENCY>
            <CODE>2100</CODE>
            <NAME>Department of Transportation</NAME>
            <ACRONYM>DOT</ACRONYM>
        </PARENT_AGENCY>
        <RULE_TITLE>Pilot Records Database (HR 5900)</RULE_TITLE>
        <ABSTRACT><![CDATA[This rulemaking would implement a Pilot Records Database as required by Public Law 111-216 (Aug. 1, 2010). Section 203 amends the Pilot Records Improvement Act (PRIA) by requiring the FAA to create a pilot records database that contains various types of pilot records. These records would be provided by the FAA, air carriers, and other persons who employ pilots. The FAA must maintain these records until it receives notice that a pilot is deceased. Air carriers would use this database to perform a record check on a pilot prior to making a hiring decision.]]></ABSTRACT>
        <PRIORITY_CATEGORY>Other Significant</PRIORITY_CATEGORY>
        <RIN_STATUS>Previously Published in The Unified Agenda</RIN_STATUS>
        <RULE_STAGE>Proposed Rule Stage</RULE_STAGE>
        <MAJOR>Undetermined</MAJOR>
        <UNFUNDED_MANDATE_LIST>
            <UNFUNDED_MANDATE>No</UNFUNDED_MANDATE>
        </UNFUNDED_MANDATE_LIST>
        <CFR_LIST>
            <CFR>14 CFR 118</CFR>
            <CFR>14 CFR 121</CFR>
            <CFR>14 CFR 125</CFR>
            <CFR>14 CFR 135</CFR>
            <CFR>14 CFR 91</CFR>
        </CFR_LIST>
        <LEGAL_AUTHORITY_LIST>
            <LEGAL_AUTHORITY>49 USC 106(g)</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 1155</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 40103</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 40113</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 40119</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 40120</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 41706</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 44101</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 44111</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 44701 to 44705</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 44709 to 44713</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 44715 to 44717</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 44722</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 45101 to 45105</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 46105</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 46306</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 46315</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 46316</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 46504</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 46507</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 47122</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 47508</LEGAL_AUTHORITY>
            <LEGAL_AUTHORITY>49 USC 47528 to 47531</LEGAL_AUTHORITY>
        </LEGAL_AUTHORITY_LIST>
        <LEGAL_DLINE_LIST/>
        <RPLAN_ENTRY>Yes</RPLAN_ENTRY>
        <RPLAN_INFO>
            <STMT_OF_NEED><![CDATA[<!DOCTYPE html>
<html>
<head>
</head>
<body>
<p>This rule implements a Pilot Records Database as required by Public Law 111-216. Section 203 of Public Law 111-216 amends the Pilot Records Improvement Act (PRIA) by requiring the FAA to create a pilot records database that contains various types of pilot records. These records would be provided by the FAA, air carriers, and other persons who employ pilots. The FAA must maintain these records until it receives notice that a pilot is deceased. Air carriers would use this database to perform a record check on a pilot prior to making a hiring decision.</p>
</body>
</html>]]></STMT_OF_NEED>
            <LEGAL_BASIS><![CDATA[<!DOCTYPE html>
<html>
<head>
</head>
<body>
<p>The legal basis for this rule is section 203 of the Airline Safety and Federal Aviation Administration Extension Act of 2010, Public Law 111-216, 124 Statute 2348 (2010).</p>
</body>
</html>]]></LEGAL_BASIS>
            <ALTERNATIVES><![CDATA[<!DOCTYPE html>
<html>
<head>
</head>
<body>
<p>The ARC proposed a phased implementation as an alternative to PRDs statutory requirement to enter all historical records dating from August 1, 2005. Instead, within 60&nbsp;days after the PRD launch date, air carriers and other persons would provide only the names, certificate numbers, and dates of birth of employees dating from the PRD launch date back to August 1, 2005. This information would be used to identify a pilot applicant's previous employer(s). The hiring air carrier would then make a paper PRIA request to those previous employers to obtain any records from before the launch date of PRD.</p>
</body>
</html>]]></ALTERNATIVES>
            <COSTS_AND_BENEFITS><![CDATA[<!DOCTYPE html>
<html>
<head>
</head>
<body>
<p>The Rulemaking Team believes that three methods of data entry would allow larger air carriers to take advantage of technology, thereby reducing costs, while allowing smaller air carriers the flexibility to enter data manually without the need for an information technology department and sophisticated computer knowledge.</p>
</body>
</html>]]></COSTS_AND_BENEFITS>
            <RISKS><![CDATA[<!DOCTYPE html>
<html>
<head>
</head>
<body>
<p>Any risk mitigation technique used to counter this additional security threat would significantly add to the time and cost required for the FAA to properly manage the air carrier user accounts and likely delay air carrier access to the PRD data. Several options were explored that would simultaneously provide appropriate security controls to protect unauthorized access to sensitive data while not impeding the air carriers from ready access to the PRD data.&nbsp;</p>
</body>
</html>]]></RISKS>
        </RPLAN_INFO>
        <TIMETABLE_LIST>
            <TIMETABLE>
                <TTBL_ACTION>NPRM</TTBL_ACTION>
                <TTBL_DATE>10/00/2015</TTBL_DATE>
            </TIMETABLE>
        </TIMETABLE_LIST>
        <ADDITIONAL_INFO>Costs and benefits are not yet determined.</ADDITIONAL_INFO>
        <RFA_REQUIRED>Undetermined</RFA_REQUIRED>
        <SMALL_ENTITY_LIST>
            <SMALL_ENTITY>No</SMALL_ENTITY>
        </SMALL_ENTITY_LIST>
        <GOVT_LEVEL_LIST>
            <GOVT_LEVEL>None</GOVT_LEVEL>
        </GOVT_LEVEL_LIST>
        <FEDERALISM>No</FEDERALISM>
        <ENERGY_AFFECTED>No</ENERGY_AFFECTED>
        <FURTHER_INFO_URL>www.regulations.gov</FURTHER_INFO_URL>
        <PUBLIC_COMMENT_URL>www.regulations.gov</PUBLIC_COMMENT_URL>
        <PRINT_PAPER>No</PRINT_PAPER>
        <INTERNATIONAL_INTEREST>No</INTERNATIONAL_INTEREST>
        <AGENCY_CONTACT_LIST>
            <CONTACT>
                <FIRST_NAME>Bryan</FIRST_NAME>
                <LAST_NAME>Brown</LAST_NAME>
                <AGENCY>
                    <CODE>2120</CODE>
                    <NAME>Federal Aviation Administration</NAME>
                    <ACRONYM>FAA</ACRONYM>
                </AGENCY>
                <PHONE>405 954-4513</PHONE>
                <EMAIL>bryan.w.brown@faa.gov</EMAIL>
                <MAILING_ADDRESS>
                    <STREET_ADDRESS>6424 S Denning Ave,</STREET_ADDRESS>
                    <CITY>Oklahoma City</CITY>
                    <STATE>OK</STATE>
                    <ZIP>73169</ZIP>
                </MAILING_ADDRESS>
            </CONTACT>
        </AGENCY_CONTACT_LIST>
    </RIN_INFO>
</REGINFO_RIN_DATA>
