Flight Data Community

Frame Format Specification

Flight Data Community

Frame Format Specification

Version: 18.024.15
Authorised by: Chris Jesse
R&D Manager

This work is licensed under a

Creative Commons Attribution-NoDerivatives 4.0 International License.

Flight Data Services, 1600 Parkway, Whiteley, PO15 7AH, England

Tel: +44 (0)1329 223663
Registered in England No 4041206
 Flight Data Community
Frame Format Specification

Contents
Contents ....................................................................................................... 2
Revision History ............................................................................................. 4
Reference(s)................................................................................................. 8
Figures ........................................................................................................... 9
1 FlightDataConverter and the Frame Format File......................... 10
2 File Specification ............................................................................... 11
2.1 File name ................................................................................................ 11
2.2 Text Format............................................................................................. 11
2.3 Content .................................................................................................. 11
2.4 Fixed Data Format Items ...................................................................... 12
3 Header ............................................................................................... 13
3.1 Synchro Equation .................................................................................. 13
3.2 File Revision ............................................................................................ 13
3.3 Aircraft Manufacturer and Model ...................................................... 13
3.4 Aircraft Registration .............................................................................. 13
3.5 Frame Type ............................................................................................ 13
3.6 Source Documents ............................................................................... 14
3.7 Comments.............................................................................................. 14
4 Frame Structure ................................................................................. 15
4.1 Sync Pattern Sequence ....................................................................... 15
4.2 Bits per Word .......................................................................................... 15
4.3 Words per Subframe ............................................................................. 15
4.4 Superframe Present .............................................................................. 15
4.5 Reliable Frame Counter ....................................................................... 16
4.6 Stretched ................................................................................................ 16
5 Parameter Group ............................................................................. 18
5.1 FlightDataPlotter.................................................................................... 18
6 Parameters ........................................................................................ 19
6.1 Name ...................................................................................................... 19
6.2 Data Type ............................................................................................... 20
6.3 Word........................................................................................................ 20
6.4 Bits............................................................................................................ 21
6.5 Subframe ................................................................................................ 21
6.6 Frame ...................................................................................................... 21
6.7 Sample Rate .......................................................................................... 21
6.8 Units ......................................................................................................... 22
6.9 Source Name ......................................................................................... 22
6.10 Mnemonic ......................................................................................... 22
6.11 Equipment Source ............................................................................ 23
6.12 Delay .................................................................................................. 23

This work by Flight Data Services is licensed under a Creative Commons Page 2
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

6.13 ARINC 429 .......................................................................................... 23

7 Data Types ......................................................................................... 24
7.1 Data Type = Unsigned .......................................................................... 24
7.2 Data Type = Signed .............................................................................. 24
7.3 Scaling Unsigned or Signed Data ....................................................... 24
7.4 Data Type = Interpolated .................................................................... 25
7.5 Data Type = Segments ......................................................................... 25
7.6 Data Type = Polynomial ....................................................................... 26
7.7 Data Type = Synchro ............................................................................ 27
7.8 Data Type = Nonlinear ......................................................................... 27
7.9 Data Type = BCD................................................................................... 28
7.10 Data Type = ASCII............................................................................. 28
7.11 Data Type = Discrete ....................................................................... 29
7.12 Data Type = Enumerated Discrete ................................................ 29
7.13 Data Type = Multi-state ................................................................... 30
8 Multipart Joining ............................................................................... 31
8.1 Part Order ............................................................................................... 31
8.2 Joining Function .................................................................................... 31
9 Patches .............................................................................................. 37
10 Postprocessing .................................................................................. 39
10.1 Overflow Correction ........................................................................ 39
11 Reserved Parameter Names........................................................... 41
12 Examples ............................................................................................ 42
12.1 Data Conversion Examples ............................................................. 42
12.2 Multipart Joining Function Examples ............................................. 46

This work by Flight Data Services is licensed under a Creative Commons Page 3
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Revision History
Version numbers for this document have the following format: Year.Day
number in the year. Hour the version was updated.
For example, an update at 3pm on the 2nd of February 2010 would have the
version number: 10.033.15 because it’s hour 15 of day number 33 of the year
2010.
Version Date Amendment Description
Number
11.276.12 3rd October Addition of source name to parameter information
(v1.9) 2011 table.
Addition of version number update information table.
11.294.16 21st October Addition of equipment source to parameter information
2011 table
AmendmPitch Triment of document version numbering
system and addition of document version number
information to start of document.
11.297.16 24th October Amendment of equipment source definition.
2011
11.298.13 25th October New data types: Interpolated and Polynomial
2011
11.304.13 31st October Removed ability to define multiple parts as comma
2011 delimited dfinition for Subframe, Word, Bits etc.
All parts have to be defined as separate sections.
11.312.16 8th November Fixed diagram images.
2011
11.314.10 10th Consistency fixes and simplifications.
November
2011
11.336.16 2nd ARINC 429 parameter attribute.
December
2011
11.362.9 28th Delay parameter attribute.
December
2011
12.5.13 5th January Superframe Counter Word and Subframe location
2012 added to Frame Structure section.
12.16.12 16th January Added Signed and Coefficients to Synchro type
2012 parameters

This work by Flight Data Services is licensed under a Creative Commons Page 4
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Version Date Amendment Description

Number
12.44.12 13th February Re-added the ARINC 429 parameter attribute. Added
2012 Reliable Frame Counter to the Frame Structure section.
Added list of unit names.
12.65.15 5th March Added reserved parameter names.
2012
12.143.1735 22nd May Reformatted to FDS standard layout. Some revisions
2012 following tests using provisional release data and latest
version of FlightDataConverter.
12.160.1446 8th June 2012 Nonlinear Radio Altimeter scaling added. Options for
Synchros corrected to reflect polynomial scaling.
12.212.1013 30th July 2012 Sign and Magnitude multipart joining function added.
12.255.1150 11th Changed Discrete True to be mandatory and default
September False value.
2012
13.018.1114 18th January Use of Binary Overflow format with equal sample rate
2013 MSB & LSB added.
Table of contents updated.
13.029.1523 29th January Synchro Max Angle scaling option added.
2013
13.037.1411 13th February Control Column Force 737 multi-part joining function
2013 added.
13.081.1610 22nd March Added patches to the specification. Updated
2013 parameter names to the POLARIS convention.
13.093.0945 3rd April 2013 Overflow Correction and Overflow Value
13.108.1100 18th April 2013 Creative Commons License.
13.116.1040 26th April 2013 First Part Validation examples for TAWS, TCAS and
Heading added.
13.119.0820 29th April 2013 Amended First Part Validation examples amended
13.130.1000 10th May 2013 Added First Part Validation Duration configuration key.
Added concept of Stretched frames.
13.134.1715 14th May 2013 Added comma-separated Word locations to the
specification and ARINC 542A parameters.
13.149.0847 29th May 2013 Units Feet Pounds added for Engine Torque.leafpad
13.161.1155 10th June Added First Part Validation States configuration key.
2013
13.165.1510 14th June Bits per Word Option

This work by Flight Data Services is licensed under a Creative Commons Page 5
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Version Date Amendment Description

Number
2013
13.248.1459 5th Pints:Quarts unit clarification
September
2013
13.302.1008 29th October Added Synchro Equations, Units were updated, added
2013 16 bits for Fixed Data Formats, added Direct Addition as
a Multipart Joining Function, Aircraft Tail Number
renamed into Tail Number, Examples updated.
13.337.1428 4th December Added Word Overrides.
2013
14.015.1654 15th January Fixed incomplete Word Overrides section.
2014
14.031.1055 31st January ASCII Data Type format updated.
2014
14.050.1350 19th February Added Sort and Expand Multipart Joining Function.
2014
14.217.1426 5th August Added workaround for Overflow Correction not working
2014 on all the signed parameters.
14.224.1030 12th August Added First Part Switch Multipart Joining Function.
2014
14.328.1707 24th PV1584 Multipart Joining Function added.
November Synchro signed text corrected for signed = True case.
2014
14.322.2155 28th Reformatted to use new document template, and
November restructured with some minor wording changes for
2014 clarity.
“First Part Validation Sustain” function added.
14.344.1102 10th Signed = True flag inserted for the Interpolated and
December Polynomial data types.
2014
15.191.1107 10th July 2015 Stretched Type “Extended” added in.
16.067.0847 7th March Addition of Enumerated Discrete type.
2016 Multipart joining “Multi-state definitions” expanded to
reflect improved naming of these lists.
16.070.1157 10th March Unit km/h added.
2016
16.162.1033 03rd June Changed the address on the cover page
2016

