In brief
A maintenance tracking spreadsheet can support planning and review when it preserves aircraft identity, task applicability, accomplishment evidence, every controlling due basis, calculation logic, exceptions, and approval history. It should not be treated as the source record or an automatic airworthiness determination.
Tools for this decision
Run the numbers while you read.
A maintenance spreadsheet should answer five questions without guesswork:
- What requirement or task applies?
- What source proves the last accomplishment?
- Which clock controls the next due point?
- What remains before that limit?
- Who reviewed the conclusion, and when?
The spreadsheet is a control layer, not a substitute for maintenance entries, work packages, approved programs, current regulatory sources, or qualified technical judgment.
What the download contains
The downloadable starter has five worksheets. It is intentionally a controlled baseline, not a preloaded maintenance program or complete component-tracking system.
| Downloaded sheet | What it supports | Important boundary |
|---|---|---|
| Start Here | Instructions and limitations | Does not authorize a maintenance program |
| Aircraft Status | Aircraft identity, status date, and current airframe/engine inputs | One-aircraft snapshot, not utilization history |
| Due Items | Calendar-, hour-, and cycle-based planning rows and remaining formulas | User must supply applicability, intervals, and last-complied facts |
| Evidence Index | Source identity, link, limitation, and reviewer | A link does not prove the source is sufficient |
| Exception Log | Open questions, consequence, action, owner, and accepted limitation | Acceptance authority comes from the operation, not the workbook |
For an operation that needs serialized-component history, a dedicated AD register, recurring utilization observations, or field-level change history, add controlled worksheets or move to a purpose-built system. Do not assume those functions are already in this starter.
Aircraft Status: identity and current inputs
The downloaded Aircraft Status sheet records one aircraft baseline. Complete the fields from current source evidence:
| Field | Entry instruction |
|---|---|
| Registration | Current registration mark; do not use as the only identifier |
| Manufacturer and model | Exact designation used by the controlling program |
| Serial number | Verify the manufacturer serial number against authoritative aircraft records |
| Status date | Date and time through which the entered utilization is current |
| Airframe hours/cycles | Source-stated or controlled derived totals |
| Engine hours | Enter against the correct installed engine identity |
| Evidence | Record the observation in Evidence Index |
The starter is not an installation-history ledger. If an engine or other serialized asset changes, preserve the superseded workbook and maintain a separate installation/removal record rather than overwriting history without a trace.
Extend it when utilization history matters
The download holds a current snapshot, not a row-by-row utilization log. Add a separate controlled sheet when you need chronology:
``text Observation ID | Aircraft/asset ID | Reading date | Aircraft hours | Aircraft cycles | Engine hours/cycles | APU hours/cycles | Other meter | Source document/link | Entered by | Reviewed by | Review date | Notes ``
Keep source-stated values separate from calculated values. If a reading is estimated or reconstructed, label the method and uncertainty rather than presenting it as observed fact.
Add validation rules for:
- Reading dates that move backward.
- Hours or cycles below the previous accepted observation.
- An engine reading attached to the wrong serial number.
- A long gap between observations.
- Missing or inaccessible source evidence.
Due Items: what the formulas do
The downloaded Due Items sheet contains these fields:
``text Item ID | ATA/system | Requirement | Authority/source | Basis | Interval | Last date | Last hours | Last cycles | Next date | Next hours | Next cycles | Remaining calendar days | Remaining hours | Remaining cycles | Status/reviewer note ``
The workbook calculates only the remaining arithmetic after the user enters current utilization and source-supported next-due limits. It does not calculate applicability, create a task interval, authorize tolerance, or decide whether a last-complied record is acceptable.
If your program requires applicability rationale, work-package assignment, forecast date, reviewer approval, or position-level control, add explicit fields rather than burying them in the status note.
Due logic without hidden assumptions
For each driver:
remaining hours = next due hours − current hours
remaining cycles = next due cycles − current cycles
remaining calendar = next due date − current date
The operational due point remains each entered hard limit. A forecast may identify which limit is expected first, but the downloaded workbook does not convert days, hours, and cycles into one controlling forecast.
If tolerance or grace is permitted, keep the base due and any authorized adjusted due in separate columns. Cite the authority and approval. Never add a generic percentage to every task.
Tracking Airworthiness Directives
The starter does not include a dedicated AD worksheet. A limited user can create separate Due Items rows and link evidence, but an AD review should preserve these additional fields in a controlled register or purpose-built system:
``text AD number/revision | Product | Applicability conclusion | Rationale | Affected asset | Required action | Method of compliance | Evidence | One-time/recurring | Last accomplishment | Next due by each driver | AMOC reference if applicable | Current-source review date | Reviewer | Exception ``
A spreadsheet match on make and model does not determine applicability. Serial range, configuration, installed articles, prior action, and the AD’s actual text may control. For U.S. review, use the FAA’s Dynamic Regulatory System; use the competent authority’s current source for another jurisdiction.
When components need their own register
The downloaded starter has no serialized-component ledger. Do not compress a complex engine, LLP, landing-gear, or rotable history into one Due Items row. A separate controlled register should capture:
- Nomenclature, part number, and serial number.
- Installed position and host asset.
- Birth or prior-history evidence.
- Life limit and controlling unit.
- Accumulated life at installation.
- Host utilization since installation.
- Current accumulated life and remaining life.
- Installation and removal sources.
- Release or trace documents.
- Repair, modification, and overhaul history.
- Evidence status and exception ID.
Do not calculate remaining life across an unsupported history segment as though it were verified. The life-limited parts guide explains the source chain in more detail.
Exception Log
Use a real exception register:
| Field | Example of what to record |
|---|---|
| Exception ID | Stable identifier, never row number alone |
| Affected task/asset | Exact link to status row |
| Issue | Missing entry, conflicting time, unreadable page, uncertain applicability |
| Evidence reviewed | Documents and searches completed |
| Consequence | Planning uncertainty, review required, status unsupported |
| Interim treatment | Hold, conservative assumption, inspection, research |
| Owner and due date | Named accountable person |
| Disposition | Resolution, acceptance, or escalation with approval |
The spreadsheet should show uncertainty, not make it disappear.
Review and change control
Require a second-person review for material baseline changes. The change log should record:
``text Change ID | Date | Sheet/record ID | Field changed | Previous value | New value | Reason | Source | Changed by | Reviewed by | Approval date ``
The starter does not contain a dedicated change-log worksheet. Preserve issued workbook versions or add a controlled change log before using it as a recurring status process. Test backups, control access, and periodically prove that source links still open. FAA AC 120-78B provides current guidance for electronic recordkeeping systems where applicable; its guidance is not itself a regulation and does not replace the rules or approvals governing a particular operation.
Go-live acceptance checklist
- [ ] Every installed asset has stable identity.
- [ ] Program and revision are defined.
- [ ] All task applicability decisions are reviewed.
- [ ] Last-accomplishment values link to source.
- [ ] Calendar, hours, and cycles are separate.
- [ ] Formula cells are locked and tested.
- [ ] AD list was reviewed against a current FAA source.
- [ ] Life-limited parts retain source traceability.
- [ ] Exceptions have owners and dispositions.
- [ ] Changes retain reviewer history.
- [ ] Backups and exports were restored in a test.
- [ ] Users know the tracker does not itself approve return to service.
Sources and further reading
Common questions
Frequently asked questions
Can I track aircraft maintenance in a spreadsheet?
A spreadsheet can support planning and reconciliation for a limited operation if it is controlled, reviewed, backed up, and linked to source records. The operator remains responsible for meeting applicable requirements, and complexity may make a purpose-built controlled system more appropriate.
What columns should an aircraft maintenance tracker include?
At minimum include aircraft or component identity, task ID and revision, applicability, interval and controlling driver, last accomplishment, next due, remaining amount, source evidence, calculation method, status, exception, owner, and review history.
Is the spreadsheet the official maintenance record?
Not necessarily. A tracker is often a status and planning layer. Required maintenance entries and retained records must still meet the applicable rules and procedures, and each tracker conclusion should link to its controlling evidence.
How often should the maintenance tracker be updated?
Update it when utilization posts, maintenance is accomplished, an applicable requirement changes, configuration changes, or an exception is resolved. The organization should define review and approval intervals appropriate to its operation.
Keep researching
Related aircraft guides
Run maintenance from connected evidence
Know what is due—and open the record that proves it.
Radar connects maintenance status, component history, compliance work, and source records across every tail in the fleet.
