2-35
7. 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.
8. Date of Test or Occurrence: This is the date the test or event occurred.
9. Record Type: The user will select whether they are entering a drug test record or an alcohol misuse record.
10. Report Type: Based on the record type selected, the user will select the report type (e.g., Verified Positive Drug Test Result, Confirmed Breath Alcohol Concentration of 0.04 or greater, Refusal, etc.).
11. Type of Test: Based on the report type selected, the user will select the type of test (e.g., Random, Post-accident, Reasonable Cause Drug or Suspicion Alcohol, Follow-up, Return-to-duty). Pre-employment testing is only available to FAA users.
2.8.1.2.2 Who Must Enter Records? Any reporting entity that is required to comply with part 120 and 49 CFR part 40 must report drug and alcohol records to the PRD in accordance with § 111.220. This includes part 121 and 135 air carriers and operators, and air tour operators as defined under § 91.147.
2.8.1.2.3 Determining Which Records to Enter and When to Enter Them. Records related to drug and alcohol testing and events are listed in Table B-2. These records must be entered within 30 days of the test or occurrence.27 This requirement does not relieve an employer or its Medical Review Officer from reporting pilot violations to the FAA’s Federal Air Surgeon within two days in accordance with §§ 120.113(d)(1) and 120.221(c)(1).28
2.8.1.3 Final Disciplinary Action Records. In accordance with § 111.230, disciplinary actions that are considered final must be entered into the PRD within 30 days of being considered final. As provided in Appendix C, the specific data fields include identifying pilot information (e.g., pilot’s last name and FAA pilot certificate number), whether the disciplinary action resulted in permanent or temporary removal of the pilot from aircraft operations, and the type of action taken by the operator in response to the event (i.e., written warning, suspension, or termination).
2.8.1.3.1 Disciplinary Records that are Subsequently Overturned. The FAA recognizes that data may be entered incorrectly or a disciplinary action may be overturned through a number of informal and formal processes. Some records may be overturned after an employee succeeds in an internal dispute made directly with the employer, while other actions may be overturned by a court or other legal forum for adjudication. Moreover, the time period for an informal or formal dispute to be resolved could vary significantly. Therefore, § 111.230 requires reporting of disciplinary action records within 30 days
27 § 111.215 28 § 111.215
2-36 after the action is final so long as there is no pending dispute between the individual pilot and the employer or once the record is realized to be incorrect.
However, if a dispute develops after the disciplinary action is entered into the PRD and the action is subsequently overturned by the employer, then the reporting entity would be required to remove or correct the data entered into the PRD through the process discussed later in the document within 10 days of the disciplinary action being overturned as described in § 111.230(c). The FAA only considers a final disciplinary action to be subsequently overturned by an agreement if the agreement indicates the underlying action did not occur or was not the pilot’s fault. A record may not be entered into the PRD until the disciplinary action is finalized. The record must be entered in the PRD within 30 days after the dispute is considered resolved or closed by the employer in accordance with § 111.230(f)(1).)29. An air carrier or operator should not report any disciplinary action to the PRD that is not considered final.
2.8.1.3.2 Determining Which Disciplinary Actions to Report. A disciplinary record is created only for discipline or termination imposed by an operator or carrier involving the pilot’s performance that is related to the individual’s performance as a pilot, as set forth in § 111.230. A disciplinary action is entered into the PRD when the action: (1) was taken by an employer;
(2) imposed an adverse penalty on the pilot, such as a suspension, termination, or written warning; (3) directly involved the individual’s performance as a pilot, which means the record captures 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 the pilot; and
(4) has not been subsequently overturned, as specified in § 111.230.
Inappropriate or wrongful conduct in the workplace for which the employee is penalized by the employer but which does not involve the pilot’s aeronautical duties, is not considered “disciplinary action” and shall not be entered into the PRD. However, if an employer determines the inappropriate or wrongful conduct relates to a pilot’s responsibilities or completion of the core duties in conducting safe aircraft operations, it must be included in the PRD in accordance with § 111.230.
2.8.1.3.3 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.
29 Some final disciplinary actions may be entered on request. See paragraph 2.8.1.6.2 for more information.
2-37
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. Date of Action: This is the date the action was considered final by the reporting entity.
6. Action Type: The record must be entered only if the disciplinary action was either a written warning, suspension, or termination related to pilot performance. Other types of disciplinary actions are not to be entered.
7. Removal from Aircraft Operations: If the action included a temporary or permanent removal from flying duties, this field must be marked “yes”.
8. Relevant Documents: Indicate whether other relevant documents exist.
2.8.1.3.4 Who Must Enter Records? Final disciplinary records must be reported to the PRD by all of the reporting entities specified in § 111.230. This includes parts 121, 125, and 135 air carriers and operators, air tour operators under § 91.147, fractional operators under part 91K, as well as those in the PAC group.
2.8.1.3.5 Determining Which Records to Enter and When to Enter Them. Records of disciplinary actions must be reported within 30 days of being considered final.30 Actions that are a written warning, suspension, or termination must be reported. If the disciplinary action does not involve removal from aircraft operations, PAC operators may elect to not enter these records into the PRD contemporaneously and may instead maintain these records for 5 years and enter them within 14 days when notified that a reviewing entity wishes to see the records, as set forth in § 111.215. This option to report the records upon request does not apply when a disciplinary action results in permanent or temporary removal of the pilot from aircraft operations. These events must be reported to the PRD contemporaneously.31
2.8.1.3.6 Relevant Documents. In accordance with § 111.230(g), each reporting entity must retain any documents that are relevant to a final disciplinary action reported to the PRD for 5 years and provide those documents to a reviewing entity on request. If a reporting entity receives a request for relevant documents, they must provide those records directly to the requester within 14 days. The relevant documents can be provided in any legible form, to include mail or email, and will not be entered directly into the PRD. More
30 § 111.215 31 § 111.215(b)(1)(i)
2-38 information about this functionality will be provided in the PRD User Guide, including directions on how to confirm receipt of the request within the PRD.
2.8.1.4 Records Concerning Separation of Employment. In accordance with § 111.235, the FAA requires relevant records concerning release from employment, resignation, termination, or disqualification with respect to employment be reported to the PRD. Air carriers and other operators are required to enter limited, specific information into the PRD pertaining to relevant separation of employment records. The information would include the following fields: (1) the final date of employment and (2) a multiple-option category field to indicate the nature of the separation of employment that would require the employer to indicate the type of separation such as resignation, termination, physical (medical) disqualification, or retirement. An “other” option will also be available if none of the listed choices apply.
2.8.1.4.1 Release from Employment Due to Performance or Extended Leave. If a pilot has been released from employment due to his or her performance as a pilot during training, qualification, proficiency, or during the period of time when a pilot is trained and qualified, the operator must enter the previously mentioned data elements as well as any record supporting the individual’s release of employment as a result of unsatisfactory pilot performance through a termination entry. Any other record pertaining to a pilot’s release from employment will be reported to the database through a similar standardized method. The FAA acknowledges that many situations could exist that result in a pilot being released from employment unrelated to his or her performance as a pilot. If a pilot is released from employment as a result of being furloughed or extended leave, the air carrier or operator must enter the individual’s final date of employment and the reason for being released from employment.
2.8.1.4.2 Pilot Resignation. Similarly, if a pilot employee resigns from his or her position with an operator for reasons that are unrelated to the pilot’s performance of the core duties and responsibilities associated with operating an aircraft safely, the air carrier or operator must enter the final date of employment with the employer and indicate that the pilot resigned. For instance, if a pilot resigned his or her position with an operator to return to school full time, the record need not explain that the pilot was returning to school; only dates must be entered into the PRD in this situation. No additional information would be permitted to be reported for inclusion in the PRD.
2.8.1.4.3 Unsatisfactory Performance as a Pilot or Disciplinary Action. However, if a pilot were terminated due to unsatisfactory performance as a pilot or as a result of disciplinary action, the operator that terminated the individual must input the final date of employment of the pilot and indicate that the individual was terminated. This type of termination of employment is required to be reported to the PRD in accordance with § 111.235. The FAA understands that
2-39 most disciplinary actions do not result in termination of employment;
however, as previously indicated, some actions or events involving a pilot’s performance (e.g., removal from duty as a result of a drug or alcohol-related violation) could lead the employer to take disciplinary action in the form of termination of employment. In such a case, part 111 requires the employer to complete PRD entries for both the record concerning the disciplinary action as well as the record concerning termination, so long as the underlying action or event was related to the individual’s performance as a pilot. For example, if a pilot resigned from a position as a result of a disciplinary action, any associated disciplinary action would still be reported to the PRD and a reviewing entity should consider both entries when evaluating that pilot.
2.8.1.4.4 Disqualification from Employment. A pilot may also separate from an employer as a result of being disqualified from employment as a pilot. The reasons could stem from no longer holding the appropriate pilot or medical certificate32 or no longer meeting the requisite eligibility terms of employment as a pilot (e.g., maintaining a valid passport or other terms listed in a company’s general operations manual). These examples of disqualification are generally unrelated to a pilot’s performance; however, they greatly affect the individual’s legal obligations related to the operation of an aircraft for an air carrier or operator. The air carrier or operator must enter the final date of employment with the employer and indicate that the pilot was disqualified through the appropriate category selection.
2.8.1.4.5 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.
32 If an individual were no longer able to hold a first-class medical certificate and as a result could no longer act as a PIC but was able to hold a second-class medical certificate and act as an SIC, an operator would input that the individual was physically disqualified as a PIC. A final date of employment would not be entered into the database in this situation because the pilot continues to be employed as an SIC.
2-40
5. Separation of Employment Date: This is the last-in-time record of any action ending the employment relationship between a pilot and the reporting entity which is not subject to any pending formal or informal dispute initiated by the pilot. No separation from employment may be considered final until 30 days after the action.
6. Separation Type: Table D-1 lists the available options. Select the most appropriate choice. An “other” option may also be.
7. Relevant Documents: Indicate whether relevant documents exist.
2.8.1.4.6 Who Must Enter Records? Records concerning separation of employment must be reported to the PRD by all of the reporting entities specified in part 111. This includes parts 121, 125, and 135 air carriers and operators, air tour operators under § 91.147, fractional operators under part 91K, as well as PAC operators.
2.8.1.4.7 Determining Which Records to Enter and When to Enter Them. Records concerning separation of employment must be reported within 30 days of being considered final.33 If the separation from employment is not a termination, PAC operators may elect to not enter these records into the PRD contemporaneously and may instead maintain these records for 5 years and enter them within 14 days when notified that a reviewing entity wishes to see the records.
2.8.1.4.8 Relevant Documents. In accordance with § 111.235(g), each reporting entity must retain any documents which are relevant to a separation from employment action reported to the PRD for 5 years and provide those documents to a reviewing entity on request. If a reporting entity receives a request for relevant documents, they must provide those records directly to the requester within 14 days. The relevant documents can be provided in any legible form, to include mail or email, and will not be entered directly into the PRD. More information about this functionality will be provided in the PRD User Guide, including directions on how to confirm receipt of the request within the PRD.
2.8.1.5 Verification of Motor Vehicle Driving Record Search and Evaluation.
Each operator that holds an Air Carrier or Operating Certificate issued in accordance with part 119 and is authorized to conduct operations under part 121, 125, or 135 is required to request and review all relevant information identified through a NDR search set forth in 49 U.S.C. Chapter 303 concerning the individual’s motor vehicle driving history before allowing that person to begin service as a pilot in accordance with § 111.110.
2.8.1.5.1 Data Fields. The PRD will include all data fields listed below, most of which must contain an entry.
33 § 111.215
2-41
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 of the operator as 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. 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. Date When NDR Search and Evaluation Was Completed: This is the date the NDR record was received and evaluated.
2.8.1.5.2 Who Must Enter Records? Records concerning the NDR search and evaluation must be reported to the PRD by parts 121, 125, and 135 air carriers and operators in accordance with § 111.110.
2.8.1.5.3 Determining Which Records to Enter and When to Enter Them. A record of the NDR search and evaluation must be entered into the PRD with 45 days of the PRD date of hire.34 Table E-1 shows which data fields are available for reporting.
2.8.1.6 PAC Operator Reporting Options. PAC operators have an option of reporting all new records contemporaneously, within 30 days of creation or being considered final, or they may wait until a request is received for certain records. This option does not apply to all record types but can substantially reduce the burden of entering pilot records into the PRD.
2.8.1.6.1 Records That Must Always be Reported Contemporaneously. Within 30 days of becoming final, the following records must always be reported to the PRD in accordance with § 111.215(b). Prompt reporting of these specific record types ensures that a reviewing entity will be provided the critical information even before requesting any additional records be provided by the pilot’s current or previous employers.
• Any final separation of employment record which resulted from a termination.
• Any final disciplinary action record which resulted in permanent or temporary removal of the pilot from aircraft operations.
34 § 111.240
2-42
2.8.1.6.2 Reporting Records on Request. For records other than those described in paragraph 2.8.1.6.1, PAC operators may elect to not enter the records contemporaneously. PAC operators may instead maintain the records for 5 years and report the records to the PRD when requested to do so by a reviewing entity in accordance with § 111.215(b). When a reviewing entity requests any outstanding records be reported, the RP registered in the PRD for the previous employer will be notified by email that they must now enter any outstanding pilot records within 14 days to comply with § 111.215(b). Once the records have been entered, the reporting entity should enter either the “PRD records complete date” or, if no additional records are necessary, the reporting entity should select the “No additional records to report to PRD date” into the PRD. This will trigger the PRD system to notify the pilot and the reviewing entity that all of the appropriate records are now available for review.
2.8.1.7 Additional Administrative Entries in the PRD. A reporting entity may enter other information into the PRD.
2.8.1.7.1 Assignment to Duty. This optional entry may be used by a reporting entity to indicate when a pilot was assigned to a specific duty position for a specific aircraft make and model. Table D-2 indicates the available fields for use when entering a pilot’s assignments to duty positions.
2.8.1.7.2 PRD Records Complete Date. During the transition period between PRIA and the PRD, a pilot’s historical records in the PRD may be incomplete because reporting entities have approximately two years to enter historical records into the PRD. Reviewing entities need a way to determine if they should request additional records from previous employers or if all of the historical records have been entered.
2.8.1.7.2.1 If there is no date entered in this field for the pilot, then the reviewing entity must assume more records are available from that reporting entity that are not yet entered in the PRD. The reviewing entity can request the additional records be entered via the request function in the PRD. When a reporting entity receives the request, they must enter any outstanding records within 14 days in accordance with § 111.215(b). When a reporting entity has entered all of the appropriate records, they should enter a date in this field to indicate they have completed the process.
2.8.1.7.2.2 If there is a date in this field, it indicates that the reporting entity has entered all records for this pilot as of the date indicated. If a PAC operator is not reporting all records contemporaneously, the operator should not enter a date indicating all records are current.
If this date is more than 30 days old and the employer is the pilot’s current employer, the reviewing entity should still request any additional records via the PRD. This will notify the employer
2-43 to ensure any records which have been generated since the date entered in the field are entered. They must report any outstanding records within 14 days and update the date to indicate it is complete.
2.8.1.7.3 No Additional Records to Report to PRD Date. This date field is used to indicate when a reporting entity has entered all available records for a pilot into the PRD and no additional records are expected. This would be appropriate in cases when a pilot no longer works for the reporting entity. As a reviewing entity, if there is a date in this field, the reporting entity entered all appropriate records and nothing more is available.
2.8.2 Historical Records. In accordance with § 111.255, the FAA requires all air carriers authorized to conduct operations in accordance with part 121 and/or 135 to provide PRIA records created and maintained by the air carrier on or after August 1, 2005. The FAA also requires operators authorized to conduct operations in accordance with parts 125 and 135 as well as part 91K fractional ownerships to provide specific records created and maintained by the operator or fractional ownership on and after August 1, 2010. PAC operators are not required to comply with these historical records reporting requirements, which only apply to part 119 certificate holders, but may voluntarily enter historical records into the PRD.
Note: All air carriers and operators required to report historical records in accordance with § 111.255(e) must continue to maintain pilot records documented as of August 1, 2005 or August 1, 2010 through the present for 5 years after reporting those records to the PRD.
2.8.2.1 Determining Which Types of Historical Records to Report. A reporting entity that is required by § 111.255 to enter historical records will report the same record information for both historical and contemporaneous records. See Table 2-2 for an overview of what record types are to be reported.
Paragraph 2.8.1 also describes the record types in more detail.
2.8.2.2 Determining Which Records Based on Age to Report. Historical records are any records dated before one year after publication of part 111. Historical records may date back to August 1, 2005 or August 1, 2010 depending on the type of reporting entity. Table 2-1 provides an overview of historical records reporting. See paragraph 2.10.3 for more information about reporting historical records during the transition between PRIA and the PRD.
2.8.3 Distinguishing Between Company Records and PRD Records. Air carriers and operators typically maintain records that are separate and in addition to records they may have obtained from the PRD or otherwise received as required by part 111. Such records are referred to as “company records” whereas the records obtained in accordance with part 111 are referred to as “PRD records.”
2-44
2.8.3.1 Company records are events or actions memorialized by an air carrier or operator to document compliance with a statute or regulation, or maintained through a company’s own initiative. These records typically are comprised of documented training and qualification events, performance, and employment-related activities during the period that an individual is employed by a company as a pilot.
2.8.3.2 PRD records are those obtained through the PRD or otherwise as required by part 111. These records are used to assist a reviewing entity in making a hiring determination. PRD records are not forwarded to another reviewing entity through a future request made in accordance with part 111.
2.8.3.3 PRD records will be archived and maintained completely separate from the reviewing entities “company” records. PRD records should never be actively used again, other than for inspection and review by that company’s FAA Principal Operations Inspector (POI) in order to verify compliance with part 111.
2.8.3.4 A PAR is never to be considered as a reviewing entity’s own “company” records. Companies must only enter records they generate about the pilot into the PRD.
2.8.4 Method of Entry for Pilot Records.35 Initially, the FAA will offer two acceptable methods for reporting entities to report data elements to the PRD. Each reporting entity could opt to use either of the methods described below. A reporting entity may also use both methods but must never report the same record using both methods as this will result in duplicative records in the PRD.
Note: The two reporting options described below are expected to be deployed on different development schedules. Option 2 is expected to be available one year after publication of part 111 which coincides with the initial reporting requirements of part 111 subpart C. Option 1 is expected to be available between one and two years after publication of the part 111.
2.8.4.1 Reporting Method Option 1: Data Transfer Using an Automated Utility.
2.8.4.1.1 The first option is transmitting data electronically using an automated utility.
In order to use this method, the employer would encode the relevant data using an automated utility using Extensible Markup Language (XML) or similar process, so it can be read by both the user and the PRD. The data is transmitted through the PRD application, and the PRD application would be able to extract the relevant information for each pilot and input the information into the appropriate fields in the PRD. Use of an automated utility
35 The PRD complies with federal information security requirements and the FAA has published a PIA for the system, available at https://www.transportation.gov/privacy.
2-45 would minimize the amount of time and effort necessary for an employer to transmit data to the PRD.
2.8.4.1.2 The amount of time an air carrier or other operator employing pilots will spend transmitting data to the PRD using such an automated utility will depend on the user’s internet connection, and volume of data being sent to the PRD. All data is transferred in XML via the automated utility by automatically populating the specified data fields. This requires that the automated utility’s data fields correspond correctly with the PRD’s data fields.
Refer to the Resources section at prd.faa.gov for instructions on setting up the automated utility.
2.8.4.2 Reporting Method Option 2: Manual Data Entry. The second method for air carriers and others employing pilots to transmit data to the PRD is through direct manual data entry, using the same pre-established data field forms for each record type. An air carrier or other operator employing pilots would use manual data entry to report the requisite information from its existing records, regardless of the format in which the records have been stored. The FAA expects that this method would only be used by those operators without the technical capability to use an automated utility using XML. Refer to the Resources section at prd.faa.gov for manual data entry instructions.36
2.8.5 Record Ownership. When a reporting entity enters a record into the PRD, the reporting entity becomes the owner of that record. The record owner is the only entity that can edit the record after it has been created. The PRD allows the transfer of record ownership from one entity to another upon acceptance of responsibility for the record content. For example, this might occur due to a merger of two airlines. Or, in the event of a business closure, the reporting entity might elect to transfer ownership of the records to a third party. Changes of record ownership are a special function. Contact the PRD administrator for assistance.
2.9 Using a Proxy to Meet the Requirements of Part 111. An air carrier or operator may choose to utilize a proxy to meet the requirements of part 111. However, an air carrier or operator maintains the responsibility to ensure compliance with part 111. Certain documentation is necessary from the FAA for a proxy to gain access to the PRD. Refer to the Resources section at prd.faa.gov for further proxy instructions.
2.10 Transitioning From PRIA to the PRD.
2.10.1 Overview. Although the PRD will replace PRIA, for 3 years and 90 days after part 111 publication PRIA is still in effect. However, part 111 has requirements which overlap with PRIA and can often be met concurrently. The overlap exists to ensure that pilot records remain available to hiring employers before they can be entered into the PRD.
During the transition period, hiring employers will need to check both PRIA and the PRD to make sure they have reviewed all of the records. This section of the AC will describe
36 The manual data entry method is expected to be available one year after publication of part 111, and concurrently the Resource guide will also become available.
2-46 how those affected by PRIA as well as part 111 can navigate this transition period. The easiest way for an operator to understand the transition is to break it into three main parts:
continued compliance with PRIA, historical record reporting, and new record reporting.
2.10.2 Continued Compliance with PRIA. Until the expiration of 3 years and 90 days after publication of part 111, certain hiring operators must continue to make PRIA requests for pilot records as part of the hiring process. The effected operators have not changed in this respect. If an effected operator is required to request records under PRIA, that operator must continue to comply with PRIA for 3 years and 90 days after part 111 is published.
The way the operator requests and views those records, however, might change. If the operator receives a PRIA records request, the operator must respond under PRIA until PRIA is sunset. Part 111 uses a phased in compliance schedule to allow plenty of time for employers and pilots to become accustomed to using the PRD and for the system to be loaded with the appropriate records.
2.10.2.1 1–179 Days After Publication. During this period, no changes concerning how a hiring employer will request records under PRIA or how a previous employer will provide those records will take effect. Prior to 90 days after publication of the final rule, all operators, entities, and bankruptcy trustees (if applicable) subject to part 111 must create an RP account in the PRD in accordance with § 111.15. This allows plenty of time for industry and the FAA to ensure everyone is ready for the next big milestone which occurs at 180 days after publication.
2.10.2.2 180 Days After Publication. Any operator that is required under PRIA to review FAA records will now review those records via the PRD in accordance with § 111.100(b). Instead of asking the pilot to complete FAA Form 8060-10 and sending that form to the FAA, you will now use the PRD. The process is detailed in paragraph 2.6.2.2, but the general process involves two basic steps.
First, the pilot logs into the PRD and grants consent to the hiring operator to see the FAA records. Second, the hiring operator logs into the PRD and views the FAA records.
2.10.2.3 One Year After Publication. One year after publication of part 111 operators defined as “reviewing entities” must begin to review any pilot records in the PRD in accordance with § 111.100(b). At the same time, reporting entities must start entering new pilot records as well as historical records into the PRD in accordance with § 111.200. If PRIA requires an operator to review records, the operator will review the FAA records and any industry records available in the PRD. If additional records are available and not yet reported to the PRD, the operator will need to request those previous employer records by sending FAA Form 8060-11 or making the request via the PRD system itself. The PRD system offers an easy function to request records about a pilot if the previous employer has not yet entered them into the PRD. If an operator is a previous employer and receives a request for records, the operator can either provide those records via the mail, email, etc. or enter those records into the PRD.