Study guide
12.3 Data Loading, Integrity Verification and Unapproved Changes
EASA Part-66 Module 05 — Digital Techniques / Electronic Instrument Systems Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Numbering Systems
1.1 Numbering Systems: Decimal, Binary, Octal and Hexadecimal 1.2 Binary Arithmetic and Signed Number Representation 1.3 Binary Coded Decimal, Gray Code and Alphanumeric Codes
2 Chapter 2: Data Conversion
2.1 Analogue and Digital Signals, Sampling and Quantisation 2.2 Digital-to-Analogue Converters 2.3 Analogue-to-Digital Converters
3 Chapter 3: ARINC 429 Data Buses
3.1 ARINC 429 Specification, Physical Layer and Topology 3.2 ARINC 429 32-Bit Word Architecture 3.3 ARINC 429 Transmission, Timing and Troubleshooting
4 Chapter 4: Advanced Avionics Data Buses and Aircraft Ethernet
4.1 ARINC 629 Digital Autonomous Terminal Access 4.2 MIL-STD-1553B Military Avionics Data Bus 4.3 AFDX / ARINC 664 Part 7 Avionics Full-Duplex Switched Ethernet
5 Chapter 5: Combinational Logic Gates and Boolean Algebra
5.1 Basic Logic Gates, Truth Tables and Logic Levels 5.2 Boolean Algebra, De Morgan Theorems and Logic Simplification 5.3 Universal Gates and Aircraft Combinational Applications
6 Chapter 6: Sequential Logic, Registers and Logic Diagrams
6.1 Bistable Multivibrators: SR, JK, D and T Flip-Flops 6.2 Shift Registers and Data Storage Elements 6.3 Asynchronous and Synchronous Counters and Logic-Diagram Interpretation
7 Chapter 7: Computer Structure and Microprocessors
7.1 Computer Architecture, Terminology and the Bus System 7.2 Semiconductor Memory Technologies 7.3 Microprocessor Operation, Instruction Cycles and I/O
8 Chapter 8: Integrated Circuits, Multiplexing and Integrated Modular Avionics
8.1 Integrated Circuit Technology, Encoders, Decoders and Scale of Integration 8.2 Multiplexing and Demultiplexing Techniques 8.3 Remote Data Concentrators and Integrated Modular Avionics
9 Chapter 9: Fibre Optics in Aviation
9.1 Physics of Light Transmission and Optical Fibres 9.2 Fibre Cable Types, Signal Degradation and Optical Components 9.3 Fibre Optic Maintenance, Termination, Splicing and Inspection
10 Chapter 10: Electronic Displays and Flight Instrument Layout
10.1 Display Technologies: CRT, LED and LCD 10.2 Electronic Flight Instrument System Architecture 10.3 Cockpit Symbology, Colour Standards and Display Reversion
11 Chapter 11: Electrostatic Sensitive Devices
11.1 Physics of Electrostatic Charge and Device Susceptibility 11.2 ESDS Damage Mechanisms: Catastrophic versus Latent Failures 11.3 ESDS Handling, Storage, Packaging and Workshop Procedures
12 Chapter 12: Software Management Control and Airworthiness
12.1 Aviation Software Classification and RTCA DO-178C / EUROCAE ED-12C 12.2 Software Configuration Management and Part Numbering 12.3 Data Loading, Integrity Verification and Unapproved Changes
13 Chapter 13: Electromagnetic Environment
13.1 Electromagnetic Interference and Compatibility 13.2 High Intensity Radiated Fields and RF Hazards 13.3 Lightning Protection, Bonding and Static Dischargers
14 Chapter 14: Engine Indication, Warning and Monitoring Systems
14.1 Airbus ECAM — Electronic Centralised Aircraft Monitoring 14.2 Boeing EICAS — Engine Indicating and Crew Alerting System 14.3 Comparison, Failure Reversion and Sensor Interfacing
15 Chapter 15: Flight Management, Navigation and Surveillance Systems
15.1 Flight Management System and Control Display Unit 15.2 Inertial Reference, AHRS/ADIRU Context and GPS 15.3 Traffic Collision Avoidance and Terrain Awareness
16 Chapter 16: Fly-By-Wire, BITE, ACARS, Cabin and Information Systems
16.1 Fly-By-Wire Flight Control 16.2 Built-In Test Equipment and Central Maintenance Computers 16.3 ACARS, Cabin Systems and Information Systems
12.3 Data Loading, Integrity Verification and Unapproved Changes
Key Takeaways Explain This Topic AI
Field-loadable software may be loaded only from approved media using the AMM procedure, typically via ARINC 615 or ARINC 615A data loaders.
CRC, checksums and, where the design uses them, digital signatures are typical integrity tools that detect corruption or truncation; they do not by themselves prove correct effectivity or part number.
Post-load verification of the resident software part number and the load report is part of the airworthiness decision, not an optional extra after a 100% progress bar.
A wrong navigation or terrain database, or a wrong flight-control-law load, can contribute to catastrophic outcomes such as controlled flight into terrain or loss of control.
Unapproved changes include unofficial copies, expired cycles, laptop edits and skipped inspections, not only obvious rewriting of source code.
Last updated: September 2026
12.3 Data Loading, Integrity Verification and Unapproved Changes
The pre-12 June 2024 detailed description for topic 5.13 closed on the possible catastrophic effects of unapproved changes to software programmes . The current Appendix I retains the broad Software management control heading and levels without that detailed sentence. This section is the practical half: how approved data loading is meant to keep the resident image identical to the released LSAP, which integrity tools are typically used, and why a wrong database or a wrong control-law load can be a catastrophic airworthiness event. The worked cases below are hypothetical maintenance scenarios used for teaching. They are not reconstructions of a named accident investigation.
Field-loadable software and approved media
Field-loadable software (FLS) is software that can be loaded into the target without removing the LRU to a workshop bench, using a portable data loader or an onboard loading function. Common industry loader protocols taught in Module 5 are ARINC 615 (often a portable data loader with storage media) and ARINC 615A (Ethernet-based loading). Older fleets used floppy discs; current fleets use optical discs, approved solid-state media or airline electronic-distribution systems that still deliver a controlled file set .
Approved media means the disc, cartridge, USB device or electronic package that the type-design holder or the operator’s approved procedure specifies. Approval covers:
- The file content (the LSAP, not a look-alike)
- The physical or electronic carrier (some USB devices are not authorised even if they electrically fit)
- Labelling, revision and quarantine in stores
- Access control so that workshop personal computers cannot silently add files
An unofficial copy made “so we have a spare in the toolbox” is unapproved media, even if the original was genuine. Copies pick up corruption, the wrong cycle, or extra files. Electronic files downloaded from an unofficial internet source are likewise unapproved. Password protection on a loader is a control against casual use; it is not permission to load unofficial content once the password is known.
Integrity verification: CRC, checksums and identity
A loader that reports “complete” has only reported that bits were written. Airworthiness needs evidence that those bits are the intended bits. Typical integrity tools specified in AMM tasks and loader design include:
- Check What it typically detects What it does not prove
- Checksum Simple corruption or truncation of a file That the file is the correct part number for this aeroplane
Cyclic redundancy check (CRC) A wider class of bit errors in the load image or media That the software is effectivity-approved or still DAL-compliant as a new design
Digital signature (where the design uses it) Tampering after the design organisation signed the image That the technician selected the correct signed image for this MSN
Target hardware identification Load into the wrong LRU type That every channel of a multi-channel system was loaded
Post-load resident P/N read-back Wrong or incomplete software identity left in the target Nothing if the technician does not actually look at the status page
Load report / configuration print Recorded evidence for the technical log Airworthiness if the report is filed without being compared with IPC effectivity
Warning
A CRC that passes means the image is internally consistent with the CRC that travelled with it. If the whole unofficial file was copied, the CRC may still pass. Integrity tools complement, and do not replace, part-number and effectivity control.
Interrupted loads, power loss, pulling the media early, or concurrent maintenance on the same bus can leave a partial image . AMM procedures specify recovery: do not dispatch; reload from approved media; follow the fault-isolation task if the target will not accept the load. Dual-channel systems may require both channels to be loaded and then compared. Independent inspection, where the task or the organisation’s procedure requires it, is another integrity layer: a second person confirms identity and result, not merely that a progress bar reached 100%.
Hypothetical scenario 1 — wrong navigation or terrain database
A technician is handed media labelled with a database cycle date that looks current. The files are loaded into a flight-management or terrain-awareness computer. After load, the CRC passes and BITE is green. Later it is found that the database was compiled for a different aeroplane type (different procedure set, different magnetic-variation model, or different terrain and obstacle coverage).
Possible effects in this hypothetical case:
The crew is presented with incorrect procedures, waypoints, or terrain or obstacle cues .
Map shifting or missing obstacles reduce the safety margin of a night or instrument-meteorological-conditions arrival.
In the worst credible case, misleading terrain-awareness or navigation data can contribute to controlled flight into terrain , which is a catastrophic failure condition.
The DAL of the operational programme does not rescue a wrong data load . Operational databases are controlled software/data loads in maintenance practice: unapproved or incorrect data can change the aircraft’s functional behaviour even when the executable code is unchanged. Cycle control (the database effective date) is part of the same restriction: an expired cycle can omit new obstacles, temporary procedures or magnetic-variation updates.
Hypothetical scenario 2 — wrong flight-control law load
A dual-channel fly-by-wire computer accepts field-loadable operational software. Media for a different weight variant or engine standard physically fits the loader. The technician loads Channel A. Channel B still contains the previous authorised standard. Comparator monitors may trip — which is a detectable failure — or, if the mismatch is not covered by monitors for that particular difference, the aircraft could leave the hangar with asymmetric or unintended control laws .
Possible effects in this hypothetical case:
Incorrect stick-to-surface gearing, protection envelopes or limiter schedules.
A channel-fail reversion to a law that was never the approved law for this aeroplane.
In the catastrophic case, loss of control because the software that satisfied DAL A objectives is no longer the software that is flying the aeroplane.
The correct hangar behaviour is: confirm IPC effectivity and service-bulletin status , load all required channels to the same authorised P/N , verify resident P/N and CRC or signature results , and do not release if any channel disagrees.
Unapproved changes: the syllabus catastrophe
Unapproved changes are not limited to rewriting source code. In maintenance they usually look ordinary:
- Using another aircraft’s media because “it is the same fleet”
- Loading an expired navigation-database cycle to get the aircraft out on time
- Editing a configuration file on a laptop to “clear a nuisance fault”
- Skipping independent inspection on a critical software load
- Accepting a 100% progress bar without reading the software status page
Each of those actions can place catastrophic-level functions (flight path, thrust, terrain awareness, stall protection) under software that has not been shown to meet its DAL. The continuing-airworthiness regulations then say the aircraft is not airworthy. The human and operational consequence can be loss of the aeroplane.
B1/B2 Level 2 application: refuse unofficial media, follow AMM integrity and identity steps, record the LSAP, and report any suspected unauthorised software as an occurrence. B3 Level 1 : know that unapproved software changes can be catastrophic and must be prevented. The classification framework in section 12.1 and the part-number discipline in section 12.2 exist so that a loader session cannot silently defeat DAL A–E.