This work by Flight Data Services is licensed under a Creative Commons Page 6
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Version Date Amendment Description

Number
16.194.0830 12th July 2016 Eng (2) Temp changed to Eng (2) Gas Temp and
recommendation for Full Scale option is added for
angular parameters.
16.202.07 20/07/2016 Name of the file changed from Flight Data Converter
Frame Format Specification to Flight Data Community
Frame Format Specification
16.259.11 15/09/2016 Description for Interleaved and Padded Stretched frame
types and an example for First Part Validation with Full
Scale option are added.
16.273.16 29/09/2016 Changed license from CC-NC-ND v3 to CC-ND v4 and
released under Flight Data Community banner.
17.033.13 02/02/2017 Units section removed from this document and added to
Flight Data Community Naming Convention document.
17.128.14 08/05/2017 Descriptions reviewed for ‘Sign and Magnitude’ and
‘Sort and Expand’.
18.024.15 24/07/2018 Word override example reviewed.

This work by Flight Data Services is licensed under a Creative Commons Page 7
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Reference(s)
Document name Version
[1] Flight Data Community Naming Convention 18.024.15

This work by Flight Data Services is licensed under a Creative Commons Page 8
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Figures
Figure 1 Specimen FlightDataPlotter Chart ..................................................... 18
Figure 2 BCD Example ........................................................................................ 43
Figure 3 Two Level Joining ................................................................................. 47
Figure 4 Complex Joining Function .................................................................. 52

This work by Flight Data Services is licensed under a Creative Commons Page 9
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

1 FlightDataConverter and the Frame Format File

Flight Data Services have a policy to place key elements of their
data analysis processes into the public domain in an effort to
promote flight safety through establishment of a lingua franca.
The Open Source software movement provides an ideal vehicle for
this policy.
One of the most difficult elements of flight data analysis is conversion
of the Flight Data Recorder (FDR) data into meaningful engineering
units. This may be achieved by passing the data into
FlightDataConverter, and this document specifies how to write the
controlling format file.

This work by Flight Data Services is licensed under a Creative Commons Page 10
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

2 File Specification
This section of the document defines the content of the Frame
Format file.

2.1 File name

FlightDataConverter will accept any valid filename for input,
although we recommend using the extension ‘.lfl’ by convention.

2.2 Text Format

For Python programmers, the Frame Format files use the configobj
library. For the rest of the world, they look like ‘.ini’ files. Here is a
simple example to show how easy the format is to read:

[[Eng (2) Gas Temp]]

# This is an example comment line
Data Type = Unsigned
Units = C
Sample Rate = 2.0
Word = 57
Bits = 12-1 # Inclusive so this is all twelve bits.
Offset = -55
Resolution = 0.2831

The square brackets and indentation denote a level of tree

structure, and each keyword is assigned a value in a simple “=”
statement, one per line.
Comment lines are prefixed by “#” character.

2.3 Content
The Frame Format will consist of up to four sections.

2.3.1 Header
Contains reference and version information

2.3.2 Frame Structure

Defines the frame layout

This work by Flight Data Services is licensed under a Creative Commons Page 11
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

2.3.3 Parameter Group

This optional section identifies subsets of the parameters and may be
used (in conjunction with the FlightDataPlotter) to select and view
data.

2.3.4 Parameters
This section contains the many Parameter Specifications. Each
Parameter Specification is self-contained, with the Parameter
Location, naming and conversion to engineering units.

2.4 Fixed Data Format Items

In the ARINC 647A-1 “Flight Recorder Electronic Documentation”
standard the following items are variables, however for the bulk of
recorder systems in service they can be considered constants and
are set as this in the current version of FlightDataConverter.
As they are fixed, they are not included in the file format but
included here for clarity.

2.4.1 Sign Convention

The sign convention shall always be positive for forwards, right and
up, so climbing right turns are positive. Positive control inputs shall
give positive aircraft movement, so aft stick, right wheel and right
pedal are positive.

2.4.2 Bits per Word

12; 16

2.4.3 Seconds per Subframe

1

2.4.4 Subframes per Frame

4

This work by Flight Data Services is licensed under a Creative Commons Page 12
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

3 Header
The Header section is the first section of the file. The information
described in the following subsections shall be stored once in the
header of the file, not in any particular order.
All items in the header are text format, and it is recommended that
they are enclosed in quotation marks, so that, for example, text that
includes commas is not converted into a list.

3.1 Synchro Equation

This mandatory text shall identify the type of synchro equation used
by the aircraft. This will determine the synchro conversion scaling to
be applied to all synchro parameters.
Equations available:
Synchro Equation = Linear
Synchro Equation = Plessey
Synchro Equation = Teledyne
Synchro Equation = Fairchild

3.2 File Revision

This mandatory text element shall identify the revision of this file.
Each time this file is changed, this item should also be changed.

3.3 Aircraft Manufacturer and Model

This mandatory text element shall identify the manufacturer and
model(s) of the aircraft to which this file applies.

3.4 Aircraft Registration

This optional text field identifies the aircraft to which this data frame
document applies.

3.5 Frame Type

This discretionary text item will define the frame identifier.

This work by Flight Data Services is licensed under a Creative Commons Page 13
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

3.6 Source Documents

This discretionary text element shall identify the reference(s) used as
the sources of information. The version numbers and issue dates of
source documents should be included where available.

3.7 Comments
This discretionary text element contains comments relevant to the
entire file.

This work by Flight Data Services is licensed under a Creative Commons Page 14
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

4 Frame Structure

4.1 Sync Pattern Sequence

Mandatory,.Constrained Text: “Standard” or “Reversed”.

4.2 Bits per Word

Optional. Number of bits per data word. Default=12.

4.3 Words per Subframe

Mandatory, Integer: Values of 64, 128, 256, 512 or 1024 permitted.

4.4 Superframe Present

Mandatory, Constrained Text: “True” or “False”.
A Superframe typically consists of 16 frames, so covers 64 seconds. A
superframe counter will be included in the data, which increments
linearly from 0 through N=2n-1 and thus may be stored in n bits (e.g.
n=4 and N=15).
When set to True, the following three fields are necessary.

4.4.1 Superframe Counter Subframe Location

Necessary, Integer: This is the Subframe Number which stores the
Superframe Counter.

4.4.2 Superframe Counter Word Location

Necessary, Integer: This is the Word Number which stores the
Superframe Counter.

4.4.3 Superframe Counter Bits

Necessary, Integer Range. This element shall identify the range of
one or more bits within a word that constitutes the Superframe
Counter sample component. (See Bits
storage definition below).

This work by Flight Data Services is licensed under a Creative Commons Page 15
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

4.5 Reliable Frame Counter

Optional, Constrained Text: “True” or “False”.
Defines whether or not the parameter with name 'Frame Counter'
records values reliably. This dictates whether or not it will be used in
the process of splitting flights.

4.6 Stretched
Optional, Section.
Defines Stretched frame configurations in 'Name = Words Per
Subframe' pairs. A Stretched frame is an extended version of the
original whose length is a multiple of the original frame. The
Stretched version will include the original frame's parameter
locations, yet will have subsequent sections where Stretch-specific
parameters can be recorded.

[Frame Structure]
Words Per Subframe = 128
[[Stretched]]

