Home  / Our Products / FDRCVR

FDR/CVR Replay & Readout Explained

Flight Data Recorder (FDR) Replay & Cockpit Voice Recorders (CVR) Readout? What is it? Why do you need it.




Innovative, Unique, Modern




                If you are searching for an affordable world class Flight Data Recorder (FDR) & Cockpit Voice Recorder (CVR) replay and readout solution that will maximize the information you receive to monitor the condition of your FDR system, we can help. Detailed analysis report can explore and understand the condition of your flight data recorder system with an unparalleled volume of information.


                We’ll help you to meet specific aviation regulatory requirements and at the same time maximize your operational efficiency. Our flight data recorder replay service can deliver an instant readout of your flight data recorder. Saving you time and effort, increasing your ability to keep the fleet active.


FDR Replay & Readout FAQs




  • What is Flight Data Recorder replay and readout?

    Flight Data Recorder replay and readout is the process of checking the health of your FDR system. This may also include important records from your Cockpit Voice Recorder (CVR)

  • What are the benefits?

    Flight Data Services FDR replay and readout system uses knowledge specific to your aircraft configuration to provide results which are specific to your aircraft make and model. Our reports provide in depth analysis of each parameter recorded by your flight data recorder system, ensuring conformance with aviation regulations.

    - Decreased lead times.

    - Automatic analysis.

    - In depth reporting.


  • Is this a requirement?

    The Air Navigation Order 2009 states that FDR replays should be conducted annually or every 12000 flight hours whichever comes first.


  • Is the data processed in flight?

    No; it is examined after a flight and for convenience many operators upload their data at regular intervals to fit in with maintenance schedules.



  • Who performs the FDR/CVR replay?

    Should you decide to do your own flight data recorder readout in house:

    - You need a means of transferring the data from the aircraft to the analysis software.

    - You need analysis software to the order of £31,000 – £61,000 ($50,000 – $100,000) per copy.

    - You need analyst expertise.



FDR Replay & Readout Explained









                NY AERO offers automatic FDR analysis to help you to determine the health of your flight data recorder system. Our patented FDR replay and readout system analyses every parameter recorded by your flight data recorder to provide the information you need to understand the condition of your system. A host of tests are used to assess each FDR parameter including:


- Data spike detection

- Change detection analysis

- Calibration tests

- Parameter noise assessment

- Recording range tests

- Sampling frequency analysis

- Parameter correlation analysis


                All tests are executed based on a set of analysis limits for each parameter which are unique to your specific aircraft and engine models.




                The report is designed to maximize the amount of information available from the replay/readout of your FDR data, providing you with the tools to monitor the condition of your flight data recorder system. Each report contains:


- Detailed analysis of each parameter.

- Information regarding any errors detected during the analysis.

- Graphs and charts.



FDR Replay & Readout Regulations





The following extracts are from ICAO Annex 6 – Operation of aircraft:


6.10.10 Flight recorders — continued serviceability Operational

checks and evaluations of recordings from the flight data and

cockpit voice recorder systems shall be conducted to ensure the

continued serviceability of the recorders.


Attachment D - 3.2 : Annual inspections should be carried out as follows:

a) the read-out of the recorded data from the FDR and

     CVR should ensure that the recorder operates correctly

     for the nominal duration of the recording;

b) the analysis of the FDR should evaluate the quality of

     the recorded data to determine if the bit error rate is

     within acceptable limits and to determine the nature and

     distribution of the errors;

c) a complete flight from the FDR should be examined in

     engineering units to evaluate the validity of all recorded

     parameters. Particular attention should be given to

     parameters from sensors dedicated to the FDR. Parameters

     taken from the aircraft’s electrical bus system need not

     be checked if their serviceability can be detected by other

     aircraft systems;





The following excerpt is taken from Advisory Circular 20-141:


8 a. Parameter Operational Check. The operator must perform an

operational and functional check to determine that each required

parameter is being recorded, that the recorded value is reasonable,

and that data quality is sufficient to interpret the data. This

operational and functional check is also referred to as a

reasonableness and quality check. Any parameter that is generated

by a sensor or transducer installed as part of the DFDRS or

exclusively used by the DFDRS must be functionally checked at the

time that the operational check is accomplished. See paragraph 7.l.(3).

The operator must retain the downloaded data (raw data in electronic

format that can be deciphered using the Data Stream Format contained

in the correlation document is acceptable) used in this check as a

permanent part of the aircraft records. The operator must note in its

maintenance program how to access the downloaded data used in this

check. See paragraph 7.l. (4) for a description of the operational and

functional check.


The aforementioned document also outlines the necessary requirements for performing an FDR replay.





The following is an extract from CAP 731 – Approval, Operations Serviceability and Readout of Flight Data Recorder Systems and Cockpit Voice Recorders:


Articles 153, 154 and 155 of the Air Navigation Order 2009 require

that operators preserve a record of one representative flight made

within the last 12 months.  The purpose of this is to ensure that,

in the event of an accident/incident, air accident investigators have

access to a readout from the flight data recording system that is

representative of the actual aircraft condition prior to the

accident/incident.  It follows that the data originating from the

selected representative flight will need to be evaluated to determine

that it comprises a valid record.




The following is an extract from EASA Safety Information Bulletin 2009-28:


1. Accident Investigators have reported several cases in which the

Flight Data Recorders (FDR) or Cockpit Voice Recorders (CVR) have not

recorded data as expected, due to a malfunction of the unit or the

installation. Such failures may remain hidden for a certain amount of time,

as it is difficult / impossible to determine the full system functionality

onboard the aircraft. This behaviour is described as a dormant failure.

Recorder issues are further discussed in detail in the study performed by BEA.


2. The European Organization for Civil Aviation Equipment (EUROCAE) has

developed ED-112, the most recent industry standard for FDR and CVR. The adoption

of that document as European Technical Standard Order (ETSO) is in process (see

Notice of Proposed Amendment NPA 2009-11). In order to allow detection of

dormant failures the document recommends performing the following maintenance



For FDR:

· Every 3 000 flight hours or every 12 months, whichever

  occurs first, download and analyse at least a whole flight

  recording. Check that all mandatory parameters are

  active and are of acceptable quality.

· Pre-Flight: check for no-failure.


The following extract is taken from Appendix II-B in ED-1112 Minimum Operational Performance Specification for Crash Protected Airborne Recorder Systems:


II-B.1.3 A copy of the recording including a whole flight (from recorder start

to recorder stop) should be made at specified intervals. The copy should be

transcribed such that all parameter samples can be resolved. All mandatory

parameters recorded should be expressed in engineering units. Inspection of

parameters should reveal defects or noise in the measuring and processing chains

and indicate necessary maintenance actions. When applicable, each mandatory

parameter should be checked for different values of its operational range. For

this purpose, some parameters should be inspected at different flight phases.

The operator shall retain the most recent copy recording.


ED-112 also specifies that the interval for performing the above task is set as 3000 flight hours or 12 months whichever comes first.



Coming Soon






Copyright 2016. All Rights Reserved by NY AERO Co., Ltd.

The information and material on this Web site is provided solely for informational purposes only. All logos, trade marks, etc. are owned by each respective companies. Owners of copyright, licenses, etc. may request us to remove any part of the web site if they feel that it is inappropriate or had unintentionally violated or misused such materials.

NY Publishing Service

  • 