Part 145 · In development · Q1 2027
8130-3 return-to-service records
In development, targeted for Q1 2027: return-to-service records tied to their work orders. 8130-3 e-signature remains a separate third-party integration, not a built-in claim. Built and in testing — not yet enabled in production.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
Who it's for
A repair station that, once this ships, would tie each return-to-service record to the work order it closes out instead of keeping two filing systems.
What it replaces
Return-to-service records kept apart from the jobs they document — replaced once this is in production.
What 8130-3 return-to-service records gives you
- In development for Q1 2027 — built and in testing
- Return-to-service records tied to their work orders
- 8130-3 e-signature stays a separate integration
RTS records tied to their work orders — in development for Q1 2027
This capability is in development, targeted for Q1 2027 and built and in testing — not yet enabled in production. Once it ships, a return-to-service record would tie to the work order it closes out, so the RTS record and the job it documents are one connection rather than two filing systems. Until it's in production, RTS records live outside the platform.
- In development for Q1 2027 — built and in testing
- Return-to-service records tied to their work orders
The 8130-3 e-signature stays a separate integration
The 8130-3 e-signature itself would stay a separate third-party integration — AviationAlley does not generate, sign, or file the 8130-3 form, and never claims to. What is in development is the return-to-service record that ties to its work order; the form's signature and issuance remain outside the platform's claim.
- 8130-3 e-signature stays a separate integration
- Part of the in-development certificate layer, not today's core
How an operator uses this
This capability is in development, targeted for Q1 2027 and built and in testing — not yet enabled in production. Once it ships, return-to-service records will tie to the work orders they close out, so the RTS record and the job it documents are one connection rather than two filing systems. The 8130-3 e-signature itself stays a separate third-party integration — AviationAlley does not generate or sign the 8130-3 form, and never claims to. It's part of the in-development certificate layer, not the maintenance core that ships today; until it's in production, RTS records live outside the platform.
Illustrative — every screen reflects what's in your own data, nothing more.
How it works
8130-3 return-to-service records, step by step
Planned: create a return-to-service record tied to its work order.
Planned: the RTS record and the job it documents will be one connection.
Planned: the 8130-3 e-signature stays a separate third-party integration, not a built-in feature.
Planned for Q1 2027 — built and in testing, not yet enabled in production.
Questions
8130-3 return-to-service records — frequently asked
Does AviationAlley generate or sign 8130-3 forms?
No. AviationAlley does not generate or electronically sign the 8130-3 form — the e-signature stays a separate third-party integration. The return-to-service records that tie to work orders are in development, targeted for Q1 2027, and not yet enabled in production.
Are return-to-service records available today?
Not yet. RTS records tied to their work orders are part of the in-development repair-station layer, targeted for Q1 2027 — built and in testing, not yet enabled in production.
Keep exploring
Other features in Part 145
Work orders
Priority, status, assignee, and parts consumed per job.
Deep diveParts inventory
Per-part minimum-quantity thresholds, facility location, and low-stock flags.
Deep diveVendors & purchase orders
Linked to the parts catalog.
Deep diveAD/SB tracking
Airworthiness directives and service bulletins on the Due-Soon → Overdue pipeline, with an explainable AOG-risk score.
Deep diveRepair-station ratings
Airframe / powerplant / accessory ratings and limitations.
Deep diveCapability list
Self-evaluated capability list items with revision control.
Deep diveRSQM document control
DRAFT → PROPOSED → APPROVED → SUPERSEDED sections.
Deep diveMechanic training records
Per-mechanic recurrent training history.
Deep diveEvery Part 145 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee 8130-3 return-to-service records on your operation.
It's part of the in-development layer for Part 145, landing Q1 2027 — join the waitlist to get on it first.