Double = 256
Quad = 512

In this example, the default 'Words Per Subframe' is 128. Two

Stretched versions of the frame are defined, 'Double' and 'Quad'.
By default, Stretched definitions will be disregarded and 128 words
per subframe flight data will be processed. If the user explicitly
defines the name of a frame stretch, flight data must be provided at
the words per subframe value of the stretch.
Parameters recorded within the stretch should be defined within a
distinct parameter section.

[Parameters]
…
[Parameters | Double]
…
[Parameters | Quad]
…

Parameters defined within the 'Parameters | Double' section are

recorded between words 129 and 256. Parameters defined within
the 'Parameters | Quad' section are recorded between words 129
and 512. Parameters defined within these sections are only included

This work by Flight Data Services is licensed under a Creative Commons Page 16
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

if the user specifies the corresponding stretch. If a parameter name

within a Stretched section is identical to one defined in the default
Parameters section, the default parameter will be overwritten.

4.6.1 Stretched - Extended

The Stretched type “Extended” version of the frame will have
parameters on the same word mapping as the original frame, but
sampled parameters at above 1Hz will be sampled to the sampling
rate of the extended version.
i.e. Pitch which is a 4Hz parameter on Word = 37, and is sampled at
Word 37, 101, 165, 229 in the base frame, will be sampled at Word
37, 165, 293, 421 in the stretched “Extended” to 512 wps frame.

4.6.2 Stretched – Interleaved

This type of Stretch creates the gaps within the data frame by
mapping the original parameter to 2n-1 word location. Additional
parameters could then be inserted into even word slots. For
example:

Old location New location

Word 1 Word 1

Word 2 Word 3 (2 X 2 – 1 = 3)

Word 3 Word 5, etc.

4.6.3 Stretched – Padded

‘Padded’ Stretch keeps the same word mapping as the original
frame as well as increases its physical size. This allows additional
parameters to be added to the second part of the frame. For
example, Pitch parameter is sampled at Word 37, 101, 165, 229 in a
256wps frame. Its stretched version, i.e. 512wps, will have the
parameters at exactly same word locations and additional different
parameters can be added between Word 257 and 512.

This work by Flight Data Services is licensed under a Creative Commons Page 17
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

5 Parameter Group
To avoid having to convert all parameters in the data file if only one
or a subset are needed, the optional Parameter Group facility may
be used.
Each line in the Parameter Group section has the format:

group_name = param1, param2, param3

In which case the group “group_name” will consist of the three listed
parameters.

5.1 FlightDataPlotter
A simple plotting program is available in the POLARIS Suite (available
from the flightdatacommunity web site) which will allow recorded
parameters to be inspected quickly against a reference altitude
trace. (This tool is designed for configuring the data frame file, and
not for data analysis).
When using FlightDataPlotter, the data presented on the plots is
defined by Parameter Groups “AXIS_n” with each list occupying one
axis of the plot. For example:

AXIS_1 = Pitch, Roll

AXIS_2 = Eng (1) N1,Eng (2) N1,Eng (3) N1,Eng (4) N1

would produce a chart like this:

Figure 1 Specimen FlightDataPlotter Chart

This work by Flight Data Services is licensed under a Creative Commons Page 18
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

6 Parameters
In the Parameter section there shall be multiple subsections, one for
each parameter stored in the FDR.
Each parameter sample consists of one or more components.
Usually there is only one component per sample. For samples with
more than one component, the components are identified in
subsections defining individual Word and Bits definitions with optional
subframe and sample rate definitions where the defaults do not
apply.
This process can be carried out in multiple stages, building up tiers of
definition. In this specification the elements of the parameter
definition are all provided at the top level, but when multiple
components are defined the definitions can be applied at lower
levels. Examples of this process follow the formal definition section.

6.1 Name
Mandatory, Text
The name of the parameter is Mandatory and must be within double
brackets as it is a second level item in the tree.
Name shall uniquely identify the recorded parameter.
The text constraints for the Name are:
 Unique relative to all other parameter names in the file
independent of case.
 No leading, trailing, or consecutive white space (tab or
space) characters.
 May include the following characters: alpha-numeric,
space, dash (-), plus (+), underscore (_).
 No more than 64 characters long.
 Shall not contain “#”
 Shall not be one of the reserved names listed at Annex A.
Comment: Flight Data Services have a list of standard names which
should be used if the output from the FlightDataConverter is to be
used with the FlightDataAnalyser.

This work by Flight Data Services is licensed under a Creative Commons Page 19
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

6.2 Data Type

Mandatory, Constrained Text
This element indicates the data type of the recorded parameter
value. The data types are listed below

6.3 Word
Mandatory, Integer or Integer List: 47 or 47, 63
A single word location will define the first of a set of equi-spaced
locations determined by the parameter sample rate.
Multiple comma-separated word locations define each location a
parameter is recorded within a subframe. This allows for parameter
definitions with varying spaces between samples. If there are
multiple word locations specified, the parameter's sample rate is
automatically derived from it. The resulting data will be blended to
account for inconsistent offsets between word locations. If the first
word location appears in the second-half of the subframe, its offset
will be shifted to the first-half and the values will be blended
accordingly.
Word numbering shall start at 1 (word 1 always contains the sync
pattern) and run to the sample rate as a maximum value.

6.3.1 Word Overrides

Optional, Numeric
The Word Overrides section is used when a parameter's word
locations are non-equidistant, e.g. 8, 72, 141, 200 for a 4Hz
parameter in a 256 words per second frame. If the parameter's word
locations were equidistant, the third location should be in word 136.
To apply this feature, create a parameter subsection named Word
Overrides. For each word override, define a pair of values including
the original word location mapped to the overriden word location.

[[Airspeed]]
…
Word = 8
Sample Rate = 4
[[[Word Overrides]]]
136 = 141

This work by Flight Data Services is licensed under a Creative Commons Page 20
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

6.4 Bits
Mandatory, Integer Range
This element shall identify the range of one or more bits within a
word that constitutes the parameter sample component. Only the
bits that apply to this component are to be identified.
The valid range of bit numbers is the consecutive bits in the word. In
the vast majority of cases, Bit 1 is the Least Significant Bit (LSB) and Bit
12 is the Most Significant Bit (MSB).
The format shall define the MSB first, followed by a hyphen (“-”)
followed by the LSB. For example, if the upper eight bits of a 12 bit
word make a component, this element would be 12-5.
If only one bit is used, then that bit location is entered as a single-
item range. For example, if only bit 3 is used, then this element is
written as 3-3.

6.5 Subframe
Default = 1, Integer
This element shall identify the subframe where the first sample or
component of a sample is stored.
Where not specified, this shall default to 1.
Subframe numbering shall start at 1 and run to 4 as a maximum.

6.6 Frame
Default = 1, Integer
For parameters recorded in a Superframe structure, this is the
number of the first Frame in the Superframe where this parameter
occurs. Superframe counting start from 1.
If not specified, it is assumed that the parameter occurs in every
Frame.

6.7 Sample Rate

Default = 1, Float
The sample rate in Hz for the parameter samples.
If multiple word locations are defined, the sample rate is
automatically derived from the number of locations.

This work by Flight Data Services is licensed under a Creative Commons Page 21
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

If there is a single word location:

Where Frame is not defined and the Sample Rate is not specified,
the Sample Rate shall be assumed to be 1Hz. (Reminder: Frame is
the first frame within a superframe where this parameter is stored).
Where Frame is defined and the Sample Rate is not specified, the
Sample Rate shall be assumed to be 0.015625 Hz (1 in 64 seconds).
Notes about sample interval computation:
Where the sample rate requires multiple equi-spaced samples in the
data, the repetition pattern is not provided explicitly and is
computed.
Where no Frame is given this will be 0.25 or greater, in powers of 2.
Where a Frame is given this may be 0.125 or smaller, in powers of 2.

