AC 120-53B

Change 1Historical

Advisory circular · Guidance for Conducting and Use of Flight Standardization Board Evaluations

A newer version is currentThis is a historical version. AC 120-53C is the version in force, approved September 11, 2025.
Approved
October 24, 2016
Last reviewed
August 9, 2024
This change
CHG 1 of AC 120-53B.
Cancels
AC120-53B
Family
AC 120-53 · 5 versions
Revision
B, change 1
14 CFR parts
121

Guidance, not mandatory unless a rule or AD requires it. DRS record last changed November 22, 2025.

Show pages 25–36
Page 37OCROpen in PDF

Appendix 2 FIGURE 8. FLIGHT STANDARDIZATION BOARD PROCESS

FSB PROCESS ORDER 8900.1

OTHER REQUIREMENTS

MDR TABLE

APPROVAL OF TRAINING

POI REVIEW PROGRAM(S) CHECK FSB PILOTS OPSPECS ETC.

FSB REPORT FAA CHDO AFS-200

NONCURRENCE

PROPOSED ODR APPROVED

TABLE(S) ODR OPERATIONS (FROM OPERATOR) TABLE(S)

MDR ODR REVISIONS

REVISION

REQUESTS (IF

NEEDED) MDR-Master Difference Requirements ODR-Operator Difference Requirements POI-Principal Operations Inspector FSB-FAA Flight Standardization Board OPSPECS-Operations Specifications

7. FAA REVIEW AND APPROVAL OF OPERATOR PROGRAMS.

a. General. The FAA has the responsibility for review, approval, and continuing surveillance of individual operator programs consistent with this AC and FSB recommendations.

Within a CHDO or Flight Standards District Office (FSDO), POIs have the responsibility for program review and approval.

Page 38 · 28Open in PDF

Appendix 2

b. Operator Application of ODRs.

(1) Operators Using Related Aircraft in Mixed Fleet Flying. If FSB recommendations are published, operators operating aircraft in mixed fleet flying in accordance with the applicable CFR may apply recommendations of this AC and the FSB report.

(2) Threshold Requiring ODR Preparation. Even though an operator has different configurations of aircraft used in mixed fleet flying, there is some threshold below which ODR tables and POI approval is not required. The threshold requiring AC and ODR application occurs when differences in related aircraft affect pilot knowledge, skills, and/or abilities pertinent to flight safety. If systems, controls, indications, procedures, or maneuvers are different and these differences have an effect that significantly relates to what the pilots needs to know or do for safe mixed fleet flight operation, then an operator should prepare ODR tables and must seek FAA approval. Conversely, ODR tables would not need to be prepared in situations that do not affect flight safety. In such instances, ODR tables are not needed, even though pilots routinely operate several related aircraft. A minimum threshold is set to preclude unnecessary administrative assessment of mixed fleet flying, which has no safety implications. If changes to the fleet do not affect pilot knowledge, skills, or abilities affecting flight safety, then such changes need not be considered in addressing FSB recommendations or this AC.

(3) FAA Review of ODR Proposals. After preparation, the carrier submits proposed ODR tables and supporting information to the CHDO and POI for review and approval. POIs evaluate the following:

(a) The operator has made an appropriate identification of a base aircraft.

(b) Operators have comprehensively identified differences in the particular fleet. This includes appropriate ODR table comparisons between the base aircraft and each related aircraft.

(c) The operator’s assessment of the effects of differences on flight characteristics and procedures for the base aircraft and each related aircraft are suitable and valid.

(d) The compliance methods listed are consistent with the requirements of the MDR tables, footnotes, Differences Tables, other pertinent FSB report recommendations, the applicable CFR, authorized deviations, and associated advisory materials.

(e) ODR provisions adequately address any “subtle differences” between related aircraft that have a possibility of inducing potentially serious pilot errors.

(f) Training materials, methods, devices, and FSTDs proposed are acceptable, approved by the NSP if necessary, or if FSB recommendations are applied, the ODR tables meet FSB constraints.

(g) Aviation safety inspectors (ASI) and aircrew program designees (APD) are prepared to apply FSB report checking standards.

(h) Implementation plans are adequate and consistent with FSB recommendations and other FAA policy.

Page 39 · 29Open in PDF

Appendix 2

(i) Other factors determined necessary by the POI are considered and any requirements met.

