On July 7, 2026, the FAA issued AC 25.1302-2B and moved a specific certification requirement to the center of the Fly-by-wire approval path: cross-validation between flight control software under DO-178C and hardware logic under DO-254. For Chinese OEMs and tier-two suppliers targeting FAA approval, this matters because the rule change ties market access more directly to how certification evidence is prepared, packaged, and submitted before entering the TC or STC review stage. The immediate pressure point is not only engineering compliance, but also documentation readiness, supplier coordination, and export program timing for eVTOL, regional aircraft, and special-mission aircraft flight control systems heading to the U.S. market.

What the FAA Changed on July 7

The confirmed facts are limited but clear. The FAA released AC 25.1302-2B on July 7, 2026. In that guidance, cross-validation between flight control software governed by DO-178C and hardware logic governed by DO-254 is brought into the core certification path for Fly-by-wire systems. The new requirement means Chinese aircraft manufacturers and tier-two suppliers must submit a combined validation evidence package to the FAA. Without that joint package, they cannot proceed into the TC or STC certification stage. The change directly affects the U.S. airworthiness route for flight control systems used in eVTOL aircraft, regional aircraft, and special aircraft intended for export to the United States.

Where the Compliance Burden Moves in Practice

Aircraft programs facing FAA entry gates

From an industry perspective, the most immediate impact falls on OEM-led aircraft programs that rely on Fly-by-wire architectures for FAA-facing certification. The reason is straightforward: the approval path now places joint software and hardware validation evidence ahead of TC or STC progression. In practical terms, affected programs need to pay closer attention to how certification materials are organized across design, verification, and submission workflows, because incomplete linkage between DO-178C and DO-254 evidence may become a blocking issue before formal review advances.

Tier-two suppliers carrying embedded compliance risk

Tier-two suppliers are also exposed because the requirement does not stop at the aircraft integrator level. Where suppliers provide hardware logic, software-related inputs, or validation records that feed the flight control system, their deliverables may now need to align with a joint evidence package rather than separate compliance tracks. What deserves closer attention is the handoff of technical documents, verification records, and supporting certification material that an OEM may need to assemble for FAA submission.

Certification and testing support functions under tighter document linkage

Certification-related service providers and testing support organizations may see the effect through a narrower documentation interface. Analysis shows that the rule change is not just about passing tests; it also changes the importance of traceable, submission-ready evidence that connects software and hardware validation. The business impact may therefore appear in review preparation, document consistency checks, evidence traceability, and the timing of certification support activities tied to export programs.

Export delivery planning and customer commitments

For export-oriented programs, the rule change may influence delivery planning because access to the FAA certification path is now tied more explicitly to a combined validation package. Observably, this creates a practical link between certification readiness and downstream commercial steps such as customer commitments, procurement sequencing, and delivery schedules. Companies involved in U.S.-bound aircraft platforms should therefore watch for changes in documentation requirements, acceptance criteria, and submission expectations in project execution.

What Companies Should Review Now

Check whether evidence is built as one package or two separate tracks

Analysis shows that companies should first review whether existing compliance work is still being managed in separate software and hardware streams. The new signal from the FAA suggests that a combined evidence package is now a prerequisite for moving into TC or STC review. Where internal teams or suppliers still work in isolated document structures, that may create avoidable submission friction.

Reassess supplier documentation and contract deliverables

What deserves closer attention is whether supplier contracts, procurement specifications, and technical delivery lists already require the validation material an OEM will need for a joint FAA package. If not, companies may need to revisit document expectations, traceability requirements, and acceptance criteria in sourcing and supplier management. This is especially relevant where tier-two suppliers support flight control functions that sit close to certification boundaries.

Watch for execution language in future certification interactions

The input does not provide detailed enforcement mechanics, so it would be premature to describe a settled execution model. Even so, companies should monitor how the new guidance is reflected in certification communications, compliance reviews, and program documentation requests. The practical issue is whether the FAA applies the guidance through consistent evidence expectations across different aircraft programs and certification stages.

Prepare for knock-on effects in timing and export readiness

From an operational standpoint, firms should treat certification packaging, technical documentation, and supplier readiness as part of export execution rather than as a late-stage approval task. Observably, if the joint package becomes a gating item before TC or STC entry, then review cycles, procurement timing, and delivery planning may all come under pressure when evidence is incomplete or not aligned across DO-178C and DO-254 workflows.

Why This Looks Like an Execution Signal, Not Just a Guidance Update

Analysis shows that this development is more significant as a certification access signal than as a routine wording change. The key point is that the requirement is tied to whether a program can enter the TC or STC stage, which gives it direct procedural weight for affected exporters. At the same time, it is more appropriate to understand this as a rule-development point that still requires observation in practice, because the provided information does not describe detailed review criteria, transition arrangements, or program-by-program implementation language.

How the Market Should Read This for Now

A measured reading is that the FAA has raised the importance of integrated certification evidence for Fly-by-wire systems and made that expectation relevant to Chinese OEMs and tier-two suppliers seeking access to the U.S. approval path. The event should not be read as a complete picture of enforcement outcomes, but it should be taken as a concrete compliance signal with possible effects on certification preparation, supplier coordination, and export delivery planning. At this stage, it is more appropriate to understand the change as an implemented requirement with execution details that still warrant close follow-up.

Basis of This Article and What Still Needs Verification

This article is based on the user-provided news title, event date, and event summary. For developments of this type, relevant source categories usually include official regulator notices, certification guidance publications, trade or customs authority information, industry association updates, standards organization materials, and reporting by established industry media. A specific official source link was not provided in the input, so the exact reference path still needs to be verified. Further observation is also needed on detailed implementation language, certification review practice, bid and tender document changes, market feedback, and how affected companies adjust their evidence preparation and supplier coordination.