For this item, PSAC submission
For this item, PSAC lifecycle data readiness checklist
Certification teams, Engineering teams and avionics suppliers use this checklist when finalizing a PSAC for submission makes pSAC lifecycle data readiness checklist a gating item. The work checks PSAC draft and revision history, software level rationale, and objectives to lifecycle data map against source records, status claims, and FAA and EASA expectations. Findings call out software level asserted without safety trace, missing serial or date support, and weak release links. The buyer receives an evidence map, discrepancy register, request list, and closure plan.
When this review is needed
- finalizing a PSAC for submission is close enough that open records items could affect acceptance or pricing.
- For this item, Software certification lead needs source-page support for pSAC submission before signing off the file.
- The delivered package has useful summaries but weak links to the underlying documents.
- A request list must be precise enough for prior operators, shops, or sellers to answer quickly.
The problem
For this item, PSAC lifecycle data readiness checklist fails quietly when summary records are accepted without the source pages. For this item, Software certification lead, Certification liaison and DER have to match serials, dates, revisions, and releases across documents that were often produced by different teams.
What gets reviewed
- Match PSAC draft and revision history to the current status line and affected serial or configuration.
- Check software level rationale for date, revision, work scope, and closure support.
- Review objectives to lifecycle data map against logbook entries, releases, and tracking exports.
- Confirm tool qualification approach is present where the acceptance criteria require it.
- Assign each exception to a closure owner with the evidence needed.
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- Pass when the source record shows the same serial, status, date, and configuration as the summary.
- Fail when software level asserted without safety trace.
- Check repetitive or life-limited items for a clear last-done and next-due basis.
- Escalate when the release or approval document is absent from the supplied package.
Evidence normally required
- For this item, PSAC draft and revision history
- For this item, software level rationale
- objectives to lifecycle data map
- tool qualification approach
Common discrepancies
- For this item, Software level asserted without safety trace.
- Tool use eliminates verification without qualification plan.
- Planned data list omits independence evidence.
What is at stake
A weak record can delay closing, trigger a reserve, or leave the next owner with a remediation task after leverage has moved. The exposure is highest where one unsupported item controls value or acceptance.
How the work runs
Frame PSAC Submission
Confirm the exact event, affected file set, buyer role, and decision standard before any for this item, psac draft and revision history is treated as sufficient.
Trace Checklist Item
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Data Readiness
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Software Aspects
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- For this item, PSAC submission discrepancy register with source-page references
- Evidence map showing accepted, disputed, and missing support
- Closure request list written as specific document asks
- Decision readout for technical and commercial stakeholders
Who uses the output
- For this item, Software certification lead uses the register to decide what can proceed and what needs escalation.
- Certification liaison uses the request list to collect missing evidence.
- DER uses the readout to brief transaction or program owners.
How the work fits into the transaction or program
This checklist covers a PSAC before it goes to the authority, and it names the hardest items: the software level assignment with its justification traced from the system safety assessment, the planned life-cycle data and which objectives are satisfied with independence at that level, the proposed means of compliance and any alternative methods flagged for early agreement, and the tool qualification approach for any tools whose output is not otherwise verified; the PSAC, the DAL rationale from the. The evidence set centers on the PSAC, the DAL rationale from the SSA, the objectives-to-data mapping, and the tool list. The likely weak points are a software level asserted without a safety-assessment trace, and tools used to eliminate verification steps with no qualification plan, both of which draw an authority finding at SOI-1. Handoff: software certification lead, finalizing a PSAC for submission, For this item, PSAC lifecycle data readiness checklist.
Jurisdiction-specific considerations
FAA and EASA references are used as record expectations for the evidence set. The review does not assume automatic acceptance by another authority, operator, or contract party.
Regulatory limits
This records checklist does not approve data, release an aircraft or part to service, or make an airworthiness determination. Regulators, authorized persons, operators, and contract parties retain the final decision under their procedures.
What this review does not cover
- Physical inspection of the aircraft, engine, part, or article
- Commercial negotiation of price, reserves, warranty, or lease terms
- Regulatory submissions or approvals made on behalf of the applicant
Specific to this review
- A PSAC can fail early even when software work is strong if the planned evidence is not explicit.
- Tool qualification is reviewed where tool output affects verification credit.
- The checklist links software level, objectives, independence, and data deliverables in one pass.
- The scope uses the PSAC Submission Completeness Checklist question as the control point, so the review stays tied to finalizing a PSAC for submission and the buyer decision behind it.
- The evidence starts with For this item, PSAC draft and revision history and follows Item Lifecycle Data Readiness references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for Software certification lead: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Plan Software Aspects Certification questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from For this item, PSAC submission discrepancy register with source-page references; it gives the next reviewer a precise map instead of another broad request for a better file.
- The source discipline is stricter on this page than on a general audit because the claim being tested is Verify a PSAC is complete and defensible before submission to the authority..
Sources
RTCA. Objectives and lifecycle data for airborne software assurance, by design assurance level (DAL A-E).
SAE International. Safety assessment methods (FHA, PSSA, SSA, FTA, FMEA) supporting development assurance level assignment.
SAE International. Development assurance process at aircraft and system level, including requirements capture and validation.
Frequently asked questions
What makes this checklists review different from a general file audit?
The scope is tied to psac submission completeness checklist and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block finalizing a psac for submission or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is for this item, psac draft and revision history, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives software certification lead a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.
Adapt the checklist to your asset, event, and jurisdiction.