(4) Differences Tables and MDRs. The POI uses the Differences Tables and the MDRs provided in the FSB report as a basis for evaluating the suitability of a particular operator’s proposed ODR table. The MDR always remains the primary basis for comparison. The AEG should be consulted in the absence of conclusive guidance in making such judgments. Guidance for evaluation of specific system or maneuver items may be found by comparison of the proposal with the Difference Table shown in the FSB report. The operator may use devices, techniques, or methods of an equal or higher difference level. Critical methods should be at least at the level specified by the FSB on the MDRs and shown in the Differences Tables. Actual ODR tables proposed by the operator may show a variety of compliance methods to satisfy a particular item, ranging from level A through the level required by the MDRs. For example, if the MDR requirement is a minimum of level C, the operator may propose to use a combination of level A bulletins, level B audiovisual presentations, and level C training devices to satisfy pertinent items. However, at least level C should be shown for critical items. The operator may choose to satisfy level C with level D or level E methods.

(5) ODR Review Example. The following is an example of the process for review of a specific item on a proposed ODR table. For each proposed ODR item, both the FSB Differences Table and MDRs are consulted and compared with the operator’s proposal. If the MDRs specify that level C devices are needed for training and checking between the base aircraft and a related aircraft and the Differences Table shows applicable level C design differences or maneuvers, then the POI should ensure that the proposed ODR table submitted also shows at least level C for those pertinent design or maneuver differences.

c. Base and Other Aircraft Identification.

(1) Selecting the Base Aircraft. Base aircraft are defined in Appendix 1. In general, base aircraft are used as reference for comparison of differences that affect, or could affect, pilot knowledge, skills, or abilities pertinent to flight safety. A base aircraft should typically be the aircraft that the operator trains to first, the aircraft that the operator has the largest number of, the aircraft most pilots fly frequently, or the aircraft that represents a configuration that the operator eventually will have as a standard. Another aircraft may be selected as a base aircraft when the previous base aircraft is being phased out, converted to a new configuration, or other such factors. A base aircraft may be reassigned at the discretion of the operator with FAA concurrence. A base aircraft is identified by make, type, and series or other distinguishing classifications. Classification should distinguish pertinent differences in configuration, handling characteristics, performance, procedures, limitations, controls, instruments, indicators, systems, installed equipment, options, or modifications.

(2) Identifying Related Aircraft. A related aircraft is an aircraft or a group of aircraft with the same characteristics that have pertinent differences from a base aircraft. Pertinent differences are those that require different or additional pilot knowledge, skills, and/or abilities that affect flight safety. Differences considered pertinent are those relating to configuration, handling characteristics, performance, procedures, limitations, controls, instruments, indicators, systems, installed equipment, options, or modifications. Related aircraft can exist between

Page 40 · 30Open in PDF

Appendix 2 different types or series or within a type or series. When identified in FSB reports, any aircraft included in a MDR table is considered a related aircraft. Like base aircraft, operators identify related aircraft by one of the following:

• Type/series;

• FAA registration “N number;”

• Operator tail number; or

• Any other classification that can uniquely distinguish pertinent differences between each related aircraft group and a base aircraft.

(3) Accounting for Each Related Aircraft. The important factor in base and related aircraft identification and ODR table preparation is that regardless of the combination used, there should be direct and complete traceability of both differences and compliance methods. There must be a clear description showing the adequacy of compliance methods to ensure proper training, checking, and currency to safely operate each aircraft assigned.

d. Approval of ODRs. Following review and determination that an operator’s program addresses the FSB recommendations, the POI approves that particular program by signing ODRs. ODR tables are approved for each applicable related aircraft. Signature of ODRs or revisions, together with other relevant documents such as training programs and operations specifications (OpSpecs), constitute approval by the POI of that operator’s differences and/or related aircraft differences training, checking, and currency program requirements. ODR tables are used for most programs. In instances where aircraft have only a few minor differences at level A, approval may take the form of a letter including necessary information in lieu of using tables.

e. FSB Revision of MDRs, Differences Tables, or Other FSB Recommendations.

When requested, the FSB reviews an operator’s proposals and if necessary, modifies MDRs, Differences Tables, and other FSB recommendations. Major changes in the MDR table may require review by the full FSB. The FSB may consider minor changes or interpretations on an ad hoc basis between FSB meetings for that aircraft. For some requests changes can be made based on existing or the supplied information. Complex cases may require testing to be conducted by the applicant before the MDR table is changed. Should the MDRs and/or Differences Tables be updated to accommodate a change request, the proposed ODR can be approved within the new MDRs and/or Differences Tables.

