What Belongs in a Return to Service Package
The work is done. The tech signed, the inspector signed, the CRS release is in. Now somebody has to hand the customer a file. That is where a lot of good work quietly falls apart, because the return to service package usually gets assembled by whoever is closest to the printer at 4:30 on a Friday.
Here is what belongs in a return to service package, why each piece is in there, and the items shops leave out most often. (As always, your repair station manual, quality control manual, and ops specs govern what your shop is required to produce and retain. Nothing here is legal advice, and your PMI's reading is the one that counts.)
What the package actually is
Strictly speaking, the FAA does not require a "package." It requires records. Under 14 CFR 43.9, the person approving an article for return to service makes a record with a description of the work performed, the date, the name of the person who did the work, and the signature and certificate number of the person approving it. Inspections have their own required wording under 43.11. Retention rules sit in Part 145, in your manual, and in the owner's operating rules.
The package is the practical version of all that: one file that shows the aircraft or article left your shop airworthy, with the supporting evidence attached instead of scattered across four systems. It exists because two years from now somebody will ask, and "it is in the system somewhere" is not an answer.
The core of every package
- The maintenance release or logbook entry. The signed 43.9 record itself, with the certificate number of the person approving return to service, the date, and the correct approval language for the work performed.
- The work order. Every discrepancy paired with its corrective action, the part numbers, and the approved data each one was worked to. How those write-ups are worded decides whether the file reads clean or reads like a guess.
- Parts documentation. The 8130-3 tags, certs of conformance, or other traceability for every part installed, matched by serial number where the part is serialized.
- Inspection records. The signed checklist or task cards for the inspection performed, not just a line in the entry saying it happened.
- Vendor releases. If a unit went out for overhaul or repair, the outside shop's release travels with your package, not just into your own file.
What gets added depending on the job
- AD compliance record. Any airworthiness directive researched or complied with during the visit: method of compliance, date, and next due where it recurs.
- Weight and balance revision. Any time equipment was added, removed, or relocated.
- Program cards. CAMP or MSP task cards signed and closed, for aircraft that run a program.
- Major repair or alteration. The FAA Form 337 and the approved data behind it, with the owner's copy in the package.
- Life limited part data. Time and cycles at installation, so the next shop is not reconstructing history from invoices.
- Deferred items. Anything found and not corrected, written plainly, with the authority under which it was deferred.
The three things shops forget
Items inspected and found serviceable. A package that only documents the parts that got replaced hides half the visit. The inspection that found nothing wrong is still evidence the inspection happened.
Paperwork on parts you already had. A part that sat on the shelf for two years still needs its tag in the file. Shelf stock is where traceability chains break most often, and an auditor knows it.
Signature authority evidence. Whoever signed the release has to be authorized under your certificate, with training and roster records behind it. That evidence does not go in the customer's package, but it needs to be one search away when a Part 145 audit asks who was qualified to sign.
Assembling it without the Friday scavenger hunt
Most shops build the package by hand. Print the work order. Dig the tags out of receiving. Find the CAMP cards. Scan the signed page. Merge the PDF and hope nothing got left out. That is an hour when everything goes well.
In Orion, the pieces attach to the work order while the job runs, so the file is built by the time anyone needs it. After the LBE sign and lock, one button pulls the signed logbook entry, the 8130-3s, the CAMP and MSP cards, and the service records into a single document for the customer. Every signature is an FAA AC 120-78B compliant e-signature with re-authentication at the moment of signing and a SHA-256 tamper hash, and the whole chain sits in the audit log. Orion is modular on published pricing, so a shop can build only the pieces it actually runs.
Want to see a complete return to service package come out of one work order? Schedule a call and we will walk one through end to end.