6.8 Units
Recommended, Text
This should be provided for all numeric parameters. The units
recognised in the POLARIS system are listed in Flight Data
Community Naming Convention [1].
A few parameters (e.g. weights and ILS deviations) may be defined
in alternative units, but will be automatically converted into
standard units for consistency. For example, if the file uses units of
mV, the parameter is assumed to be an ILS input and is rescaled into
dots automatically.

6.9 Source Name

Optional, Text
The name or reference used in the source information.

6.10 Mnemonic
Optional, Constrained Text
This is a common abbreviation for the parameter name (e.g., IAS for
Indicated Air Speed).
The constraints for the Mnemonic Code are:
 Be unique relative to all other Mnemonic Codes in the file,
independent of case.

This work by Flight Data Services is licensed under a Creative Commons Page 22
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

 Use only alphanumeric characters, periods and/or

underscores.
 Use no more than 12 characters.

6.11 Equipment Source

Optional, Text,
Equipment source according to the manufacturer source
information. For parameters that use multiple equipment sources,
the sources may be defined in a comma separated list.

6.12 Delay
Optional, Float
This is the transfer delay of the parameter between the moment of
measurement and the moment of recording the data, in
milliseconds.
This value is used within POLARIS to maintain precise timing accuracy
in the relationship between parameters.

6.13 ARINC 429

Default = “False”, Logical
This identifies whether the parameter was received by the FDAU on
an ARINC 429 data bus. This is useful when carrying out data
validation as the ARINC 429 “No Computed Data” flag is normally
reflected by the FDAU recording square-wave type data. Has no
effect on the conversion of the flight data.

This work by Flight Data Services is licensed under a Creative Commons Page 23
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

7 Data Types

7.1 Data Type = Unsigned

The MSB of the recorded data carries a positive value before scaling
into engineering units.
That is, 0xFFF > 0x000 or in decimal, 4095 > 0.
Note that this description applies to the format of the recorded
data, not the engineering units. So, if a Resolution of 1 and Offset of -
1000 is applied to this example, the engineering values will have a
range -1000 to +3095.
See below for scaling options.

7.2 Data Type = Signed

The sign bit is the MSB of the recorded data and when set the value
is negative prior to scaling.
That is, 0xFFF < 0x000 or in decimal, -1 < 0.

7.3 Scaling Unsigned or Signed Data

The scaling options below apply to both Unsigned and Signed data
types. When omitted, no scaling will be applied and the range will
be determined by the original data type, with a resolution of 1 per
bit, no offset.

7.3.1 Resolution
Optional, Float
The value of a single, least significant, bit of data.

7.3.2 Offset
Optional, Float
The value of the parameter when the recorded data = 0.

7.3.3 Full Scale

Optional, Float

This work by Flight Data Services is licensed under a Creative Commons Page 24
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

The value of the parameter when the recorded data is at positive

full scale plus one bit.
Can be used in combination with Offset, in which case the Full Scale
defines the range from minimum to maximum. Although, this option
cannot be used in combination to Resolution option.
For angular parameters, such as Heading, Full Scale option is highly
recommended and is preferred over Resolution as it avoids the data
overflow outside the given range. Although, care should be taken
when ‘Full Scale’ option is used with ‘First Part Validation’ function as
full scale should only be applied to the part where the value of the
parameter is recorded. An example of such case is included in
Section 12.2.5.4.

7.4 Data Type = Interpolated

Interpolated parameters are associated with a lookup table of
points that define a scaling function.

7.4.1 Points
Mandatory, Integer = Float
If the Data Type is Interpolated, Points must be provided to decode
the parameter. At least two points are needed, as illustrated below:

[[[Points]]]
0 = 0
1 = 10
10 = 1000

Values between the points will be linearly interpolated.

Values beyond the first or last points in the table are scaled by
extrapolating the first or last line segments.
For interpolated signed parameters the flag “Signed = True” can be
applied which applies two's complement prior to the interpolation
tables.

7.5 Data Type = Segments

Segment parameters are associated with multiple linear equations
that define a scaling function.

This work by Flight Data Services is licensed under a Creative Commons Page 25
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

7.5.1 Segments
Mandatory, Integer, (Optional Integer) = Float, Float
If the Data Type is Segments, Segments must be provided to decode
the parameter. The first float specifies the Resolution of that
segment and the second the Offset.
If the optional second integer is not given, it will be assumed the
given equation applies to all binary values greater than the first
value.
At least two segments are needed, as illustrated below:

[[[Segments]]]
0, 159 = 3.129, 0
159 = 0.6256, 400

This is the equivalent of a resolution of 3.129 and offset of 0 for all

binary output greater than or equal to 0 and less than 159 and a
resolution of 0.6256 and offset of 400 for binary output greater than
or equal to 159.

7.6 Data Type = Polynomial

Using a polynomial or inverse function.

7.6.1 Coefficients
Mandatory, Integer = Float
If the Data Type is Polynomial, the coefficients must be provided to
decode the parameter.
For example, for formula x2 + 2x -3 the definition will be:

[[[Coefficients]]]
0 = -3
1 = 2
2 = 1

This can also be used for inverse computation, as sometimes

required for frequency based speed signals. In this case just enter
the coefficient as -1 to obtain the inverse function.

[[[Coefficients]]]

This work by Flight Data Services is licensed under a Creative Commons Page 26
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

-1 = 423836.5686
For polynomial signed parameters the flag “Signed = True” can be
applied which applies two's complement prior to the polynomial
tables.

7.7 Data Type = Synchro

Nonlinear synchro sensors requiring 8-part linearization. The recorded
values will be converted from a binary unsigned value to an angle
from 0-360 deg.

7.7.1 Signed
Optional, “True” or “False”, default “False”.
When False, the resulting angle will be in the range 0-360 deg, and
when True the value will be in the range -180 to +180deg.

7.7.2 Max Angle

Max Angle is used when a synchro range other than 0-360 or +/- 180
is required. This gives the range 0 to Max Angle & Max Angle-360 to
0.
For example:

Max Angle = 240

This gives an angular range of -120 deg to +240deg.

7.7.3 Synchro Scaling

The converted angle may be scaled using a polynomial function
with coefficients defined as above. In this case the input to the
polynomial is the synchro angle, not the recorded integer value.

7.8 Data Type = Nonlinear

This data type is designed to cater for specific nonlinearities that
cannot satisfactorily be accommodated using the scaling functions
defined above. Each function will be defined by a Sensor Type
statement.

This work by Flight Data Services is licensed under a Creative Commons Page 27
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

7.8.1 Sensor Type = ARINC_552

This function is defined in the ARINC_552 radio altimeter standard. It
assumes that the signal has been fed into an ARINC 573 HLDC input
where 32V=4095 bits full scale.

7.8.2 Data Type = ARINC 542 Pneumatic Airspeed

Applies the ARINC 542 Pneumatic Airspeed algorithm.

7.8.3 Data Type = ARINC 542 Pneumatic Altitude

Applies the ARINC 542 Pneumatic Altitude algorithm.

7.9 Data Type = BCD

For a single Binary Coded Decimal character, the minimum format
is:

[[Test2]]
Data Type = BCD
Word = 6
Bits = 8-5
Resolution = 100

However, as soon as there is more than one digit a multipart

parameter definition is required and this type of information must be
provided for each character. Examples are provided at the end of
this specification.

7.10 Data Type = ASCII

Text using the ASCII character set. May be a reduced character set
using only 8, 7 or 6 bits.
If the Data Type is ASCII and it has 8 or 7 bits, no other information is
required to decode the parameter. Each ASCII character will be
identified by a separate Word and Bits definition and converted
directly into a text character.
If the Data Type is ASCII and it has 6 bits, the conversion will be done
using the default value of the ASCII string to which an offset of 32 will
be added.

This work by Flight Data Services is licensed under a Creative Commons Page 28
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

