Product Loads revisited; introducing ARINC 448

Six years ago we released a blog, “Product Loads – the good, the bad and the ugly” in which we highlighted the risks and challenges of software product loads in FSTDs; at that time those risks and challenges were considered theoretical by some. Fast forward to this October where at the Flight Simulation Engineering and Maintenance Conference (FSEMC (2026)) there were several questions that echoed the issues we raised six years previously in 2020. Given that ARINC report 448 (Guidance for Software Product Load Release for Flight Simulation Training Devices (FSTD)) has now been published (September 2026) which provides a framework to address these issues, we thought it a good time to take another look at this topic.

Remind me, what do we mean by a product load?

This is where the Training Device Manufacturers (TDMs) maintain a single load for a given aircraft type/FSTD family type and deploy it to multiple operators’ FSTDs. In some ways product loads are a sign of the industry catching up with practices we are all familiar with. Today, it would be unthinkable for a software supplier to modify and recompile an operating system for each individual customer.

And that’s good because of?

Operators benefit from receiving tested corrections, improved standardisation and greater consistency across devices. For TDMs, maintaining a common software baseline reduces support complexity and allows defects to be corrected once rather than across multiple customer-specific variants.

So everything is rosy in the garden?

Not quite. In our 2020 blog, we highlighted a few areas we thought would be problematic for operators, and recent operator feedback at the FSEMC suggests these concerns were well founded. During the conference, operators discussed issues such as the effort required to test each load, in particular re-running QTGs. Added to this were problems with incomplete release notes and instability. As an example, take a seemingly minor software update affecting aerodynamics, avionics, or instructor station functionality that may require significant operator effort to assess, test, document and, where applicable, revalidate by re-running QTGs.

As one operator recently intimated to us, they never implement a new product load immediately upon release; they always let others find the bugs first. For us, this was a very real illustration of the fact that there are problems that need addressing.

Enter ARINC Report 448.

In July 2022, the FSEMC Steering Committee established the Software Load Release (SLR) Working Group composed of members drawn from operators, aircraft manufacturers, and Training Device Manufacturers (TDMs) to address these concerns. This working group’s remit was to produce a document to aid the TDMs and aircraft manufacturers in providing standardised release notes and information. As stated above, this document has now been published and is available from the ARINC store*.

For the first time, operators have industry-agreed guidance describing the information they should expect from software suppliers and the processes they should apply when evaluating new product loads.

The document itself is split into three main sections. The first section serves to provide users with a common terminology with which to address the issues.

The second section is guidance for the entities providing the software product releases and outlines what an operator should expect from the supplier with each load, namely:

  • Reason for Changes: defines the reasons for changes that trigger a new release.
  • Scope of Software Product Load Release: defines the scope of the changes, including why it was released.
  • Details of Software Product Changes: allows the receiver to obtain a clear understanding of the changes, necessary for the operator’s configuration control.
  • Testing of Software Product Load Release: an indication of the level of testing performed as changes are introduced.
  • Deliverables to SPLR Receivers.

The third section is aimed at device operators (referred to as “SPLR Receivers” in the report). This section gives practical advice to the operators on how to install and test the new loads, or indeed whether to install them or not. We’d recommend that all operators who have devices with product loads read this section carefully and incorporate the guidelines into their engineering and maintenance procedures.

So ARINC 448 solves all the problems?

Sadly, a report or standard, however well drafted, can’t magic away all the issues. Like all the excellent standards published by ARINC, and in our sector specifically the ones published by the FSEMC, they are not mandatory. Any standard is only as good as how companies follow it. That said, if the TDMs and aircraft manufacturers incorporate the guidelines of ARINC 448 into their load development and deployment processes, it will be a major step forward.

Whilst ARINC 448 will not eliminate software load risks, it does provide operators and suppliers with a common framework for managing them. Organisations that embed its principles into procurement, configuration management and maintenance processes are likely to realise the greatest benefits

One final thought on ARINC 448: this report, like all the other FSEMC reports, was developed by industry representatives on a voluntary basis. Anyone who has been involved in an ARINC working group will tell you that they involve a lot of effort, often in their own time. We’d encourage organisations to get involved in future working groups.

How can SIM OPS help?

Whether you’re introducing product loads for the first time, reviewing your engineering procedures, or assessing compliance with ARINC 448, SIM OPS can provide practical support based on experience as both software suppliers and operators. We can assist with process development, change assessment, testing strategies and load acceptance activities, contact us at info@sim-ops.com .

* ARINC 448 is available from the ARINC store at the link below and is free of charge to FSEMC members.

https://aviation-ia.sae-itc.com/standards/arinc448-448-guidance-software-product-load-release-flight-simulation-training-devices-fstd