Appendix 2
(2) System Overview. The system uniformly applies FAA master requirements in a way that tailors a particular aircraft to any operator’s unique situation or fleet. The FAA approves unique operator and fleet requirements for each operator based on FAA master requirements.
The system develops FAA master requirements based on objective criteria and tests, with the applicant’s (usually an aircraft manufacturer) support for analysis and testing. FSB reports for related aircraft describe FAA master requirements. MDRs express the minimum acceptable difference levels between related aircraft. An operator’s training and qualification program, checklist, operations manuals, and other such approvals are byproducts of compliance with MDRs. Operators comply with MDRs using unique operator difference requirements (ODR), tailored to that operator’s programs and approved by the FAA. ODRs based on and in compliance with the MDRs specify requirements uniquely applicable to a particular operator’s mixed fleet flying situation. An operator’s specific document describes ODRs by identifying a base aircraft, differences between related aircraft, and that operator’s compliance methods for each related aircraft.
b. Master Differences Requirements (MDR).
(1) MDR Applicability. MDRs are those requirements applicable to training and qualification that pertain to differences between related aircraft. MDRs specify the minimum acceptable difference levels between related aircraft that may be approved for operators.
One related aircraft is selected by the operator as a reference for comparison purposes and is considered a base aircraft. This is typically the first aircraft on which pilots are qualified, or is the aircraft of which an operator has the largest number. Difference levels between the base aircraft and other related aircraft then specify the minimum difference requirements to be met for pilot training and qualification. Major differences in a particular fleet are defined between groups of related aircraft rather than specifying differences between each possible configuration and combination of configurations between related aircraft. MDRs are specified in terms of training and checking difference levels as shown on an MDR table.
(2) MDR Content. MDRs specify the minimum training and checking acceptable to the FAA for pilot training and qualification regarding differences.
(3) MDR Formulation, Description, and Revision. MDRs are formulated by the FAA FSB for related aircraft. MDRs are originally specified when an aircraft is first TC’d. MDRs are formulated using standardized tests and evaluations in conjunction with the aircraft type certification or supplemental type certification process. MDRs are based on an applicant’s proposal, FAA evaluation of that proposal, in-service experience, and test results when tests are necessary. FSB determinations also consider operator recommendations, safety history, and other relevant information. MDRs are described in recommendations of an FSB report and may be revised if necessary. MDRs are revised when aircraft are developed or modified, tests or in-service experience shows a need for revision, a revision is requested by an applicant and evidence indicates the need for revision, or rules or FAA policies change. MDRs are revised by a process similar to that used for initial formulation of requirements.
(4) MDR Use. MDRs are applied to specific operators through formally described ODRs that are developed by and tailored to each operator. FAA field offices use the MDRs as the basis
Appendix 2 for approval of an individual operator’s differences or related aircraft differences training program.
(5) The MDR Table. An example of typical MDRs for the Boeing 737-200, -300, -400, -500, -600, -700, -800, and -900 is shown in Figure 1. MDR table requirements are shown for each pair of aircraft by notations in each element of corresponding columns and rows of the table. Each element of the table identifies the minimum difference training and checking requirements applicable to mixed fleet flying. Differences levels are arranged as training/checking. The MDR table identifies a pertinent base aircraft and particular aircraft for which requirements are sought. Note the minimum difference levels that correspond to the pertinent column and row, and special requirements in footnotes, if applicable.
(6) Use of Higher or Lower Difference Levels. Operators will satisfy difference requirements by using the methods acceptable for the specified level or a higher level. Lower level methods may be used in addition to the required levels but may not substitute for the required level or be used exclusively instead of the required level.
FIGURE 1. MASTER DIFFERENCES REQUIREMENTS TABLE
FROM AIRCRAFT Boeing 737 BASIC Boeing 737 -100, -200 (SP77) Boeing 737-200 ADV Boeing 737-300, -400, -500 (NON-EFIS) Boeing 737-300, -400, -500 (EFIS) Boeing 737-600, -700, -800, -900
TO AIRCRAFT Boeing 737 BASIC Boeing 737-100, -200 (SP77) A/A
(2) NAV-B/B
(6) PMS-C/B B/A
(2) NAV-B/B
(6) PMS-C/B C*/C C/C* D/D Boeing 737-200 ADV B/A
(1) PDCS- C/B
(2) NAV-B/B
(4) AFCS- C/B
(6) PMS-C/B A/A
(1) PDCS- C/B
(2) NAV-B/B
(4) AFCS- C/B
(6) PMS-C/B C*/C*
(1) PDCS- B/B
(2) NAV-B/B
(5) LIMITED
FMS-C/B C*/C*
(1) PDCS- B/B
(2) NAV-B/B D/D
(1) PDCS- B/B
(2) NAV-B/B Boeing 737-300, -400, -500 (NON-EFIS) C*/C*
(5) LIMITED
FMS-C/B C*/C*
(5) LIMITED
FMS-C/B A/A
(7) CROSS
SERIES- A/A C/B (8) C/B Boeing 737-300, -400, -500 (EFIS)
(3) C*/C*
(5) LIMITED
FMS-C/B
(3) C*/C*
(5) LIMITED
FMS-C/B
(3) C/B A/A
(7) CROSS
SERIES- A/A
(8) C/B
(9) PFD/ND- D/C Boeing 737-600, -700, -800, -900 D/D D/D (8) C/B
(9) PFD/ND- D/C
(8) C/B
(9) PFD/ND- D/C A/A
(9) PFD/ND- D/C
(11) EDFCS- C/C
Appendix 2
(7) Differences Within a Series. Differences may exist even within series shown on an MDR table. MDR elements may show requirements from one series to another identified in the footnotes. Such requirements, however, apply only if pertinent differences exist between those aircraft.
(8) More Than One Related Aircraft. When an operator assigns a pilot to more than one related aircraft of the same TC (e.g., Boeing 737-100/-200/-300/-400/-500/next generation), or more than one aircraft with different TCs (e.g., Boeing 757 and Boeing 767) designated as related, each pertinent requirement of the MDR table applies.
(9) Special Requirements.
(a) MDR Footnotes. Footnotes can be used to credit, constrain, or set alternate levels when special situations apply. Use of footnotes permits accommodation of variations in installed equipment, options, pilot knowledge, or experience on other aircraft, training methods or devices, or other factors that are not addressed by basic levels between aircraft. For example, a footnote may allow credit or apply constraints to the use of a particular flight guidance control system (FGCS), flight management system (FMS), or electronic flight instrument system (EFIS), which is installed on aircraft. Footnotes are an appropriate means to address requirements that relate to specific systems (e.g., flight director and FMS) rather than a particular aircraft. In such instances, generic knowledge or experience with the particular system may be readily transferable between related aircraft. Footnotes may also be used to set different requirements for initial training or checking rather than for recurrent training or checking. When necessary, footnotes are fully described in the body of the FSB report.
(b) Other Limitations. Other limitations may occasionally be identified within a difference level (e.g., C*). The asterisk following the difference level in such instances identifies a special requirement or limitation pertaining to a particular training method, checking method, or device. Such notes typically relate to acceptable FSTDs when the FSTD evaluation and approval process or standard criteria of this AC are not available to address a particular situation appropriately.
(10) MDRs for Aircraft with the Same or Different TC. A single FSB report and MDR table may apply to aircraft that are assigned the same TC with the same type rating
(e.g., Boeing 737-100/-200/-300/-400/-500 and next generation). A single FSB report and MDR table may also apply to different TC’d aircraft (e.g., Boeing 757 and Boeing 767). When it is determined that level E training is required for an aircraft with the same aircraft TC and a different type rating is determined, a single MDR table for all series of that TC’d aircraft still applies (e.g., Boeing 747 and Boeing 747-400). Minimum acceptable difference levels are assigned based on standard tests described in Appendix 3, Rating and Level Tests—Planning and Application.
c. Difference Levels.
(1) General Description. Difference levels specify FAA requirements proportionate to and corresponding with increasing differences between related aircraft. A range of five difference levels in order of increasing requirements, identified as A through E, are each specified for training and checking. MDRs are specified in terms of difference levels. Difference
Appendix 2 levels are used to credit knowledge, skills, and abilities applicable to an aircraft for which a pilot is already qualified and current, during initial, transition, or upgrade training for other related aircraft. Operators who conduct mixed fleet flying where credit is sought, should apply difference levels and address all mixed fleet flying requirements to ensure compliance with FAA requirements necessary to ensure safe operations.
(2) Basis for Levels. Difference levels apply when a difference with potential to affect flight safety exists between related aircraft. Differences may also affect knowledge, skills, or abilities required of a pilot. If no differences exist or if differences exist but do not affect knowledge, skills, abilities, or flight safety, then difference levels are not assigned; nor are they applicable to pilot training and qualification. When difference levels A through E apply, each difference level is based on a scale of differences in design features or maneuvers. In assessing the effects of differences, both flight characteristics and procedures are considered, since flight characteristics address handling qualities and performance, while procedures include normal and abnormal/non-normal/emergency items.
(3) Relationship Between Training and Checking Levels. While particular aircraft are often assigned the same level (e.g., C/C) for training and checking, such assignment is not necessary. Levels may be assigned independently. For example, an aircraft may be assigned level C for training and level D for checking (e.g., C/D).
(4) Evaluation for Determination of Aircraft Type Ratings.
(a) Aircraft with the same TC when evaluated for type rating determination are assigned the same type rating if training differences are no greater than level D.
(b) Aircraft of the same make having different TCs, that have training differences no greater than level D, will be assigned different type ratings that may be considered in common with each other.
(c) Aircraft of the same make that have level E training difference requirements will be assigned a different type rating. Aircraft with systems such as Head-Up Display (HUD), Enhanced Vision Systems (EVS), or Synthetic Visions Systems (SVS) may require Level E training without requiring a new type rating.
d. Training Difference Levels.
(1) Level A Training. Level A training is that training between related aircraft that can adequately be addressed through self-instruction. Level A training represents a knowledge requirement that, once appropriate information is provided, understanding and compliance can be assumed. Level A compliance is achieved by such methods as issuance of operating manual page revisions, dissemination of operating bulletins, or differences handouts to describe minor differences in aircraft. Level A training is limited to the following situations:
(a) A change that introduces a different version of a system/component for which the pilot has already shown the ability to understand and use (e.g., an updated version of an engine).
Appendix 2
(b) A change that results in minor or no procedural changes and does not adversely affect safety if the information is not reviewed or forgotten (e.g., a different vibration damping engine mount is installed, expect more vibration in descent; logo lights are installed, use is optional).
(c) Information that highlights a difference, which is evident to the pilot, inherently obvious, and easily accommodated (e.g., different location of a communication radio panel, a different exhaust gas temperature limit that is placarded, or changes to non-normal “read and do” procedures).
(2) Level B Training. Level B training applies to related aircraft with system or procedure differences that can adequately be addressed through aided instruction. At level B, aided instruction is appropriate to ensure pilot understanding, emphasize issues, provide a standardized method of presenting material, or aid retention of material following training.
Level B aided instruction can utilize audiovisual presentations, computer-based tutorial instruction, or stand-up lectures. Situations not covered under level A training may require level B training (or higher levels) if certain tests described in later paragraphs fail.
(3) Level C Training. Level C training applies to related aircraft having part task differences that affect knowledge, skills, and/or abilities. Level C training can only be accomplished through use of devices that are capable of systems training. The training objectives focus on mastering individual systems, procedures, or tasks, as opposed to performing highly integrated flight operations and maneuvers in “real time.” Level C may require self-instruction or aided instruction, but cannot be adequately addressed by a knowledge requirement alone. Training devices are required to supplement instruction, ensure attainment or retention of pilot skills and abilities, and accomplish the more complex tasks, usually related to operation of particular aircraft systems. Typically, the minimum acceptable training method for level C training would be interactive computer-based training (CBT), cockpit procedure trainers, part task trainers (e.g., FMS or Traffic Alert Collision and Avoidance System (TCAS)), or a level 4 or 5 flight training device (FTD).
(4) Level D Training. Level D training applies to related aircraft having full task differences of knowledge, skills, and/or abilities. Level D training can only be accomplished with devices capable of performing flight maneuvers in a dynamic real-time environment.
The devices enable integration of knowledge, skills, and abilities in a simulated flight environment, involving combinations of operationally oriented tasks and realistic task loading for each relevant phase of flight. Level D training requires mastery of interrelated skills that cannot be adequately addressed by separate acquisition of those skills. However, the differences are not so significant that a full transition training course is required. Training for level D differences requires a training device that has accurate, high-fidelity integration of systems and controls, and realistic instrument indications. Level D training may also require maneuvers, visual cues, motion cues, dynamics, control loading, or specific environmental conditions.
Weather phenomenon such as low visibility, CAT III, or windshear may or may not be incorporated. Where simplified or generic characteristics of an aircraft type are used in devices to satisfy difference level D training, significant negative training must not occur as a result of the simplification. Typically, the minimum acceptable training method for level D training would be FTD level 6.
Appendix 2
(5) Level E Training. Level E training applies to aircraft having such significant full task differences that a high-fidelity environment is required to attain or maintain knowledge, skills, or abilities. Training at level E can only be satisfied by the use of a full flight simulator (FFS) qualified at level C or D consistent with FAA criteria. Level E training, if done in an aircraft, should be modified for safety reasons where maneuvers can result in a high degree of risk (e.g., an engine set at idle thrust to simulate an engine failure). As with other levels, when level E training is assigned, suitable credit or constraints may be applied for knowledge, skills, and/or abilities related to other pertinent related aircraft. Credits or constraints are specified for the subjects, procedures, or maneuvers shown in FSB reports and are applied through the ODR table.
NOTE: Training difference levels specified by the FSB represent minimum requirements. Operators may use a device associated with a higher difference level to satisfy a training difference requirement. For example, if level C differences are assessed due to installation of a different FMS, operators may train pilots using the FMS installed in a FFS as a system trainer if a dedicated part task FMS training device is not available.
e. Checking Difference Levels.
(1) Initial and Recurrent Checking. Differences and related aircraft differences checking addresses any pertinent pilot qualification requirements and any other checks specified by FSB reports. Initial and recurrent checking levels are the same unless otherwise specified by the FSB. In certain instances, it may be possible to satisfactorily accomplish recurrent checking objectives in devices that do not meet initial checking requirements. In such instances, the FSB may recommend certain devices that do not meet initial check requirements for use to administer recurring checks. The POI/Training Center Program Manager, in coordination with the FSB, may require checking in the initial level device when doubt exists regarding pilot competency or program adequacy.
(2) Level A Checking. Level A checking indicates that no check is required at the time of training. A pilot is responsible for knowledge of each related aircraft flown. Difference items should be included as an integral part of subsequent recurring proficiency checks.
(3) Level B Checking. Level B checking indicates that a “task” or “systems” check is required following training. Level B checking typically applies to particular tasks or systems such as FMS, TCAS, or other individual systems or related groups of systems.
(4) Level C Checking. Level C checking requires a device suitable for meeting level C (or higher) difference training requirements following training. The checking is conducted relative to particular maneuvers or systems determined by the FSB. An example of level C checking: evaluation of a sequence of maneuvers demonstrating a pilot’s ability to use a FGCS or FMS. An acceptable scenario would include each relevant phase of flight that uses the FGCS or FMS.
(5) Level D Checking. Level D checking requires a check for one or more related aircraft following training. The check covers the particular maneuvers, systems, or devices determined by the FSB. Level D checks are performed using scenarios representing a real-time
Appendix 2 flight environment and devices permitted for level D difference training. A full proficiency check is typically conducted on the base aircraft, and a partial proficiency check on the related aircraft, covering all pertinent differences.
(6) Level E Checking. Unless specified, level E checking requires that a full proficiency check be conducted in a level C or D FFS. As with other levels, when level E checking is assigned, suitable credit or constraints may be applied for knowledge, skills, and/or abilities related to other pertinent related aircraft. Credits or constraints are specified for the subjects, procedures, or maneuvers shown in FSB reports and are applied through the ODR table.
NOTE: Assignment of level E checking requirements alone does not result in determining a separate type rating. Only the assignment of level E training requirements may result in a separate type rating determination.
f. Competency Regarding Abnormal/Non-Normal/Emergency Procedures.
Competency for non-normal maneuvers or procedures is generally addressed by checking requirements; however, particular abnormal/non-normal/emergency maneuvers or procedures may not be mandatory for checking or training. In this situation, it may be necessary to periodically practice or demonstrate those maneuvers or procedures even though it is not necessary to complete them during each check. In such instances, the FSB may specify a currency requirement for training or checking applicable to abnormal/non-normal/emergency maneuvers or procedures that are to be performed. This is to ensure that extended periods of time do not elapse in a series of repeated training and checking events in which significant maneuvers or procedures may never be accomplished. When an abnormal/non-normal/emergency maneuver or procedure is not mandatory and is not accomplished during each proficiency training or proficiency check, but is still important to occasionally practice or demonstrate, the FSB may establish a currency requirement. When determined by the FSB, these currency requirements identify each abnormal/non-normal/emergency maneuver or procedure and an applicable time period or any other necessary/appropriate constraints.
g. Difference Level Summary. Difference levels are summarized in Figure 2 below for training and checking. Complete descriptions of difference levels for training and checking are given above.
FIGURE 2. DIFFERENCE LEVEL TABLE
DIFFERENCE LEVEL TRAINING CHECKING A Self-instruction None B Aided instruction Task or system check C Systems devices Check using device D Maneuver devices* Check using level 6 or higher FSTD E Level C or D FFS or aircraft# Proficiency check using level C or D FFS or aircraft * = FFS or aircraft may be used to accomplish specific maneuvers.
# = A new type rating is normally assigned.
Appendix 2
h. OE, Operating Cycles, and Consolidation of Knowledge and Skills. Credits towards part 121 requirements for OE, operating cycles, and line operating flight time for consolidation of knowledge and skills may be permitted if performed in “designated” related aircraft.
i. Supervised Line Flying (SLF). Experience associated with the introduction of equipment or procedures requiring postqualification skill enhancement during which a pilot occupies a specific pilot position and performs particular assigned duties for that pilot position under the supervision of a check pilot qualified for the operator. One or more of the reasons described below may apply:
(1) Introduction of new systems (e.g., Automatic Dependent Surveillance Broadcast (ADS-B), Runway Area Advisory System (RAAS), etc.).
(2) Introduction of new operations (e.g., oceanic operations, Extended Operations (ETOPS)).
(3) Experience for a particular pilot position (e.g., pilot in command (PIC) or second in command (SIC)).
(4) Special characteristics (e.g., effects of unique airports, mountainous areas, unusual weather, special air traffic control (ATC) procedures, or nonstandard runway surfaces) on this aircraft.
j. Recency of Experience. Credit towards the recency-of-experience requirements of part 121 may be permitted for takeoffs and landings performed in designated related aircraft.
k. Operator Difference Requirements (ODR).
(1) ODR Purpose. If differences exist within an operator’s fleet, which affect pilot knowledge, skills, or abilities pertinent to systems or procedures, ODR tables provide a uniform means for operators to comprehensively manage differences and related aircraft differences training programs and provide a basis for FAA approval of mixed fleet flying.
(2) ODR Content. ODRs identify a base aircraft, describe differences between aircraft, and show an operator’s methods of compliance with FAA requirements. The FAA approves an operator’s initial ODR and each subsequent revision for the following:
(a) Base Aircraft. ODRs identify an aircraft or group of aircraft within an operator’s fleet as a base aircraft. The base aircraft serves as a reference for comparison with other related aircraft to describe their differences.
(b) Significance of Differences. Differences are described in summary form and are categorized by differences in design features and maneuvers. Differences are evaluated relative to their effect on either flight characteristics, pilot skills, and/or procedures.
Appendix 2
(c) Compliance Methods. ODRs show how each operator’s program addresses differences, through description of training and checking methods for each fleet. ODRs describe the specific or unique constraints or credits applicable, and any precautions necessary to address differences between aircraft. ODRs must comply with and may not be less restrictive than FAA MDRs and other FSB recommendations if they are part of the operator’s approved training program. Constraints or credits may be applied to all aircraft in a fleet or only to certain aircraft.
Constraints or credits may address FSTDs, checking methods, knowledge, skills, procedures, maneuvers, or any other factors that apply to or are necessary for safe operations. Training and checking compliance methods are proposed and revised by each operator consistent with Differences Tables found in FSB reports.
(3) Standard ODR Format. ODRs are depicted in tables in summarized form.
If necessary, any explanation of details about differences, constraints, and credits, precautions or compliance methods are included in attachments or appendices to ODR tables or are cross-referenced to other operator documents. Figure 3 shows the general format for ODR tables, including examples of design and maneuver differences. The far left column lists design or maneuver differences that are pertinent. The “Remarks” column summarizes specific areas or items of difference. The “Flight Characteristics” and “Procedural Change” columns identify what (if any) difference effects are noted. The “Compliance Methods” section of the table notes the particular operator’s approved means of compliance with FAA MDR recommendations.
The following abbreviations apply:
• ACFT — Aircraft.
• AFDS — Auto Flight Display System.
• AV — Audiovisual Presentation.
• CBT — Computer-Based Training.
• EFIS — Electronic Flight Instrument System.
• EICAS — Engine Indicating and Crew Alerting System.
• FSTD — Flight Simulation Training Device.
• FLT CHAR — Flight Characteristics.
• FMC — Flight Management Computer.
• FMS — Flight Management System.
• PROC CHNG — Procedural Changes.
• SU — Stand-Up Instruction (traditional classroom instruction).
Appendix 2 FIGURE 3-1. DESIGN OPERATOR DIFFERENCE REQUIREMENTS
TABLE EXAMPLE
DESIGN OPERATOR DIFFERENCE REQUIREMENTS TABLE FROM BASE AIRCRAFT: 737-200 ADVANCED TO RELATED AIRCRAFT: 737-300 APPROVED BY (POI):
COMPLIANCE METHOD
TRAINING CHECKING DESIGN
FEATURE REMARKS FLT CHAR PROC CHNG
AIRPLANE
CONFIGURATION
- BODY EXTENSION 104”
- WING TIP EXTENSION 14”
- DORSAL FIN
- w/STC ST01219SE,
BLENDED
WINGLET
YES NO B AV/ SU/ CBT
PANEL LAYOUT - ADDITION OF
FMC/AFDS/AT/IRS ETC.
NO NO B AV/ SU/ CBT
WEIGHTS - GROWTH
RELATED
CHANGES
NO NO B AV/ SU/ CBT
Appendix 2 FIGURE 3-2. MANEUVER OPERATOR DIFFERENCE REQUIREMENTS
TABLE EXAMPLE
MANEUVER OPERATOR DIFFERENCE REQUIREMENTS TABLE FROM BASE AIRCRAFT: 737-200 ADVANCED TO RELATED AIRCRAFT: 737-300 APPROVED BY (POI):
COMPLIANCE METHOD
MANEUVER REMARKS FLT CHAR PROC CHNG TRAINING CHECKING
- OPTIONAL USE
OF AFDS, AND
A/T (ALSO
AN OPTION FOR -200 AFCS
AIRPLANES)
- OPTIONAL USE
OF FMCS
- OPTIONAL USE
OF AFDS, AND A/T (ALSO AN OPTION FOR -200 AFCS
AIRPLANES)
- OPTIONAL USE
OF FMCS
NO SEE APP C FMS/ AT C* + OE
NON-NORMAL
MANEUVERS NORMAL
TAKEOFF, CLIMB,
CRUISE,
DESCENT,
INSTRUMENT
APPROACHES,
LANDING
NO SEE APP FMS/ AT C*
(4) ODR Approval, Distribution, and Availability. ODRs are approved for each fleet by an operator’s FAA POI in accordance with FSB report recommendations. ODRs must be prepared, reviewed, approved, and then used to govern training before start of operations.
The operator retains approved ODRs with a duplicate copy as part of FAA CHDO records.
(5) ODR Revision. ODR tables are revised by operators and reapproved by the FAA when fleet characteristics change or when compliance methods change. Fleet characteristic changes include redesignation of base aircraft, modification of aircraft, addition of aircraft, change of aircraft, or phaseout of aircraft. Changes in compliance methods refer to introduction of new or different training methods, contracting for use of different FSTDs, revision of checking methods, or other such changes. Revisions to ODRs are also prepared, reviewed, and approved before operating.
NOTE: Paragraph 6 describes the development, approval, and application of ODR tables to individual operators’ programs. Paragraph 7 describes FAA review and approval of programs by POIs.
Appendix 2
5. FORMULATION OF FSB REPORTS, MDRs, AND DETERMINATION OF TYPE RATINGS.
a. Formulation Process Overview. The process for FAA formulation and revision of MDR requirements is shown in Figure 4. The process determines which information is required for an aircraft. It includes a proposal for requirements, tests, and evaluations of the proposed requirements. It then finalizes, applies, and implements the FSB recommendations. Applicants propose MDRs, examples of ODRs, and any other FSB recommendations that are necessary.
Proposals for requirements are based on design objectives, analysis, evaluation of in-service experience, other programs that have been proved acceptable to the FAA, or other methods.
Setting of requirements is based on an objective set of tests and standards, analysis of results, and FAA judgments considering in-service experience. The applicant and the FAA prepare and conduct standardized tests. The applicant provides test support, and the FSB conducts the evaluation. The FSB, in conjunction with the applicant, evaluates the results, and the FAA formulates proposed minimum requirements. The FSB sets final recommendations by specifying MDRs and other FSB recommendations. An FSB report that describes findings can be found on FSIMS under Publications. The formulation and application process of FSB recommendations starts at the time a new aircraft is proposed to the FAA and continues throughout the fleet life of that aircraft. For aircraft already in service, the process may be initiated when significant modifications are proposed, a new piece of equipment (e.g., a HUD) requiring operational evaluation is introduced and requested by operators, or when mixed fleet flying takes place.
The FAA addresses periodic revisions of requirements when necessary, and revisions are initiated by the FAA and applicants as needed.
b. Proposals for MDRs, Example ODRs, and Special Requirements.
(1) When Proposals are Necessary. The FAA usually determines when proposals are necessary and advises the applicant what information is needed, in conjunction with aircraft type certification or supplemental certification programs. Necessary information may include MDRs for related aircraft or other elements of the FSB reports. The applicant considers existing MDRs and existing or proposed ODRs.
(2) Proposal Formulation. An operator, manufacturer, or an organization that modifies aircraft proposes a new design or modification. The applicant will then do the following:
(a) Formulate necessary information for training, checking, and currency for the aircraft in proposals for MDRs and example ODRs.
(b) Prepare example ODR tables for candidate aircraft to support development of a proposed MDR. These examples represent proposals for programs for those specific aircraft and configurations that the FAA could approve.
(c) Identify related aircraft for the proposed MDR table.
(d) Formulate any necessary tests to assess difference levels and associated training, checking, and currency requirements for incorporation in the MDR table.