Maintenance program status
Bombardier CRJ family maintenance program records review
This review confirms that the maintenance program a CRJ has actually been operated to matches the approved program its records claim, revision by revision. It suits a lessor, airline, or management team pricing or inducting a specific tail, and it runs against one serial number rather than a fleet template. The work traces program revisions in force at each check, any task-interval escalations applied, and the bridging analysis used when the tail changed operator or program. You receive an exception list tied to source approvals, a map from each program line to its evidence, and a closure plan scoped to that airframe.
When this review is needed
- A CRJ is changing operator and its prior program has to be reconciled to the receiving program before induction.
- A buyer wants proof the tail was maintained to the program revisions its status report asserts.
- Task escalations were applied over the years and no one has checked the approval basis behind each one.
- A high-cycle regional tail is being priced and the program status drives what maintenance falls due next.
The problem
A CRJ that has run short regional sectors for years accumulates program revisions, escalations, and at least one operator change, and the status report the file presents is a summary of all that history rather than proof of it. The escalation that eased a structural interval may have been approved for a different program, or a bridging analysis may have been started and never closed. The status looks settled until someone has to defend a single line of it.
What gets reviewed
- Program revision in force reconciled to each check the CRJ has completed
- Task-interval escalations traced to the approval that authorized them for this program
- Bridging analysis reviewed where the tail moved between operators or programs
- Source-document references behind the current status confirmed as retrievable
- Program lines with no supporting approval flagged as open exceptions
- Structural and zonal program tasks checked against the aging-airframe additions this family carries
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
- Each escalated interval is authorized by an approval that names this program and effectivity
- The program revision the status report cites matches the revision the check packages were worked to
- A bridging analysis referenced in the file is complete rather than opened and abandoned
- Structural inspection tasks reflect the revisions applicable to the tail's cycle band
- Every status line resolves to a source document rather than to the tracking summary alone
Evidence normally required
- The current maintenance program status report for the serial number
- The approved maintenance program and its revision history
- Escalation approvals and any task-interval extension records
- Bridging analyses from prior operator or program changes
- Check package cover sheets showing the program revision worked to
Common discrepancies
- An escalation applied against an approval that covered a different program revision
- A bridging analysis started at an operator change but never signed off
- Structural task intervals that lag the revision applicable to the tail's cycles
- A status line whose source approval cannot be produced from the file
What is at stake
Operating a CRJ to a program status that its approvals do not support means checks come due on the wrong date, and a task treated as escalated may in fact still sit at its baseline interval. At a transaction that surfaces as a repriced maintenance reserve, and at induction it becomes work the receiving operator has to perform before the tail flies revenue sectors.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Rebuild the revision timeline
Order the program revisions in force against the checks the CRJ actually completed.
Test each escalation
Confirm every interval extension was approved for this program and effectivity.
Close the bridging
Verify each operator-change bridging analysis is complete rather than abandoned.
List and sequence exceptions
Flag unsupported program lines and order them by what blocks induction or pricing.
What the buyer receives
- An exception list mapping each unsupported program line to what it lacks
- A source map linking every current status figure to its governing approval
- A closure plan sequenced by which lines block induction or pricing first
Who uses the output
- Asset managers pricing the maintenance falling due against a verified program status
- CAMO and continuing-airworthiness leads inducting the tail onto a receiving program
- Records teams closing program exceptions before the next check or transaction
How the work fits into the transaction or program
Program status is the frame every other CRJ record hangs on, so this review usually runs early and sets the intervals the task-card and non-routine reviews are read against. Its closure plan feeds the induction work when the tail moves operators, and its source map anchors the maintenance figures a buyer prices from.
Aircraft-specific considerations
CRJ airframes tend toward high cycles on short regional sectors, which brings the aging-structure program additions and landing-gear life items forward faster than block hours suggest. A tail that has passed through several operators carries more escalation and bridging history than block hours alone imply, so the program review is scoped to that specific cycle band and operator chain rather than to a family default.
Jurisdiction-specific considerations
A CRJ moving from an FAA program toward EASA oversight has to satisfy CAMO program-management expectations that treat escalations and bridging differently from the receiving-carrier approach the file was built on, so the review notes where a program line will need rework for the receiving system.
Regulatory limits
The review reconciles the recorded program status to the approvals behind it and lists what is unsupported. It does not approve a program revision, authorize an escalation, or determine that the aircraft is airworthy.
What this review does not cover
- Developing or approving a maintenance program revision or escalation
- Performing the maintenance tasks the program calls due
- Any airworthiness determination on the aircraft
Specific to this review
- An escalation is only as good as the program revision it was approved against; carrying it to a later revision quietly voids the extension.
- Bridging analyses are a frequent CRJ gap because operator changes are common on this type and the analysis is easy to start and leave unsigned.
- On high-cycle regional tails the structural program additions drive the next due check more often than the hourly tasks do.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
U.S. Government (eCFR). Maintenance recordkeeping and retention requirements for Part 135 operators.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
Do you confirm the maintenance was actually performed, or only that the program is approved?
This review confirms the program the tail was operated to is the approved one and that escalations and bridging are supported. Whether each due task was accomplished is checked against the task-card and logbook records, which is a separate review that reads against the intervals this one fixes.
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.