2-12 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-13
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 9-AMC-AVS-PrdSupport@faa.gov 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-14
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-15
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 9-AMC-AVS-PRDSupport@faa.gov 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-16 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 9-AMC-AVS-PRDSupport@faa.gov 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
2-17 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:
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
2-18 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
2-19 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.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-20 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-21 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-22 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-23 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