If the following syntax is used [ASCII offset = xx] then the output will
be the default value of the ASCII string to which the specified offset
will be added (xx should be an integer value).
Where multiple ASCII characters are combined into a single
parameter, a multipart parameter “String Join” definition is required.
Data Type = ASCII is needed at both the parameter and part levels.

7.11 Data Type = Discrete

The default for single bit parameters stored in a single bit
If the Data Type is Discrete, the following information may be
provided to decode the parameter.

7.11.1 Logic
Optional, “Normal” or “Inverted”, default = “Normal”.
“Normal” in which case a stored 1 is displayed as 1 and the True text,
a stored 0 is displayed as 0 and the False text is displayed.
“Inverted” in which case a stored 1 is displayed as 0 and the False
text, a stored 0 is displayed as 1 and the True text is displayed.

7.11.2 True
Mandatory, Text.
The text to display when logic is True.

7.11.3 False
Optional, Text. Default is “-”.
The text to display when logic is False.

7.12 Data Type = Enumerated Discrete

Discrete parameters which evaluate True when some data has
specific values and False otherwise. (Currently only identified on the
Embraer Phenom TAWS encoding).

7.12.1 True Values

Mandatory, List
A list of values for which the discrete evaluates to True.

This work by Flight Data Services is licensed under a Creative Commons Page 29
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

7.12.2 True
Mandatory, Text.
The text to display when logic is True.

7.12.3 False
Optional, Text. Default is “-”.
The text to display when logic is False.

7.13 Data Type = Multi-state

Parameters with a finite number of predefined states.

7.13.1 State
Mandatory, [Integer = Text] List
For each mapped state, an Integer = Text pair shall be provided. For
example,

[[[State]]]
0 = Arm
1 = Capture
2 = Engaged

Unspecified states shall default to “Undefined”.

Note that the identification word for the list of states is “State” in the
singular.

This work by Flight Data Services is licensed under a Creative Commons Page 30
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

8 Multipart Joining
Where a parameter consists of multiple components, arrangements
are needed to join these parts. This section examines the available
options. As before, examples follow later in the document.

8.1 Part Order

Mandatory, List of named Components
Part Order defines the order in which the individual parts of a multi
part parameter will be joined. It is a comma separated list, and
where order is important it is from the Most Significant Part to the
Least Significant Part.
Each Part of the multi part parameter will be a component at the
next lower level.
For simple parameters, the Data Type, Units and Scaling (Full
Scale/Resolution) may be recorded in the Parameter Name Level
and will apply to the whole parameter, but it is more conventional to
define these at part level before joining.
Sample Rate, Word, Subframe, Frame, Bits, Decimal Value (BCD
only) for each Part will be recoded at the Part Level.
If the parameter is of Data Type BCD or ASCII the Multipart Joining
Function for each section needs to be declared as BCD or ASCII as
appropriate.

8.2 Joining Function

Mandatory, Multipart Joining Function type.
For a multipart joining function, a joining function must be defined
from those listed below.
There is no default Joining Function.

8.2.1 Multipart Joining Function = Numeric Addition

When a parameter has multiple parts (which may have been scaled
individually) which join by arithmetically summing the (scaled) values
of each part then the “Numeric Addition” Multipart Joining Function
shall be used. This is mainly used for BCD joining.

This work by Flight Data Services is licensed under a Creative Commons Page 31
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

8.2.2 Multipart Joining Function = Direct Addition

Direct addition function simply joins two parts of a parameter. For
example if one part has 3 bits and the other one has 5 bits after the
joining we’ll have one parameter of 8 bits.
The part order is in descending bit order, so the part containing the
output word sign bit or MSB comes first and the part with the LSB last.
As the component parts are just sequences of bits being added
together, any scaling or data type definitions will be ignored. This
information must be provided at the higher level.

8.2.3 Multipart Joining Function = Binary Overflow

Where the sample rate of the MSB is lower than the sample rate of
the LSB components, it is necessary to use this algorithm which uses
the LSB sample in the same subframe as the MSB as reference point,
and correct for scaling errors in the remaining subframes that arise
due to timing differences.
For example. If the LSB contains 6 bits, it can hold a value between 0
and 63. If the value in the subframe with the MSB is 1 and the value
in the current subframe is 62, then the local value will be corrected
by subtracting 64 to give a value at summation of -2. Similarly, if the
current value is 3 and the value in the subframe with the MSB is 61,
the current value will be set to 67 prior to combination and scaling.
This function may also be used where the sample rates of the MSB
and LSB are the same and timing differences lead to overflow or
underflow errors.
The sequence of the component parts is critical; the parts must be
listed in descending magnitude. For example, Coarse before Fine.

This work by Flight Data Services is licensed under a Creative Commons Page 32
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

8.2.4 Multipart Joining Function = First Part Validation

This joining function is used when the recording of a parameter is
dependent on the value/state of another parameter. The
Parameter will contain two parts:
 The first part, used to validate whether the parameter has
been recorded.
 The second part containing the value of the parameter
The “First Part Validation” joining function will specify the value/state
of the first part parameter which will indicate that the second part
parameter has been recorded. If the second part parameter has
not been recorded it will be given a “Not Recorded” value.

8.2.4.1 First Part Validation Duration

Optional, Numeric
An optional configuration key, “First Part Validation Duration”,
defines the minimum time in seconds of valid data which will be
unmasked. The default value is 5 seconds.

8.2.4.2 First Part Validation Sustain

Optional, Logical
If this is defined as True, the converted value will be maintained until
a new value is defined. This allows parameters to be de- multiplexed.

8.2.4.3 Multi-state definitions

Optional, List
The validation parameter can have a data type of 'Multi-state' if this
optional configuration key is defined. The value of this configuration
key is a comma-separated list of states which indicate the validity of
the second part. If a single state is defined, it must be followed by a
comma to denote a list. There are three optional names for this
definition, any of which can be used as convenient.
“First Part Valid States” = A list of values for which the first part is valid.
“First Part Invalid States” (or the deprecated “First Part Validation
States”) = A list of values for which the first part is invalid.

This work by Flight Data Services is licensed under a Creative Commons Page 33
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

8.2.5 Multipart Joining Function = First Part Switch

This joining function is used when a discrete value determines the
location or additional processing of a Parameter’s data.
First Part Switch requires three Parameter subparts. The first subpart
must define the location of a discrete value. When this value is one,
data from the second subpart will be sampled for this Parameter.
When this value is zero, data will be sampled from the third subpart
instead of the second. The second and third subparts must have an
equal sampling rate to avoid complications when data switches
between subparts.

8.2.6 Multipart Joining Function = String Join

This joining function simply concatenates ASCII characters.

8.2.7 Multipart Joining Function = Sign and Magnitude

This function is used when a parameter has negative parts which are
not calculated using the complement of the number (i.e. taking
11100 when the number reads 00011). Thus, the negative number
increases from 0 towards the negative limit rather than vice-versa.
When using this function, the most significant bit of the binary
number will define the sign and is treated as a separate entity,
whereas, the rest of the digits will give the magnitude only. For
example, 11100 will be split into 1 (sign) and 1100 (the magnitude).
Now, MSB will define if the value is positive or negative i.e. positive if
0 and negative if 1. The rest of the digits would give a number i.e.
1100 = 12. So the answer to 11100 is -12.

8.2.8 Multipart Joining Function = Control Column Force 737

This function is used for 737 aircraft for “Control Column Force
(Capt)” and “Control Column Force (FO)” parameters. The
parameter must have the following parts in the order specified:
“Control Column Force (Local)”, “Control Column Force (Foreign)”
and “FCC Local Limited Master”. The “FCC Local Limited Master”
subpart must be defined as a Multi-state parameter with states of
either “FCC (L)” or “FCC (R)”. The parameter name must end with
either “(Capt)” or “(FO)” which determines whether to use “FCC (L)”
or “FCC (R)” within the joining function. An example is included in
this document within Chapter 9.14.

This work by Flight Data Services is licensed under a Creative Commons Page 34
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