f. Proving Tests. When a related aircraft is introduced by an applicant, the requirements for proving tests may be effected. FAA Order 8900.1 describes policies for FAA approval of proving tests.

g. Line-Oriented Flight Training (LOFT) or SLF. When operators have LOFT or SLF programs and additional related aircraft are approved, the POI should review those LOFT or SLF programs to ensure applicability to each related aircraft. SLF in the aircraft, or in some instances FFS (as determined by the FSB), may be necessary in accordance with recommendations of the FSB report and with the approval of the POI.

Page 41 · 31Open in PDF

Appendix 2

h. OE. As described in this AC and FSB reports, OE is consistent with definitions and requirements of the applicable CFR.

i. Limitations on the Total Number of Related Aircraft. When mixed fleet flying involves pilots operating more than a base aircraft and a single additional related aircraft, additional constraints limiting the total number of aircraft may apply. When more than two related aircraft are flown, POIs should specifically ensure that subtle or compounded differences between the various related aircraft do not result in confusion of procedures, maneuvers, or limitations. ODRs proposed for the overall combination of aircraft to be flown should be examined to ensure the following:

(1) That multiple differences do not result in confusion of requirements or an excessive level of complexity for pilots to adjust to or retain important differences information;

(2) That subtle variations in difference information are not mistakenly applied and lead to unsafe conditions; and

(3) That the amount of difference information is not excessive, not applied to the wrong aircraft, or not forgotten.

j. Aircraft That Do Not Have an FSB Report. When an FSB report is not prepared for a given TC’d aircraft, or when MDRs, Differences Tables, or other recommendations are not shown, programs are approved in accordance with the applicable CFR, Order 8900.1, and other pertinent inspector guidance material.

8. APPLICATION OF FSB REQUIREMENTS.

a. General. FAA pilot certification inspectors and Designated Pilot Examiners (DPE) should be familiar with FSB recommendations regarding the proper administration of any necessary checks or evaluations for aircraft covered by the FSB report.

b. Checks Regarding Complex Systems.

(1) Checking is required for differences associated with systems that are determined to be at or greater than level B.

(2) Complex systems checks include hands-on operation and ensure demonstrated procedural proficiency in each applicable mode or function. Specific items and flight phases to be checked are specified (e.g., initialization, takeoff, departure, cruise, arrival, approach, and pertinent non-normals).

NOTE: The FSB may recommend additional training beyond that which is otherwise required by 14 CFR to qualify in each TC’d aircraft.

9. FSTD APPROVAL.

a. NSP Representation to the FSB. An NSP member may serve as an advisor to the FSB or as a member of the FSB, to address designation of and approval processes for FSTDs.

Page 42 · 32Open in PDF

Appendix 2

b. Coordination of NSP Criteria with the FSB. NSP development of criteria for FSTDs and approval test guides for new aircraft are coordinated with the FSB. This ensures compatibility of FSB/NSP requirements and effective use of resources for development of approval test guides and determination of FSB recommendations.

NOTE: FSTDs are qualified for use in accordance with part 60.

10. REVIEW AND APPROVAL. FSB reports are approved as designated by the Office of the Director (AFS-1). In the event that revision of an FSB report is necessary, the FSB is provided with necessary policy guidance to implement applicable changes.

11. APPEAL OF FAA DECISIONS. When there is disagreement with recommendations of an FSB report, that disagreement may be expressed to the FSB chairman for the pertinent TC’d aircraft. If an issue cannot be resolved, the issue may then be addressed to AFS-200.

Additional information, data, or analysis may be provided to support differing views regarding the FSB recommendations in question.

Appendix 3 Page i (and ii) APPENDIX 3. RATING AND LEVEL TESTS—PLANNING AND APPLICATION

TABLE OF CONTENTS Paragraph Page

1. PREPARATION1

2. TYPE RATING DETERMINATION THROUGH ANALYSIS—LEVEL A OR B

TRAINING ONLY2

3. FUNCTIONAL EQUIVALENCE—LEVEL A OR B TEST 1 (T1)3

a. Test Purpose3

b. Test Subjects3

c. Test Process3

d. Safety Pilot3

e. Successful Test4

f. Failure of Test4

