Part 29 rotorcraft
Part 29 certification basis mapping for surveillance equipment
This support walks a surveillance installation's evidence against the Part 29 certification basis so a supplier or modifier knows what still has to be shown before submittal. It is used by equipment suppliers and aircraft modifiers building a transport-category rotorcraft package around a transponder, ADS-B unit, or antenna. The work reads the transponder performance data, ADS-B message integrity substantiation, antenna siting analysis, and installation assumptions against the applicable Part 29 rules and the accepted means of compliance for each. You get a standards map that ties each rule to its evidence, a gap list ranked for closure, and a sequence for answering finding requests.
When this review is needed
- A transponder or ADS-B installation on a transport-category rotorcraft is heading to submittal and no one has mapped its evidence to the applicable Part 29 rules.
- An authority has issued finding requests on surveillance substantiation and the responses have to trace back to specific paragraphs.
- Antenna siting on a rotorcraft airframe raises interference and pattern questions the evidence does not yet answer.
- A supplier is reusing fixed-wing surveillance data on a rotorcraft and needs to know where the Part 29 basis diverges.
The problem
Surveillance evidence for a rotorcraft tends to arrive as a stack of vendor test reports and a fixed-wing analysis that was never re-anchored to Part 29. The transponder and ADS-B data may be sound on their own, but no one has drawn the line from each Part 29 paragraph to the report that satisfies it. When the authority asks how the installation meets a specific rule, the team hunts through the package rather than pointing to a mapped line.
What gets reviewed
- Applicable Part 29 paragraphs for the surveillance function identified and listed as the certification basis
- Transponder and ADS-B performance data matched to the accepted means of compliance for each rule
- Antenna siting, pattern, and interference analysis checked against the installation the rotorcraft actually carries
- Environmental qualification per DO-160G categories relevant to the mounting location
- Software assurance evidence at the DO-178C level claimed for the surveillance function
- Installation assumptions reconciled with the rotorcraft's electrical and structural interfaces
What gets validated
- Each cited Part 29 paragraph maps to a specific report, drawing, or analysis rather than a general claim of compliance
- ADS-B message integrity substantiation covers the position source and latency the installation actually uses
- Antenna pattern data reflects the fitted location on the airframe, not a generic mounting
- DO-160G environmental categories match the vibration and temperature environment of the rotorcraft zone
- The software level claimed for the surveillance function is supported by DO-178C lifecycle data at that assurance level
Evidence normally required
- The proposed Part 29 certification basis or the issue paper defining it
- Transponder and ADS-B vendor test reports and MOPS compliance statements
- Antenna installation drawings with siting and pattern analysis
- DO-160G environmental qualification reports for the surveillance units
- The installation description covering electrical load, wiring, and structural attachment
Common discrepancies
- A Part 29 paragraph listed in the basis with no report cited against it
- Antenna pattern data carried over from a fixed-wing installation that does not represent the rotorcraft mounting
- ADS-B integrity evidence that assumes a position source the installation does not use
- Environmental qualification tested to a category below the rotorcraft zone's actual vibration environment
What is at stake
A surveillance package that cannot show the rule-to-evidence link stalls at the first substantive finding, and each round of clarification pushes the authorization date. If antenna interference or ADS-B integrity is queried late, the fix can mean re-testing on the airframe, which is far more expensive than confirming the coverage before the package leaves the building.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Define the surveillance basis
List the Part 29 paragraphs that apply to the transponder, ADS-B, and antenna function and confirm them against any issue paper.
Match evidence to rules
Tie each vendor report, analysis, and qualification result to the paragraph it is meant to satisfy.
Test the installation assumptions
Check antenna siting, environmental category, and position source against the rotorcraft the equipment is fitted to.
Rank and sequence the gaps
Order the open items by cost and by whether they need airframe access, then set the closure order.
What the buyer receives
- A standards map linking each applicable Part 29 rule to the evidence that satisfies it
- A ranked gap list naming the missing or mismatched surveillance evidence
- A closure sequence that orders the gaps by cost and by dependency on airframe access
Who uses the output
- Certification engineers assembling the surveillance submittal for the authority
- Suppliers deciding what surveillance test or analysis still has to be run
- Program leads sequencing gap closure against the authorization timeline
How the work fits into the transaction or program
This work sits between vendor qualification and the formal Part 29 submittal. It takes the surveillance test data the supplier already holds and anchors it to the certification basis, so the package that reaches the authority reads as a mapped set of findings rather than a folder of reports. The gap list it produces feeds the test and analysis plan for whatever is still open.
Start with a single asset
Confirm requirements trace through verification.
Jurisdiction-specific considerations
FAA and EASA can define the surveillance certification basis for a transport-category rotorcraft differently, and ADS-B mandate rules diverge between the two systems. The mapping notes where a paragraph accepted under one authority needs separate substantiation under the other so a dual submittal does not assume equivalence that is not there.
Regulatory limits
The mapping shows where surveillance evidence supports the Part 29 basis and where it falls short. It does not issue a compliance finding, approve the installation, or make an airworthiness determination. Those decisions rest with the authority and its designees.
What this review does not cover
- Running the transponder, ADS-B, or antenna testing itself
- Writing or approving the surveillance software or its DO-178C data
- Issuing any Part 29 compliance finding or installation approval
Specific to this review
- Rotorcraft main-rotor modulation can degrade a transponder or ADS-B antenna pattern in ways a fixed-wing siting analysis never modeled, so antenna evidence is checked against the actual airframe.
- The vibration environment in a rotorcraft avionics bay often exceeds the DO-160G category a supplier qualified to for fixed-wing, which is a frequent source of a late re-test.
- ADS-B integrity substantiation stands or falls on the position source, so a package that maps every antenna rule but leaves the source assumption implicit is still incomplete.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.
SAE International. Development assurance process at aircraft and system level, including requirements capture and validation.
Frequently asked questions
Can surveillance data qualified for a fixed-wing installation be reused on a rotorcraft?
Some of it can, but the antenna pattern, environmental category, and installation effects usually have to be re-examined for the rotorcraft airframe. The mapping identifies which fixed-wing evidence carries across the Part 29 basis and which has to be re-substantiated.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.