8.2.9 Multipart Joining Function = Sort and Expand

This function is used to expand multiple parts of a parameter into a
continuous series of data. In most cases, parameters above 1Hz are
evenly distributed in the data frame. For example, if a parameter in
Word 2 is sampled at 4Hz in a 64 wps data frame, it will be recorded
in word locations 2, 18, 34 and 50. Sometimes, the parameters are
not evenly distributed within the frame, for example, a 4Hz
parameter in word locations 2, 3, 4 and 5. In such cases, 'Sort and
Expand' function allows us to arrange each part (or sample) of the
parameter so that the data can be read in the correct order of time
sequence. The order of the parts (or samples) is given in the data
frame documentation. For example:

[[Acceleration Lateral]]
Source Name = COG LATERAL ACCELERATION
Sample Rate = 4.0
Units = g
Multipart Joining Function = Sort and Expand
Part Order = PART_1, PART_2, PART_3, PART_4
Data Type = Signed
[[[PART_1]]]
Sample Rate = 1.0
Data Type = Signed
Word = 97
Subframe = 1
Bits = 12-1
Resolution = 0.00390625
[[[PART_2]]]
Sample Rate = 1.0
Data Type = Signed
Word = 96
Subframe = 1
Bits = 12-1
Resolution = 0.00390625
[[[PART_3]]]
Sample Rate = 1.0
Data Type = Signed
Word = 95
Subframe = 1
Bits = 12-1
Resolution = 0.00390625
[[[PART_4]]]
Sample Rate = 1.0
Data Type = Signed
Word = 94
Subframe = 1
Bits = 12-1
Resolution = 0.00390625

This work by Flight Data Services is licensed under a Creative Commons Page 35
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

The resulting data for this parameter will include a value from
PART_1, followed by PART_2, followed by PART_3 and finally followed
by PART_4. This sequence will repeat throughout the data. Please
note that in above example Word 97 is recorded before Word 94 in
the data frame.
“Sample Rate” must be defined for this joining function at the top
level and under individual parts. Moreover, the value of sample rate
at the top level must be equal to the combined sample rates of the
sub-parts. The superframe offset of this parameter will be forced to 0
to be compatible with alignment in the Flight Data Analyzer.

8.2.10 Multipart Joining Function = PV1584 Altitude STD

This function has been specifically designed to add the Pressure
Altitude parameters for the BAe 146-300 data frame.
The Pressure Altitude is split into two components
 Altitude Low (Altitude from -2,900ft to +20,900ft)
 Altitude High (Altitude from +14,250ft to +51,750ft).
The joining function computes the average altitude where there is
an overlap of recorded altitude (i.e. in the range 14,250ft to
20,900ft), by gradually blending the two signals.
An example is provided in the Examples section.

This work by Flight Data Services is licensed under a Creative Commons Page 36
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

9 Patches
Patches can be added to a frame to alter or remove parameters if
a certain condition is met. This feature is intended to minimise
duplication where differences exist between aircraft models, engine
types and individual aircraft.
Patches are defined within the Parameters section of the LFL file. The
format of a patch section title is defined as follows:

[[Parameter Name | Patch Condition Property |

Patch Condition Value 1(, Patch Condition Value 2,
..)]]

The contents of a patch section will override the configuration of the

original parameter. An example patch section follows:

[[Altitude Radio | Tail Number | G-ABCD,G-EFGH]]

Units = ft
[[[SIGNED]]]
Word = 54

In this example, if the Tail Number is either “G-ABCD” or “G-EFGH”,

the configuration of the “Altitude Radio” parameter will be
overriden by the contents of the patch section. The patched
parameter's Units will be changed to “ft”, and the Word location of
the “SIGNED” subpart will become “54”. The target parameter must
be defined separately within the frame along with any subparts
referenced within the patch. It is recommended that patches
appear directly after the parameter being overriden in the LFL.
It is possible to exclude parameter if it matches a condition by
including “Recorded = False” within a patch section.

[[Aileron (L) | Engine Manufacturer | General Electric]]

Recorded = False

In the above example, the parameter named “Aileron (L)” will be

excluded if the Engine Manufacturer is equal to “General Electric”.
The following properties may be specified within a patch condition:
 Aircraft Family (e.g. B737)
 Aircraft Series (e.g. B737-300)
 Aircraft Model (e.g. B737-5L9)

This work by Flight Data Services is licensed under a Creative Commons Page 37
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

 Aircraft Tail Number (e.g. G-ABCD)

 Engine Manufacturer (e.g. General Electric)
 Engine Series (e.g. CF6-50)
 Engine Type (e.g. CF6-50E2)

This work by Flight Data Services is licensed under a Creative Commons Page 38
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

10 Postprocessing

10.1 Overflow Correction

There are cases when format of the data does not allow to
represent the full value range. In many cases it results in overflows,
which does not cause information loss, only distortion of the
representation. In that case Overflow Correction may be applied:

[[Altitude Radio]]
Data Type = Signed
Overflow Correction = True
Units = ft
Sample Rate = 0.5
Word = 50
Subframe = 1
Bits = 12-1

In this example values are stored in 12 bits of data which is not

enough to represent the altitude. The values overflow which can be
corrected with our correction procedure.

10.1.1 Overflow Value

There is a known bug in this function for the signed parameters. For
these kind of parameters which need an overflow correction the
solution is to take the full scale of the parameter which is the
decimal value of the parameter bits without the sign bit, multiply it
with the specified resolution and the final value should be entered
as being the Overflow Value.
Example: Slat – defined on bits 12-4 and it is a Signed parameter,
resolution = 0.78
9 bits = resolution of 511
511*0.78 = 398.58 => an Overflow Value = 398.58

[[Slat Angle]]
Data Type = Signed
Overflow Value = 398.58
Overflow Correction = True
Units = deg
Resolution = 0.78
Word = 27

This work by Flight Data Services is licensed under a Creative Commons Page 39
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Bits = 12-4

Overflow Correction uses the saturated value for the binary range
by default to determine the point of overflow. In some cases point of
overflow may be different. For the overflow detection algorithm to
work correctly we need to declare this value:

[[Groundspeed (1)]]
Data Type = Unsigned
Multipart Joining Function = Numeric Addition
Overflow Correction = True
Overflow Value = 400
Units = kt
Part Order = DIGIT_1, DIGIT_2, DIGIT_3
[[[DIGIT_1]]]
Data Type = BCD
Resolution = 100
Bits = 12-11
Word = 40
Subframe = 1
Sample Rate = 0.5
[[[DIGIT_2]]]
Data Type = BCD
Resolution = 10
Bits = 10-7
Word = 40
Subframe = 1
Sample Rate = 0.5
[[[DIGIT_3]]]
Data Type = BCD
Resolution = 1
Bits = 6-3
Word = 40
Subframe = 1
Sample Rate = 0.5

In this example BCD representation was used with only 2 bits for the
most significant digit (which gives the value range up to 399). Values
over 399 knots overflow in this representation.

This work by Flight Data Services is licensed under a Creative Commons Page 40
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

11 Reserved Parameter Names

The following names are reserved as they will be automatically
generated either when processing frame doubled raw data or
during the downsampling procedure:
Time
QAR – Year
QAR – Month
QAR – Day
QAR – Hour
QAR – Minute
QAR – Second
QAR – Major Version
QAR – Minor Version
QAR – Number of Power Ups
QAR – Sequence Number
QAR – Word Rate
QAR – Serial Number
QAR – Software Configuration
QAR – Last Error
QAR – Number of Low Power Indicators

This work by Flight Data Services is licensed under a Creative Commons Page 41
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

12 Examples
The examples given here are not exhaustive, but should assist the
user to interpret the specification given above.

12.1 Data Conversion Examples

These are examples of conversion in a single stage. If necessary
these building blocks can be joined using a multipart joining function
illustrated later in this annex.

12.1.1 Synchro Example

