ARINC Industry Activities
"Together We Set the Standard"
Top Banner





ARINC Standards

Upcoming Events


Creating Value for Aviation Through Collaboration Image

Software Distribution and Loading (SDL) Subcommittee

Last Update: June 9, 2017

Co-Chairman - Rod Gates, American Airlines
Co-Chairman - Ted Patmore, Delta Air Lines

APIM 13-007: Standards for Shop Loading LRUs (pdf, 194K)
APIM 16-002: Common Standards for Software Data Loading and Data Management (pdf, 131K)
APIM 16-015: Ground System Definition for eEnabled Aircraft (pdf, 96K)

Goal: The objective is to develop standards for software data loading. This includes development of a high-speed data loader with high-density storage media. Standards for file format, media type, part numbering and terminology will be developed in a way that can be used for various data loading devices.

Scope: This subcommittee prepares documents for the interfaces between the software data loader and the target hardware. It also prepares standard formats for loadable software airplane parts so that all of the requirements of configuration management of LSAPs may be accomplished.

Benefit: The work of this subcommittee allows common tools to be used for the transfer of LSAPs from the airline to the target hardware, whether it is installed onboard the aircraft or on the test bench.

Go to the Manufacturer's Code Assignment Information

Current Drafts:

Draft 1 of ARINC Project Paper 645: Common Standard for Software Distribution and Loading

Circulation Prior to Adoption Action
Draft 2 of ARINC Project Paper 849: Data Loading Specification for Aircraft Components

Next Meeting Announcement:

Working Papers:

XML Support Files:

Last Meeting Report:

Software Distribution and Loading (SDL) Subcommittee
March 1-3, 2017, in Portland, Oregon

Associated Technical Application Bulletins:

Cyclic Redundancy Codes (CRC) Test Cases
  Staff: Scott L. Smith
Reference: 13-047/ABN-41
Effective: March 15, 2013 - Indefinite

ARINC Report 665, Loadable Software Standards, Section 4.0 defines the use of Cyclic Redundancy Codes (CRC), also known as Cyclic Redundancy Checks.

ARINC Report 665-3, Section 4.2.9, CRC Examples refers to Appendix K, which provides guidance on the calculation of loadable software part CRCs. Appendix K provides an orientation to, instructions for and examples of Loadable Software CRCs and references sample files and corresponding CRCs provided in electronic code formats in this Technical Application Bulletin (TAB).

Submit Feedback for this bulletin

Staff Contact

Scott Smith