BMS F-16C/D 4.34, Flight Manual

Page: 199 / 234

T.O. BMS1F-16CM-1 BMS 4.34 Change 2.00
BMS 4.34 Dash 1
© Red Dog 2012-2019
Page: 199
3.4.1.1. MFL management at ramp start
It is normal to have faults reported during the ramp start sequence. As the systems come online
multiple faults will be reported until all systems are nominal. These faults will clear by themselves as
the systems come online, or as the pilot powers up and checks other systems.
Once the aircraft is ready to taxi the pilot clears the MFL by pressing OSB 3 on the TEST page to
reset the MFL to a clean state, which will help tracking in flight faults better if they occur.
Clearing the MFL initiates a survey of all current malfunctions and detects and reports persistent faults
occurring in the system. If a fault is still present after MFL clearing, it will be displayed again on the
TEST page. If the faulty system has been shut down, the system cannot report the fault and the TEST
page will remain void of that fault report.
After take-off once the aircraft reaches 120 Kts with gear up the pseudo fault TOF will be created to
record the take-off time. Please note, if the MFL is cleared in flight the TOF pseudo fault will be
replaced by the mission time at MFL clearing.
If the flight happens without any malfunctions the next pseudo fault that will be generated will be the
landing fault (LAND) that will record the landing time when the airspeed falls below 80 kts with the
gear down.
3.4.1.2. DTC fault recording
All MFL faults can be reviewed after the flight by analysing the DTC_last_flight_faults file located in the
\User\Logs folder.
This file will be overwritten every time you enter 3D, so is only available before your next flight.
The file has the following structure:
[ 0:00] [ 0:00] [SET] [4]
[FLCS BIT PASS ] [-1]
[ 0:24] [ 0:24] [SET] [2] [TOF ] [4]
[ 1:21] [ 1:21] [SET] [123] [DMUX BUS FAIL] [3]
[Total mission time]
[Time from last MFL clear] [Action] [ID] [Fault] [Test Number]
•
Total mission time indicates at which time into the mission the fault occurred.
•
Time from last MFL clear will indicate the time since the
MFL was cleared (if the pilot didn’t
clear the MFL with OSB 3, it will be equal to the first time block).
•
Action can be SET or CLEAR. SET refers to a fault occurring. CLEAR refers to a fault being
cleared (by pilot action most of the time).
•
ID is a number internal to BMS and irrelevant for the user.
•
Fault lists the system where the malfunction appeared (PFL).
•
The Test number corresponds to the second column on the MFL test page and may provide
further information about which subsystem failed. See 3.4.3 for a list of test numbers.