[[Aileron (L)]]
Data Type = Synchro
Sample Rate = 1
Word = 12
Bits = 12-1
[[[Coefficients]]]
0 = -1
1 = 0.912
2 = 0.0053

This work by Flight Data Services is licensed under a Creative Commons Page 42
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

12.1.2 Binary Coded Decimal

Figure 2 BCD Example

[[Altitude Radio]]
Data Type = Signed
Units = ft
Multipart Joining Function = Direct Addition
Full Scale = 2048
Part Order = SIGN, MSH, LSH
[[[SIGN]]]
Sample Rate = 1
Word = 128
Bits = 12-12
[[[LSH]]]
Sample Rate = 1
Word = 128
Bits = 11-1
[[[MSH]]]
Sample Rate = 1
Word = 186
Bits = 2-1

This work by Flight Data Services is licensed under a Creative Commons Page 43
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

12.1.3 BCD With Restricted Range Character

[[Month]]
Sample Rate = 0.015625
Units = mo
Part Order = DIGIT1, DIGIT2
Multipart Joining Function = Numeric Addition
[[[DIGIT1]]]
Data Type = BCD
Word = 49
Subframe = 3
Frame = 14
Bits = 5-5
Resolution = 10
[[[DIGIT2]]]
Data Type = BCD
Word = 49
Subframe = 3
Frame = 14
Bits = 4-1
Resolution = 1

Where Bits 4-1 have a resolution of 1 and Bit 5 has a resolution of 10.
As there are only 12 months in a year, this format is adequate for the
Gregorian calendar!
Once each part has been scaled they are summed together to give
the complete parameter value.

12.1.4 BCD with Some Digits in Superframe

[[Altitude Baro inHg]]

Data Type = Unsigned
Units = inHg
Multipart Joining Function = Numeric Overflow
Part Order = MSH, LSH
[[[LSH]]]
Data Type = Unsigned
Sample Rate = 0.25
Multipart Joining Function = Numeric Addition
Part Order = DIGIT1, DIGIT2
[[[[DIGIT1]]]]
Word = 186
Subframe = 1
Bits = 8-5
Resolution = 0.001
[[[[DIGIT2]]]]

This work by Flight Data Services is licensed under a Creative Commons Page 44
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Word = 186
Subframe = 1
Bits = 12-9
Resolution = 0.01
[[[MSH]]]
Sample Rate = 0.015625
Multipart Joining Function = Numeric Addition
Part Order = DIGIT1, DIGIT2, DIGIT3
[[[[DIGIT1]]]]
Word = 256
Subframe = 4
Frame = 12
Bits = 5-2
Resolution = 0.1
[[[[DIGIT2]]]]
Word = 256
Subframe = 4
Frame = 12
Bits = 9-6
Resolution = 1
[[[[DIGIT3]]]]
Word = 256
Subframe = 4
Frame = 12
Bits = 12-10
Resolution = 10

12.1.5 Reverse Order BCD

[[Origin]]
Units = min
Sample Rate = 0.015625
Word = 192
Subframe = 1
Frame = 16,1
Bits = 4-1,8-5,12-9
Resolution = 0.1,1,10
Meaning:
Value in Bits 4-1 has resolution 0.1
Value in Bits 8-5 has resolution 1.0
Value in Bits 12-9 has resolution 10.0

This work by Flight Data Services is licensed under a Creative Commons Page 45
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

12.2 Multipart Joining Function Examples

12.2.1 Multi Part - Signed

[[Latitude]]
Multipart Joining Function = Overflow Correction
Data Type = Signed
Units = deg
Full Scale = 90
Part Order = LSH, MSH
[[[LSH]]]
Sample Rate = 1
Word = 177
Bits = 12-1
[[[MSH]]]
Sample Rate = 0.25
Word = 179
Subframe = 3
Bits = 12-5

12.2.2 Multi Part – BCD

[[Altitude Baro inHg (1)]]

Data Type = Unsigned
Units = inHg
Part Order = MSH, LSH
Multipart Joining Function = Overflow Correction
[[[LSH]]]
Data Type = Unsigned
Sample Rate = 0.25
Multipart Joining Function = Direct Addition
Part Order = DIGIT1, DIGIT2
[[[[DIGIT1]]]]
Data Type = BCD
Word = 186
Subframe = 1
Bits = 8-5
Resolution = 0.001
[[[[DIGIT2]]]]
Data Type = BCD
Word = 186
Subframe = 1
Bits = 12-9
Resolution = 0.01
[[[MSH]]]
Data Type = Unsigned
Sample Rate = 0.015625
Multipart Joining Function = Direct Addition
Part Order = DIGIT1, DIGIT2, DIGIT3

This work by Flight Data Services is licensed under a Creative Commons Page 46
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

[[[[DIGIT1]]]]
Data Type = BCD
Word = 256
Subframe = 4
Frame = 12
Bits = 5-2
Resolution = 0.1
[[[[DIGIT2]]]]
Data Type = BCD
Word = 256
Subframe = 4
Frame = 12
Bits = 9-6
Resolution = 1
[[[[DIGIT3]]]]
Data Type = BCD
Word = 256
Subframe = 4
Frame = 12
Bits = 12-10
Resolution = 10

12.2.3 Multistate With Joining Function

Figure 3 Two Level Joining

[[Altitude Baro inHg (1)]]

Data Type = Unsigned
Units = inHg
Multipart Joining Function = Numeric Overflow
Part Order = MSH, LSH
[[[LSH]]]

This work by Flight Data Services is licensed under a Creative Commons Page 47
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Data Type = Unsigned

Sample Rate = 0.25
Multipart Joining Function = Numeric Addition
Part Order = Raw3, Raw4
[[[[Raw3]]]]
Word = 186
Subframe = 1
Bits = 8-5
Resolution = 0.001
[[[[Raw4]]]]
Word = 186
Subframe = 1
Bits = 12-9
Resolution = 0.01
[[[MSH]]]
Sample Rate = 0.015625
Multipart Joining Function = Numeric Addition
Part Order = Raw0, Raw1, Raw2
[[[[Raw0]]]]
Word = 256
Subframe = 4
Frame = 12
Bits = 5-2
Resolution = 0.1
[[[[Raw1]]]]
Word = 256
Subframe = 4
Frame = 12
Bits = 9-6
Resolution = 1
[[[[Raw2]]]]
Word = 256
Subframe = 4
Frame = 12
Bits = 12-10
Resolution = 10

12.2.4 Multi Part - Signed with separate Signed Bit

[[Altitude Radio]]
Data Type = Signed
Units = ft
Multipart Joining Function = Overflow Correction
Full Scale = 2048
Part Order = SIGNED, MSH, LSH
[[[SIGNED]]]
Sample Rate = 1
Word = 128
Bits = 12-12
[[[LSH]]]
Sample Rate = 1

This work by Flight Data Services is licensed under a Creative Commons Page 48
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Word = 128
Bits = 11-1
[[[MSH]]]
Sample Rate = 1
Word = 186
Bits = 2-1

12.2.5 Multipart with First Part Validation

12.2.5.1 Normal True State

[[Azimuth]]
Sample Rate = 1
Units = loc-ddm
Data Type = Signed
Full Scale = 0.4
Multipart Joining Function = First Part Validation
Part Order = MLS Select Left, Azimuth
[[[MLS Select Left]]]
Data Type = Discrete
Sample Rate = 0.25
Word = 31
Subframe = 3
Bits = 1-1
True = Recorded
[[[Azimuth]]]
Word = 48
Bits = 12-3

12.2.5.2 Inverted True State

[[TAWS Pull Up]]

Multipart Joining Function = First Part Validation
Part Order = TAWS Inop, TAWS Pull Up,
Data Type = Discrete
True = Warning
[[[TAWS Inop]]]
Data Type = Discrete
Sample Rate = 0.25
Word = 61
Subframe = 4
Bits = 3-3
Logic = Inverted
[[[TAWS Pull Up]]]
Sample Rate = 0.25
Word = 45
Subframe = 1
Bits = 3-3

