> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Compliance Documents Reference
> AD/SB tracking statuses, RII catalog structure, FAA Form 337 requirements, and compliance document types.
PlaneConnection tracks maintenance compliance documents across the fleet,
covering Airworthiness Directives (ADs), Service Bulletins (SBs), Required
Inspection Items (RII), FAA Form 337 filings, and other regulatory
compliance records. This page documents the data structures, statuses, and
regulatory requirements for each compliance document type.
Compliance document management requires `maintenance_ops:read` permission to view and
`maintenance_ops:write` to create, submit, or modify records. For the regulatory context behind
these requirements, see [FAA Part 5 Explained](/en/explanation/faa-part-5).
## AD/SB Compliance Tracking
### Item Types
PlaneConnection tracks four categories of compliance items under the AD/SB
compliance system:
| Item Type | Description | Regulatory Basis |
| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| **Airworthiness Directive (AD)** | Mandatory corrective action issued by the FAA when an unsafe condition exists in a product. Compliance is legally required. | 14 CFR Part 39 |
| **Service Bulletin (SB)** | Recommended action issued by the manufacturer. May become mandatory if referenced by an AD. | Manufacturer guidance |
| **Certification Maintenance Requirement (CMR)** | Mandatory tasks identified during type certification that must be performed at specified intervals. | 14 CFR 25.1309 |
| **Engineering Change** | Design modification requiring tracking for configuration management. | Operator internal |
### AD/SB Statuses
Each compliance item carries a status reflecting its current disposition:
| Status | API Value | Description |
| ------------------------------------------ | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Open | `open` | Item has been identified as applicable to one or more aircraft but compliance action has not been initiated. |
| Complied | `complied` | Compliance action has been completed and documented. Includes the compliance date, method, and reference to the work order or logbook entry. |
| Recurring | `recurring` | AD or SB requires repetitive compliance at specified intervals. The system tracks both initial compliance and recurring due dates. |
| Not Applicable | `not_applicable` | Item has been reviewed and determined not applicable to the operator's aircraft (different serial number range, modification status, etc.). Requires documented justification. |
### AD/SB Status Lifecycle
```mermaid theme={}
stateDiagram-v2
[*] --> Open : AD/SB identified
Open --> Complied : One-time compliance completed
Open --> Recurring : Initial compliance completed (repetitive AD)
Open --> Not_Applicable : Determined N/A with justification
Recurring --> Recurring : Recurring compliance completed (resets interval)
Complied --> [*]
Not_Applicable --> [*]
```
### AD/SB Compliance Statistics
The compliance dashboard displays real-time statistics:
| Metric | Description |
| ------------------ | ----------------------------------------- |
| **Total** | All tracked AD/SB items across the fleet. |
| **Open** | Items requiring compliance action. |
| **Complied** | Items with completed one-time compliance. |
| **Recurring** | Items on repetitive compliance schedules. |
| **Not Applicable** | Items reviewed and determined N/A. |
### Compliance Record Fields
When marking an AD/SB as complied, the following fields are captured:
| Field | Type | Required | Description |
| ------------------- | ------ | :------: | -------------------------------------------------------------------------------------------- |
| `compliance_date` | Date | Yes | Date the compliance action was performed. |
| `compliance_method` | String | Yes | How compliance was achieved (e.g., "Inspection per AD instructions", "Modification per SB"). |
| `work_order_ref` | String | No | Reference to the work order under which the compliance was performed. |
| `logbook_entry_ref` | String | No | Reference to the maintenance logbook entry documenting the work. |
| `performed_by` | String | Yes | Name and certificate number of the person who performed the work. |
| `notes` | Text | No | Additional compliance notes or remarks. |
## Required Inspection Items (RII) Catalog
### Regulatory Basis
14 CFR 135.427 requires Part 135 operators using a continuous airworthiness
maintenance program (CAMP) to designate Required Inspection Items -- those
maintenance tasks that, if performed improperly or with incorrect parts,
could result in a failure, malfunction, or defect endangering safe operation.
**Key requirements under 14 CFR 135.427:**
* The operator must prepare and maintain a list of RII items
* Each RII requires a **separate inspection** by a person other than the one
who performed the work (14 CFR 135.427(b)(3))
* The inspector must hold **Required Inspection Authorization (RIA)** granted
by the operator
* RII items must be reviewed and updated as the fleet composition or
maintenance program changes
### RII Catalog Structure
Each RII item in PlaneConnection includes:
| Field | Type | Description |
| ----------------- | ------- | -------------------------------------------------------------------------------------------- |
| `item_number` | String | Sequential identifier within the operator's RII catalog (e.g., "RII-001"). |
| `description` | Text | Detailed description of the inspection item and the safety concern it addresses. |
| `aircraft_type` | String | Aircraft type or model to which this RII applies. |
| `ata_chapter` | String | ATA 100 chapter code identifying the affected system. |
| `inspection_type` | String | Type of inspection required (e.g., "visual", "NDT", "operational check", "functional test"). |
| `interval_hours` | Number | Inspection interval in flight hours (if applicable). |
| `interval_cycles` | Number | Inspection interval in landing cycles (if applicable). |
| `interval_months` | Number | Inspection interval in calendar months (if applicable). |
| `requires_ria` | Boolean | Whether the inspection requires a person with RIA delegation. Always `true` for RII items. |
### RII Inspection Workflow
```mermaid theme={}
flowchart LR
A["Maintenance\nPerformed"] --> B["Initial\nInspection"]
B --> C{"RII\nItem?"}
C -- No --> D["Standard\nSign-off"]
C -- Yes --> E["Separate\nRII Inspection"]
E --> F{"Inspector\nHolds RIA?"}
F -- Yes --> G["RII\nSign-off"]
F -- No --> H["Reject:\nUnauthorized"]
G --> I["Return to\nService"]
```
An RII inspection must be performed by a person **other than** the individual who performed the
maintenance work. The inspector must hold a current Required Inspection Authorization from the
operator. PlaneConnection
validates this separation-of-duties requirement during the work order verification step.
## FAA Form 337 Requirements
### When Form 337 Is Required
FAA Form 337 (Major Repair and Alteration) must be filed for any major
repair or major alteration as defined in 14 CFR Part 43, Appendix A.
| Category | Definition | Examples |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Major Repair** | A repair that, if improperly done, might appreciably affect weight, balance, structural strength, performance, powerplant operation, flight characteristics, or other qualities affecting airworthiness. | Wing spar repair, engine case weld, flight control surface rework |
| **Major Alteration** | An alteration not listed in the aircraft, aircraft engine, or propeller specifications that might appreciably affect those same qualities. | Avionics suite upgrade, cargo conversion, supplemental type certificate (STC) installation |
### Form 337 Record Fields
| Field | Type | Required | Description |
| --------------------- | ------ | :------: | ----------------------------------------------------------------------------------- |
| `form_number` | String | Yes | FAA Form 337 tracking number. |
| `aircraft_id` | String | Yes | Aircraft registration (tail number). |
| `serial_number` | String | Yes | Aircraft serial number. |
| `type` | Enum | Yes | `major_repair` or `major_alteration`. |
| `description` | Text | Yes | Description of the repair or alteration performed. |
| `data_approval` | String | Yes | Approved data used (STC, DER-approved data, AC 43.13, manufacturer data). |
| `performed_by` | String | Yes | Name and certificate number of the person performing the work. |
| `approved_by` | String | Yes | Name and certificate number of the authorized inspector (IA) who approved the work. |
| `completion_date` | Date | Yes | Date the repair or alteration was completed. |
| `faa_district_office` | String | No | FSDO where the Form 337 was filed. |
| `filed_date` | Date | No | Date the form was submitted to the FAA. |
Per 14 CFR 43.9(a), the operator must retain one copy of each Form 337 with the aircraft's
maintenance records. PlaneConnection stores the form data and supports attaching a scanned copy
of the signed original. Record integrity hashing (SHA-384) ensures the digital record has not been
tampered with after entry.
## Compliance Document Types
The compliance documents system in PlaneConnection covers a broader set of
maintenance records beyond AD/SB tracking:
| Document Type | Description | Regulatory Reference |
| ----------------- | ----------------------------------------------------------------------------------- | --------------------- |
| **Work Order** | Completed and verified work order records. | 14 CFR 43.9 |
| **FAA 8130-3** | Authorized Release Certificate for parts (domestic) or EASA Form 1 (international). | 14 CFR 21.303 |
| **Logbook Entry** | Maintenance logbook entries per 14 CFR 43.9 content requirements. | 14 CFR 43.9 |
| **Form 337** | Major Repair and Alteration records. | 14 CFR 43.9(a) |
| **AD Compliance** | Airworthiness Directive compliance records. | 14 CFR Part 39 |
| **SB Compliance** | Service Bulletin compliance records. | Manufacturer guidance |
### Document Statuses
Compliance documents follow a review workflow:
| Status | API Value | Description |
| ------------------------------------------ | ---------------- | ----------------------------------------------------------------------------------------------- |
| In Queue | `in_queue` | Document submitted and awaiting initial review. |
| Pending Review | `pending_review` | Under active review by the compliance team. |
| Accepted | `accepted` | Document reviewed and accepted as compliant. |
| Rejected | `rejected` | Document rejected. Requires correction and resubmission. |
| Archived | `archived` | Document has been archived after acceptance. Retained per 14 CFR 91.417 retention requirements. |
### Document Review Lifecycle
```mermaid theme={}
stateDiagram-v2
[*] --> In_Queue : Document submitted
In_Queue --> Pending_Review : Assigned for review
Pending_Review --> Accepted : Review passed
Pending_Review --> Rejected : Issues found
Rejected --> In_Queue : Corrected and resubmitted
Accepted --> Archived : Retention period management
Archived --> [*]
```
## Record Retention
14 CFR 91.417 specifies minimum retention periods for maintenance records:
| Record Type | Retention Period | Regulation |
| ----------------------------------------------------------- | ---------------------------------------------------- | ------------------------ |
| Maintenance, preventive maintenance, and alteration records | Until the work is superseded or the aircraft is sold | 14 CFR 91.417(a)(1) |
| Total time in service (airframe, engine, propeller) | Indefinite (transferred with aircraft) | 14 CFR 91.417(a)(2)(i) |
| Current status of life-limited parts | Indefinite (transferred with aircraft) | 14 CFR 91.417(a)(2)(ii) |
| Time since last overhaul (items with TBO) | Indefinite (transferred with aircraft) | 14 CFR 91.417(a)(2)(iii) |
| Current inspection status and due dates | Indefinite (transferred with aircraft) | 14 CFR 91.417(a)(2)(iv) |
| AD compliance status | Indefinite (transferred with aircraft) | 14 CFR 91.417(a)(2)(v) |
| Major alteration Form 337 records | Indefinite (transferred with aircraft) | 14 CFR 91.417(a)(2)(vi) |
PlaneConnection retains all compliance documents indefinitely with tamper-evident hash chain
protection. Soft-deleted records are preserved in the database for regulatory compliance. See
[Record Integrity Anchors](/en/reference/record-integrity-anchors) for the technical details of
the 5-layer integrity system.
## Related
How work orders progress through completion and verification.
SHA-384 hash chains and blockchain anchoring for tamper-evident records.
Data flow between compliance documents, work orders, and other modules.