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
2-24 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.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.
2-25 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 R ecords 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 Part 125:
§ 111.200(a)(1) No Yes Yes Yes Yes Part 91K:
§ 111.200(a)(2) 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-26
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.
2-27 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.
2-28 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 F or 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.