(b) Analog discrete inputs or analog warning inputs that are not normally exercised during flight.
(2) The functional check need not include other parameters that verify the accuracy of the output during the source systems operational or functional check. This includes digital discrete input and digital warning input that are not normally exercised during flight.
3-3. ICA. Operators must either follow the TC/STC holder provided ICA as part of its maintenance program or develop their own. The operator developed ICA must identify all requirements that would have been established at time of certification and any others subsequently identified by the FAA, e.g., those applicable under airworthiness directive (AD).
These instructions must include as a minimum:
a. Data stream. The data stream format and correlation data outlined in appendix 1. If this is not available, it should be created from the document or software used to convert the raw data into EU. If the information needed cannot be derived from the download document/software, then the operator must perform the necessary test and analysis to reproduce the necessary documentation (see appendix 2 if applicable).
b. Dedicated sources. A list of dedicated sources is defined in appendix 6. Include procedures for a ground check of these sources. Provide sufficient information, including source, label, and word, to verify the range and accuracy of the recorded data as specified in the applicable operating rule.
c. Removal and replacement. Include removal and replacement instructions for DFDRS equipment and dedicated sensors. Also include instructions for conducting a functional check of the equipment and verification of the parameter range and accuracy.
d. Software. If paragraph 2-6 of this AC applies, include procedures for loading software during DFDRS installation or during DFDRS maintenance. (See FAA Order 8110.49, Software Approval Guidelines.)
Appendix 1 APPENDIX 1. STANDARD DATA FORMAT FOR DIGITAL FLIGHT DATA
RECORDERS, DATA STREAM FORMAT, AND CORRELATION DOCUMENTATION
1. DFDR. The DFDR records flight data in a digital format. Data is normally grouped into words that are synchronized in a data stream. The data stream must be correlated to EU or to discrete states for an accident investigator to use the data. This appendix provides the specific information that operators must provide to the NTSB investigators decoding and converting the raw data stream recorded by the DFDR. This data format information can be contained within an electronic file or in hardcopy document format.
2. Guidelines for documentation. Information regarding acceptable guidelines for documentation of DFDR data content and format are also available in the Flight Recorder Electronic Documentation (FRED) document, ARINC Specification 647A. The ARINC FRED specification provides a standard format for electronic documentation of DFDR data. This standard format supersedes an older electronic format, the Flight Recorder Configuration Standard, Document TP13140E. Although the FRCS documentation format is acceptable, because FRED supersedes TP13140E, the preferred electronic format is the ARINC FRED format. The FRED specification, ARINC 647A, can be obtained by contacting:
ARINC Inc.
Document Section 2551 Riva Road Annapolis, MD 21401-7465 Telephone: (410) 266-4117 Fax: (410) 266-2047 E-mail: standards@arinc.com
3. Definitions. The following definitions apply to terminology often used in the DFDR correlation documentation. These definitions are derived from ARINC Characteristic 717-10, Flight Data Acquisition and Recording System, dated April 1, 1998. An operator using another data stream format must provide definitions unique to its format in the correlation documentation.
a. DFDR bit number. Defines a specific bit location within a DFDR system word on the output from the DFDR. The DFDR bit number is used to locate the bits that are dedicated to a given parameter within the word. For example, DFDR bit numbers 3-12 indicate bit 3 through bit 12. The lowest bit number is normally the least significant bit.
b. Lexicon. A dictionary of all mnemonic codes and the associated parameters each represents. To aid in the standardization of parameter identification, ARINC Specification 647A appendix C contains a recommended lexicon.
c. Mnemonic code. An abbreviation of the parameter name intended to be used in formats where the parameter name is too large. The mnemonic code must be unique and used to identify the parameter as described in the applicable appendix (14 CFR part 121 appendix B or M, part 125 appendix E, or part 135 appendices B through F). The aircraft manufacturer normally assigns a mnemonic code to each parameter. This code is normally correlated to the parameter A1-1
Appendix 1 name in the aircraft manufacturer’s interface control document. However, an installer or an operator may assign a mnemonic code to an added parameter. The mnemonic code must uniquely identify the parameter relative to all other parameters being recorded by the DFDR.
Additional characters may be necessary to uniquely identify the parameter as installed on the aircraft.
d. Parameter name. The name of the function being recorded. The documentation must contain a means to correlate each recorded parameter name to those in the applicable appendix (part 121 appendix B or M, part 125 appendix E, or part 135 appendices B through F). Where possible, the parameter name should correlate to the aircraft manufacturer’s or applicant’s interface control documentation. Sufficient information must be contained in the parameter name to make it unique and to convey information on its source.
e. Range. The full range of a parameter (minimum to maximum) expressed in EU. Where the parameter range accommodated in the aircraft exceeds the parameter range specified in the regulations, (e.g., pressure altitude in large aircraft,) the applicant should provide for recording the range accommodated in the aircraft. Enter “NA” for discrete parameters. Range of a parameter is defined by either:
(1) The full recordable range of the parameter on the flight recorder, or
(2) The parameter’s operational range. The operational range is typically a subset of the recordable range. The inclusion of operational range is useful in analysis of the recorded data.
Note: The inclusion of a parameter’s recorded range does not imply the parameter is recorded linearly on the flight recorder.
f. Signal source. The aircraft subsystem, or the dedicated transducer or signal conditioner, used to provide the signal for the DFDR, FDAU, or DFDAU (or equivalent).
g. Superframe cycle. A subdivision of a given word slot address in a subframe. This typically provides 16 additional addresses. A counter provides the cycle number reference. The cycle number must be documented as a parameter.
h. Word number. The location of a 12-bit word within the subframe. Word numbering starts at 1 (the first word in the subframe).
4. Data stream format.
a. Data stream format. The data stream format defines where an analyst must look in the DFDR output to find a selected parameter or other information. Data stream format and encoded data format characteristics must be described and accurate to the specification provided by the manufacturer. The output of the data stream format should provide clear header and parameter information from the DFDR. Most DFDR data are encoded using the ARINC Characteristic 573 or ARINC Characteristic 717. Although these ARINC data bus encoding systems do not specify the data format, they provide the framework within which the data is formatted, in a fixed-frame format or a multiple-frame format as identified in ARINC Characteristic 767.
A1-2
Appendix 1
b. Frames and subframes. Specifically, they generate 12-bit words with a word rate that may vary, i.e., 32, 64, 128, 256, 512, or 1024 (words/second). The data is organized into frames that are repeated every 4 seconds. Each frame consists of 4 subframes. Each subframe occupies 1 second in the data stream, however, not all data streams are ARINC compliant and a subframe may occupy more or less than 1 second. The first word in each subframe normally provides the frame synchronization pattern. The data stream format should enable the analyst to locate header information and parameter information in the DFDR output.
c. Header information. For DFDRs conforming to ARINC characteristics, the information listed below should be stored in a header file. (For other DFDR frame structures, the number of subframes per frame must be omitted and the frame structure must be uniquely described.) The header file must include:
(1) Aircraft make and model.
(2) Aircraft serial number.
(3) DFDR make and model/part number.
(4) Number of subframes per frame, for a fixed-frame; or a description of each of the frame formats in a multiple-frame format data stream.
d. Record information.
(1) For a fixed-frame format:
(a) Bits in the DFDR word.
(b) Number of DFDR words in a subframe.
(c) Time duration of the subframe (seconds).
(2) For a multiple-frame format:
(a) List of parameters in the frame, in order.
(b) The number of bits used to store each parameter.
e. Parameter information. The identification for each parameter should include:
(1) Parameter name—must be unique from all other parameters recorded.
(2) Mnemonic code—a common abbreviation for the parameter, which must be unique from the mnemonic codes of all other parameters recorded.
f. Parameter location. Both component(s) and timing information should be provided for each parameter sample. Usually there is only one component. For samples having more than one component, the components should be ordered from least significant to most significant in the data stream. Each sample location for a parameter should have the same total number of bits.
A1-3
Appendix 1 The following items must be provided for a parameter sample location when a fixed-frame format is used:
(1) Subframe number.
(2) Word number.
(3) Bit numbers.
(4) If superframe cycles are used, also provide:
(a) Cycle counter name.
(b) Cycle numbers.
5. Lexicon of mnemonic codes. If mnemonic codes are used, a lexicon of these codes must be provided.
6. EU conversion. EU conversions must convert decimal counts to the parameter value measured. Where the parameter is used by the pilot in flight (e.g., airspeed, altitude, and heading), the conversion must be correlated to the value shown to the pilot. Other values must be correlated to values sensed by the aircraft. Where an EU conversion results in an interim parameter (e.g., alternating current voltage ratio No. 1, frequency, direct current voltage ratio No. 2, potentiometer, or synchro angle,) the conversion formula converting this interim parameter to the actual parameter must also be provided. Each recorded parameter must be converted to an EU. Both signage (whether or not the raw data contains a plus or minus sign and the location of the sign in the parameter bits) and raw data range must be provided. Standardized signage is provided in ARINC Specification 647A appendices E and F. Instructions must be provided to enable the accident investigator to convert the recorded data to EU. An example of acceptable conversion equations are as follows:
a. Linear equation.
EU = A0 + A1 × CNTS10 where: EU is the value in engineering units A0 is the number of EU when the CNTS10 = 0 A1 is the slope of the line in EU per decimal count CNTS10 is the number of binary or binary coded decimal (BCD) counts converted to decimal counts
b. Piece-wise linear equation. In some instances it may be necessary to correlate the data using multiple linear equations. For example, the data of Figure 1- 1 of this appendix was obtained using two linear equations as follows:
A1-4
Appendix 1 For Altitude (EU) ≤ 500 feet For Altitude (EU) > 500 feet A 0 = (− 0.002) A0 = (− 0.29673) A1 = (0.0200231) A1 = (0.013351) where, ≤ indicates equal to or less than > indicates greater than
c. Polynomial equation.
EU = A0 + A1 × CNTS10 + A2 × CNTS102 +.A x × CNTS 10X where, EU is the value in engineering units CNTS10 is the number of binary or BCD counts converted to decimal counts A0 is the number of EU when the CNTS10 = 0 A1 , A2 ,.A X are coefficients developed by a curve fit
d. Unique equation. Where a unique equation applies, explicit documentation must be developed at the time of certification and approved by the FAA. This documentation may contain sufficient information to allow a tool programmer the ability to develop a conversion that uses his tool efficiently.
7. EU data correlation. When certifying new parameter implementations, an acceptable procedure to correlate the recorded data to the data derived from the conversion equation follows:
a. Set or read the device being measured (radio altimeter altitude for example) to a known fixed data point.
b. Record the data in the Raw Data (EU) column of Table 1-2 of this appendix.
c. Record the decimal counts from the DFDR record in the CNTS10 column of Table 1-2.
Note: The DFDR normally records counts in a binary format. Most equipment manufacturers provide a digital output port and test equipment to access the data.
Data can be displayed in binary, octal, or hexadecimal format with octal being the most common. Convert the counts to decimals using instructions provided by the equipment manufacturer.
d. Repeat the instructions in paragraphs a through c above until a sufficient number of data points have been collected for correlation.
Note: The number of required data points will vary depending upon the parameter and the transducer. As a minimum, three data points must be recorded for linear equation parameters, one at the mid-point (or null point) and the others A1-5
DFDR Radio Altitude Conversion 2500 2000 = -1500 <t 0 ,, 1000 .. a: ---- Raw Data 500 ---,I;- Derived Data 0 0 ~ "' co ~ N "' ~ ~ co "' "' ~ co "' "' "' "' "' ~ ..,. .... "' ~ N N N "' "' Counts 8/17/10 AC 20-141B Appendix 1 at each end point of the range for the parameter. For polynomial equation parameters, the more data points taken for correlation will produce a higher quality conversion formula. Also, the recorded data points must include one at each end of the range and sufficient intermediate points to produce an accurate conversion formula. For piece-wise linear equations, a minimum of three data points must be recorded for each linear segment of the equation.
e. Derive the EU value for each recorded CNTS10 value using the conversion equation or method provided. Record the derived value for each data point. When necessary, intermediate conversion methods may be used to improve conversion accuracy of the parameter.
f. The tabulated raw data and the derived data must also be plotted to confirm the prediction capability of the equation (linear, piece-wise linear, polynomial or unique). The plot must cover the full operating range for the parameter. See Figure 1-1 for an example plot. In the example of Figure 1-1, the data is so closely correlated (correlation coefficient = 0.99985) that the raw data and the derived data appear to be superimposed on each other.
FIGURE 1-1. AN EXAMPLE PLOT OF THE RADIO ALTIMETER IN FEET VERSUS
DECIMAL COUNTS
8. Discrete decipher logic. The correlation documentation must contain decipher logic for discrete parameters. The decipher logic must identify the status of the discrete represented by each binary state (e.g., “0” =OFF, “1”=ON). In instances where a group of discrete states is represented by multiple binary bits, the entire discrete word must be presented in the correlation document. See Table 1-1. The word slot, subframe, and bit logic for the specific discrete codes must be identified in the documentation.
A1-6
Appendix 1 TABLE 1-1. EXAMPLE OF GROUPED DISCRETE CODES DECIPHER LOGIC Word Slot Subframe Discrete Status Discrete Codes 7 6 5 4 3 2 1 A/P Mode Throttle “OFF” 1 1 0 0 0 0 0 A/P Mode Throttle “RETARD” 1 1 0 0 0 0 1 A/P Mode Throttle “CLAMP” 1 1 0 0 0 1 0 A/P Mode Throttle “SPD/MCH,ALPHA” 1 1 0 0 0 1 1 A/P Mode Throttle “SPD/MCH,FLAP” 1 1 0 0 1 0 0 A/P Mode Throttle “SPD/MCH,SLAT” 1 1 0 0 1 0 1 A/P Mode Throttle “SPEED” 1 1 0 0 1 1 0 A/P Mode Throttle “EPR LIMIT” 1 1 0 0 1 1 1 A/P Mode Throttle “SPD/EPR LIMIT” 0 1 0 0 0
9. Validation of EU correlation.
a. Correlation coefficient. Calculate the correlation coefficient between the raw data and the derived data. Table 1-2 may be used to aid this calculation. The following method may be used to calculate the correlation coefficient for a parameter that is linearly converted.
r = ([ N × Σ(x × y)− Σx × Σy N × Σx2 − (Σx)2 ]× [N × Σy2 − (Σy)2 ])1/ 2 where, r = correlation coefficient N = number of data points x = raw data (EU) y = derived value (EU) Σ = indicates the sum of the values that follow (e.g., Σx equals the sum of all x values) A1-7
Appendix 1 TABLE 1-2. CORRELATION TABLE DECIMAL COUNTS TO EU Parameter No. Parameter Conversion Method □ Linear □ Polynomial □ Unique A0 Unique Equation Reference:
A1 A 2 A3 A 4 A5 Data Point No. Raw Data (EU) CNTS10 Derived Value (EU) 1 2 3 4 5 6 7 8 9 10
b. Calculate the correlation coefficient. Table 1-3 demonstrates the steps in solving for the correlation coefficient.
TABLE 1-3. CORRELATION COEFFICIENT CALCULATION Parameter No. Parameter Name Mnemonic Code Parameter Word Location Subframe Superframe Cycle Assigned Bits (1 through 12) A1-8
Appendix 1 Sign Convention Correlation Coefficient Data Pt No.
x Raw Data (EU) y Derived Value (EU) 2x 2y x × y 1 2 3 4 5 6 7 8 9 10 N= Σx = Σy = Σx2 = Σy2 = Σ(x × y) =
(1) N × Σ(x × y) =
(2) Σx × Σy =
(3) Subtract (2) from (1) N × Σ(x × y)− Σx × Σy =
(4) N × Σx2 =
(5) Square the sum of x (Σx) and subtract this square from (4) [N × Σx 2 − (Σx)2 ]=
(6) N × Σy2 =
(7) Square the sum of y (Σy) and subtract this square from (6) [N × Σy − (Σy) 2 ]=
(8) Multiply (5) and (7) A1-9
N X I:( X X y )- LX X I:y .J [ N x LX 2 - ( LX )2 ] x [ N x I:y 2 - ( I:y )2 ] Appendix 1 [N × Σx 2 − (Σx)2 ]× [N × Σy2 − (Σy)2 ]=
(9) Take the square root of (8) [N × Σx2 − (Σx)2 ]× [N × Σy2 − (Σy)2 ] =
(10) Divide (3) by (9) 1 = = Note: The correlation coefficient (r) must not be less than 0.99.
c. Non-linear conversions. For non-linear parameter conversions, the following method, or method in paragraph d. below, may be used to calculate the correlation coefficient. The Sum of Least Squares is used to determine the fit of data to a function in non-linear regression. The objective in the curve fit is to minimize the sum of the squared errors. Coefficient of Determination or the Sum of Least Squares method is performed by using the following equation:
n RSS = Σ( i − ∫(xi )) 2 i=1 where xi and yi are known values and f(xi) is the calculated y value from the curve fit function.
d. Coefficient of determination, R2 SSER 2 = 1− SST SST = Σ(yi − y) 2 ,SS E = Σ(yi − yˆ i )2 i i Where SSE is the RSS in paragraph (c) above.
SST is the Total Sum of Squares. The range of R2 is from 0 to 1.
0 = no correlation and the data is correlated when R2 = 1.
A1-10
Appendix 2 APPENDIX 2. REVERSE DFDR DATA CORRELATION PROCEDURES
1. Purpose of this appendix.
a. Reverse engineer a DFDR data correlation document. This appendix characterizes reverse DFDR data correlation procedures acceptable to the FAA. We outline steps you can take to reverse engineer a DFDR data correlation document. Reverse DFDR data correlation procedures can be useful if a baseline data correlation document does not exist for a particular aircraft installation. Instead of recreating a data correlation document, an aircraft operator may follow these procedures. This appendix may be beneficial in reducing time and cost to develop or obtain a data correlation document.
b. Ensuring performance. The following procedure gives information to DFDR test engineers and operators who conduct maintenance checks and other DFDR airworthiness certification activities. These procedures may be used to ensure the DFDRS, as installed, is performing its intended function. Allowable tolerances in the CFRs are greater than those tolerances derived in this appendix. These procedures are an acceptable means to show compliance with DFDR operating requirements in parts 91, 121, 125, 129, and 135.
2. Definitions. Several key terms used in this appendix need to be identified and defined to establish an unambiguous understanding of the language. These terms defined herein are for purposes of this appendix material and are applicable to the following reverse DFDR data correlation procedures.
a. Conventional corm of digital outputs. When extracting the recorded DFDR data, the conventional form of digital outputs is the numerical format implementation of how the digital data is displayed. For example, data can be represented in the form of octal numbers, hexadecimals, etc. This digital output is commonly converted into decimal units, and further converted into useful engineering data.
b. Conversion document. Information on how to represent a system’s EU in the form of decimal units or vice versa. Depending on the ARINC Specification 429 word structure, the conversion method may vary from classic analog look-up tables to digital binary representation high-order polynomial equations. A conversion document can be referred to as a DFDR’s “data map.”
c. DFDR field test. A validation check performed onboard an aircraft to compare actual data to recorded data. For the purposes of this definition, keep in mind that the data correlation document is unproducible. Other required validation steps must be performed and are described later in this appendix. The following steps are typical DFDR field test procedures.
(1) Test each required parameter over a precise and realistic functional range.
(2) Record the DFDR data output in any conventional form (i.e., hexadecimal, octal, binary, etc.).
(3) Using common mathematical techniques, convert the DFDR data output into decimal units, depending on the conventional form of digital output.
A2-1