U.S. patent application number 13/513824 was filed with the patent office on 2012-10-11 for digital recording and replay system for an aircraft and method for reproduction of onboard instrumentation of an aircraft.
This patent application is currently assigned to PILATUS FLUGZEUGWERKE AG. Invention is credited to Bruno Cervia, Paul Gibson, Robert Milns, Daniel O'Connor.
Application Number | 20120259508 13/513824 |
Document ID | / |
Family ID | 42668304 |
Filed Date | 2012-10-11 |
United States Patent
Application |
20120259508 |
Kind Code |
A1 |
O'Connor; Daniel ; et
al. |
October 11, 2012 |
Digital Recording and Replay System for an Aircraft and Method for
Reproduction of Onboard Instrumentation of an Aircraft
Abstract
Digital recording and replay system (100) for an aircraft,
comprising a Mission Computer (MC) with an Operational Flight
Program (OFP) for generating instrument data (ID) for onboard
instruments of the aircraft; a Mission Data Recorder (MDR)
connected to said Mission Computer (MC) for recording said
instrument data (ID); and a Mission Debriefing System (MDS);
wherein the Mission Debriefing System (MDS) is configured to
reproduce the onboard instruments of the aircraft based on
instrument data (ID) retrieved from the Mission Data Recorder
(MDR). Method for reproduction of onboard instrumentation of an
aircraft, comprising the steps of connecting a Mission Data
Recorder (MDR) to a Mission Computer (MC) of an aircraft having an
Operational Flight Program (OFP) for generating instrument data
(ID) for onboard instruments; recording instrument data (ID);
providing a Mission Debrief System (MDS) and causing it to
reproduce the onboard instruments of the aircraft based on
instrument data (ID) retrieved from the Mission MDS Data Recorder
(MDR).
Inventors: |
O'Connor; Daniel;
(Ennetmoos, CH) ; Cervia; Bruno; (Buochs, CH)
; Milns; Robert; (Buochs, CH) ; Gibson; Paul;
(Alpnachstad, CH) |
Assignee: |
PILATUS FLUGZEUGWERKE AG
Stans
CH
|
Family ID: |
42668304 |
Appl. No.: |
13/513824 |
Filed: |
December 6, 2010 |
PCT Filed: |
December 6, 2010 |
PCT NO: |
PCT/EP2010/068999 |
371 Date: |
June 22, 2012 |
Current U.S.
Class: |
701/33.4 |
Current CPC
Class: |
G01C 23/00 20130101;
G07C 5/085 20130101; B64D 43/00 20130101; B64D 45/00 20130101; G09B
9/08 20130101; B64D 2045/0065 20130101 |
Class at
Publication: |
701/33.4 |
International
Class: |
G07C 5/00 20060101
G07C005/00 |
Foreign Application Data
Date |
Code |
Application Number |
Dec 4, 2009 |
EP |
PCT/EP2009/066449 |
Claims
1. A digital recording and replay system for an aircraft,
comprising: a Mission Computer with an Operational Flight Program
configured to digital signal process input source signals and
generate instrument data of onboard instruments of an aircraft; a
Mission Data Recorder operatively connected to said Mission
Computer configured to record said instrument data; and a Mission
Debriefing System configured to reproduce the onboard instruments
of the aircraft based on instrument data retrieved from the Mission
Data Recorder.
2. A digital recording and replay system for an aircraft according
to claim 1, the Mission Data Recorder comprising a first means for
receiving a Removable Memory Module configured to store said
instrument data.
3. A digital recording and replay system for an aircraft according
to claim 2, the Mission Debriefing System comprising a second means
for receiving a Removable Memory Module configured to store said
instrument data.
4. A digital recording and replay system for an aircraft according
to claim 1, wherein the Mission Debriefing System is operatively
connectable to said Mission Data Recorder and configured to
retrieve said recorded instrument data and subsequently reproduce
the onboard instruments of the aircraft within the aircraft using
onboard instruments of the aircraft based on instrument data
retrieved from the Mission Data Recorder.
5. A digital recording and replay system for an aircraft according
to claim 1, wherein said instrument data comprises parameters of an
avionics system of the aircraft and wherein said reproduction by
the Mission Debriefing System comprises a reconstruction of a
display as a pilot would see the display during a flight of the
aircraft during which said instrument data has been recorded.
6. A digital recording and replay system for an aircraft according
to claim 1, wherein said instrument data comprises input data
transferred to a graphics card of the aircraft and driving a
display of the aircraft.
7. A digital recording and replay system for an aircraft according
to claim 6, wherein the Mission Computer is configured to send said
input data as packets to the Mission Data Recorder.
8. A digital recording and replay system for an aircraft according
to claim 7, wherein the Mission Computer is configured to include
in said packets a header defining the data contained within the
packet.
9. A digital recording and replay system for an aircraft according
to claim 7, wherein the Mission Computer is configured to send
additional packets to the Mission Data Recorder comprising data of
additional aircraft avionics systems other than said display.
10. A digital recording and replay system for an aircraft according
to claim 1, wherein said instrument data comprises event data
generated in response to pilot actions.
11. A digital recording and replay system for an aircraft according
to claim 10, wherein said event data is generated from onboard
controls of the aircraft.
12. A method of reproducing onboard instrumentation of an aircraft,
comprising the steps of: operatively connecting a Mission Data
Recorder to a Mission Computer of an aircraft having an Operational
Flight Program configured to generate instrument data of onboard
instruments of the aircraft; recording instrument data generated by
the Mission Computer using said Mission Data Recorder; and
reproducing the onboard instruments of the aircraft with a Mission
Debrief System based on instrument data retrieved from the Mission
Data Recorder.
13. A method of reproducing onboard instrumentation of an aircraft
according to claim 12, wherein the Mission Data Recorder comprises
a first means for receiving a Removable Memory Module configured to
store said instrument data, and further comprising the steps of
inserting a Removable Memory Module configured to store said
instrument data into said first means, and storing said instrument
data in the Removable Memory Module.
14. A method of reproducing onboard instrumentation of an aircraft
according to claim 13, wherein the Mission Debriefing System
comprises a second means for receiving said Removable Memory
Module, and further comprising the steps of: removing the Removable
Memory Module from said first means; and inserting the Removable
Memory Module into the second means.
15. A method of reproducing onboard instrumentation of an aircraft
according to claim 12, wherein the reproducing step includes the
steps of: operatively connecting the Mission Debriefing System to
the Mission Data Recorder; retrieving said recorded instrument
data; and reproducing the onboard instruments of the aircraft
within the aircraft using onboard instruments of the aircraft.
16. A digital recording and display system for an aircraft
according to claim 3, further comprising a Removable Memory Module
configured to store said instrument data, removable from said first
means, and insertable into the second means.
Description
PRIORITY
[0001] The present application claims priority from
PCT/EP2009/066449 filed Apr. 12, 2009.
FIELD OF THE INVENTION
[0002] The present invention relates to a Digital recording and
replay system for an aircraft and to a method for reproduction of
onboard instrumentation of an aircraft.
BACKGROUND OF THE INVENTION
[0003] Quite often there is a need to be able to replay/reproduce
the exact instrumentation presented to the pilots of an aircraft
after a flight. Furthermore, one needs to be able to present this
instrumentation in the context of the particular scenario and also
to be able to reconstruct the pilot's reaction to the events
occurred during the flight. In addition the reaction of an airplane
in response to the pilot's actions needs to be documented.
[0004] Several systems are known which are able to record aircraft
parameters and store instrumentation data as a video and/or audio
recording. These systems are known as flight data recorders and
cockpit voice/image recorders. They are usually placed in an
aircraft for the purpose of facilitating the investigation of an
aircraft accident or incident. In newer aircrafts installation of
cockpit image recorders has been proposed to provide a video
recording of the instruments within the cockpit. Such systems
typically consist of a camera and microphone located in the cockpit
to continuously record cockpit instrumentation, the outside viewing
area, engine sounds, radio communications, and ambient cockpit
sounds. After an accident or incident, the flight data recorders
and cockpit voice/image recorders are retrieved and a video and/or
audio recording made during the flight is reconstructed along with
recorded flight parameters.
[0005] However, known systems suffer from the major drawback that
since they record aircraft parameters and an audio and/or video
feed they can't reliably reproduce the instruments exactly as shown
to the pilot. This is due to the fact that the video images
recorded might be blurred, the camera view might be blocked, etc.
or generally of low quality. Furthermore, due to the high storage
capacity requirements for a video recording covering all
instruments, either the length of such a recording is limited, or
some of the instruments are not covered by the video recording.
[0006] Furthermore, the reconstruction of the onboard
instrumentation based on a video recording is a very time-consuming
procedure prone to errors.
[0007] In an attempt to overcome these disadvantages, an other kind
of known system records merely aircraft parameters on the bases of
which such onboard instruments are constructed. These instruments
are then to be reconstructed based on the recorded parameters.
However, relying merely on the set of recorded parameters does not
necessarily allow a faithful reconstruction of the onboard
instrumentation. One cause for this is the malfunction of the
avionics systems of the aircraft.
[0008] A special field where such a reconstruction of onboard
reconstruction is frequently performed is in the field of training
aircrafts where the exact training environment is reconstructed for
debrief and training analysis purposes. This field of application
poses special requirements on such recording and replay systems,
such as their ability to allow a quick and reliable reconstruction
of the training environment including onboard instrumentation but
also of visual and audible alerts received through different
channels of onboard avionics systems. Furthermore, such systems
must be able to be reused numerous times and their processing
should be as straight-forward as possible.
[0009] Such training aircrafts are provided with a so-called
mission computer as well with an operational flight program
defining the training scenario performed by the pilot/trainee.
Therefore, the recorded instrument data needs to be recorded in
relation with this scenario since the onboard instruments are
always in relation with the operational flight program and only
make sense in this context.
OBJECTIVE OF THE INVENTION
[0010] The objective of the present invention is thus to provide a
recording and replay system for an aircraft that is able to
reliably reconstruct the onboard instruments of an aircraft,
preferably a training aircraft, comprising a mission computer with
an operational flight program. A further objective of the invention
is to ensure that the onboard instrumentation is easy to
reconstruct and can store instrument data covering a prolonged
period of time.
[0011] Furthermore it is an objective of the present invention to
provide a method for reproduction of onboard instrumentation of an
aircraft able to reliably reconstruct the onboard instruments of an
aircraft, preferably a training aircraft. Said method should allow
quick reconstruction of onboard instruments of an aircraft brought
in relation with an operational flight program of a mission
computer of the aircraft.
SUMMARY OF THE INVENTION
[0012] The above-identified objectives of the present invention are
solved by a recording and replay system for an aircraft, comprising
a mission computer with an operational flight program for
generating instrument data for onboard instruments of the aircraft;
a mission data recorder connected to said mission computer for
recording said instrument data as processed by mission computer
with an operational flight program; and a mission debriefing
system; wherein the mission debriefing system is configured to
reproduce the onboard instruments of the aircraft based on
instrument data retrieved from the mission data recorder.
[0013] The above-identified objectives of the present invention are
also solved by a method for reproduction of onboard instrumentation
of an aircraft, comprising the steps of: connecting a mission data
recorder to a mission computer of an aircraft having an operational
flight program for generating instrument data for onboard
instruments of the aircraft; recording instrument data as processed
by mission computer with an operational flight program and sent to
the onboard instruments of the aircraft using said mission data
recorder; providing a mission debrief system; and causing said
mission debrief system to reproduce the onboard instruments of the
aircraft based on instrument data retrieved from the mission data
recorder.
[0014] The objectives identified above are solved by the present
invention in that instrument data for the onboard instruments of
the aircraft, are recorded by the mission data recorder instead of
aircraft parameters or video recording of the actual instruments.
In other words the system records aircraft parameters where the
signals have been processed through digital systems for accuracy
and latency and relevance to the operator of the aircraft. The
instruments of the aircraft can then be reconstructed based on the
recorded parameters. Relying on the set of recorded parameters
gives a faithful reconstruction of the activities onboard
instrumentation central to the operations of the aircraft,
including an accurate representation of malfunctions. One cause for
this is the malfunction of the avionics systems of the aircraft
which lies at the heart of the computing systems used to process
the data.
[0015] The concept of debrief reconstruction uses recorded
parameters of the avionics systems to reconstruct the onboard
instruments as the pilot/operator would see them during flight,
without the use of video systems.
[0016] This concept allows all pilot debrief to take place using
the reconstructed instrumentation data, rather than basing debrief
on recorded video. The additional onboard instruments available due
to the recording method are an additional training aid provided for
very little overhead compared to recording the additional 20-30
video streams that would traditionally be required under such a
debriefing system. The digital signal processing of incoming source
signals such as barometric altitude, airspeed or body lateral
acceleration is carried out to present the data to the operator,
and this can be re-used by the recording system to maximize
efficiency.
ADVANTAGEOUS EFFECTS
[0017] In view of the drawbacks of the prior art, the objective of
the present invention and the inventive solution summarized above,
the present invention has the main advantage that the data recorded
reliably reflects the onboard instrumentation as used by the
operator, as opposed to known systems recording merely aircraft
parameters that are supposed to result in some expected
instrumentation display, while at the same time simplifying the
retrieval and minimizing the storage requirements, as compared to a
recording of a video image of the instruments which is susceptible
to errors in reconstruction, requires significantly more storage
capacity and might not even cover all onboard instruments.
BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Further characteristics and advantages of the invention will
in the following be described in detail by means of the description
and by making reference to the drawings. Which show:
[0019] FIG. 1 A schematic block diagram of the first embodiment of
the recording and replay system according to the present
invention;
[0020] FIG. 2A A schematic block diagram of the mission computer of
an aircraft as being connected to a mission data recorder according
to the present invention;
[0021] FIG. 2B A schematic block diagram depicting the integration
of the mission data recorder of the present invention with the
avionics system of an aircraft.
DESCRIPTION OF PREFERRED EMBODIMENTS
[0022] Certain terms will be used in this patent application, the
formulation of which should not be interpreted to be limited by the
specific term chosen, but as to relate to the general concept
behind the specific term.
[0023] In the context of the present application, training
functionality shall mean the functionalities of a training aircraft
which relate to the training of a pilot/trainee in an emulated
environment within the aircraft. The training functionalities
further relate to tactical scenarios, simulated warfare, all these
according to a training syllabus.
[0024] The term aircraft shall mean in the context of the present
application any kind of aircraft including recreational, civil but
especially training aircrafts providing tactical/training
functionalities.
Hardware Architecture
[0025] FIG. 1 shows a schematic block diagram of the first
embodiment of the recording and replay system according to the
present invention. This figure depicts the essential concept of the
invention, i.e. the interaction between the mission computer MC,
the mission data recorder MDR and the mission debriefing system
MDS.
[0026] The mission computer MC is a central part of the avionics
system of a training aircraft and comprises the operational flight
program OFP, a dataset defining the training scenario and/or
mission of the aircraft, wherein the operational flight program OFP
takes as input unprocessed data, applies digital signal processing
techniques for presentation to the operator and generates
instrument data ID for onboard instruments of the aircraft. The
mission computer MC carries out digital signal processing of
incoming source signals from a number of sources such as air data
computers, radar altimeters and inertial reference systems that
supply raw data transposed from the original analogue signal
measurement. To ensure that the data is supplied to the
pilot/operator in a manner that is usable, the information is
sampled and filtered to show a relatively stable value whilst
reflecting the current trends in the aircraft parameters. Once this
processing is carried out by the operational flight program OFP
within the mission computer MC, the processed instrument data ID
can be presented to the operator, and this can be re-used by the
mission data recorder MDR to maximize efficiency in re-presenting
this data in ground based debrief systems.
[0027] The mission data recorder MDR, a data recording and recovery
device is connected to the mission computer MC, is provided for
recording the instrument data ID generated by the operational
flight program OFP. The role of the mission data recorder MDR is to
record instrument data ID to allow post flight mission analysis and
debrief--to support the training of aircrew in the aircraft.
[0028] It shall be noted that the mission data recorder MDR is not
a replacement or alternative for an accident or flight data
recorder.
[0029] The mission debriefing system MDS is a data recovery and
instrumentation reconstruction system, configured to reproduce the
onboard instruments of the aircraft based on instrument data ID
retrieved from the mission data recorder MDR.
Mission Computer
[0030] FIG. 2A shows schematic block diagram of the mission
computer MC of an aircraft as being connected to a mission data
recorder MDR. The connection is preferably established via a
mission bus 11. In a preferred embodiment of the present invention,
the mission bus 11 is used to download new operational flight
program OFP files into the mission computer MC; download mission
files; download digital map tiles; and to upload instrument data ID
for recording by the mission data recorder MDR. The mission
computer MC initiates all transfers on the mission bus 11. The
mission computer MC mounts the removable memory module RMM of the
mission data recorder MDR as a remote disk drive in order to
download mission files and/or to retrieve digital map tiles. Means
for receiving said removable memory module RMM are provided within
the mission data recorder MDR, such as a memory card slot or
suitable connectors.
[0031] The mission computer MC also controls the instrument data ID
at the instruments output for the onboard instruments such as the
Multi-Function Display MFD and Up Front Control Panel UFCP for
example. The mission computer MC has a graphics card dedicated to
drawing the onboard instruments such as the displays for the
multi-function display MFD based on the instrument data ID.
[0032] The mission computer MC main board contains the operational
flight program OFP that calculates the instrument data ID required
for the onboard instruments. This instrument data ID is transferred
to the graphics cards.
[0033] To reduce loading, the packets of the instrument data ID are
only sent when their data content has changed. Each packet is
otherwise only sent every few seconds to ensure subsequent playback
synchronization is achieved rapidly during reconstruction.
[0034] The same instrument data ID can also be transferred to the
mission data recorder MDR due to the underlying similarity in the
data structure. Therefore at the same time as sending the
instrument data ID to the graphics cards, the instrument data ID is
sent to the mission data recorder MDR preferably as UDP packets
over the Ethernet link.
[0035] A header is added to the mission data recorder MDR output
that defines the instrument data ID contained within a packet. A
small number of additional packets are included on the mission data
recorder MDR output that use the same data architecture/structure
but are not sent to the graphics cards. These are included to aid
reconstruction of other systems other than the aircraft
multi-function display MFD (e.g. Up-Front Control Panel UFCP or
Primary Flight Display PFD).
Mission Data Recorder
[0036] FIG. 2B shows a schematic block diagram depicting the
integration of the mission data recorder MDR of the present
invention with the avionics system of an aircraft.
[0037] The role of the mission data recorder MDR is to record
instrument data ID to allow post flight mission analysis and
debrief--to support the training of aircrew in the aircraft. In a
preferred embodiment of the present invention, the mission data
recorder MDR uses Ethernet input, video and audio inputs. The
Ethernet input is from the mission computer MC, and carries the
data used to generate the onboard instruments such as the
multi-function display MFD displays. The video shows head-up
display HUD symbology overlaid on a forward view of the outside
world.
[0038] The mission data recorder MDR is further connected to the
audio management unit AMU which controls all audio signals within
the aircraft.
[0039] In a two-cockpit training aircraft, the head-up display HUD
is installed in the front cockpit position, and incorporates a
forward-looking camera. This camera produces a video image of the
view ahead of the aircraft for display on the rear seat head-up
display repeater HUDR. The head-up display HUD symbology is
superimposed over the image of the outside world on the head-up
display repeater HUDR. In this case, the video is of the video seen
on a head-up display repeater HUDR, and shows head-up display HUD
symbology overlaid on a forward view of the outside world. In this
two-cockpit training aircraft, the audio is of the front cockpit
headset audio so that all radio and intercom traffic and alert
tones are available.
[0040] Additional event data, generated by the pilot via additional
controls of the aircraft such as a console mounted event button or
a stick mounted trigger and pickle buttons, are also recorded by
the mission data recorder MDR
[0041] In a preferred embodiment, the mission computer MC
transmits, via UDP broadcast on the Ethernet ports 6003 (display
data and instrumentation) and 6005 (Radar picture). This is the
instrument data ID that is used for the generation of the onboard
instruments such as multi-function display MFD display graphics.
Some additional data that is available in the mission computer MC
and used on further onboard instruments such as the primary flight
display PFD is also transmitted on the Ethernet bus.
[0042] The mission data recorder MDR receives this UDP data, and
records it. The mission data recorder MDR does not make any attempt
to decode the UDP port 6003/6005 broadcast data. The resultant UDP
contents are preferably stored on a removable memory module
RMM.
[0043] In a preferred implementation, the instrument data ID is
stored on the removable memory module RMM in files that are
nominally 30 MB in size--this equates to approximately 5 to 6
minutes of recording time. Individual file sizes are limited so
that if a file should become corrupted then only 5 to 6 minutes of
data are lost.
[0044] Time stamp information is embedded within the recording,
such that at replay/reconstruction the actual time of the recording
can be determined, for cross-relation to other external events and
also to allow synchronized replay with the video and events data
(and recordings from other aircraft).
[0045] Preferably, the video and audio data are combined into a
single recording stream. The audio is added to the video (left and
right channels) to become a standard video with stereo audio
channels. The audio/video is compressed for example using MPEG-2
compression, at 720 by 480 pixels image size and 60 frames per
second. The resultant MPEG digital data is stored on the removable
memory module RMM.
[0046] The data is recorded in files that are 30 seconds in
length--these are approximately 30 MB is size. The individual file
sizes are limited so that if a file should become corrupted then
only 30 seconds of video are lost.
[0047] Time stamp information is embedded within the recording,
such that at replay the actual time of the recording can be
determined, for cross-relation to other external events and also to
allow synchronised replay with the head-down Ethernet recorded data
and events data (and recordings from other aircraft).
[0048] When the aircrew actuates an additional control of the
aircraft such as pressing the event button, trigger or pickle
button in either the front or rear cockpits of a two-cockpit
training aircraft, the mission computer MC detects this. The
mission computer MC then passes a UDP packet to the mission data
recorder MDR with the event source code. The mission data recorder
MDR records the time and event type.
[0049] In the replay/reconstruction, the event types and times can
be listed. The time the event was made can be jumped to (offset by
a defined amount, e.g., 5 seconds before the event was made) and
the replay (video and/or head-down) played from that point.
[0050] The removable memory module RMM operates as a conventional
storage, with files stored within folders. Usually the removable
memory module RMM is removed/replaced for each flight.
[0051] In a preferred implementation there are 6 folders on the
removable memory module RMM:
[0052] Channel1
Within Channel1 are sub-folders that are created at the start of
each recording session (power-up). These sub-folders then hold the
video recording files for that recording session.
[0053] ENet
Within ENet are the Ethernet head-down recording files and log
files for all the recording sessions.
[0054] Events
Within Events is a file for each recording session. Each file
contains any event data recorded for that session.
[0055] Logs
Within Logs is a file for each recording session; each file
contains log information for the video recording of that
session.
[0056] Mission
The Mission folder is relevant to data upload.
[0057] MAP (may be renamed according to the ground planning and
mission computer MC configurations).
The MAP folder is relevant to data upload.
Mission Debriefing System
[0058] The mission debriefing system MDS is designed to facilitate
training by assisting the instructor to reinforce key learning
points from the training sortie. It also provides a reliable
indication of student performance on solo sorties.
[0059] In the preferred implementation, the mission debriefing
system MDS reads the Channel 1, ENet and Events folder of the
removable memory module RMM to retrieve information as described
above.
[0060] Means for receiving said removable memory module RMM are
provided within the mission debriefing system MDS, such as a memory
card slot or suitable connectors.
[0061] The video information is replayed to give a combined head-up
display HUD/outside world picture. This information cannot be
stored solely in instrument data ID due to the inclusion of the
outside world picture that cannot faithfully be reproduced.
[0062] The mission debriefing system MDS displays/regenerates for
example the following onboard instruments based on instrument data
ID:
[0063] Up-Front Control Panel (UFCP);
[0064] Left Multi Function Display (LMFD);
[0065] Primary Flight Display (PFD); and
[0066] Right Multi Function Display (RMFD).
[0067] Mission debriefing system MDS regenerates onboard
instruments of the aircraft as per the instrument data ID recorded
on the removable memory module RMM during the mission. The mission
debriefing system MDS allows the user to regenerate any recorded
multi-function display MFD page even if it was not actually
selected for display during the mission (i.e. selected by the pilot
during flight) as all instrumentation is recorded regardless of
display selected.
[0068] These additional displays are available at very little
overhead compared to recording the additional 20-30 video streams
that would traditionally be required under such a debriefing
system.
[0069] The Events information is used to highlight within the
replay/reconstruction where certain events occurred. Events of
interest to a debrief scenario may then be used to quickly navigate
through the mission.
[0070] In a further embodiment of the present invention, the
mission debriefing system MDS is connectable to said mission data
recorder MDR for retrieving said recorded instrument data ID and
subsequently reproduce the onboard instruments of the aircraft
based on instrument data ID retrieved from the mission data
recorder MDR, said reproduction being performed within the aircraft
using the onboard instruments of the aircraft. This has the
advantage that since the reconstruction is performed within the
aircraft, the environment thus reconstructed will be a true
reconstruction of the environment during flight.
[0071] In an even further embodiment of the present invention, the
mission debriefing system MDS is connectable to a mission data
recorder MDR for retrieving said recorded instrument data ID and
subsequently reproduce the onboard instruments of the aircraft
based on instrument data ID retrieved from the mission data
recorder MDR, said reproduction being performed within a simulator
comprising a mission computer MC corresponding to said simulator
replicating the onboard instruments of the aircraft. This has the
advantage that since the reconstruction is performed within a
simulator replicating the aircraft, the environment thus
reconstructed will be a true reconstruction of the environment
during flight without occupying an aircraft.
[0072] It will be understood that many variations could be adopted
based on the specific structure hereinbefore described without
departing from the scope of the invention as defined in the
following claims.
REFERENCE LIST
TABLE-US-00001 [0073] mission debriefing system MDS operational
flight program OFP mission data recorder MDR removable memory
module RMM mission computer MC audio management unit AMU instrument
data ID multi-function display MFD primary flight display PFD
head-up display HUD head-up display repeater HUDR recording and
replay system 100 mission bus 11
* * * * *