4. HANDLING QUALITIES COMPARISON BETWEEN AIRCRAFT—TEST 2 (T2)4

a. Test Purpose4

b. Test Subjects4

c. Test Process4

d. Safety Pilot5

e. Successful Test5

f. Failure of Test5

5. SYSTEM DIFFERENCES TEST AND VALIDATION OF TRAINING AND

CHECKING—TEST 3 (T3)5

a. Test Purpose5

b. Test Subjects6

c. Test Process6

d. Successful Test6

e. Failure of Test6

6. CURRENCY VALIDATION—TEST 4 (T4)7

a. Test Purpose7

b. Test Subjects7

c. Test Process7

d. Successful Test7

e. Failure of Test8

7. INITIAL OR TRANSITION TRAINING/CHECKING PROGRAM VALIDATION—

TEST 5 (T5)8

a. Test Purpose8

b. Test Subjects8

c. Test Process8

d. Successful Test8

e. Failure of Test8

8. COMMON TAKEOFF AND LANDING CREDIT (CTLC)—TEST 6 (T6)9

a. Test Purpose9

b. Test Subjects9

c. Test Process9

d. Successful Test9

e. Failure of Test9

Page 44 · 1Open in PDF

Appendix 3 APPENDIX 3. RATING AND LEVEL TESTS—PLANNING AND APPLICATION

1. PREPARATION.

a. The type rating, difference level definition, and test process are initiated when an applicant presents an aircraft for type certification. If the applicant presents a candidate aircraft to the Flight Standardization Board (FSB) as a new aircraft type certification with no anticipated application for type rating credit for similarities with aircraft previously type certificated (TC), then the FSB analyzes the training program requirements using test T5.

The results of T5 will determine a separate type rating and the minimum required training, checking, and currency standards as applicable to that TC’d aircraft. If the applicant presents an aircraft seeking pilot training, checking, or currency credit, based on similarities with an aircraft previously TC’d, a series of possible tests (T1/T2/T3) are developed and used to determine its level of difference with the base aircraft of comparison. The results of these tests will determine the minimum required training, checking, and currency standards as applicable to the candidate aircraft. T6 comparisons may permit common takeoff and landing credit (CTLC) between different TC’d aircraft. In Appendix 2, the details of these situations provide further amplification.

b. To begin the evaluation process for related aircraft, the applicant identifies the base aircraft and the candidate aircraft. The aircraft are then assigned to logical aircraft groups to be described in Master Difference Requirements (MDR) tables and the FSB report.

c. The applicant identifies major differences pertinent to the aircraft and makes comparisons with the proposed candidate aircraft. A differences document (i.e., an appropriate sample Operator Difference Requirements (ODR) table) summarizes the identified differences. Since combinations of related aircraft may be numerous and only typical differences are needed at this stage for test definition, the applicant may select representative ODRs for preparation.

d. Based on the above analysis (including preliminary flight test results or flight simulation estimates, if available), the applicant proposes difference levels to be specified in each cell of the MDR table for the various aircraft combinations.

e. The applicant proposes applicable elements of the test process (T1 through T5 and T6 for CTLC) and a plan for validation of the intended difference levels. Specific aircraft, times, devices, etc., are identified to conduct the required tests for the candidate aircraft. Included in the proposal are any necessary interpretations of expected results using established standards.

Any special, unique, or additional definitions of successful outcomes are also identified.

f. The scope of T1 through T6 is keyed to basic visual flight rules (VFR) and instrument flight rules (IFR) operations in the National Airspace System (NAS).

g. A Federal Aviation Administration (FAA)/applicant agreement is reached on the grouping of aircraft, proposed tests, test plans, schedules, subjects, and interpretation of possible outcomes.

Page 45 · 2Open in PDF

Appendix 3

h. Test subject qualifications are addressed at the time of test specification when a test agreement is reached with the applicant. Test subjects for all tests except T6 are drawn from the FAA. Subject selection considers the factors such as the following:

(1) Background skills of test subject (previously qualified aircraft);

(2) General flight experience and currency;

(3) Test requirements such as location, short notice access, and skills needed for subjects;

(4) Technical areas, qualifications, or experience that subjects should not have to avoid test prejudice;

(5) Eventual FAA geographic or operator related distribution requirements for aviation safety inspectors (ASI), aircrew program managers (APM), and principal operations inspector (POI) personnel; and

(6) Other special experience as needed for a particular program.

