Skip to content

Manuals and software records

E2 CAFM revision and interim procedure evidence

airlines, CAMOs, Aircraft records teams use this page when E2 fleet audit or first lease return puts the CAFM revision record under review. The work traces CAFM revision record and Operational procedure evidence to Electronic manual record, Crew or operations acknowledgment, current status data, and supplied acceptance criteria. Findings identify missing source pages, unsupported applicability, serial or location conflicts, and open corrective evidence. The buyer receives a cited register, evidence map, request list, and closure plan.

When this review is needed

  • A E2 fleet audit or first lease return is approaching and the records owner needs a page-level proof set.
  • The summary status uses shorthand that cannot be defended without the underlying task, release, or configuration record.
  • A counterparty has asked which exceptions are true blockers and which are retrieval issues.

The problem

CAFM revision record evidence often looks complete until the reviewer asks which page proves the actual aircraft, engine, component, or location. The review focuses on those trace points instead of accepting inherited status language.

What gets reviewed

  • Confirm each affected E2 aircraft has the required CAFM revision or interim procedure evidence.
  • Review electronic manual control logs for revision identity, date, and applicability.
  • Check operations acknowledgment evidence where compliance relies on procedure use.
  • Compare aircraft compliance matrix with the AD status report.
  • Identify evidence that must be exported from manual systems for lease or audit review.

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 aircraft applicability, CAFM revision, interim procedure, and status update are aligned.
  • Fail when the manual system shows a revision but the aircraft status file has no source reference.
  • Pass when operations evidence identifies the procedure and affected aircraft group.
  • Fail when a fleet bulletin is used without aircraft-level effectivity.

Evidence normally required

  • AD status report
  • CAFM revision evidence
  • interim procedure record
  • electronic manual control log
  • operations acknowledgment evidence
  • aircraft compliance matrix

Common discrepancies

  • CAFM revision controlled electronically but not exported to the records package.
  • Interim procedure acknowledged by operations but absent from AD status evidence.
  • Aircraft compliance matrix excludes one affected tail.
  • Status list updated before the manual revision effective date.

What is at stake

If the gap survives to closing or delivery, the next owner may inherit a disputed status line and a harder retrieval problem. Schedule, reserve, or acceptance decisions can then rest on assumptions instead of records.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Frame 2026 Cafm

Confirm the exact event, affected file set, buyer role, and decision standard before any cafm revision record is treated as sufficient.

02

Trace Performance Evidence

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.

03

Sort Revision Interim

Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.

04

Package Manuals Software

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

  • Manuals and software records discrepancy log with source-page citations
  • Evidence map for accepted, rejected, and unresolved lines
  • Targeted retrieval list for records owners
  • Closure brief for technical and commercial decision makers

Who uses the output

  • CAMO manager uses the register to decide which lines can be accepted or escalated.
  • Performance engineer uses the evidence map to request missing technical records.
  • Technical records manager uses the closure plan for transaction, audit, or delivery decisions.

How the work fits into the transaction or program

AD 2026-02-11 applies to all Embraer ERJ 190-300 and -400 (E190-E2/E195-E2) airplanes after an inconsistency was identified in the takeoff calculation module of the computerized airplane flight manual, requiring AFM revision; evidence compliance for an AD whose object is software and documentation rather than hardware: which CAFM version each tail uses, when the revision was incorporated, and how the operator controlled interim takeoff performance procedures. The evidence set centers on AD status report, CAFM revision evidence, interim procedure record, and electronic manual control log. The likely weak points are CAFM versions managed by the performance engineering team with no aircraft-records entry, interim procedures unevidenced, and per-tail applicability confused on mixed E2 fleets. Handoff: CAMO manager, E2 fleet audit or first lease return, E2 CAFM revision and interim procedure evidence.

Jurisdiction-specific considerations

FAA references are used as evidence context for recordkeeping and compliance support. The review does not treat one authority's record format as automatic acceptance by another authority or by a counterparty.

Regulatory limits

This work is an evidence review only. It does not approve a repair, modification, inspection, manual revision, aircraft, engine, appliance, or part, and it does not replace the regulator, authorized release personnel, operator, or maintenance organization.

What this review does not cover

  • Physical inspection or borescope work outside the records set
  • Engineering approval of repairs or alternate methods
  • Commercial negotiation of credits or reserves

Specific to this review

  • For this review, manuals and software AD evidence often lives outside maintenance records, so export control is part of the review.
  • A recurring records trap is that aircraft-level effectivity prevents a fleet revision from being over-applied.
  • The file should show whether compliance came from a CAFM revision, an interim procedure, or both.
  • The scope uses the 2026 Cafm Takeoff Performance question as the control point, so the review stays tied to E2 fleet audit or first lease return and the buyer decision behind it.
  • The evidence starts with CAFM revision record and follows Evidence Review Revision Interim 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 CAMO manager: 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 Procedure Manuals Software Records questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
  • The handoff value comes from Manuals and software records discrepancy log with source-page citations; 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 CAFM revision and interim procedure evidence under AD 2026-02-11 on E2s..

Sources

Frequently asked questions

What makes this records review different from a general file audit?

The scope is tied to 2026 cafm takeoff performance and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block e2 fleet audit or first lease return or can be closed later without changing the decision.

What evidence has to be available before this work starts?

The starting point is cafm revision record, 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 camo manager 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.

Talk through the aircraft, records, evidence, deadline, and next useful step.