faa-8110-49
FAA Airborne Software and AEH Approval Guidance
Source: Federal Aviation Administration. Adapted from the sibling 2026-09-27 prototype build and re-checked against the 2026-10-12 FAA source pin, the four documents vetted in LICENSE as rows S1-S4 | Licence: Public Domain (US Government work, 17 U.S.C. 105) | Chapters: 13
When to use
Prerequisites: none, plain Markdown; no MCP server, API key, or licence tier needed at runtime.
Use this skill for questions about how the FAA reviews and approves the software and airborne electronic hardware sides of a certification project: how a software review is planned and what its objectives are, how much FAA involvement a project should expect and how the worksheets score it, what a software conformity inspection covers and when Form 8120-10 is used, what AC 20-115D recognizes and how DO-178B-era processes carry forward, and what AC 20-152A requires for custom devices, COTS IP, COTS devices, and circuit board assemblies. The pack answers with the FAA's own frameworks, cited by chapter and source row.
How to Use This Skill
- Without arguments: read the Core Frameworks below for the review process, the level-of-involvement logic, conformity inspection, and the recognition chain from FAA guidance to the RTCA/EUROCAE standards.
- With a topic: use the Topic Index to find the chapter, then ask directly (e.g. "which LOI worksheet applies at software level B", "does this COTS IP block need AC 20-152A objectives").
- With a chapter: ch01 orientation (which document answers which question); ch02-ch04 the FAA review, involvement, and conformity machinery of Order 8110.49A; ch05-ch06 AC 20-115D software development assurance and legacy software; ch07-ch10 AC 20-152A airborne electronic hardware.
Supporting files: glossary.md, cheatsheet.md.