This work by Flight Data Services is licensed under a Creative Commons Page 49
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

12.2.5.3 Inverted True State – Multistate

[[TCAS Combined Control]]

Source Name = TCAS Combined Control
Data Type = Multi-state
Multipart Joining Function = First Part Validation
Part Order = TCAS Failed, TCAS Combined Control,
[[[TCAS Failed]]]
Data Type = Discrete
Sample Rate = 1
Word = 235
Bits = 2-2
Logic = Inverted
[[[TCAS Combined Control]]]
Data Type = Multi-state
Multipart Joining Function = Direct Addition
Part Order = PART_1, PART_2,
[[[[PART_1]]]]
Word = 63
Sample Rate = 1
Bits = 10-8
Subframe = 1
[[[[PART_2]]]]
Word = 225
Sample Rate = 1
Bits = 5-3
Subframe = 1
[[[[State]]]]
0 = No Up Advisory
1 = Clear of Conflict
2 = Drop Track
3 = Altitude Lost
4 = Up Advisory Corrective
5 = Down Advisory Corrective
6 = Preventive

12.2.5.4 Multipart with Full Scale option

[[Heading]]
Source Name = Mag Heading
Data Type = Unsigned
ARINC 429 = True
Units = deg
Multipart Joining Function = First Part Validation
Part Order = Mag-True Data, Heading
[[[Mag-True Data]]]
Data Type = Discrete
Sample Rate = 1
Word = 15
Bits = 2-2
Logic = Inverted
[[[Heading]]]

This work by Flight Data Services is licensed under a Creative Commons Page 50
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Data Type = Unsigned

Sample Rate = 1
Word = 15
Bits = 12-3
Full Scale = 360

12.2.6 Multipart with First Part Switch

[[Aileron (L)]]
Data Type = Unsigned
Part Order = Switch, Signal 1, Signal 2
Multipart Joining Function = First Part Switch
[[[Switch]]]
Sample Rate = 0.25
Word = 31
Subframe = 3
Bits = 1-1
[[[Signal 1]]]
# Sampled when Switch is one
Sample Rate = 2
Word = 15
Bits = 12-3
[[[Signal 2]]]
# Sampled when Switch is zero
Data Type = Unsigned
Sample Rate = 2
Word = 16
Bits = 5-1
Resolution = 0.687

This work by Flight Data Services is licensed under a Creative Commons Page 51
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

12.2.7 VOR/ILS Frequency

Figure 4 Complex Joining Function

[[ILS-VOR Frequency (1)]]

Multipart Joining Function = First Part Validation
Part Order = MLS SELECT, VOR/ILS FREQ LEFT
[[[MLS SELECT]]]
Data Type = Discrete
Sample Rate = 0.25
Word = 56
Subframe = 4
Bits = 7-7
True = Recorded
[[[VOR/ILS FREQ LEFT]]]
Data Type = BCD
Units = MHz
Multipart Joining Function = Numeric Addition
Part Order = P1, P2, P3, P4
[[[[P1]]]]
Data Type = BCD
Units = MHz
Resolution = 10
Sample Rate = 0.25
Word = 49
Subframe = 2

This work by Flight Data Services is licensed under a Creative Commons Page 52
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Bits = 12-10
[[[[P2]]]]
Data Type = BCD
Units = MHz
Resolution = 1
Sample Rate = 0.25
Word = 49
Subframe = 2
Bits = 9-6
[[[[P3]]]]
Data Type = BCD
Units = MHz
Resolution = 0.1
Sample Rate = 0.25
Word = 49
Subframe = 2
Bits = 5-2
[[[[P4]]]]
Data Type = BCD
Units = MHz
Resolution = 0.01
Multipart Joining Function = Direct Addition
Part Order = MSH, LSH
[[[[[LSH]]]]]
Sample Rate = 0.25
Word = 52
Subframe = 2
Bits = 12-10
[[[[[MSH]]]]]
Sample Rate = 0.25
Word = 49
Subframe = 2
Bits = 1-1

12.2.8 Multistate With Joining Function

[[TCAS Combined Control]]

Data Type = Multi-state
Multipart Joining Function = Direct Addition
Part Order = PART1, PART2
[[[PART1]]]
Data Type = Multi-state
Bits = 10-8
Word = 63
Sample Rate = 2
[[[PART2]]]
Data Type = Multi-state
Bits = 5-3
Word = 63
Sample Rate = 2
[[[State]]]

This work by Flight Data Services is licensed under a Creative Commons Page 53
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

0 = No Up Advisory
1 = Clear of Conflict
2 = Drop Track
3 = Altitude Lost
4 = Up Advisory Corrective
5 = Down Advisory Corrective
6 = Preventive

12.2.9 Multipart – Sign and Magnitude

[[Latitude]]
Data Type = Unsigned
Units = deg
Multipart Joining Function = Sign and Magnitude
Part Order = Latitude Sign, Latitude Degrees
[[[Latitude Sign]]]
Data Type = Discrete
Sample Rate = 0.25
Word = 122
Subframe = 2
Bits = 12-12
[[[Latitude Degrees]]]
Source Name = Latitude Degrees
Units = deg
Multipart Joining Function = Numeric Addition
Part Order = Degrees, Minutes, Seconds
[[[[Degrees]]]]
Data Type = Unsigned
Sample Rate = 0.25
Word = 122
Subframe = 2
Bits = 9-1
Resolution = 1.0
[[[[Minutes]]]]
Data Type = Unsigned
Sample Rate = 0.25
Word = 124
Subframe = 2
Bits = 12-7
Resolution = 0.01666667
[[[[Seconds]]]]
Data Type = Unsigned
Sample Rate = 0.25
Word = 124
Subframe = 2
Bits = 6-1
Resolution = 0.000277778

This work by Flight Data Services is licensed under a Creative Commons Page 54
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

12.2.10 Multipart – Control Column Force 737

[[Control Column Force (Capt)]]

Data Type = Unsigned
Units = lbs
Part Order = Control Column Force (Local), Control
Column Force (Foreign), FCC Local Limited Master
Multipart Joining Function = Control Column Force 737

[[[Control Column Force (Local)]]]

Source Name = CC FORCE (PITCH CWS LOCAL)
ARINC 429 = True
Data Type = Signed
Units = lb
Sample Rate = 2
Word = 25
Bits = 12-1

[[[Control Column Force (Foreign)]]]

Source Name = CC FORCE (PITCH CWS FOREIGN)
ARINC 429 = True
Data Type = Signed
Units = lb
Sample Rate = 2
Word = 32
Bits = 12-1

[[[FCC Local Limited Master]]]

Source Name = FCC Local Limited Master
Data Type = Multi-state
Sample Rate = 1
Word = 56
Bits = 2-1
[[[[State]]]]
0 = FCC (L)
1 = FCC (R)
2 = FCC (L)
3 = FCC (L)

12.2.11 Multipart Joining Function = PV1584 Altitude STD

[[Altitude STD]]
Data Type = Unsigned
Units = ft
Multipart Joining Function = PV1584 Altitude STD
Part Order = Altitude STD Low, Altitude STD High
[[[Altitude STD Low]]]
Source Name = Altitude below 17500 ft
Data Type = Unsigned
Units = ft

This work by Flight Data Services is licensed under a Creative Commons Page 55
Attribution-NoDerivatives 4.0 International License.
 Flight Data Community
Frame Format Specification

Sample Rate = 1.0

Word = 58
Subframe = 1
Bits = 12-1
Resolution = 5.81
Offset = -2900
[[[Altitude STD High]]]
Source Name = Altitude above 17500 ft
Data Type = Unsigned
Units = ft
Sample Rate = 1.0
Word = 57
Subframe = 1
Bits = 12-1
Resolution = 9.157
Offset = 14250

This work by Flight Data Services is licensed under a Creative Commons Page 56
Attribution-NoDerivatives 4.0 International License.