Embraer E-Jet maintenance-program records review

When this review is needed

• An E-Jet is changing hands and the buyer needs the applied program revision confirmed against the approved baseline.
• The aircraft moved from one operator's program to another and the bridging analysis has to be checked rather than assumed.
• Task intervals were escalated during the operator's tenure and the approval behind each escalation must be located.
• A status list was built from a tracking system and no one has reconciled it back to the approved program document.

The problem

A tracking system reports task status against whatever program it was configured with, and on an E-Jet that has passed through more than one regional operator the configured program is not always the approved one. Escalations get applied ahead of their approval, bridging between programs leaves interval math no one reworked, and the status list reads clean while the basis underneath it has drifted. The people who set the program up have usually moved on by the time anyone asks.

What gets reviewed

• The approved maintenance program and revision the E-Jet was actually maintained against
• Task intervals as applied compared against the approved program for this serial number
• Escalation approvals and the analysis supporting each interval extension
• Bridging analyses that carried the aircraft between successive programs
• The source references behind each program status line, back to the approved document
• Program status as presented in the tracking system versus the underlying approvals

What gets validated

• The program revision applied in the tracking system matches an approved revision on file
• Each escalated interval is supported by an approval that names the task and the aircraft
• The bridging analysis reconciles task history across the program change without an unexplained interval jump
• Program status lines resolve to the approved program document rather than a spreadsheet copy
• Repetitive-task counts and next-due figures follow from the approved intervals, not a superseded revision

Evidence normally required

• The approved maintenance program document and its revision history
• The current maintenance-program status list or tracking-system export
• Escalation approvals and the supporting engineering analyses
• Any bridging analysis used when the aircraft moved between programs
• The operating history that establishes which programs applied and when

Common discrepancies

• A tracking system configured to a program revision the operator never held approval for
• An escalated interval applied months before the approval that authorizes it
• A bridging analysis that skips a task class, leaving its interval unaccounted across the change
• Next-due figures computed off a superseded revision that still reads current on the status list

What is at stake

If the applied program cannot be tied to an approved revision, every interval computed from it is in question, and the next operator inherits a status list they cannot stand behind. An escalation without its approval forces the task back to its unescalated interval, which can pull a check forward and reprice the deal. Bridging errors surface at the first heavy check under the new program, when the schedule least tolerates them.

How the work runs

What the buyer receives

• An exception list of program status lines that do not reconcile to an approved basis
• A source map tying each program interval to its approved revision and approval
• A closure plan sequencing the escalations and bridging steps that need supporting evidence

Who uses the output

• Asset managers pricing an E-Jet against a program status they can defend
• Continuing-airworthiness teams inducting the aircraft onto a receiving program
• Records teams reconciling the tracking system back to the approved program document

How the work fits into the transaction or program

The program review sits underneath every other status the aircraft carries, because AD applicability, task due-dates, and check forecasts all compute off the program in force. Running it first means the rest of the file rests on a confirmed basis rather than a tracking configuration nobody has checked against the approved document.

Aircraft-specific considerations

E-Jets tend to accumulate program history across regional operators with different utilization patterns, so a single serial number can carry two or three program bases with bridging between them. High cycle-to-hour ratios on short regional sectors push cycle-driven tasks faster than a fleet template assumes, which is exactly where an unchecked escalation or a bridging error does the most damage. The review is scoped to the actual program lineage for that tail rather than a family-level assumption.

Jurisdiction-specific considerations

The same E-Jet may have been maintained under an FAA-accepted program and later a program approved under EASA continuing-airworthiness rules, and the two structure task approvals and escalations differently. The review notes where a program element that was acceptable under one system needs a different supporting record to satisfy the other.

Regulatory limits

The review reads the program records and their approvals and reports what reconciles. It does not approve a maintenance program, authorize an escalation, accept the aircraft onto any program, or make an airworthiness determination.

What this review does not cover

• Authoring or revising the maintenance program itself
• Granting or endorsing any task escalation or interval extension
• Any airworthiness or program-acceptance decision, which rests with the operator and authority

Specific to this review

• The program in the tracking system is a configuration choice, so it can diverge from the approved revision without any entry looking wrong.
• An escalation applied ahead of its approval is invisible on the status list but reverts the task to its base interval the moment the gap is found.
• Bridging errors hide until the first heavy check under the new program, because that is when the reworked intervals first come due.
• A single E-Jet serial number can carry two or three successive program bases, so the review has to establish which program applied over each period before any interval can be trusted.
• High cycle-to-hour ratios on short regional sectors pull cycle-driven tasks faster than a fleet template assumes, which is where an unchecked escalation does the most damage.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits