Supplemental Type Certification
Zero-failure programs where certification, partners, and supply chains must execute against gated evidence.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Certification Outcome Discovery
Align on program objectives, airframe constraints, regulatory history, stakeholders, and measurable success criteria for the STC effort.
Discovery Questions
How this STC must perform for your program
- Tell me in one sentence the primary reason you're pursuing an STC now
- Estimate the top three business outcomes this approval must deliver for your fleet
- Which airframe or fleet context best describes where this modification will be installed
- Who in your leadership will sign off on program success, and who will run day-to-day delivery
- How tight is your target timeline for certificate issuance, and which of these best matches your deadline
- If the program slips, what is the nearest financial or operational consequence your team must avoid
Where your current plan is most likely to surprise you
- Walk me through the last time a certification timeline slipped, what caused it, and what it cost your operation
- Describe any airframe-specific constraints we should assume up front, including inspection access, structural hot spots, or fatigue limits
- Which analyses or tests have you already completed for this modification, and can any be reused
- Who currently holds DER or local regulator relationships for this airframe inside your organization
- Are there design assumptions in your current package that would require redesign if a regulator requests more substantiation
- What single unresolved technical risk would make you stop the program today
When certification problems compound cost and delay
- In the last STC your team ran, which regulator comments forced the biggest redesign, and why were they missed earlier
- List the top points in your process where DER availability or response times create bottlenecks
- Estimate the average number of regulator review cycles you typically experience on similar packages
- How many aircraft or shop hours does each additional review cycle typically consume for your team
- If timeline certainty improved by half, what concrete changes would you make to procurement, production, or commercial terms
- Identify the single cost or schedule threshold that would lead your leadership to pause the project
Regulatory and operational red lines
- Identify any prior FAA or EASA findings on this airframe that directly affect your modification scope
- Describe required access or facility constraints, such as hangar availability, ferry permits, special tooling, or ferry flights
- Name the primary point of contact your team will use for handing over conformity inspections and signing off work packages
- List the internal teams you must commit full-time versus part-time during execution
- Confirm whether your program requires export or import approvals, and who in your organization owns that process
- Should DER assignments be unavailable within your timeline, would you cancel, delay, or seek alternate jurisdiction or scope changes
Who else you are weighing and why
- Why might your team keep working with the current incumbent instead of engaging an outside certification partner
- Share the external firms or internal approaches you have evaluated for similar STC work in the last 18 months
- What would have to be true about your existing approach for you to stay with it rather than change providers
- Has anyone on your engineering or MRO team proposed handling certification entirely internally, and what resource gaps did they identify
- Suppose an incumbent could guarantee regulator engagement and zero rework, would your team still consider external partners
- Rank the reasons you might switch providers from most to least important
Acceptance: the finish line your team needs
- Imagine the regulator issued the certificate tomorrow, what deliverables and documentation would your team require to accept the work
- Tell the acceptance criteria your legal or asset management teams insist on before signing off on an STC
- Define the metrics your team will use to measure in-service success at 6 and 12 months
- Provide the operational or warranty obligations your team requires to include in the acceptance package
- Name the single acceptance requirement, if unmet, that would prevent final payment or formal closeout
Schedule, stakeholders, and the decision moment
- Suppose you had to commit to a go or no-go date today, what internal or external events determine that deadline
- Provide the approvers your team must brief at each milestone, and indicate who holds veto authority
- Compare already allocated budget to your expected full program cost
- Are there procurement or contract clauses your legal team considers non-negotiable
- Would a short exclusivity period in a proposal block you from engaging if schedule and price matched your targets
- When does your team expect to make a final selection of a certification partner
Practical next steps and immediate blockers
- Pinpoint the single onboarding barrier that would stop your team from starting within your target window
- Share the documents or artifacts your team can provide within five business days to accelerate our technical review
- Please indicate the day-to-day contact your team will assign for data access, drawings, and test coordination
- Report any blackout periods in your maintenance schedule or fleet operations that would prevent tests or inspections in the next six months
- Assuming you can supply the requested artifacts and assign a contact this week, will your team sign an engagement to start within 30 days
- Sketch what a successful first 30 days looks like for your team, and name who must be involved to make it happen
-
Technical Working Sessions
Run focused sessions with engineering, DERs, and regulatory liaisons to validate assumptions, surface gaps, and prioritize analyses and tests.
Working Meetings
- Assumption and Technical Baseline Review
- Risk and Analysis Prioritization Workshop
- DER and Regulatory Liaison Alignment
- Test Program and Flight Test Scoping Review
- Procure or plan procurement for identified instrumentation and test support services.
- An evidence matrix is produced that defines submission content by certification gate.
- A clear escalation path for unresolved technical issues is agreed.
- Compile the regulator and DER position notes into a formal position log.
- Publish the evidence matrix and map it to the prioritized analysis plan.
- Record the escalation path and criteria for raising formal regulatory queries.
- Translate analysis requirements into test objectives and points
- A draft test program is produced with defined test points, instrumentation needs, and pass criteria.
- Preliminary schedule windows and critical dependencies are identified and captured for booking actions.
- A short list of mitigation actions for critical dependencies is agreed to prevent schedule slips.
- Publish the draft test program including test points, instrumentation list, and pass criteria.
- Initiate booking requests for targeted test windows and record provisional aircraft availability.
- Confirm engagement assumption and success criteria
- The technical baseline document is agreed and will be the single source of truth for downstream work.
- A prioritized gap list is produced with short descriptions and evidence required to close each gap.
- Regulatory and DER points of contact are captured and their expected level of engagement is noted.
- Publish the agreed technical baseline document including the prioritized gap list.
- Collect and share the missing airframe records and drawings identified in the gap list.
- Confirm DER and regulator contact availability and record the expected evidence each will require.
- Review prioritized gap list and classify required analyses
- A ranked analysis and test list is produced with LOE estimates and regulatory risk ratings for each item.
- The immediate work package for the next 4 to 8 weeks is agreed and ready for resourcing.
- Key dependencies and long-lead items are identified and flagged for scheduling action.
- Publish the prioritized analysis and test plan with LOE and risk ratings.
- Prepare scopes of work and cost estimates for the first-wave analyses.
- Identify and initiate procurement of any long-lead test services or lab time needed.
- Present prioritized analysis plan and evidence assumptions
- A documented record of regulator and DER positions is captured and accepted as the basis for analysis work.
- Review existing airframe data and configuration baseline
- Capture regulator and DER positions on methods and acceptance criteria
- Estimate level of effort and schedule impact per analysis
- Define pass criteria and acceptance thresholds
- Assign regulatory risk rating and sequencing constraints
- Validate regulatory history and current liaison contacts
- Map schedule windows, aircraft availability, and resource constraints
- Agree evidence matrix and minimum submission content per gate
- Identify critical test dependencies and mitigation actions
- Confirm escalation and decision pathways
- Prioritize the near-term work package
- Surface and prioritize technical gaps and risky assumptions
-
Solution Experience
Walk through how the certification program, analyses, and verification activities will deliver the buyer's outcomes using the customer's airframe context and risk scenarios.
Solution Experience
- Solution Experience — Certification Program Walkthrough
- Confirm the current state and its cost
- You confirm that the proposed gate-by-gate plan and verification activities eliminate the late-stage redesign risk identified in Discovery.
- Deliver a draft gate-by-gate certification schedule and regulatory risk matrix based on the provided airframe data before the follow-up session.
- Map gates to regulatory risk
- You agree to measurable acceptance criteria and regulator interaction points required at each gate.
- Provide complete aircraft drawings, previous regulator correspondence, and DER availability windows for the target airframe.
- Proof through a high-risk scenario
- Confirm the internal decision makers and budget threshold required to proceed to Mutual Commit.
- You identify the remaining evidence and decision criteria needed to move toward Mutual Commit.
- Schedule proposed flight-test windows and regulator touchpoint dates for the execution phase.
- Confirm success criteria and acceptance
- Validate this maps to your needs
- Agree next decision steps
- Solution Experience — Certification Program Walkthrough
- Solution Experience Deck
- Certification Solution Brief
- meeting
- slides
- document
-
Certification Scope
Define modification modules, required analyses, flight test and inspection activities, deliverables, responsibilities, schedule milestones, and regulatory risk at each gate.
Scope Configuration
- Submit STC regulatory application package
- Provide structural analysis report (FEA)
- Deliver damage-tolerance and fatigue substantiation
- Produce system safety assessment report
- Create installation and wiring installation drawings
- Develop flight test plan and procedures
- Execute flight test campaign and data collection
- Analyze flight test data and deliver report
- Perform conformity inspections and release findings
- Draft Instructions for Continued Airworthiness (ICA)
- Generate repair and installation manuals
- Support DER engineering approval and sign-off
- Prepare aftermarket component certification package
- Provide weight, balance, and performance analysis
Scope Questions
Submit STC regulatory application package
- Which certification authority will receive the STC application?
- How many aircraft types/variants (by model and series) must be included in the single STC application?
- Describe the existing Type Certificate Data Sheet (TCDS) items or certification basis paragraphs the modification affects
- Identify which supporting artifacts you will provide at application submission
- When do you expect to submit the initial application package to the regulator?
- Who in your organization will be the regulatory point of contact for application questions and clarifications?
Provide structural analysis report (FEA)
- Which finite element analysis (FEA) deliverables do you require (stress report, model files, mesh export, load case matrix)?
- How many primary structural load cases (e.g., limit, ultimate, gust) should be included in the FEA report?
- Specify which baseline structural drawings or 3D models you will provide as inputs for model correlation
- Describe the correlation approach you expect between FEA and physical data (e.g., modal survey, proof load test, strain gage correlation)
- Do you need the FEA report to reference specific certification standards or analysis methods (for example, FAR 25 or EASA CS 25 load factors, safe-life vs damage tolerance)?
- Provide the preferred delivery format for FEA artifacts (report PDF, neutral mesh, native solver files)
Deliver damage-tolerance and fatigue substantiation
- Which damage-tolerance regime do you require for substantiation (safe-life, damage-tolerance, fail-safe) for the affected structure?
- How many structural detail locations require fatigue crack growth analyses or strain-life calculations?
- Identify the service life or flight cycles to be substantiated (e.g., 60,000 cycles, 20 years)
- Which inspection intervals or threshold tasks do you expect to appear in the airworthiness limitations section based on the damage-tolerance work?
- Describe any existing fatigue test data, fleet damage history, or structural modifications that should be included in the fatigue substantiation
- Are there specific non-destructive inspection (NDI) methods required for substantiation acceptance (e.g., eddy current, ultrasound, borescope)?
Produce system safety assessment report
- Which system or subsystem safety standard should the assessment reference (for example, ARP4761-style functional failure conditions or equivalent)?
- Identify the functional failure conditions and worst-case operating modes for the modified system that the safety assessment must cover
- Describe the integration interfaces that will require SSA focus (for example, electrical power bus, flight control mechanical linkages, avionics databus)
- Which quantitative thresholds or probability targets (e.g., catastrophic, hazardous, major) should be used to classify failure conditions in the report?
- Do you require failure modes and effects analysis (FMEA) worksheets and traceability to verification tests?
- Who will own action-item closure for any mitigations identified by the SSA (you or we)?
Create installation and wiring installation drawings
- Which drawing standards and revision control should be used for installation drawings (for example, company drawing standard, regulatory drawing numbering)?
- How many distinct installation zones or shipsets (cabin, forward electronics bay, empennage) require drawing documentation?
- Specify whether wiring installation drawings must include wiring diagrams, harness routing, and wire size/type callouts
- Do you have existing wiring schematics or harness part numbers that must be reused or referenced?
- Which physical access and panel removal procedures should be reflected on the drawings to support conformity inspections?
- Provide the preferred drawing deliverable format for regulatory submission and shop use (PDF, CAD neutral, native CAD)
Develop flight test plan and procedures
- Which flight test objectives should the plan cover (handling qualities, performance, flutter clearance, systems functionality)?
- Which aircraft serial numbers or fleet CPTs (controlled production tails) will be available for flight test?
- Which flight envelope expansion is required for certification (altitude, Mach, center-of-gravity extremes)?
- What test instrumentation and data acquisition channels must be specified in the plan (strain gages, air data, GPS/IMU, video)?
- Describe any required ground or bench tests that must precede flight sorties (functional checks, taxi tests, rigging verification)
- Which acceptance criteria will define a successful flight test sortie for a given maneuver (e.g., no critical vibrations, system fault codes cleared)?
Execute flight test campaign and data collection
- How many flight hours or sorties do you anticipate for the complete test campaign?
- Which test roles must you provide versus those we will provide (test pilot, flight test engineer, telemetry support)?
- When will aircraft availability windows for flight test be locked (dates or month ranges)?
- Are ferry flights or special permissions required to reposition aircraft for test that we should budget for?
- Which ground support equipment and test instrumentation will you supply (portable data recorders, strain bridge amplifiers, telemetry link)?
- Identify any operational constraints for flight test (passenger-cabin limitations, maintenance curfews, noise abatement)
Analyze flight test data and deliver report
- Which data reduction standards and reference documents should guide the flight test analysis (for example, signal processing windows, filtering methods)?
- What key performance indicators do you expect reported from flight test (Vmcg, climb gradient, handling-qualities metrics)?
- Which time-aligned datasets must be delivered with the report (raw telemetry, reduced channels, synchronized video)?
- Describe the threshold criteria for reporting anomalies that require immediate engineering disposition
- Who will approve the final flight test analysis report for regulator submission?
- Provide the required turnaround time for delivering the flight test report after the final sortie
Perform conformity inspections and release findings
- Which assemblies and shipsets require conformity inspection (left/right wing, empennage, cabin modules)?
- How many conformity inspection checkpoints do you expect during production and pre-flight (initial, in-process, final)?
- Which inspection evidence formats do you require for release (photographic record, signed inspection checklist, calibrated measurement logs)?
- Who provides the authorized inspector or certifying staff for conformity release (your quality staff, we provide an authorized inspector, DER inspection)?
- What documentation will constitute a released conformity package for the shipset (signed checklist plus nonconformance dispositions)?
- What evidence will validate and close a conformity nonconformance raised during inspection (corrective action photos, re-measurement, DER approval)?
Draft Instructions for Continued Airworthiness (ICA)
- Which ICA sections must be included (scheduled maintenance tasks, inspection tasks, airworthiness limitations, replacement parts list)?
- How will ICA tasks be referenced to existing maintenance publications and zones (AMM chapters, IPC references)?
- Which format and revision control do you require for ICA delivery for both regulator and line maintenance use (PDF, ATA iSpec 2200)?
- Which maintenance intervals or threshold values should be proposed based on the substantiation (flight hours, cycles, calendar time)?
- What acceptance criteria will confirm the ICA is complete for regulator review (inclusion of tasks, task descriptions, necessary measures and tools)?
- Do you require training materials or task cards derived from the ICA for line maintenance crews?
-
Mutual Commit
Finalize commercial and legal terms, IP/data access, acceptance criteria, and confirm resource and regulatory engagement commitments.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Pricing & Payment Schedule
- Intellectual Property & Data Access Agreement
- Regulatory Engagement Commitment
- Resource & DER Assignment Confirmation
- Acceptance & Deliverables Signoff
- Change Order Agreement
- Insurance & Liability Schedule
- Non-Disclosure Agreement (NDA)
- Export Control & ITAR Compliance Addendum
-
Deployment
Operationalize the certification plan with readiness checks, execution, and acceptance gating.
-
Pre-Deployment Readiness
Lock aircraft availability, DER assignments, test windows, regulator points-of-contact, and required access approvals before execution begins.
Pre-Deployment Questions
Environment and site access
- Which aircraft (serial and tail numbers) are reserved for this program and on which dates is each aircraft available? (one line per aircraft so we can lock test windows)
- Is full physical access to each reserved aircraft confirmed (hangar/line access, confined spaces, required tooling)?
- If access is not fully confirmed, what is the latest date by which full access approvals will be provided? (date we must have to avoid schedule delays)
People and ownership
- Who is the buyer's designated program manager responsible for schedule approvals and day-to-day coordination? (name and role - used to escalate decisions)
- What is the DER assignment status for this program? (so we can confirm regulatory resource availability)
- If DERs are named or partially assigned, list each DER role, the assigned name (or 'TBD'), and the effective start date. (one line per role)
Timing and constraints
- Provide the earliest acceptable start date for certification execution and any absolute blackout dates (e.g., lease return windows, peak ops) that must be avoided. (dates only)
- Are there regulator availability constraints or local blackout periods that affect submission reviews or meetings (e.g., office closures, restricted review windows)?
- If yes, list regulator blackout windows or known restrictions with dates and the regulator office affected. (so we can sequence submissions)
Equipment, approvals, and test logistics
- What is the status of required site and personnel access approvals (hangar entry, security badges, ground support equipment, tooling)?
- Are flight test instrumentation, telemetry, and required sensors available and assigned for the planned test points? (so we can confirm instrumentation lead and schedule)
- Who will arrange conformity and on-aircraft inspections: buyer, seller, or a third-party? Provide the named owner or choose the arranging party.
-
Certification Execution
Execute structural and systems analyses, conformity inspections, flight test program, and regulatory submissions while tracking responses against the milestone schedule.
-
Certificate Acceptance & Closeout
Confirm regulator approvals, deliverable acceptance, and sign-off on maintenance and installation data before formally closing the program.
Checklist items
- Receive regulator-issued approval document for the modification
- Obtain signed conformity inspection acceptance from assigned inspector/DER
- Obtain written authorization to return the modified aircraft/part to service
- Secure buyer-designated approver acceptance of the final deliverable package
- Confirm Instructions for Continued Airworthiness (ICA) delivered and acknowledged
- Verify IP and data access/licensing agreements are fully executed
- Close all regulatory open findings or document accepted deferred items
- Publish and grant access to the final certification package in the agreed repository
- Update aircraft/part maintenance records with certification entries
- Issue final program closeout report and obtain sign-off
-
-
Sustainment & Success
Monitor in-service performance, track open regulatory or maintenance issues, and capture enhancements or lessons learned for future programs.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- 90-day Regulatory and Maintenance Closeout (around day 90)
- Quarterly Operational Review — Sustainment
Issues & Enhancements
- Schedule targeted follow-up workshops for any high-frequency failure modes identified in the review.
- Create and circulate the corrective action tracker with target dates for each remediation item.
- Schedule regulator follow-up calls or written responses where needed and note expected reply dates.
- Status of all open regulatory findings
- Close all resolvable regulatory and maintenance items or capture a documented remediation plan with firm dates for residual items.
- Verify time-to-resolution and unscheduled removal rates are within Certification Scope thresholds or have corrective plans to reach them.
- Confirm maintenance and installation data updates have been distributed to line and shop teams.
- Publish a 90-day closeout report that lists closed items and remediation plans with deadlines.
- Update maintenance manuals and distribute confirmation receipts from named maintenance teams or depots.
- Log any remaining regulator engagements with expected reply dates and escalate if replies exceed the agreed timeline.
- Operational metrics dashboard
- Confirm whether reliability and repair-time metrics remain within Certification Scope targets or require further corrective action.
- Reduce backlog of open regulatory and maintenance items with clear owners and deadlines for the next quarter.
- Capture a prioritized list of lessons and enhancements to feed into future modification programs.
- Publish the quarterly operations dashboard with trend charts and a backlog tracker.
- Create a prioritized enhancement register with estimated effort and recommended timing for future programs.
- Reconfirm scope, success criteria, and owners
- Confirm the modification was installed and conformity inspections completed for aircraft that entered service.
- Document all early operational or regulatory blockers with named owners and target resolution dates.
- Agree the timeline and owner for the first measurement data pack to be delivered before the next meeting.
- Publish a deployment validation report listing installed serial numbers, conformity inspection records, and any deferred work.
- Open tracked tickets for each regulatory or maintenance blocker with target resolution dates.
- Deliver first-measurement data pack (flight hours, incident log, maintenance actions) at least 5 days before the next review.
- Present first 4-10 week operational data
- Determine whether in-service reliability incidents per 1,000 flight hours and unscheduled removal counts are on track versus Certification Scope targets.
- Document root cause for any off-target metric and agree corrective actions with completion dates.
- Ensure open regulatory findings have a documented response path and regulator follow-up date.
- Publish the first-measurement dashboard with normalized incident rates and open findings status.
- Maintenance non-conformance and inspection follow-up
- Trend analysis and recurring root causes
- Deployment and conformity validation
- Gap diagnosis and root-cause review
- Operational reliability metrics review
- Early operational signals
- Open issues burn-down and compliance monitoring
- Corrective actions and remediation plan
- Lessons learned and enhancement capture
- Documentation and training updates
- Open regulatory and maintenance issues triage
- Regulator engagement and open correspondence
- Confirm timeline to ongoing cadence
- Closure confirmation or remediation plan
- Agree next quarter priorities and checkpoint
- Immediate remediation actions