i. During preparation for testing and evaluation of results, appropriate Aircraft Certification Flight Test Branch coordination is accomplished so that flight characteristic issues and, in particular, special flight characteristics can be suitably identified and addressed.

NOTE: Tests T1 and T2 must be conducted in the candidate aircraft for the determination of training, checking, and currency requirements. A full flight simulator (FFS) may be used for FSB-selected T-tests that involve partial task evaluation of systems or components that do not directly relate to aircraft handling qualities or core pilot skills. These types of tests would normally require only a training device with no visual or motion capabilities.

The FSB chairman may elect to use a FFS before its qualification by the National Simulator Program (NSP).

2. TYPE RATING DETERMINATION THROUGH ANALYSIS—LEVEL A OR B TRAINING ONLY.

a. Typically, with the introduction of a new aircraft, or when training credit is sought in a comparison of a base and candidate aircraft, the T1 through T5 testing process determines type rating. Not all changes or modifications to an aircraft or on occasion, the certification of a related aircraft may require flight-testing to assess their impact upon type rating. Type rating determination through analysis may be considered if the changes do not influence aircraft handling, introduce no significant change to systems operation or pilot procedures, and can be addressed at level A or B training.

b. The analysis process can be used if the aircraft handling has not changed significantly.

In most cases, it should be obvious that the change will not affect aircraft handling, but if additional data is needed to make the determination, the information can be obtained from the assigned FAA Aircraft Certification Service (AIR) or through the applicant’s flight test data.

Following is a list of typical changes evaluated through the analysis process:

Page 46 · 3Open in PDF

Appendix 3

(1) Maximum operating weights (revised aircraft Type Certificate Data Sheet (TCDS)).

(2) An engine type or thrust change that does not require significant design changes to aircraft flight controls.

(3) Maximum passenger capacity (revised aircraft TCDS).

(4) Avionics upgrades (Supplemental Type Certificate (STC) or manufacturer production line upgrade).

(5) Proven Electronic Flight Bag (EFB) installation (STC or manufacturer production line upgrade).

(6) Passenger to cargo conversions or freighter variation of passenger aircraft.

c. When the analysis process is completed, it is recorded as a revision to the training courseware and to the existing FSB report for the base and/or candidate aircraft.

3. FUNCTIONAL EQUIVALENCE—LEVEL A OR B TEST 1 (T1).

a. Test Purpose. The T1 test is conducted to determine if training level A or B is appropriate between the base and candidate aircraft.

NOTE: If the applicant communicates that the training and/or checking requirements for the candidate aircraft may exceed level B, the T1 test can be waived and the evaluation process then moves directly to the T2 test.

By waiving the T1, the applicant acknowledges that differences exist between the base and candidate aircraft, and may demand that training and/or checking requirements up to but not exceeding level D are applied.

b. Test Subjects. Test subjects are designated FAA FSB members, trained, experienced, and current on the base aircraft with no training for the candidate aircraft. The applicant may provide proficiency training in the base aircraft to the designated FSB members before testing begins.

c. Test Process. Applicants initiate the test process when they propose that the minimum training and checking requirements for the base and candidate aircraft are no greater than level B differences. T1 is typically conducted using one group of test subjects. Subjects will initially be given a “no jeopardy” flight check for their base aircraft to calibrate performance before taking the pertinent flight check in the candidate aircraft being evaluated. The flight check undertaken in the candidate aircraft will address the differences between the base aircraft and candidate aircraft. The test may be administered or observed by more than one FSB member to ensure consistency and uniformity of test procedures and common understanding of subject performance and outcomes.

d. Safety Pilot. A “safety pilot,” serving as pilot in command (PIC) in the aircraft and functioning as pilot monitoring in either seat, will intervene to prevent damage to the aircraft or to limit maneuvers that endanger safety of flight.

Page 47 · 4Open in PDF

Appendix 3

e. Successful Test. FSB members decide the outcome of the T1 test consistent with previously agreed upon criteria. The FSB determines the areas of training required and specifies necessary devices or training limitations. If the T1 test is passed, the pertinent aircraft pairs are assigned to level A or level B training differences. Successful completion of T1 results in the designation of a type rating that is either the “same” as, or is “in common” with the base aircraft.

f. Failure of Test. If the T1 test is failed and retesting is not considered, level A or B cannot be assigned. This generally requires completion of T2 and T3. If requesting training credit, the applicant may ask for and receive credit for those items passed in T1. T1 retesting may be considered at the discretion of the FSB.

