Avionics Upgrade Planning: Scope, Approval, Integration and Acceptance

An avionics quote is not useful because it contains the newest display or navigator. It is useful when it defines a complete, approvable installation for a specific aircraft and leaves the owner with a panel that works as a system.

That changes the first question from "Which box should I buy?" to "What operational problem must this installation solve, and what else must change for it to solve that problem?"

Write the mission requirement before choosing equipment

Describe the flights and failure cases the panel must support. A short requirements sheet might cover:

• VFR or IFR operations and the approach capability actually required;
• navigation, communication, surveillance and weather inputs;
• autopilot coupling and mode-annunciation requirements;
• electrical-load, standby-power and reversion needs;
• display visibility, control placement and workload;
• database and software-update responsibilities; and
• which existing instruments, antennas and wiring will remain.

Separate required outcomes from optional features. This gives each shop the same problem to quote and reduces the chance that two very different scopes are compared as if they were equivalent.

Confirm eligibility for the exact aircraft

A product approval or model name does not, by itself, establish that an installation is approved in every aircraft. Before accepting a quote, identify:

1. the aircraft make, model and serial number;
2. the applicable supplemental type certificate and approved model-list eligibility, when used;
3. any installation limitations or required companion equipment;
4. the approved data the installer intends to use; and
5. whether a field approval or another approval path is required for any part of the alteration.

The FAA's STC installation guidance also distinguishes permission to use the design data from the approval of the physical installation. The installer still has to determine that the alteration is compatible with the aircraft's existing configuration.

Map every interface, not just the headline units

Build an interface map before the panel is opened. It should show the data and control paths between the navigator, displays, radios, transponder, audio panel, autopilot, sensors, antennas and electrical system.

For each retained component, record:

Interface question	What the quote should resolve
Data compatibility	Required protocol, adapter, converter or software level
Autopilot integration	Available lateral and vertical modes, annunciation and disconnect behaviour
Audio and radio path	Switching, monitoring, sidetone and alert routing
Position source	Which unit supplies position to each dependent system
Electrical load	Normal, abnormal and standby-power assumptions
Antennas and wiring	Reuse, replacement, inspection and routing scope
Removed equipment	Panel work, weight-and-balance change and unused wiring treatment

This is where apparently similar quotes often diverge. One may include a required adapter, antenna, circuit protection, panel fabrication and configuration work while another leaves those items as later variations.

Normalize the quotes

Ask each shop to separate equipment, labour and contingencies, then compare the same fields:

• exact part numbers and included accessories;
• removal and retained-equipment scope;
• panel, wiring, antenna and electrical work;
• approval basis and paperwork;
• configuration, database and software work;
• ground and flight-test scope;
• pilot familiarisation or training;
• warranty responsibility for equipment and installation;
• exclusions, shop-supply charges and variation rates; and
• expected aircraft downtime and scheduling assumptions.

A low headline number can be a narrower scope rather than a lower price for the same outcome. Do not add generic resale percentages to the calculation. Treat sale value as aircraft- and market-specific, and make the operating requirement carry the decision.

Close the approval and records loop

Agree on the expected records before work begins. Depending on the alteration, the handover package may include approved data or STC documents, installation instructions, an FAA Form 337, weight-and-balance and equipment-list amendments, logbook entries, flight-manual supplements and instructions for continued airworthiness.

FAA Form 337 is used for major repairs and major alterations. The FAA's field-approval process addresses alterations for which approved data are not otherwise available. AC 43.13-2B can provide acceptable alteration methods only within its stated purpose and limitations; it is not a blanket substitute for the correct approval basis.

The owner should be able to identify what was installed, under what authority, which limitations apply and what continuing actions are now required.

Accept the installed system, not the invoice

Before return to normal use, compare the completed aircraft with the agreed interface map and approved documentation. The responsible installer determines and records airworthiness; the owner or operator also needs a practical handover.

That handover should cover:

• configuration and software versions;
• normal and abnormal power-up behaviour;
• source selection and reversion;
• navigation, communication and surveillance checks;
• autopilot modes and disconnects, when installed;
• alerts, annunciations and database status;
• limitations in the applicable flight-manual supplements; and
• defects, deferred items and warranty contacts.

Use the approved manuals and appropriate instruction before relying on unfamiliar automation in instrument conditions. An installation is complete when its approval, integration, records and operating behaviour all agree.

Sources

• FAA: Supplemental Type Certificates
• FAA: Installing an STC
• FAA: Field Approval Process
• FAA: Form 337, Major Repair and Alteration
• FAA: AC 43.13-2B, Acceptable Methods, Techniques, and Practices - Aircraft Alterations
• Garmin: Avionics interface information