AC 120-68J Pilot Records Database and Pilot Records Improvement Act
This advisory circular (AC) provides operators and pilots with guidance regarding Title 14 of the Code of Federal Regulations (14 CFR) part 111: the Pilot Records Database (PRD) and the Pilot Records Improvement Act of 1996 (PRIA). The PRD facilitates the sharing of pilot records among pilot employers in a clearinghouse managed by the Federal Aviation Administration (FAA). In accordance with part 111, all 14 CFR part 119 certificate holders, operators that conduct operations in accordance with a fractional ownership program (fractional ownerships), and air tour operators holding a Letter of Authorization (LOA) issued in accordance with 14 CFR part 91, § 91.147 are required to access the PRD and evaluate the available data for each individual pilot candidate prior to making a hiring decision. Also in accordance with part 111, part 119 certificate holders, entities conducting public aircraft operations (PAO), air tour operators, fractional ownerships, and other specific entities operating under part 91 or 14 CFR part 125 are required to report records on individuals employed as pilots into the PRD. The PRD contains employer and FAA records on an individual’s performance as a pilot for the life of the individual. Records contained within the database would only be permitted to be used as a hiring aid in an operator’s decision-making process for pilot employment. This AC should be used in combination with the appropriate PRD user guides. For more information contact [email protected]
Text read by OCR from a scanned file (12 of 136 pages). Check the original, as some words may be misread.
U.S. Department of Transportation Federal Aviation Administration
Advisory Circular
Subject: Pilot Records Database and Pilot
Records Improvement Act
Date: 6/28/21 AC No: 120-68J Initiated by: AFS-600 Change:
This advisory circular (AC) provides operators and pilots with guidance regarding Title 14 of the Code of Federal Regulations (14 CFR) part 111: the Pilot Records Database (PRD) and the Pilot Records Improvement Act of 1996 (PRIA). The PRD facilitates the sharing of pilot records among pilot employers in a clearinghouse managed by the Federal Aviation Administration (FAA). In accordance with part 111, all 14 CFR part 119 certificate holders, operators that conduct operations in accordance with a fractional ownership program (fractional ownerships), and air tour operators holding a Letter of Authorization (LOA) issued in accordance with 14 CFR part 91, § 91.147 are required to access the PRD and evaluate the available data for each individual pilot candidate prior to making a hiring decision. Also in accordance with part 111, part 119 certificate holders, entities conducting public aircraft operations (PAO), air tour operators, fractional ownerships, and other specific entities operating under part 91 or 14 CFR part 125 are required to report records on individuals employed as pilots into the PRD. The PRD contains employer and FAA records on an individual’s performance as a pilot for the life of the individual. Records contained within the database would only be permitted to be used as a hiring aid in an operator’s decision-making process for pilot employment. This AC should be used in combination with the appropriate PRD user guides.
Robert C. Carty Deputy Executive Director, Flight Standards Service
ii
CONTENTS Paragraph Page
Chapter 1. General … 1-1
1.1 Purpose of This Advisory Circular (AC) … 1-1
1.2 Audience … 1-1
1.3 Where You Can Find This AC … 1-2
1.4 What This AC Cancels … 1-2
1.5 Related 14 CFR Parts … 1-2
1.6 Applicability … 1-2
Chapter 2. Pilot Records Database … 2-1
2.1 Definitions … 2-1
2.2 Applicability … 2-2
2.3 Background … 2-3
2.4 Records Contained in the PRD … 2-4
2.5 Accessing the PRD … 2-7
2.6 Review and Evaluation of Records … 2-16
2.7 Special Circumstances Involving Few or No Records to Evaluate … 2-22
2.8 Entering Company Records in the PRD … 2-24
2.9 Using a Proxy to Meet the Requirements of Part 111 … 2-45
2.10 Transitioning From PRIA to the PRD … 2-45
2.11 FAA Inspectors’ Access to PRD Records … 2-48
Chapter 3. Pilot Records Improvement Act of 1996 … 3-1
3.1 Purpose of This Chapter … 3-1
3.2 How to Use This Chapter … 3-1
3.3 PRIA Background … 3-1
3.4 Applicability … 3-2
3.5 Company Records vs. PRIA Records … 3-3
3.6 The Request Process … 3-4
3.7 Designated Agent (DA) … 3-5
3.8 Best Practices … 3-5
3.9 Information for the Pilot-Applicant … 3-5
3.10 Information for the Hiring Employer on PRIA Procedural Considerations … 3-9
iii
3.11 Information for Previous Employers Responding to PRIA Records Requests … 3-17
3.12 PRIA Considerations for the Hiring Employer … 3-22
Chapter 4. Administrative Information … 4-1
4.1 PRIA-Related Regulations … 4-1
4.2 Definitions … 4-1
4.3 Commonly Used Acronyms and Abbreviations … 4-2
4.4 Other PRIA Resources … 4-3
4.5 PRIA Contact Information … 4-3
4.6 AC Feedback Form … 4-3
Appendix A. Training, Qualification, and Proficiency Records … A-1
Appendix B. Drug and Alcohol Records … B-1
Appendix C. Final Disciplinary Action Records … C-1
Appendix D. Employment History Records … D-1
Appendix E. Verification of Motor Vehicle Driving Record Search and Evaluation … E-1
Appendix F. Example PRD Output of Records Report … F-1
Appendix G. Forms … G-1
List of Tables
Table 2-1. PRD Overview of Record Reporting by Population … 2-7
Table 2-2. Record Reporting by Operator … 2-25
Table A-1. Data Fields … A-1
Table A-2. Part 121 Subparts N and O Training Record Options … A-3
Table A-3. Part 121 Subpart Y Training Record Options … A-6
Table A-4. Part 135 Training Record Options … A-9
Table A-5. Part 125 Testing Record Options … A-11
Table A-6. Part 91 Subpart K Fractional Ownership Operator’s Training Record Options ... A-12
Table A-7. Public Use, Air Tour, and Corporate Operators Record Options … A-14
Table B-1. Data Fields … B-1
Table B-2. Report Type Options … B-2
Table C-1. Data Fields (all required) … C-1
Table D-1. Data Fields … D-1
Table D-2. Assignment to Duty (entry of this record is optional) … D-2
Table E-1. Data Fields … E-1
1.2 Audience.
CHAPTER 1. GENERAL
1.1 Purpose of This Advisory Circular (AC). This AC provides operators and pilots with guidance regarding Title 14 of the Code of Federal Regulations (14 CFR) part 111: the Pilot Records Database (PRD) and the Pilot Records Improvement Act of 1996 (PRIA). The PRD facilitates the sharing of pilot records among pilot employers in a clearinghouse managed by the Federal Aviation Administration (FAA). In accordance with part 111, all 14 CFR part 119 certificate holders, operators that conduct operations in accordance with a fractional ownership program (fractional ownerships), and air tour operators holding a Letter of Authorization (LOA) issued in accordance with 14 CFR part 91, § 91.147 are required to access the PRD and evaluate the available data for each individual pilot candidate prior to making a hiring decision. Also in accordance with part 111, part 119 certificate holders, entities conducting public aircraft operations (PAO), air tour operators, fractional ownerships, and other specific entities operating under part 91 or 14 CFR part 125 are required to report records on individuals employed as pilots into the PRD. The PRD contains employer and FAA records on an individual’s performance as a pilot for the life of the individual. Records contained within the database would only be permitted to be used as a hiring aid in an operator’s decision-making process for pilot employment. This AC should be used in combination with the appropriate PRD user guides.1
1.1.1 Effects of Guidance. This guidance is not legally binding in its own right and will not be relied upon by the FAA as a separate basis for affirmative enforcement action or other administrative penalty. Conformity with the guidance is voluntary only, and nonconformity will not affect rights and obligations under existing statutes and regulations.
1.2 Audience. This AC is intended for use by pilots and operators who are required by PRIA and part 111 to share or review pilot records. Specifically, it applies to the following:
• Each operator that holds an Air Carrier or Operating Certificate issued in accordance with part 119 and is authorized to conduct operations under 14 CFR part 121, 125, or 135.
• Each operator that holds management specifications (MSpecs) for a fractional ownership program issued in accordance with part 91 subpart K (part 91K).
• Each operator that holds an LOA issued in accordance with § 91.147.
• Each operator that operates two or more aircraft described in part 111, § 111.1, in furtherance of or incidental to a business, solely pursuant to the general operating and flight rules in part 91, or that operates aircraft pursuant to a Letter of Deviation Authority (LODA) issued under part 125, § 125.3.
• Each entity that conducts PAO as defined in Title 49 of the United States Code (49 U.S.C.) § 40102(a)(41) on a flight that meets the qualification criteria for public
1 The FAA expects to publish further PRD user guides for reporting records to the PRD within one year.
1.6 Applicability.
aircraft status in 49 U.S.C. § 40125, unless the entity is any branch of the United States Armed Forces, National Guard, or reserve component of the Armed Forces.
• Each trustee in bankruptcy of any operator or entity described in § 111.1.
• Each person that submits or is identified on the application described in § 111.15 and is approved by the Administrator to access the PRD.
• Each person who is employed as a pilot by, or is seeking employment as a pilot with, an operator subject to the applicability of part 111.
1.3 Where You Can Find This AC. You can find this AC on the FAA’s website at https://www.faa.gov/regulations_policies/advisory_circulars.
1.4 What This AC Cancels. AC 120-68H, Pilot Records Improvement Act and the Pilot Records Database, dated April 21, 2017, is canceled.
1.5 Related 14 CFR Parts. Title 14 CFR parts 61, 91, 107, 111, 120, 121, 125, and 135.
1.6 Applicability. This AC explains how to comply with both part 111 as well as PRIA. Chapter 2 is specific to the PRD and Chapter 3 is specific to PRIA. The requirement to review a pilot’s records under PRIA will remain in effect until 3 years and 90 days after publication of part 111. Part 111 and the PRIA will run as parallel processes until PRIA is sunset. Operators subject to PRIA will find that compliance with part 111 will facilitate compliance with portions of PRIA during the transition period. The PRIA information in this AC has been updated to reflect where integration with the PRD is possible.
2.1.10 PRD Date of Hire.
CHAPTER 2. PILOT RECORDS DATABASE
2.1 Definitions. Definitions annotated with an asterisk (*) are also regulatory definitions captured in 14 CFR part 111, § 111.10.
2.1.1 Authorized User. An individual who is employed by an operator, entity, or trustee and who is designated by a responsible person (RP) to access the PRD on behalf of that employer for purposes of reporting and evaluating records that pertain to an individual pilot applicant.*
2.1.2 Begin Service as a Pilot. The earliest date on which a pilot serves as a pilot flightcrew member or is assigned duties as a pilot in flight for an operator or entity that is subject to the applicability of part 111.*
2.1.3 Corporate Flight Department. For the purpose of this AC, this term refers to an operator meeting the applicability of § 111.1 which means they operate two or more aircraft which are standard airworthiness airplanes that require a type rating under 14 CFR part 61, § 61.31(a) and/or turbine-powered rotorcraft in furtherance of or incidental to a business, solely pursuant to the general operating and flight rules in 14 CFR part 91, or that operates aircraft pursuant to a Letter of Deviation Authority (LODA) issued under 14 CFR part 125, § 125.3.
2.1.4 Final Disciplinary Action Record. A last-in-time record of corrective or punitive action taken by an operator or entity who is subject to applicability of this part in response to an event pertaining to pilot performance. No disciplinary action is considered final until the operator determines the action is not subject to any pending dispute.*
2.1.5 Final Separation from Employment Record. A last-in-time record of any action ending the employment relationship between a pilot and an operator or entity who is subject to the applicability of this part. No separation from employment is considered final until the operator determines the separation is not subject to any pending dispute.*
2.1.6 Historical Record. A record that an operator subject to the applicability of part 111 subpart C must generate and maintain in accordance with Title 49 of the United States Code (49 U.S.C.) § 44703(h)(4) and must report to the PRD in accordance with § 44703(i)(15)(C)(iii).*
2.1.7 Operator. Any operator subject to part 111 as described in § 111.1.
2.1.8 Pilot. An individual certificated by the FAA at the airline transport, commercial, or remote pilot level that is the subject of a record in the PRD.
2.1.9 PRD Administrator. The individual who manages the PRD on behalf of the FAA.
2.1.10 PRD Date of Hire. The earliest date on which an individual begins any form of required training in preparation for that individual’s service as a pilot on behalf of an operator or entity subject to the applicability of part 111 or performs any duty as a pilot for an operator or entity subject to the applicability of part 111. This definition includes both
2.2.1.4 Optional Record Review.
direct employment and employment that occurs on a contract basis for any form of compensation. The PRD date of hire has a different regulatory definition than “hire” as defined under the drug and alcohol testing regulations (14 CFR part 120, § 120.7(j)).*
2.1.11 Proxy. A person who is designated by an RP to access the PRD on behalf of an operator, entity, or trustee subject to the applicability of this part for purposes of reporting or retrieving records.*
2.1.12 Record Pertaining to Pilot Performance. A record of an activity or event directly related to a pilot’s responsibilities or completion of the core duties in conducting safe aircraft operations, as assigned by the operator employing that pilot.*
2.1.13 Responsible Person (RP). The individual identified on the application required by § 111.15 and who meets at least one of the criteria in § 111.15(e). The individual should be serving in a required management position listed under 14 CFR part 119, § 119.65(a) or other applicable regulation. These positions may include the following positions: Director of Safety, Director of Operations, Chief Pilot, Director of Maintenance, or Chief Inspector.*
2.1.14 Reporting Entity. An operator, entity, or trustee who is subject to the applicability of part 111 subpart C, including its RP, authorized users, and proxies.*
2.1.15 Reviewing Entity. An operator that is subject to the applicability of part 111 subpart B, including its RP, authorized users, and proxies.*
2.2 Applicability.
2.2.1 Access and Evaluate Records. The following operators are required to access and evaluate a pilot’s records in the PRD prior to making a hiring decision in accordance with § 111.100:
2.2.1.1 Part 119 Certificate Holders. All certificate holders operating in accordance with 14 CFR part 121, 125, or 135 are required to access and evaluate an individual’s records in the PRD prior to making a hiring decision.
2.2.1.2 Fractional Ownerships. Any person who has been issued management specifications to operate in accordance with part 91 subpart K (part 91K) is required to access and evaluate an individual’s records in the PRD prior to making a hiring decision. Compliance with § 111.105 satisfies the pilot safety background check specified in part 91, § 91.1051 until that provision sunsets.
2.2.1.3 Air Tour Operators. An air tour operator that has been issued a Letter of Authorization (LOA) in accordance with § 91.147 is required to access and evaluate an individual’s records in the PRD prior to making a hiring decision.
2.2.1.4 Optional Record Review. Corporate flight departments and public aircraft operations (PAO) may also elect to review records in accordance with part 111 subpart B, as set forth in § 111.100. If reviewing records in the PRD,
2.3 Background.
the operator must comply with § 111.120, which requires receipt of a pilot’s consent to access records.
Note: Regardless of how an operator obtains pilot services from an individual (e.g., direct employment, contractor, temp agency, or other means of compensation), a part 119 certificate holder, fractional ownership, or air tour operator as defined in § 91.147 is responsible for accessing and evaluating the individual’s records in the PRD prior to making a hiring decision to operate the approved aircraft.
2.2.2 Requirement to Enter Records. The following operators are required to enter pilot records into the PRD in accordance with § 111.200. Paragraph 2.8 and Appendices A through E provide an explanation of the types of records to be entered into the PRD by each reporting entity in order to meet the requirements of part 111 subpart C.
2.2.2.1 Part 119 Certificate Holders. All certificate holders operating in accordance with parts 121, 125, and 135 are required to enter pilot records as set forth in § 111.200 on all pilots they have employed since 2005 for air carriers and 2010 for operators.
2.2.2.2 Fractional Ownerships. Operators conducting operations as fractional ownerships are required to enter pilot records as set forth in § 111.200 for all pilots it employs.
2.2.2.3 PAC Operators. This group of operators, which includes PAO, air tour operators, and corporate flight departments, has identical reporting requirements.
2.2.2.3.1 Air Tour Operators. Air tour operators conducting operations in accordance with § 91.147 are required to enter pilot records as set forth in § 111.200 for all pilots it employs.
2.2.2.3.2 Corporate Flight Departments. Corporate flight departments are required to enter pilot records as set forth in § 111.200 for all pilots it employs.
2.2.2.3.3 Entities Conducting PAO. PAO are required to enter pilot records as set forth in § 111.200 for all pilots it employs.
2.2.2.4 Trustee in Bankruptcy. A trustee in bankruptcy is required to continue to comply with the reporting requirements for the PRD in accordance with the reporting entity’s obligations in part 111, as set forth in § 111.200.
2.3 Background. The Airline Safety and Federal Aviation Administration Extension Act of 2010 (Public Law (PL) 111-216, Section 203) (the PRD Act) replaces PRIA by requiring the FAA to create a PRD that contains pilot records. The PRD Act requires the PRD to contain pilot records dating from August 1, 2005 for FAA certification events, enforcement records, pilot employment history, training data, and drug and alcohol testing records. The PRD Act also requires that the PRD replace PRIA after a period of
2.4.1.2 Accident and Incident Information.
transition. Until the PRD is fully implemented, PRIA remains in effect. Therefore, air carriers and certain other operators must continue to provide pilot records to an air carrier or air operator seeking information on an individual pilot in accordance with PRIA. As established by PRIA, air carriers are required to evaluate all available pilot records prior to making a hiring decision. To effectuate the requirements of the PRD Act, the FAA promulgated part 111, which implements the PRD. Compliance with part 111 will ensure that operators have a full picture of an individual’s aviation background before permitting that individual to begin service as a pilot.
2.4 Records Contained in the PRD.
2.4.1 FAA Records. In accordance with the PRD Act, the FAA must include certain certification records and enforcement records in the PRD. The PRD is also populated with accident and incident information. Any other records maintained by the FAA that are not included in the PRD may be accessed and evaluated, with the consent of the subject, through a Privacy Act request. The requirements for accessing and evaluating FAA records are contained in § 111.140.
2.4.1.1 Airmen Certification Information. Reviewing entities should use airmen certification information the FAA maintains to validate a pilot’s qualifications. The PRD provides an individual’s current airman certificates, associated ratings, and any limitations to the certificate or ratings. The date and certificate grade sought for any failed attempt to pass a practical test required to obtain a certificate or type rating under part 61 (since August 2010) is included in the airman certification information. Also, the PRD contains a pilot’s latest medical certificate, including its class and any limitations.
Note: The PRD does not contain any medical data history (e.g., responses to medical history questions on the medical application).
2.4.1.1.1 Correcting Inaccuracies. The certificate and medical information displayed in the PRD is reported by the Airman Certification Branch. If a pilot discovers inaccuracies in the pilot certificate or medical information contained in the PRD, they should contact the Airman Certification Branch at 866-878-2498. The Privacy Act provides a process to correct records in FAA systems. The PRD does not actually contain these records so they cannot be corrected in the PRD. The records can only be corrected at the original source of the information.
2.4.1.2 Accident and Incident Information. Summaries of accidents and incidents that occurred on or after October 1, 2015, are included in the PRD to provide a reviewing entity the opportunity to review any negative data or helpful information that displays a pilot’s decision-making skills. Records will be shown when the pilot was listed as either first pilot (pilot in command (PIC)) or second pilot (second in command (SIC)). It is important to note that the
2.4.1.4 Relevant Drug and Alcohol Testing Information.
pilot may not have been acting as PIC even though there is a report is associated with that pilot.
Note: A report provided in the PRD is not the same as what may be shown in a National Transportation Safety Board (NTSB) investigation of the same event. The FAA and the NTSB often perform parallel investigations. Only the NTSB determines the probable cause of an accident. It is possible a pilot will be associated with an accident or incident in the PRD but found not to be involved in the actual cause of the event by the NTSB. Reviewing entities should also review the NTSB report for an accident found in the PRD by visiting its website, available at https://data.ntsb.gov/carol-main-public/keyword-search.
2.4.1.2.1 Correcting Inaccuracies. The accident and incident information displayed in the PRD comes from the Accident and Incident Database System (AIDS). If a pilot discovers inaccuracies in the information contained in the PRD, the pilot should contact the original FAA office which investigated the accident or incident, likely the same FAA office from which the inspector-in-charge (IIC) was assigned. The Privacy Act provides a process to correct records in FAA systems. The PRD does not actually contain these records so the records cannot be corrected in the PRD. The records can only be corrected at the original source of the information.
2.4.1.3 Enforcement Information. The PRD includes summaries of legal enforcement actions resulting in a finding by the Administrator of a violation of 49 U.S.C. or a regulation prescribed or order issued under 49 U.S.C. that was not subsequently overturned dated on or after August 1, 2010. These records are limited to enforcement action resulting in a suspension, revocation, or civil penalty.
2.4.1.3.1 Correcting Inaccuracies. The enforcement information displayed in the PRD comes from the Enforcement Information System (EIS). If a pilot discovers inaccuracies in the information contained in the PRD, the pilot should contact the original FAA office which investigated the enforcement case. This will most likely be the same FAA office from which the IIC was assigned. The Privacy Act provides a process to correct records in FAA systems. The PRD does not actually contain these records so the records cannot be corrected in the PRD. The records can only be corrected at the original source of the information.
2.4.1.4 Relevant Drug and Alcohol Testing Information. The PRD includes records related to pre-employment drug or alcohol testing violations for a pilot that was not hired, and records of drug or alcohol testing violations with an employer regulated by another Department of Transportation (DOT) agency where the individual was employed as a pilot. These records are uploaded by the FAA on behalf of the regulated employer or employer regulated under another DOT agency.
2.4.2 Operator, Entity, and Trustee Records.
2.4.1.4.1 Correcting Inaccuracies. The drug and alcohol testing information entered into the PRD by the FAA comes from the employer or potential employer that reported the result to the FAA. If a pilot discovers inaccuracies in the information contained in the PRD, the pilot should contact the employer or potential employer that reported the drug or alcohol violation to the FAA to confirm whether the information in the PRD is accurate. If the pilot still believes that the information is inaccurate, the employer should contact the FAA’s Drug Abatement Division at [email protected] to update the PRD.
Note: If the record was entered by a reporting entity, not the FAA, then a pilot can mark a record as inaccurate using the process described in paragraph 2.6.2.3.
2.4.2 Operator, Entity, and Trustee Records. Operators, entities, and trustees as described in paragraph 2.7.4 are required to report certain records to the PRD in accordance with part 111 subpart C. These records, memorialized by reporting entity, include training, qualification and proficiency records, final disciplinary actions, drug and alcohol records, and records concerning separation of employment. The specific data points that operators must enter into the PRD in accordance with the recordkeeping requirements part 111 are described in Appendices A through E. All operators, entities, and trustees subject to the applicability of part 111 subpart C are required to comply with the contemporaneous record reporting provision after the implementation date prescribed in § 111.200. Air carriers and certain other operators are required to comply with the historical record reporting provision of § 111.255. Table 2-1 below shows compliance information for the historical record reporting provision of part 111.
2.5 Accessing the PRD.
Table 2-1. PRD Overview of Record Reporting by Population
Records Required to
be Entered into the PRD
Record Documentation Date
Part 121 and
135 Air Carriers
and 135 Operators and
Part 91K Fractional Ownerships
Corporate Operators, Air Tour
Operators Under § 91.147, and Public Aircraft Operations
Historical
Records
Records predating 8/1/2005 N/A N/A N/A
Historical
Records
Records dating from 8/1/2005 through 7/31/2010 Must Report2 N/A N/A
Historical
Records
Records dating from 8/1/2010 through 1 year after publication of part 111
Must Report3 Must Report4 Voluntary Reporting
New Records
Records created 1 year after publication of part 111
Must Report5 Must Report6 Must Report7
Note: Table 2-1 is only intended to be an overview of PRD reporting requirements. PRIA reporting is not included.
2.4.3 Pilot Records Removal from the PRD. Pilot records are maintained in the PRD until the pilot reaches 99 years of age or if the FAA receives a certified copy of a death certificate. Certified copies of death certificates may be mailed to the Aviation Data Systems Branch at the following address:
Federal Aviation Administration ATTN: Aviation Data Systems Branch (PRD) P.O. Box 25082 Oklahoma City, OK 73125
2.5 Accessing the PRD. The FAA controls accessibility to the PRD by managing user access to the database and the activity within the PRD. The following individuals are eligible to request access to the PRD by following the procedures in the PRD User Guide:
2 § 111.255(a) 3 § 111.255(b) 4 § 111.255(b) 5 § 111.200(a)(1) 6 § 111.200(a)(2) 7 § 111.200(a)(3)–(5)
2.5.1.3 Characteristics of the RP:
2.5.1 Responsible Person (RP). The PRD administrator approves the RP in accordance with § 111.15. All other user roles and accounts, excluding pilot accounts, are approved by each operator’s RP or user manager. Only certain individuals can qualify as the RP depending on the type of operator.
2.5.1.1 When a registration request is received, the PRD administrator determines if the request can be approved by comparing the applicant against individuals listed in various FAA databases or documents. The following guidelines apply regarding who can be approved as the RP:8
• For operations under part 121, the RP should be a person serving in a management position required by § 119.65(a).
• For operations under part 125, the RP should be a person serving in a management position required by § 125.25(a).
• For operations under part 135, the RP should be a person serving in a management position required by § 119.69(a).
• For operations under § 91.147, the RP should be a person designated as the RP on the operator’s LOA.
• For operations under part 91K, the RP should be a person designated by the fractional ownership program manager and who is employed by the fractional ownership program.
• For all other operators, the RP should be employed by the operator.
2.5.1.2 The PRD administrator will reference various FAA databases and documents to determine who is eligible, such as the Safety Assurance System (SAS), operations specifications (OpSpecs), and management specifications (MSpecs), as appropriate. Because the PRD administrator is verifying information by these sources, it is important that the information contained in these sources is current. Operators are responsible for notifying their FAA office promptly if this information has changed and needs to be updated in the FAA records.
2.5.1.3 Characteristics of the RP:
1. Operators are accountable for the RP.
2. The operator and RP are jointly responsible for entering, accessing, editing, and monitoring all activity by the reporting entity in the PRD, subject to the limitations of use.
3. The eligibility requirements described in § 111.15 ensure that the individual is certificated, or otherwise known, by the FAA.
4. The RP may delegate PRD access to an authorized user or proxy.
8 See § 111.215 for specific RP requirements.
5. The PRD administrator will approve or reject each application to be an RP submitted via the PRD.
2.5.2.3 User Manager.
6. The RP will automatically have the authorized consumer, authorized contributor, and user manager roles. The RP does not need to register for any additional roles.
2.5.2 Authorized Users. An individual who is employed by the operator that has been assigned access rights to the PRD on behalf of that individual’s employer by the RP to perform specific functions within the PRD. These access rights are conferred by various user roles.
2.5.2.1 Authorized Consumer. An individual who is employed by the operator that has been assigned access rights to the PRD on behalf of his/her employer by the RP. The following points describe the responsibilities and authority of each authorized consumer.
1. An authorized consumer can only view or download pilot records via the PRD.
2. An authorized consumer may not delegate access to the PRD to any other person.
3. The RP can generate additional internal requirements for authorized consumer prior to granting PRD access.
2.5.2.2 Authorized Contributor. An individual who is employed by the operator who has been assigned access rights to the PRD on behalf of that employer by the RP. The following points describe the responsibilities and authority of each authorized contributor.
1. An authorized contributor can upload airman records to the PRD and can also edit records in the PRD which are currently under the control of the same reporting entity.
2. An authorized contributor may not delegate access to the PRD to any other person.
3. The RP can generate additional internal requirements for authorized contributors prior to granting PRD access.
2.5.2.3 User Manager. An individual who is employed by the operator that has been assigned access rights to the PRD on behalf of that employer by the RP. The following points describe the responsibilities and authority of each user manager.
1. A user manager may delegate, remove, and otherwise manage users within the PRD on behalf of a RP.
2. A user manager may not access or enter PRD records. This does not prohibit a user manager from also being given other roles by the RP.
3. The RP can generate additional internal requirements for user managers prior to granting PRD access.
2.5.2.4 Proxy. An organization or individual that is not directly employed by an operator that has been assigned access rights to the PRD on behalf of that operator by the RP. The following points describe the responsibilities, authority, and eligibility of each proxy.
2.5.2.5 Pilot.
1. A proxy will designate a Proxy RP which will be approved by the reporting/reviewing entities’ RP.
2. The Proxy RP may then delegate additional proxy roles as needed to perform the required functions within the PRD.
3. Proxies have limited use of the PRD based on the authority delegated by RP.
4. Operators that elect to use a proxy should ensure that procedures exist to validate that the proxy is able to comply with the regulations in part 111 and any additional requirements imposed by an RP. These procedures could include the proxy’s authority to access the database, requirements for the proxy’s facilities, prohibitions against using the operator’s user ID during periods of inactivity with the operator, any sanctions that could be administered against the proxy if the agreement was not followed, and any other details that an operator determines as reasonable.
5. The RP is responsible for all actions which occur in the PRD by other users the RP has approved.
2.5.2.5 Pilot. The PRD is prepopulated with information about pilots who hold specific FAA certificates and meet other criteria. This preloading of pilot information allows the PRD to register pilots in the PRD and also ensure valid pilot certificate numbers are being used when reporting entities are entering records. However, not all individuals who hold FAA pilot certificates are prepopulated into the PRD. Because the PRD is intended to be used in the hiring process for certain operators, pilots who do not meet basic eligibility for those positions are not prepopulated. For example, pilots who hold a private pilot certificate would not be eligible to act as a pilot for an air carrier, so the PRD does not contain any pilot information for individuals who only hold a private pilot certificate. The PRD populates with pilots who hold a:
• Commercial pilot certificate and FAA medical,
• Airline transport pilot (ATP) certificate and FAA medical, or
• Remote pilot certificate and FAA medical.
2.5.2.5.1 The following points describe the responsibilities and authority under the PRD for each pilot.
1. All pilots have certain protections concerning the request, transfer, receipt, evaluation, and maintenance of their PRD records. The confidentiality of the PRD records will be protected in the following manner pursuant to part 111:
2.5.3.1 Creating an Account in MyAccess.
• A hiring employer receiving the PRD records may use them only in making a hiring determination.
• Only company personnel directly involved in the hiring process may view and evaluate the records.
2. The FAA encourages all individual pilots to review their PRD records for accuracy and to submit correction requests, if necessary, to the originator of the record.
3. Pilots will be able to grant consent in accordance with the PRD User Guide and part 111 subpart D.
4. Refusal to hire and release from liability. As set forth in 49 U.S.C. § 44703(j)(4), an air carrier may refuse to hire a pilot who does not provide the necessary consent for an air carrier to view that pilot’s PRD Airman Record (PAR) or who does not execute a release from liability for any claim arising from access to the individual’s records in the database or use of records in the PRD by the reviewing entity in accordance with the requirements of part 111. However, in accordance with 49 U.S.C. § 44703(j)(3), no air carrier may require a pilot to execute a release from liability for any claim arising from furnishing fraudulent or intentionally false information or known omissions maintained in violation of a criminal statute.
5. Records from the National Driver Register (NDR). Upon obtaining a pilot’s written consent, the operator will perform an NDR search using the pilot’s name and other data and request copies of any state records that come up as a result of that search. The pilot may request a copy of the state records the operator receives under § 111.120(c).
2.5.3 Creating Accounts for Access to the PRD. Electronic access to the PRD has two separate registration steps: creation of an account in MyAccess, if the user does not already have one, and PRD account registration.9 Each PRD account can have multiple user roles as needed. The available PRD user roles are described in paragraph 2.5.2.
2.5.3.1 Creating an Account in MyAccess. The FAA uses MyAccess to validate users for login into several FAA web applications, including the PRD. Although identity validation through MyAccess is a separate service from the PRD, successful verification of identity is a prerequisite for access to the PRD. The PRD support team cannot assist with MyAccess issues, as it is a completely separate system. When a user attempts to access the PRD website
9 https://www7.transportation.gov/individuals/privacy/myaccess-electronic-identity-authentication-service- %E2%80%93-may-31-2017
2.5.3.2 Creating User Accounts and Roles in the PRD.
at prd.faa.gov, the user will be prompted to log in via MyAccess. If the user is an FAA employee or contractor with a Personal Identity Verification (PIV) card and personal identification number (PIN), the user may log in using their PIV card and PIN. If the user needs to create an account, the user will see a link on the login screen which will help them create a new MyAccess account. As part of the new account creation process in MyAccess, the user will verify their identity by providing identifying information. If the user is unable to successfully complete the identity verification process, that person may not be able to create an account in MyAccess. Contact the FAA Help Desk at 844-322-6948 for assistance with MyAccess. To ensure the user contacts the correct support staff, users should specify that they are having trouble creating an account in MyAccess. If the caller tells them the trouble is with the PRD, the Help Desk will send the user to the PRD support staff who cannot assist with MyAccess concerns. See paragraph 2.5.4 for information about alternatives which may be available to a user who cannot create an account in MyAccess.
2.5.3.1.1 During the MyAccess registration process, the user will be asked to provide an email address. This email address will become an important part of the user’s MyAccess account. The FAA recommends users do not use employer-based email addresses, but rather personal email addresses. The MyAccess account is intended to be used by a person irrespective of where that person is employed. It will stay with the user even after a change in employers in the future. Access to various FAA applications which use MyAccess may change; however, MyAccess identity validation remains valid even if the user changes employers. If a user registers in MyAccess with an employer-based email address, that user may lose access to that email address in the future if they change employers. This could cause the user to lose access to the MyAccess account as well.
2.5.3.1.2 Each user should not create multiple MyAccess accounts with different email addresses. Because a user’s permissions in the various applications which use MyAccess are directly controlled by the user’s unique MyAccess account, if a user creates multiple MyAccess accounts, the user may be locked out of various applications or have restricted access to applications.
Note: Every user who accesses the PRD must have their own valid MyAccess account. Inappropriate use or sharing of MyAccess credentials may result in denial of access to the PRD in accordance with § 111.25.
2.5.3.2 Creating User Accounts and Roles in the PRD. Although each individual should have only one MyAccess account, consistent with the guidance in paragraph 2.5.3.1, a person may register for various user roles in the PRD, as appropriate. If a user has several different roles, the user will be asked which roles and/or companies for which they intend to perform actions during that session.
2.5.3.2.1 Importance of Selecting the Correct Operator when Registering. During the registration process for certain user accounts and roles in the PRD, a person will be asked to indicate for which operator that individual is registering. It is important that the correct company entry be selected. The available operators are loaded from one of the FAA’s databases. The database contains a directory entry for every operator known to the FAA. This includes all the types of operators from corporate operators to air carriers that are eligible to use the PRD. Take care to select the correct company; there are a wide range of operators listed in this directory. Some operators use a “doing business as” (DBA) name which is different from the official operator name recognized by the FAA. The PRD does not support DBAs so it is important to use the primary company name as entered in the FAA’s database.
2.5.3.2.1.1 Many operators have very similar names so the PRD also displays a unique code alongside the operator name to help users determine which entry the user should use. If an operator has been issued a “designator” by the FAA, then the designator will be displayed with the operator name. For example, “Sample Airlines (SAM1)”. If a user does not know the appropriate designator, this information is often printed on OpSpecs, MSpecs, and on the Air Carrier or Operating Certificate.
2.5.3.2.1.2 Many operators may not have been issued a designator by the FAA. In these cases, the PRD generates a unique key which is displayed in place of a designator. These are much longer in length. For example, “Sample Operator (NM00RNTECODSF TEST)”.
2.5.3.2.1.3 Cases might exist in which an operator appears to be listed twice in the selection box, once with a designator, and once with a unique key. This is due to the way the FAA creates entries in its database and is considered normal. In these cases, always use the entry with the four character designator.
2.5.3.2.1.4 It is also possible that an operator is not known to the FAA and thus does not appear in the selection list. If the appropriate operator name cannot be found when registering in the PRD, email [email protected] for assistance.
2.5.3.2.2 Registering as an RP. RP registrations are approved by the PRD administrator. After a registration request is received, the PRD administrator will ensure that the person registering as the RP meets the requirements of § 111.15 by comparing the submitted information with information the FAA has stored about each operator, such as in the SAS or in the OpSpecs. The PRD administrator may contact you or other company personnel to verify your eligibility. For specific instructions on how to submit a registration application, review the Resources section found at prd.faa.gov.
2.5.4.1 Pilots Who Cannot Create an Account in MyAccess.
2.5.3.2.3 Registering as an Authorized Consumer, Contributor, or User Manager. These roles are approved, edited, or rejected by the operator’s RP. After a registration request is submitted for one of these roles, the RP, or a user manager, approves or rejects the request. For specific instructions on how to submit a registration application, review the Resources section found at prd.faa.gov.
2.5.3.2.4 Registering as a Pilot. Pilot registrations are an automated process completed by the PRD. After a pilot logs in via MyAccess, the pilot will arrive at the PRD pilot registration screen unless they have already created a pilot role in the PRD. The pilot will be prompted to enter various information from their pilot certificate, which will be verified by the PRD. For specific instructions on how to register as a pilot, review the Resources section found at prd.faa.gov.
2.5.3.2.5 Registering as a Proxy. Proxies who wish to access the PRD on behalf of an operator will create a Proxy RP account. Additional proxy roles are available and those roles generally work the same as non-proxy accounts. The biggest difference is that a Proxy RP account is always a specific combination between an operator and a proxy company. When a Proxy RP wishes to register for access to an operator’s records, the operator RP must approve the request. Once approved, the Proxy RP has access to the same records as the operator RP. The Proxy RP can also approve other proxy users, such as proxy consumers, to have access to the same records for that specific operator. The operator RP or PRD administrator can revoke access at any time. For specific instructions how to register as a Proxy RP or other proxy role, review the Resources section found at prd.faa.gov.
2.5.4 Denial of Database Access. Electronic access to the PRD may be denied for various reasons set forth in § 111.25. Denial might result from violations of part 111, identity verification failures, ineligibility to access the PRD, or other reasons. In some cases, alternate procedures might be available to you that will still allow you to participate in the PRD process.
2.5.4.1 Pilots Who Cannot Create an Account in MyAccess. If a pilot who needs to access the PRD cannot create an account in MyAccess, the pilot will not be able to access the PRD electronically. The FAA has developed alternate procedures which will allow the pilot to access their records contained in the PRD, grant consent to employers, and dispute records as inaccurate.
2.5.4.1.1 Reviewing Your Records Contained in the PRD. If a pilot cannot access the PRD directly to review that pilot’s records, the pilot may request their records be provided by submitting FAA Form 8060-14, Pilot Consent/Revocation for Air Carrier Access to Pilot Records Database, in accordance with § 111.315(c). The PAR will be mailed to the pilot’s address on file. PARs will only be provided for pilots who are eligible to participate in the PRD. See paragraph 2.5.2.5 for eligibility requirements.
2.5.4.3 Reporting or Reviewing Entity Personnel Who Cannot Create an…
2.5.4.1.2 Granting or Revoking Consent to Your PAR. Normally, pilots will access the PRD directly to grant or revoke consent electronically in accordance with § 111.310. If a pilot is unable to access the PRD directly, the pilot may submit FAA Form 8060-14 to grant consent to one or more aviation employers to see their PAR. When consent is granted, the FAA will email a copy of the PAR to the pilot if an email address is provided. Otherwise, the FAA will mail a copy of the PAR to the pilot’s address on file. Pilots may also update their employment history for the previous 5 years using the same form. Pilots are required to ensure their employment history for the previous 5 years is accurate when granting consent, in accordance with § 111.310(b). A pilot consent always has an expiration date, but a pilot may revoke consent early by submitting another FAA Form 8060-14.
2.5.4.1.3 Report Records as Inaccurate or Disputed. If a pilot determines his or her PAR has an inaccurate or missing record and they cannot access the PRD directly, that pilot may submit FAA Form 8060-15, Pilot Records Database Pilot Record Dispute, to mark records as inaccurate or missing. This will initiate the record dispute process as though the pilot had accessed the PRD directly. Records can only be disputed for pilots who are eligible to participate in the PRD. See paragraph 2.5.2.5 for eligibility requirements. The record dispute process is described in paragraph 2.6.2.3.
2.5.4.2 Pilots Who Cannot Register in the PRD. The PRD is prepopulated with pilots who hold an FAA commercial pilot, ATP, or remote pilot certificate who have a current FAA medical certificate. If the pilot does not hold one of those certificates, that pilot will not be able register in the PRD even if they have created an account in MyAccess without additional assistance. If the pilot meets these criteria, has created an account in MyAccess, but cannot register as a pilot in the PRD, he or she should:
1. Ensure their first name is entered in the registration form exactly as it appears on the pilot certificate. If their last name, which is prefilled from MyAccess, is not exactly the same as printed on the pilot certificate, they will not be able to register.
2. Verify that the pilot holds a commercial pilot, ATP, or remote pilot certificate issued by the FAA and a current FAA medical. Only these types of airman certificates are prepopulated into the PRD. It may take up to 30 days for new pilot certificates to be loaded into the PRD.
3. Check that the certificate number and date of issuance is entered exactly as displayed on the most recent pilot certificate. Temporary pilot certificates are not supported by the PRD.
4. If the trouble persists, email the PRD support account at [email protected] for assistance.
2.5.4.3 Reporting or Reviewing Entity Personnel Who Cannot Create an Account in MyAccess. All users must first create an account in MyAccess
2.6.1.2 As required by § , company personnel must take appropriate…
before the user can create an account in the PRD. If you need access to the PRD as a reporting or reviewing entity, but cannot pass the identity verification process of MyAccess, you may be able to have your identity verified via an alternate process. Contact [email protected] or your Certificate Management Office (CMO) for assistance.
2.5.4.4 Requesting Reconsideration when Access is Denied. If the Administrator has denied a user access to the PRD in accordance with § 111.25, that person may submit a request for reconsideration. The person requesting reconsideration may submit a statement to the address below including the following items:
• Full name and email address,
• Date access was denied,
• An explanation of the facts and circumstances involved in the denial of access,
• Reasons why the Administrator should reconsider the denial, and
• Signature of the person who was denied access.
Mail the request for reconsideration to:
Federal Aviation Administration ATTN: Aviation Data Systems Branch (PRD) P.O. Box 25082 Oklahoma City, OK 73125-0082
2.6 Review and Evaluation of Records.
2.6.1 The PRD Process.
2.6.1.1 The PRD Act and part 111 require reviewing entities to use the PRD to assess the qualifications of an individual in determining whether to hire the individual as a pilot. The records available in the PRD are intended to assist reviewing entities in making informed hiring decisions. The records may indicate areas of concern where additional review may be appropriate. The PRD is not intended to be the only information source considered when evaluating a pilot as a new employee. The PRD is a starting point from which additional investigation may be warranted. Reviewing entities should involve flight operations subject matter experts (SME) early in the records review process to ensure that any perceived training issues are identified and fully evaluated. SMEs may be able to better interpret the collection of records in a holistic manner, which will provide more useful indicators than any single record can provide.
2.6.1.2 As required by § 111.30, company personnel must take appropriate action to protect the privacy of the pilot and the confidentiality of the records, as well
as ensure that the information contained in the database is not divulged to anyone not directly involved in the hiring decision, with the exception of an FAA inspector. The core activities and subprocesses in the PRD process includes the following:
2.6.2.2 Granting Consent.
1. The pilot logs into the PRD system to view that pilot’s PAR and update employment history.
2. The PRD application retrieves and displays the pilot’s current PAR assembled from various sources with a date and time stamp.
3. The PRD application permits the pilot to provide consent to release the pilot’s PAR to one or more reviewing entities.
4. The PRD application stores the pilot’s consent and the PAR at the time the pilot provides his or her consent.
5. The PRD application receives a reviewing entity’s request for a PAR.
6. The PRD application verifies if the pilot has granted consent to the reviewing entity to retrieve the PAR and if the consent is still valid. If the consent has expired or been revoked, the PRD system returns a notification to the reviewing entity stating that the pilot’s records are unavailable.
7. The PRD system retrieves and presents the pilot’s PAR to the reviewing entity as it existed when consent was granted by the pilot. The record can be downloaded for review and storage by the reviewing entity. The PRD system also notifies the pilot that the reviewing entity has received a copy of the pilot’s PAR.
Note: The FAA will conduct random audits of the application and its usage by air carriers and operators to ensure the PRD is being used in accordance with part 111.
2.6.2 The Pilot’s Role in the PRD Process. The pilot is responsible for ensuring his or her employment history is accurate and for granting consent to reviewing entities. The pilot also controls the PRD accuracy and dispute function regarding employer-generated records in their PAR.
2.6.2.1 Employment History. Before granting consent to a reviewing entity, pilots must ensure their employment history is accurate and lists all operators who employed them as a pilot for the last 5 years in accordance with § 111.310. This includes employers where a pilot may have begun training, but did not finish. Keep in mind that previous employers may have entered records related to a pilot regardless if the pilot listed them in their history.
2.6.2.2 Granting Consent. Reviewing entities are not able to view a pilot’s records in the PRD unless the pilot grants consent to that specific operator in accordance with § 111.120. The pilot is also given an opportunity to see the records exactly as they will be displayed to the reviewing entity. The pilot can
decide how many days (30, 45, or 60) the PAR is available and can revoke access to the PAR at any time. It is important for pilots to understand that when consent is granted for a reviewing entity to view a PAR, the information in that PAR will not change even if other information in the PRD changes. The PAR acts as a snapshot in time and reflects the records at the moment consent was granted. Information in the PRD changes. For example, a previous employer might add more records, and the pilot could want the new information to be shown to a reviewing entity. The pilot can refresh the PAR with new information by granting consent again to that reviewing entity. Consequentially, reviewing entities may ask the pilot to grant consent again if they believe too much time has passed from initial consent, even though the consent has not yet expired.
2.6.2.2.1 Importance of Selecting the Correct Operator when Granting Consent. When granting consent for a reviewing entity to see a pilot’s PAR, the pilot will be asked to indicate which specific operator for which they are granting consent. It is important for the pilot to select the correct company entry. The available operators which are displayed are loaded from one of the FAA’s databases. Take care not to select the wrong company; some operators use a “doing business as” (DBA) name which is different from the official operator name recognized by the FAA. The PRD does not support DBAs so it is important to use the primary company name as entered in the FAA’s database.
2.6.2.2.1.1 Many operators have very similar names so the PRD also displays a unique code alongside the operator name to help users determine which entry they should use, called a designator. If an operator has been issued a designator by the FAA, then the designator will be displayed with the operator name. For example, “Sample Airlines (SAM1)”. If a user does not know the appropriate designator, they can often find this information printed on OpSpecs, MSpecs, and on the Air Carrier or Operating Certificate.
2.6.2.2.1.2 For operators that have not been issued a designator by the FAA, the PRD generates a unique key which is displayed in place of a designator. These are much longer in length. For example, “Sample Operator (NM00RNTECODSF TEST)”.
2.6.2.2.1.3 An operator might appear to be listed twice in the selection box, once with a designator, and once with a unique key. This is due to the way the FAA creates entries in its database and is considered normal.
2.6.2.2.1.4 If a pilot grants consent to the wrong operator, then the intended reviewing entity will not be able to see the PAR. The reviewing entity, when they ask the pilot to grant consent to the PAR, should clearly instruct the pilot which company name to select in the
PRD. If a pilot accidentally selects the wrong company when granting consent, the company selected by mistake will not be able to see any of the pilot records because the company would not also have the pilot’s name and pilot certificate number with which to retrieve the PAR.
2.6.3.1 Initiate the Inaccuracy and Dispute Function in the PRD.
2.6.2.2.1.5 If a pilot is not sure which company name to select when granting consent, the pilot should ask the reviewing entity that is requesting the records what company name to select.
2.6.2.3 Inaccurate Records. Pilots should carefully review the records provided in the PRD before granting consent to a reviewing entity. Because the PRD is not the authoritative record source of the information and displays key information from the original records, pilots should initiate corrections or disputes to have the records corrected in the original sources. If a pilot discovers inaccuracies in FAA records, the pilot initiates the correction processes described in paragraph 2.6.2.4. If a pilot finds inaccuracies or wishes to dispute a record entered by a source other than the FAA, that pilot initiates the PRD correction request process described in paragraph 2.6.3.1.
2.6.2.4 Corrections. If the pilot finds an error, the pilot can use the PRD inaccuracy and dispute process to request the record be corrected in accordance with § 111.320. See paragraph 2.6.3.1 for more information about how to have records corrected.
2.6.2.5 User Guides. Various user guides that explain how to perform pilot functions in the PRD are available in the Resources section at prd.faa.gov.
2.6.3 Record Inaccuracies and Disputes. For FAA record sources, the information displayed in the PRD will be updated once the original record source is updated, normally within 24 hours. In the event of non-FAA records, the reporting entity, or current record owner, is responsible for updating the records in the PRD so that the PRD accurately reflects the information in the authoritative record source. Pilots need to be aware that any previously granted consent will need to be refreshed to include any updated information. PARs which a pilot has consented to release are snapshots of the records at that instant and will not automatically update if the information available to the PRD changes.
2.6.3.1 Initiate the Inaccuracy and Dispute Function in the PRD. The PRD includes an inaccuracy and dispute function, which is used by the pilot if they discover an employer-generated record is inaccurate in accordance with § 111.320. When a pilot reports a record as inaccurate, the PRD will notify the record owner that the pilot requested a correction. The PRD will also provide contact information to the record owner if the pilot provides the information to facilitate communication between the record owner and the pilot. If the record owner makes the correction to the pilot’s satisfaction, then the process is complete. If the record owner does not resolve the matter to the pilot’s satisfaction, then the record can be marked as in dispute. When a record is
2.6.5.1 The “PRD records complete date” field indicates when all the…
marked in dispute in the PRD, it will still be displayed to reviewing entities as any other record would. However, it will be flagged as “disputed” in the PAR. This is intended to indicate to the reviewing entity that the pilot has indicated the record is inaccurate. This will provide an opportunity for the reviewing entity and pilot to discuss the matter. For specific direction on how to use the inaccuracy and dispute process, see the Resources section at prd.faa.gov.
2.6.4 Records Provided to a Reviewing Entity by the NDR or Department of Motor Vehicles (DMV). To obtain records from the NDR or the appropriate chief driver licensing official of a state, a request must be made to the state which issued the airman’s driver’s license in accordance with § 111.110. Most states will use a unique form to request the driving history of the airman. The proper form for each state should be used. While the FAA does provide FAA Form 8060-13, National Driver Register Records Request (PRIA), to request driving records, it should only be used in cases when the state of issuance does not provide a state-specific form. The NDR will provide a report that indicates if a negative record (one with an action taken against the individual’s driver license) is located. If a negative record is located, the reviewing entity air carrier or operator must obtain the individual’s record from the state reporting the negative record as required by § 111.110(a)(3). A negative report would include:
1. A record of any suspension or revocation of the pilot’s driver’s license from the previous 5-year period, including the state where the offense occurred; and/or
2. A record of any convictions of driving under the influence (DUI) from the previous 5-year period, including the state where the offense occurred.
Note: Not all states will forward the DMV records request to the NDR. In these cases, reviewing the record of the state which issued the airman’s driver’s license is sufficient. Other states may also be willing to process your NDR request as well.
2.6.5 Requesting Additional Records Not Yet Entered into the PRD. Some situations might exist in which a reporting entity may have additional pilot records to enter. During the transition period from PRIA, this may be because the reporting entity is still loading historical records. After the transition period, while most reporting entities will enter records contemporaneously, exceptions exist. Some reporting entities may only enter records after it was asked to enter the records by a reviewing entity, in accordance with § 111.215. There are three data fields that assist in determining whether a reviewing entity needs to request additional records. Table D-1 includes these three fields, which are the “PRD records complete date,” “No additional records to report to PRD date,” and “Relevant documents” fields.
2.6.5.1 The “PRD records complete date” field indicates when all the pilot records to the date listed have been entered into the PRD. If the operator is the pilot’s current employer and the date is older than 30 days, or the reporting entity is a PAO, air tour operator, or corporate flight department, you may assume additional records are available and should use the Records Request function provided in the PRD. Using this function will notify the reporting entity that
2.6.7.1 Air carriers and operators regulated under part 120 must…
any additional records must be entered. The reporting entity may simply update the date if there are no additional records to report. Keep in mind that if additional records are added, the pilot will need to grant a fresh consent for the new records to be visible in the PAR.
2.6.5.2 The “No additional records to report to PRD date” is used to indicate that the records have all been reported to the PRD and no additional records are expected. If there is a date populated in this field, you can assume the pilot no longer works for this reporting entity and the records in PRD are complete. A related separation of employment record will also exist. A pilot may use the Records Request function to verify there are no more records available if there are conflicting indicators such as subsequent records reported by the former employer after that date.
2.6.5.3 In accordance with §§ 111.230 and 111.235, a reviewing entity or a pilot may request documents relevant to final disciplinary action records and separation from employment records reported by a reporting entity. The PAR display will indicate if relevant documents exist. The PRD does not contain these relevant documents, but a reviewing entity can request them from the reporting entity for up to 5 years from the record date. The reporting entity, upon being notified of the request via the PRD, must provide the relevant documents directly to the requester within 14 days. “Relevant” means that the documents form the basis for the record reported to the PRD. Additional information about requesting these relevant documents will be available in the PRD User Guide.
Note: For specific instructions for using the PRD Records Request function, see the Resources section at prd.faa.gov.
2.6.6 Allow Pilot Applicants an Opportunity to Respond. Before making a final hiring decision, the reviewing entity should provide the pilot with a reasonable opportunity to discuss the records provided in the database as well as any documents relevant to a final disciplinary or separation from employment action which the reporting entity may have provided to the reviewing entity. This would typically be completed during the company’s interview process in order to fully evaluate the individual for a pilot position. The PRD is not intended to be the final source of information that a hiring air carrier or operator should consider. It is intended to highlight where additional information and review would be appropriate.
2.6.7 Compliance with Title 49 of the Code of Federal Regulations (49 CFR) Part 40.
2.6.7.1 Air carriers and operators regulated under part 120 must continue to comply with the drug and alcohol records check under 49 CFR part 40, § 40.25 if there is a violation in PRD or the pilot worked in a different safety-sensitive position with a former DOT-regulated employer within two years. The hiring employer may use FAA Form 8060-12 or the FAA’s sample written release form under 49 CFR § 40.25 to obtain these records, keeping in mind the
2.7.1 Pilots Seeking Employment after Completing Military Duty.
recordkeeping requirements are different for non-pilots. In accordance with 49 CFR § 40.25(j), a hiring operator must ask the airman whether he or she has tested positive or refused to test on any pre-employment drug or alcohol test administered by an employer that the airman sought, but did not obtain, employment (for safety-sensitive transportation work covered by DOT drug and alcohol testing rules) during the past two years.
2.6.7.2 Keep in mind that PRD (and the use of FAA Form 8060-12) is only required for newly hired pilots. In a situation where a pilot returns from a break in performing flightcrew member duties (either as a result of a furlough or extended absence), an additional PRD request would not be required by part 111. In this situation, an employer may check the PRD to see if there was a reported violation during the break, or request drug and alcohol records from any DOT-regulated employer where the pilot worked during their extended leave, in accordance with 49 CFR § 40.25.
2.6.8 Showing Evidence of Compliance with Part 111.
2.6.8.1 In order to show compliance with part 111, reporting entities may be asked to demonstrate they have entered records as appropriate into the PRD. An aviation safety inspector (ASI) may ask that you show that a given pilot record has been entered into the PRD by accessing the PRD and locating records matching the official recordkeeping source.
2.6.8.2 Reviewing entities should download or otherwise retain the PAR retrieved from the PRD as part of reviewing the pilot records. As with PRIA, the PAR should be kept separate from your other pilot records, and information from a PAR should never be entered again into the PRD or provided to another entity. An ASI may ask you to show the PAR obtained from the PRD. You may also be asked to show evidence that you requested and evaluated any records from the NDR.
2.7 Special Circumstances Involving Few or No Records to Evaluate. An air carrier or operator employing pilots may encounter special circumstances that result in an individual’s records related to the performance as a pilot not being entered into the PRD. Therefore, a hiring air carrier or operator will not be able to review such records in the PRD. When a record is not viewable in the PRD, the air carrier or operator may apply the good faith exception as set forth in § 111.115 and described in paragraph 2.7.6. However, in circumstances when the individual being considered for a pilot position has been employed by operators that are not required to report records to the PRD, the reviewing entity should request the individual’s records related to the performance as a pilot from the previous employers directly to be able to make a more informed hiring decision.
2.7.1 Pilots Seeking Employment after Completing Military Duty. PRD will not contain prior employment records from the U.S. Armed Forces for a pilot who has been an active member of any branch of the U.S. Armed Forces, the National Guard, or a Reserve component of the U.S. Armed Forces. However, the individual’s FAA records and other
2.7.5.2 Suppressed Industry Records.
industry records will be available in the PRD. The NDR must also be queried in accordance with § 111.110.
2.7.2 Pilots Formerly Employed by a Foreign Air Carrier or Operator. Foreign air carriers and operators are not required to comply with part 111. Therefore, if a pilot was previously employed by a foreign air carrier or operator, no industry records from that foreign air carrier or operator will be maintained in the database. However, the individual’s FAA records will be available in the PRD as well as any other records provided to the PRD by reporting entities. The reviewing entity must also query the NDR in accordance with § 111.110.
2.7.3 Foreign Civil Aviation Authority Records. Records maintained by a foreign civil aviation authority will not be included in the PRD.
2.7.4 PRD Records after Cessation of Business, Liquidation, or Bankruptcy.
2.7.4.1 Cessation of Business. If a reporting entity ceases business or surrenders its part 119 certificate (as applicable) for any reason, the reviewing entity should follow the provisions of the good faith exception described in paragraph 2.7.6.
2.7.4.2 Liquidation or Bankruptcy. If an air carrier or operator ceases business and goes into liquidation or bankruptcy, a trustee is generally appointed by the court for the protection of the property and disbursement of certain assets for a designated period of time. This may include reporting all PRD-related records in accordance with part 111.
2.7.4.3 Request for Outstanding Records. A reviewing entity making a request for PRD-related records to a reporting entity that is currently being liquidated or known to be in bankruptcy should still request any outstanding records be entered in the PRD.
2.7.5 Suppressed Records. There are special circumstances when records contained in the PRD may need to be suppressed or otherwise made unavailable for display in a PAR. For example, this could be due to a court order. When records are suppressed, they are not displayed in the PAR and there is no indication to the reviewing entity that a record is being suppressed.
2.7.5.1 Suppressed FAA Records. If the PRD administrator must suppress one or more FAA records for a pilot, then the PRD will not display any FAA records in the pilot’s PAR. In place of the FAA records, a statement will appear that the FAA records are suppressed. Because a suppression order can be specific to a single record or perhaps a type of record, a reviewing entity should submit an FAA Form 8060-10, FAA Records Request (PRIA), to request access to any FAA records which may be releasable. The FAA will determine which, if any, FAA records may be released and provide those records.
2.7.5.2 Suppressed Industry Records. Reporting entities have the ability to suppress and unsuppress records they own in the PRD. There may be various reasons to
suppress a record, such as when required by a legal order. When a record is suppressed, it is invisible to all but the record owner. The PAR does not display an external indication when an industry record is suppressed. For specific information about using the record suppress function as a reporting entity, see the Resources section at prd.faa.gov.
2.8 Entering Company Records in the PRD.
2.7.6 Good Faith Exception. The “good faith exception,” as set forth in § 111.115, permits hiring air carriers or operators to employ pilots who have been previously employed by defunct air carriers or operators that did not enter records in the PRD. If an individual was employed by an air carrier after August 1, 2005, all of the pilot’s records are included in the PRD once the transition period is complete and if the air carrier was still in operation at the time of PRD implementation. Additionally, if an individual was employed by a part 121, 125, or 135 operator after August 1, 2010, all of the pilot’s records are included in the PRD if the operator was still in operation at the time of PRD implementation. However, if a pilot’s former employer was no longer in business prior to PRD implementation, that pilot’s records may not be included in the PRD. In that circumstance, the hiring employer must still attempt to view the pilot’s records in the PRD and evaluate the available records in their entirety in accordance with § 111.115. Records not reported to the PRD on an individual’s performance as a pilot by an air carrier or operator that is no longer in operation are not required to be considered for hiring purposes and is considered to meet the “good faith exception.”
2.7.6.1 The reviewing entity’s following activities would suffice to fulfill the reviewing entity’s obligation under the PRD: query of the PRD, completion of the NDR check (if applicable), review of the pilot’s employment history, submission of requests to any employers listed on the pilot’s employment history that have not indicated that all records for that pilot are already in the PRD, and submission of PRIA requests to all the employers listed on the pilot’s employment history either in the PRD or with FAA Form 8060-11, Air Carrier and Other Records Request (PRIA), until PRIA is sunset. When the reviewing entity waits at least 30 calendar-days to receive those records, it can exercise the good faith exception.
2.8 Entering Company Records in the PRD. Part 111 requires reporting entities to report certain records to the PRD. These records are divided into two categories based on when the records were created. Records dated before one year after publication of part 111 are considered historical records and any records created on or after one year after publication of part 111 are considered new records. Additionally, five types of records are included in the PRD. These include drug and alcohol records; training, qualification, and proficiency records; final disciplinary action records; records concerning separation of employment; and verification of motor vehicle driving record search and evaluation. There are also records collected, such as when a pilot was assigned to duty for a particular aircraft, or when a reporting entity has completed the transition from PRIA to PRD and has entered all the records for a particular pilot. Not all record types in the PRD apply to all types of reporting entities. Table 2-2 summarizes which record types apply to which reporting entities. There may be additional records to report that are not listed in the table. Refer to part 111 subpart C.
Table 2-2. Record Reporting by Operator
Drug and Alcohol
Records in Accordance with
Part 12010
Training, Qualification and Proficiency
Records11
Final Disciplinary
Action Records12
Records Concerning
Separation of Employment13
Verification of Motor
Vehicle Driving Record Search and
Evaluation14
Parts 121 and 135: § 111.200(a)(1)
Yes Yes Yes Yes Yes
No Yes Yes Yes Yes
No Yes Yes Yes No
Air tour § 91.147: § 111.200(a)(3)
Yes Yes (may be reported on request)
Yes (may be reported on request, exceptions apply, see § 111.215(b)(1))
Yes (may be reported on request, exceptions apply, see § 111.215(b)(1))
No
Operators described in § 111.1(b)(4): § 111.200(a)(4)
No Yes (may be reported on request)
Yes (may be reported on request, exceptions apply, see § 111.215(b)(1))
Yes (may be reported on request, exceptions apply, see § 111.215(b)(1))
No
Public aircraft operators:15 § 111.200(a)(5)
No Yes (may be reported on request)
Yes (may be reported on request, exceptions apply, see § 111.215(b)(1))
Yes (may be reported on request, exceptions apply, see § 111.215(b)(1))
No
Trustee in bankruptcy: § 111.200(a)(6)
As required by operator circumstances
As required by operator circumstances
As required by operator circumstances
As required by operator circumstances
As required by operator circumstances
10 § 111.220(a) 11 § 111.225 12 § 111.230 13 § 111.235 14 § 111.240 15 § 111.1(b)(5)
2.8.1.1 Training, Qualification, and Proficiency Records.
2.8.1 Company Records. Part 111 requires reporting entities to promptly report certain records to the FAA for inclusion in the database in accordance with § 111.205. Operators must maintain some of these records independent of part 111, including those kept pursuant to §§ 121.683, 125.401, and 135.63(a)(4)16, which show compliance with applicable flightcrew member requirements for training, qualification, proficiency, and continued training and qualifications. These records are also required to be reported to the PRD in accordance with § 111.225. In accordance with § 111.235, operators must report records concerning release from employment due to physical or professional disqualification of any flightcrew member. Additionally, § 111.220 requires operators to report certain drug and alcohol testing records maintained in accordance with part 120 and 49 CFR part 40 for inclusion in the database. Not every pilot record that a reporting entity might maintain is required to be entered into the PRD.
An operator must review the requirements of part 111 subpart C and utilizing the data elements in Appendices A through E. An operator must report an event to the PRD if the event memorialized in the reporting entities’ official recordkeeping system meets the criteria contained in part 111 and is listed or described in the appendices. Some appendices include an “other” record type. This does not imply that all pilot records not specifically listed are to be entered as “other. The FAA will provide detailed instructions in future user guides regarding when to use the “other” reporting option. In absence of such direction, reporting entities should not enter records using this option and should instead use the appropriate selection methods to specify the type of record being entered.
2.8.1.1 Training, Qualification, and Proficiency Records. To specifically identify the training records that a reporting entity must enter into the PRD in accordance with § 111.225, the FAA has provided a list of regulations and data elements in Appendix A. Some operating rule parts, such as part 121, have many possible entries due to varying regulatory pilot training requirements. Certain elements in an air carrier or operator’s training program that may be unusual or occur at irregular intervals. Common data points apply to all training records, as described in Table A-1. Specific training programs are detailed in Tables A-2 through A-7. For specific direction on how to enter records into the PRD, see the Resources section at prd.faa.gov.
Note: As set forth in § 111.245, Aviation Safety Action Program (ASAP) records must not be entered into the PRD. For example, training conducted as part of an ASAP recommendation is often in addition to training normally required by the regulations. Thus, this additional training under ASAP would not be reported to the PRD. In accordance with AC 120-66, Aviation Safety Action Program, official
16 These provisions also require certain records to be kept concerning compliance with flight and duty rules, as well as requirements for physical examinations. However, consistent with the statutory mandate, records regarding flight time, duty time, and rest time are not required to be reported for inclusion in the PRD. In addition, while certain medical certification information is reported by the FAA to the PRD, the reporting of records demonstrating an air carrier’s or operator’s compliance with medical qualification requirements are reported through categorical options in the database as provided further in this AC.
training records and personnel files should not reflect correction actions associated with ASAP.
2.8.1.1.1 Data Fields. The PRD will include all data fields listed below, most of which must contain an entry.
1. Reporting Entity Designator: This is the designator or other reporting entity identifier as established by the FAA. This will be prefilled based on the logged-in user.
2. Reporting Entity Name: This is the name as established by the FAA and recorded in the official FAA data sources. This will be prefilled based on the logged-in user.
3. Pilot Certificate Number: This is the pilot’s FAA certificate number related to the activity being entered. The PRD will ensure that the certificate number and last name are valid and match a known pilot who holds an appropriate FAA pilot certificate.
4. Pilot Last Name: This is the pilot’s last name. The PRD will ensure that the certificate number and last name are valid and match a known pilot who holds an appropriate FAA pilot certificate.
5. Start Date: This is the date the event began.
6. End Date: This is the date the event was completed.
7. Aircraft Make/Model: This is the applicable make and model of aircraft related to the event. For Unmanned Aircraft Systems (UAS), specific make and model may not be available in the list. You may use the “UAS-NONCERT-SMALL<55” or “UAS-NONCERT-LARGE≥55” entries.
8. Duty Position: This will be either PIC or SIC as appropriate.
9. Training/Testing Program: This is the type of training program applicable to the record being entered. This selection will determine what training events are available.
10. Training Event: This is the specific event being entered into the PRD.
11. Results: Enter if the event was completed as satisfactory or unsatisfactory. This is synonymous with complete or incomplete.
12. Evaluator Comments: Some events will allow evaluator comments to be reported if such comments are included in the official record. Not all events will allow comments to be entered. If the PRD allows comments for an event, the contributor entering the record cannot deviate from the text provided by the evaluator if the evaluator provided any comments. The contributor should not enter any comments here unless the evaluator entered comments of the official record.
13. Other Event Description: This is used in special circumstances in which the FAA directs reporting entities to use the “other” event type.
Contributors should not use this event type to enter events in the PRD that are not specifically listed in the Training Event list unless the FAA specifically directs this option be used.
14. Unsatisfactory Tasks or Maneuvers: Some events, if marked as unsatisfactory, will require the contributor to enter a list of what tasks or maneuvers were not completed satisfactorily, in accordance with § 111.225(c)(6) and (7). On most forms used to record checking events, these will be marked as “Unsatisfactory.” List all of the tasks or maneuvers marked as unsatisfactory or equivalent.
15. Incomplete Tasks or Maneuvers: Some events, if marked as unsatisfactory, will require the contributor to enter a list of what tasks or maneuvers were not attempted, in accordance with § 111.225(c)(6) and (7). On most forms used to record checking events, these will be marked as “Incomplete.” List all of the tasks or maneuvers marked as incomplete or equivalent.
2.8.1.1.2 Part 121 Air Carrier Training Programs Approved in Accordance with Part 121 Subparts N and O. Training programs are developed to meet prescribed regulatory requirements, such as crewmember qualification requirements, flight training and checking tasks, and the requirements for the use of airplane simulators and other training devices. Training programs may also include operator specific elements beyond the minimum required training events prescribed in part 121 subparts N and O. Both the prescribed regulatory requirements and the additional elements are included in a certificate holder’s training program curriculum.
2.8.1.1.2.1 A standard data input for a certificate holder’s training program curriculum will stem from the pilot training categories and curriculum segments. Examples of categories are initial new hire, upgrade, and recurrent training. Examples of curriculum segments would be emergency training, differences training, and systems training. Thus, the FAA requires a certificate holder to enter the category of pilot training and curriculum segment in which a pilot participated. The results of each specific curriculum segment would be reflected in the database as satisfactory (complete) or unsatisfactory (incomplete).17
2.8.1.1.2.2 For example, an individual participating in a certificate holder’s initial SIC new hire training could complete basic indoctrination and emergency training as required by §§ 121.415(a) and 121.417 prior to entering into initial ground training as a SIC for a specific aircraft type as required by § 121.419(c)(1) or (2), as appropriate.
17 A satisfactory or unsatisfactory result may also be submitted to the PRD as a pass or fail, or complete or incomplete, since these terms are used synonymously by certificate holders with approved training programs.
Once the individual has successfully completed the certificate holder’s initial ground training as a SIC for a specific aircraft type, the individual will participate in the certificate holder’s approved initial flight training as required by § 121.424(a). The individual will complete the initial flight training following an initial proficiency check in accordance with § 121.441. The SIC will then complete the required operating experience on the specific aircraft type as prescribed in § 121.434(a) prior to serving as a fully trained and qualified pilot for the certificate holder. Of all the events completed by the pilot, only some are reportable to the PRD. Table A-2 specifies which records fulfill the regulatory requirement in § 111.225 and must be entered in the PRD.
2.8.1.1.3 Determining Which Records to Enter and When to Enter Them. Appendix A contains several tables used to determine which records should be reported. Records related to pilots trained under part 121 subparts N and O are listed in Table A-2. New records must be entered within 30 days of creation18 and historical records must be entered as described in paragraph 2.10.3 and § 111.255.
2.8.1.1.4 Training Programs Approved in Accordance with Part 121 Subpart Y, Advanced Qualification Program. Advanced Qualification Program (AQP) is an alternative method for training and evaluating pilots based on instructional systems design, advanced simulation equipment, and comprehensive data analysis to continuously validate curriculums. Requirements of part 121 subparts N and O that are not specifically addressed in the certificate holder’s AQP continue to apply to the certificate holder and to the individuals being trained and qualified by the certificate holder. It incorporates data-driven quality control processes for validating and maintaining the effectiveness of curriculum content.19 The goal of AQP is to achieve the highest possible standard of individual and crew performance through effective training that will enhance professional qualifications. For more information on AQP, refer to AC 120-54, Advanced Qualification Program.
2.8.1.1.5 AQP Recordkeeping. AQP recordkeeping is identical to that required under traditional parts 121 and 135 training programs. However, for AQP, records should clearly indicate that the training used to qualify pilots, other flightcrew members, instructors, or evaluators was accomplished under an AQP curriculum. One noted difference from part 121 subparts N and O training programs is that initial operating experience (IOE) is part of the qualification curriculum. Because IOE is part of the qualification curriculum for AQP, the associated PRD records must include comments from evaluators and any unsatisfactory tasks from the IOE. The FAA notes that a pilot being trained in
18 § 111.215 19 Data is collected by each air carrier, de-identified, and submitted to the FAA on a monthly basis, in electronic format, for analysis. However, each air carrier is required to maintain records on pilots that have been trained through AQP similar to those required by other parts of 14 CFR.
accordance with part 121 subpart Y will compile training records for the indoctrination curriculum, qualification curriculum, and continuing qualification curriculum; however, some comments related to those events may not directly reflect the performance of either or both pilots. Comments related to those events will not be included in the PRD. Comments on the performance of a pilot that were documented by an individual acting in a capacity other than a check pilot or evaluator will not be accepted in the database, as previously discussed. For example, any comments recorded by an instructor, other than an instructor acting in the capacity of a check pilot or evaluator, are not permitted to be reported to the PRD.
2.8.1.1.6 Determining Which Records to Enter and When to Enter Them. Appendix A contains several tables used to determine which records should be reported. Records related to pilots trained under part 121 subpart Y are listed in Table A-3. New records must be entered within 30 days of creation20 and historical records must be entered as described in paragraph 2.10.3 and § 111.255.
2.8.1.1.7 Part 125 Operator’s Training Records to be Reported to the PRD. In accordance with part 111 subpart C, certain pilot records documented in accordance with § 125.401 are to be entered into the PRD. In addition to identifying records, § 125.401 also requires specific training records to be maintained that verify compliance with other regulations. Specifically, the records should display whether or not that crewmember complies with the required proficiency checks and qualification requirements.
2.8.1.1.8 Recording Required Part 125 Pilot Qualifications Events. The FAA requires all part 125 operators to keep records on an individual’s performance as a pilot that satisfies recent flight experience and the applicable qualification regulations in accordance with § 125.401. For example, a certificate holder is required to document and maintain records on specific pilot testing and qualification events under part 125 including the initial and recurrent pilot testing requirements and instrument proficiency checks (IPC). In accordance with § 125.291(a), each pilot in command (PIC) must pass a written or oral test on specific knowledge of the aircraft and operation. Additionally, a PIC must pass an IPC in accordance with § 125.291(a) and complete an approach procedure in accordance to § 125.291(b). The satisfactory completion of these required testing and qualification events as well as the date accomplished, aircraft type, duty position, testing and qualification part, regulation requiring the action (event), and the result of the action would be required to be reported to the PRD when the event is listed in Table A-5.
2.8.1.1.9 Determining Which Records to Enter and When to Enter Them. Appendix A contains several tables used to determine which records should be reported. Records related to pilots tested under part 125 are listed in Table A-5. New
20 § 111.215
records must be entered within 30 days of creation21 and historical records must be entered as described in paragraph 2.10.3 and in accordance with § 111.255.
2.8.1.1.10 Part 135 Air Carrier and Operator Training Records to be Reported to the PRD. In accordance with part 111 subpart C, the FAA requires certain pilot records documented in accordance with § 135.63(a)(4) to be entered into the PRD, subject to the limitations in § 111.225(b). Some of the records maintained in accordance with § 135.63(a)(4) are identifying, such as a pilot’s name, FAA pilot certificate type, ratings held, and duties. Other records kept pursuant to § 135.63(a)(4) require maintenance of training and proficiency records, including: (1) the date and result of each of the initial and recurrent competency tests and proficiency and route checks required by part 135 and the type of aircraft flown during that test or check; and (2) the date and completion of the initial phase and each recurrent phase of the training required by part 135. Additionally, § 135.63(a)(4) requires a certificate holder to maintain a pilot’s aeronautical experience, flight time, authorizations to act as a check pilot, and any action taken concerning the pilot’s release from employment for physical or professional disqualification.
2.8.1.1.11 Variations Among Part 135 Training Programs. Similar to part 121 pilot training programs, part 135 training programs are approved for a specific air carrier or operator. Therefore, one part 135 training program will vary significantly from one air carrier/operator to another. Additionally, the differences among the approved training programs compound since certificate holders may seek FAA approval for a training program through various subparts of parts 121 and 135.
2.8.1.1.12 Records for Specific Pilot Training and Checking Events. Some areas that require a certificate holder to record and maintain records on specific pilot training and checking events under part 135 are the initial and recurrent pilot testing requirements, IPCs, and line checks. In accordance with § 135.293(a), each pilot must pass a written or oral test on specific knowledge of the aircraft and operation. Additionally, a pilot must pass a competency check in accordance with § 135.293(b). Some pilots are required to complete an IPC in accordance with § 135.297. Finally, all PICs are required to complete a line check in accordance with § 135.299. An operator must report the satisfactory completion of these required training and checking events as well as the date accomplished, aircraft type, duty position, training program approval part and subpart, regulation requiring the action (event), and the result of the action in accordance with § 111.225. Additionally, § 111.225 requires an operator to report check pilot comments.22 The FAA notes that many certificate holders and FAA inspectors utilize FAA Form 8410-1, Airman Proficiency/Qualification Check, as a job aid to ensure all required tasks are
21 § 111.215 22 As previously indicated, instructor comments will not be accepted into the database.
completed during an evaluation in an aircraft or flight simulation training device. This form, as well as other job aids, could be used in documenting a training or checking event and recorded into the PRD after the event has taken place and the certificate holder could maintain the FAA form for demonstration of compliance.
2.8.1.1.13 Meeting Recordkeeping Requirements. All training must meet the recordkeeping requirements of § 135.63(a)(4). Thus, a pilot training record maintained by a part 135 air carrier or operator that displays compliance with a pilot training program approval would be required to be entered into the PRD when included in Table A-4. Similar to the part 121 pilot training records to be reported to the PRD, the varying degrees of data maintained by a certificate holder noted in part 121 subparts N, O, and Y, as well as part 135 subparts E, G, and H, will be entered into the PRD as the example for record entry previously described in the method of record entry section.
2.8.1.1.14 Using Distinct Qualifiers for Training Fields in the PRD. In order to differentiate the regulations under which training program approval was granted, the PRD will use distinct qualifiers in the training fields. For example, if an individual completes a training program approved for a part 135 certificate holder in accordance with part 121 subparts N and O, the certificate holder would enter the training program approval part and subpart as “135NO” in the PRD to note the certificate holder’s operating rule part and the subpart the certificate holder conducted the pilot training. This permits a reviewing entity to fully understand the type of training that an individual has participated in. Indicating the regulations governing the training program approval allows reviewing entities the opportunity to review the robustness and similarities of its pilot training program compared to the individual’s previous experience with other pilot training programs.
2.8.1.1.15 Determining Which Records to Enter and When to Enter Them. Appendix A contains several tables used to determine which records should be reported. Records related to pilots trained under part 135 are listed in Table A-4. New records must be entered within 30 days of creation23 and historical records must be entered as described in paragraph 2.10.3 and § 111.255.
2.8.1.1.16 Part 91 Subpart K Fractional Ownership’s Training Program Records. All fractional ownerships must have an approved training program for their pilots and may seek approval for that training program in accordance with §§ 91.1065 through 91.1107; part 135 subparts E, G, and H; or part 121 subparts N and O.24 Regardless of which pilot training program is used, compliance with the regulation requires provision of all applicable records. The fractional ownership’s program manager must keep training records of
23 § 111.215 24 A training program approved in this manner for a fractional ownership will be able to input a value for the training program that differs slightly from that of a traditional part 91K training program.
each pilot used in accordance with § 91.1027(a)(3). The records include the pilot’s current duties (e.g., PIC or SIC) and the date of the pilot’s assignment to those duties, the date and result of each of the initial and recurrent competency tests and proficiency checks required and the type of aircraft flown during that test or check, any action taken concerning the pilot’s release from employment for physical or professional disqualification, and the date of the satisfactory completion of initial, transition, upgrade, and differences training and each recurrent training phase. Each program manager for a fractional ownership program is required to enter these records to the PRD.
2.8.1.1.17 Determining Which Records to Enter and When to Enter Them. Appendix A contains several tables used to determine which records should be reported. Records related to pilots trained under part 91K are listed in Table A-6. New records must be entered within 30 days of creation25 and historical records must be entered as described in paragraph 2.10.3 and § 111.255.
2.8.1.1.18 Pilot Training Records that Commercial Air Tour Operators, Corporate Flight Departments, and Public Aircraft Operators Maintain (PAC Group). Commercial air tour operators, corporate flight departments, and public aircraft operators conduct operations with minimal oversight from the FAA, including in the area of pilot training. These operators are not required to maintain an approved pilot training program or maintain a recordkeeping system of a pilot’s training events. However, all pilots must record certain events in their pilot logbooks to document their currency as an FAA pilot certificate holder. While these events must be recorded by pilots in their logbooks, the FAA presumes that operators employing pilots are maintaining similar pilot training and currency records to ensure their pilots are current for operational safety purposes. Operators have also established customized training programs that are tailored to an individual operation and have documented training and qualification events in various formats. Considering that certain part 61 regulations require data elements to be recorded during an event, the FAA is requiring operators to enter an individual’s performance as a pilot in the database that documents the minimum training and qualification26 requirements when the operator is maintaining such records.
2.8.1.1.19 Determining Which Records to Enter and When to Enter Them. Appendix A contains several tables used to determine which records should be reported. Records related to pilots operating under part 91 are listed in Table A-7. PAC operators have an option of entering new records within 30 days of generating or otherwise collecting the record, or, for certain records, those operators may maintain the record outside of the PRD for 5 years and enter the records only when notified by the PRD a reviewing entity is requesting the records, in
25 § 111.215 26 The FAA views qualification requirements broadly as any certificate, rating, training, checking, testing, and experience required to be qualified or maintain qualification for a position (e.g., PIC) in a particular operation (e.g., part 121). Not all qualification requirements must be reported to the PRD. Refer to § 111.225(b).
Continue reading ↓ 120 of 357 passages shown