4. HANDLING QUALITIES COMPARISON BETWEEN AIRCRAFT—TEST 2 (T2).

a. Test Purpose. The T2 test compares handling qualities between the base and candidate aircraft. At the discretion of the FSB chairman, the T2 test may be completed through analysis, without requiring an aircraft flight. Determining if the analysis process can be used requires verification that the aircraft handling has not changed significantly as described in the “test process.” In most cases, it should be obvious that the change will not affect aircraft handling, but if the determination requires additional data, the information is obtained from the assigned FAA Aircraft Certification Office (ACO) or through the applicant’s flight test data. With FAA agreement, elements of T2 may be incorporated within the T3 test to verify that an advanced FFS or aircraft training is not needed to address handling qualities.

NOTE: If T2 is conducted on an aircraft that is expected to require a separate type rating with CTLC, credit will be validated by using the T6 process.

b. Test Subjects. Test subjects are designated FAA FSB members who are trained, experienced, and current on the base aircraft with no training for the candidate aircraft. Training to proficiency may be provided in the base aircraft to the designated FSB members by the applicant before the start of testing.

c. Test Process. The applicant initiates the test process when they analyze available flight or simulation test data, and aircraft design or system differences, and determine that handling similarities exist between the base and candidate aircraft. From this determination applicants make their T2 proposal. Before the test, representatives of the FSB review the T2 test profile to ensure that critical handling quality aspects of the candidate aircraft are examined. The flight evaluation consists of relevant parts of a proficiency check as determined by the FSB chairman.

T2 consists of a comparison between selected pilot qualification flight check maneuvers (normal and non-normal) administered first in the base aircraft (using either the actual aircraft or a level C or D FFS), then in the candidate aircraft. Although T2 testing should always be accomplished in the candidate aircraft, some portions that significantly affect aircraft safety, such as flight control failures, may be conducted in a FFS suitable for the test. Subject pilots are evaluated on performance of required maneuvers consistent with standards set by the CFR and an assessment of the degree of difficulty in performing maneuvers in the candidate aircraft compared to the base aircraft. The test may be administered or observed by more than one FSB

Page 48 · 5Open in PDF

Appendix 3 member to ensure consistency and uniformity of test procedures and common understanding of subject performance and outcomes.

d. Safety Pilot. The safety pilot serving as PIC in the aircraft and functioning as pilot monitoring in either seat will intervene to prevent damage to the aircraft or to limit maneuvers which endanger safety of flight. The safety pilot can only assist the subject pilot in areas unrelated to the handling qualities determination. For example, the safety pilot can remove impediments to progression of the test but cannot fly, coach, or train the subject on any aspect of the test related to handling, vision cues, or motion cues. The safety pilot may not actuate primary flight controls during the evaluation, or instruct, lead, or coach test subjects in any manner. The safety pilot may:

(1) Perform all routine pilot monitoring duties.

(2) Set up or adjust systems including those normally operated by the pilot flying in accordance with pretest agreements.

(3) Address or resolve procedural impediments.

(4) Manage and satisfy checklists.

(5) Make normal callouts.

e. Successful Test. The FSB members decide T2 test outcome consistent with previously agreed upon criteria. Acceptable pilot performance in completion of designated maneuvers, without training, establishes that the candidate and base aircraft are sufficiently alike in handling characteristics to permit assignment of level B, C, or D. The test process can then advance to the T3 test.

f. Failure of Test. Failure of T2 means that major handling differences exist during critical phases of flight or that numerous less critical differences were identified that warrant training in an FFS or aircraft. Accordingly, level E differences will be assigned and the FAA will issue a separate type rating. With a T2 failure, the next step in the testing process is T5 to validate level E requirements and the proposed training course. Failure of the T2 does not necessarily mean that the base and candidate aircraft do not share a high degree of system and/or handling commonality. The applicant may elect to use the data collected during the T2 process to justify approval of a shortened type rating course for pilots that are trained on the base aircraft and are transitioning to the candidate.

5. SYSTEM DIFFERENCES TEST AND VALIDATION OF TRAINING AND CHECKING—TEST 3 (T3).

a. Test Purpose. The T3 test is used to evaluate the proposed differences and/or related aircraft differences training, checking, and training devices at level B, C, or D.