Direct Answer — Correcting a Logbook Entry
To correct a maintenance logbook entry the right way, do not erase, white-out, overwrite, or backdate anything. Instead, make a new, separate correcting entry: date it with the actual date you make it, describe what was wrong and what the correct information is, and sign it with the content a maintenance entry needs under 14 CFR §43.9 — including, where a return-to-service approval is involved, the signature, certificate number, and kind of certificate of the authorized person. Leave the original entry visible and reference it. The reason the procedure matters is the falsification line: the FAA treats a fraudulent or intentionally false entry (historically §43.12, consolidated into 14 CFR Part 3, Subpart D as of November 3, 2025) as one of the most serious recordkeeping violations — and a clumsy fix can make an honest mistake look like one. A transparent, dated correcting entry is the proof that it was honest. This is general information, not legal advice.
New entry
Correct by adding a new, dated, signed entry — never by altering the original
Never erase
Erasing, overwriting, or backdating is what turns a mistake into a falsification problem
§43.9
A correcting entry must carry the same required content as any maintenance entry
Maintenance records are how you prove what was done to an aircraft, when, by whom, and that it was approved for return to service by someone authorized to do it. Because so much rides on those records being accurate and trustworthy, the FAA cares not only about what your entries say but about whether the record can be trusted as an honest, unaltered history. That is why something as ordinary as fixing a typo has a right way and a wrong way — and the wrong way can create a problem far bigger than the original mistake.
The good news is that the right method is simple, and it has not changed. This guide walks through exactly how to make a correcting entry, the one return-to-service signature trap in §43.9 that catches people, what you must never do, how corrections work in an electronic logbook, and a handful of common real-world scenarios. For the bright line you are staying on the right side of, see falsification of maintenance records under §43.12.
The Right Method: A New, Dated, Signed Correcting Entry
There is no magic FAA form for a logbook correction. The accepted practice is grounded in a simple idea: the maintenance record is a chronological history, and history is not rewritten — it is added to. When you find an error, you leave the original entry where it is and make a new entry that corrects it. Done properly, that new entry carries the same weight and the same required content as any other maintenance entry.
The correcting-entry procedure, step by step
Leave the original entry exactly as it is
Do not erase, white-out, scribble over, or tear out the original. It stays legible and in place. The original is part of the record, and the fact that you corrected it openly is what demonstrates good faith.
Make a new entry, dated with today’s actual date
The correcting entry carries the real date you are writing it — not the date of the work being corrected. Backdating is the cardinal error. You can and should reference the original inside the new entry.
Clearly identify what is being corrected
State plainly what was wrong and what the right information is. For example: "This entry corrects the May 3, 2026 entry, which recorded tach time 1,204.6; the correct tach time at completion was 1,240.6." Specificity is what makes it transparent.
Include the required §43.9 content
A description (or reference to acceptable data) of the corrected work, the date, and — if a return-to-service approval is involved — the signature, certificate number, and kind of certificate of the authorized person. A correction is not a license to make a looser, less-complete entry.
Sign it with the right authority
A clerical clarification of your own prior entry can be initialed and dated by you. But anything that touches the substance of maintenance or a return-to-service approval must be signed by a person holding the appropriate certificate authority — and only for work actually performed.
Illustrative correcting entry (example only — not a template for any specific situation)
“6/15/2026 — Correcting entry. The 5/3/2026 entry for the No. 1 engine oil change recorded the incorrect tach time as 1,204.6. The correct tach time at completion of that work was 1,240.6. All other details of the 5/3/2026 entry remain accurate. [Signature], A&P #1234567, Mechanic.”
Note what this does: it is dated today, it leaves the original entry untouched, it names exactly what is being corrected and the right value, and it is signed with the certificate number and kind of certificate. Anyone reading the record sees an honest, transparent fix — not a rewrite. Wording for an actual entry should fit your situation and, where airworthiness or approval is involved, be made by the authorized person.
The single most important principle: the original stays, the correction is added, and the correction is dated honestly. Everything else is detail. If you remember nothing else from this page, remember that — because it is the difference between a clean record and a falsification question. For the full element-by-element requirements your entries (and corrections) must meet, see what a §43.9 maintenance entry must contain.
A correction is only as good as the audit trail behind it.
FileFlo keeps your maintenance and airworthiness records append-only, time-stamped, and attributed — so a correction is a transparent, versioned new entry, never a silent overwrite, and the history proves itself. See where your aviation records stand in a few minutes.
The §43.9 Return-to-Service Signature Trap
Here is the part people miss. When you sign a maintenance entry that approves work for return to service, 14 CFR §43.9(a) says the signature constitutes the approval for return to service only for the work performed. That sentence is small but it controls how corrections work — because it means a signature is not a general endorsement of the record. It is a specific, bounded approval of the specific work that was actually done.
What §43.9(a) requires in every entry
Each person who maintains, performs preventive maintenance, rebuilds, or alters an aircraft must make an entry containing:
- (1)A description (or reference to data acceptable to the Administrator) of work performed.
- (2)The date of completion of the work performed.
- (3)The name of the person performing the work if other than the person specified in paragraph (a)(4).
- (4)If the work performed is satisfactory, the signature, certificate number, and kind of certificate held by the person approving the work. The signature constitutes the approval for return to service only for the work performed.
Source: 14 CFR §43.9(a). Verify the current text via the Cornell Legal Information Institute (law.cornell.edu/cfr/text/14/43.9). Inspections under parts 91/125 and §§135.411(a)(1)/135.419 are recorded under §43.11 instead.
Why the trap matters when you correct
You cannot "correct" your way into approving work you did not do
Because the signature approves only the work actually performed, a correcting entry cannot retroactively sign off maintenance that was never done or that you are not authorized to approve. If the original problem is that required work was not actually completed, the honest fix is to do the work and record it — not to write a correction that papers over the gap.
A correction touching a return-to-service approval needs the right signer
Fixing a clerical detail in your own entry is one thing. But if the correction changes anything about the approval for return to service, it has to be signed by someone holding the appropriate certificate authority — the right kind of certificate for that category of work — not just whoever is handy.
A missing certificate number makes even an accurate entry defective
An entry (or correction) that approves return to service but omits the certificate number or kind of certificate is non-compliant on its face, even if everything it says is true. When you correct, carry the full §43.9(a)(4) content — signature, certificate number, and kind of certificate.
For how digital signatures satisfy the certificate-number and kind-of-certificate requirement in an e-logbook, see electronic aircraft maintenance records and digital signatures, and for the record most exposed to alteration claims when an approval changes, see the FAA Form 337 for major repairs and alterations.
What You Must Never Do — The Falsification Line
The reason all of this matters is that the FAA treats a fraudulent or intentionally false maintenance record as one of the most serious violations there is — and the difference between an honest correction and a falsification often comes down to how the fix was made. The prohibition historically lived in 14 CFR §43.12 and, as of November 3, 2025, has been consolidated with the FAA's other falsification rules into 14 CFR Part 3, Subpart D (final rule at 90 FR 42517; §3.403 addresses fraudulent or intentionally false statements, §3.405 addresses incorrect statements and omissions of fact). The conduct it reaches is about intent to deceive — not honest mistakes you correct openly.
An honest correction looks like this
- A new, dated entry that explains the change in plain terms.
- The original (incorrect) entry stays visible and legible.
- The correction carries today’s real date — never backdated.
- It carries the §43.9 content and the right signature authority.
- In an electronic record, the prior version is preserved and time-stamped.
This is what creates a falsification problem
- Erasing, whiting-out, or overwriting the original entry.
- Backdating a correction so compliance appears to have been timely.
- Replacing a page or re-printing a "clean" record with no trail.
- Signing off an inspection or work that was never actually done.
- Altering a record during or after an inquiry to tidy it up.
The stakes — why the procedure is worth getting exactly right
Falsification is treated far more severely than an ordinary recordkeeping miss: it is a basis to suspend or revoke the offender's certificate, and intentional false statements in records used to show compliance with federal requirements can also carry separate federal criminal exposure. We do not quote case counts or dollar figures here because outcomes are entirely fact-specific. The point for your daily practice is simpler: a transparent, dated correcting entry is not just good housekeeping — it is the evidence that your mistake was honest. For the full picture of what the falsification rule prohibits and where it now lives, read falsification of maintenance records (§43.12), and for how educational compliance actions differ from formal enforcement, see compliance action vs. enforcement.
Correcting an Electronic or Digital Maintenance Record
Everything above applies equally to electronic records — and a well-built electronic system actually makes corrections cleaner, because the right behavior is enforced rather than left to discipline. The wrong way is an editable field that lets someone change an entry and have the old value silently vanish. The right way is an append-only record: the original version is preserved, and a correction is captured as a new, time-stamped, attributed version that references it.
Entries are write-once; corrections are new versions
Once an entry is committed, it is locked. A correction is added as a new versioned entry that points back to the one it corrects — there is no mechanism to overwrite history. That removes both the temptation and the means to quietly rewrite an entry.
Every version is time-stamped and attributed
The system records when each entry and each correction was made, and by which identified person. A backdate is impossible to hide because the real timestamp is captured independently of any date typed into a field.
The audit trail proves the correction was transparent
If anyone ever asks "was this record altered?", you produce the full, tamper-evident history showing the original, the correction, the date, and the author — instead of asking to be believed.
It still has to meet the FAA’s electronic-records expectations
Immutability is necessary but not sufficient. Electronic records must also be legible, retained for the required periods, protected from unauthorized change, and carry the §43.9 content and proper signatures. A good system handles both the integrity and the compliance content.
For the specifics of how e-logbooks and digital signatures satisfy the FAA's requirements, see electronic aircraft maintenance records and digital signatures. And if the underlying problem is not a wrong entry but missing records, that is a different procedure entirely — see how to reconstruct lost aircraft logbooks, where the cardinal rule is that a reconstruction must be transparently labeled as such, never dressed up to look like an original.
Common Correction Scenarios — and the Right Move
Most corrections fall into a handful of patterns. Here is how to think about each — recognizing that anything touching airworthiness or arising during an inquiry is a question for your IA, repair station, or counsel, not a blog.
| The situation | The right move |
|---|---|
| Transposed tach/time or a typo in your own recent entry | New dated correcting entry stating the right value; original left visible. A trivial single-word slip may be a single struck-through, initialed line — but when in doubt, add an entry. |
| Wrong part number or work-order reference recorded | New correcting entry identifying the original entry and the correct part/reference. If the part actually installed differs from what was approved, that is a maintenance question, not just a paperwork one. |
| Wrong date of completion written in | New correcting entry with the actual completion date; never overwrite the original date. If the real date affects an inspection or AD interval, flag it to your IA. |
| Discovered an entry approved return to service for work not finished | Stop. This is an airworthiness and potentially a legal issue — do not write around it. Complete and record the work, and involve your IA/repair station; consult counsel where appropriate. |
| Need to correct an entry made by another mechanic | You can record what you observe and correct factual detail you can support, signed with your authority — you cannot speak for their approval or sign off their work. |
| Error noticed during or after an FAA inquiry or an event | Do not alter anything to clean it up. Preserve records as they are (including electronic version history) and talk to qualified aviation counsel before acting. |
FileFlo as the Records-Proof Layer — Not Your Mechanic or Your Lawyer
FileFlo is a compliance document intelligence platform — a proof layer for your records. To be clear about what it does not do: it does not perform or approve maintenance, decide airworthiness, represent you to the FAA or NTSB, respond to a records demand for you, give legal advice, or guarantee any outcome. Those are decisions for your IA, your repair station, and your counsel. What FileFlo does is make corrections transparent by design and your records easy to produce and prove.
- Captures every entry append-only, time-stamped, and attributed — so a correction is a versioned new entry, never a silent overwrite
- Preserves a tamper-evident history you can produce on demand to show a record was not altered or backdated
- Holds §43.9 entries, inspection records, Form 337s, and AD-compliance records together with the credentials behind each sign-off
- Classifies 600+ document types and flags gaps in the retention chain before they become "missing record" questions
- Surfaces an inspector- or investigator-ready records index, so "produce and prove the records" is a button, not a scramble
- Keeps the documents current and complete — it is the proof layer, not your maintenance program, your safety program, or your attorney
FileFlo classifies 600+ document types and manages records across Part 91, Part 135, and Part 145 operators. Pricing: Starter $89/mo, Professional $299/mo. 5-day free trial, no credit card required. FileFlo keeps the documents that prove compliance audit-ready — it is not an SMS, a dispatch/flight-operations system, a maintenance program, or an enforcement-defense service, and it does not claim SOC 2 certification.
Related Reading
What a §43.9 Maintenance Entry Must Contain
The required elements every entry — and every correction — must carry.
Falsification of Maintenance Records (§43.12)
The bright line a correction must stay on the right side of.
Electronic Records & Digital Signatures
How e-logbooks and digital signatures satisfy FAA requirements.
How to Reconstruct Lost Aircraft Logbooks
When the problem is missing records, not a wrong entry.
FAA Form 337: Major Repair & Alteration
The record most exposed to alteration-for-fraudulent-purpose claims.
NTSB Part 830 Reporting & Records
Why records must be preserved — never cleaned up — after an event.
Compliance Action vs. Enforcement
When the FAA educates vs. when it pursues formal enforcement.
Records Request During an Investigation
What happens when the FAA asks for your records — and why integrity matters most then.
What Records a Part 135 Operator Must Keep
The full recordkeeping picture for on-demand charter.
Frequently Asked Questions
How do you correct a maintenance logbook entry the right way?
You do not erase, white-out, or overwrite the original. The accepted method is to make a new, separate entry that states the correction, is dated with the actual date you are making it, and is signed with the same content any maintenance entry needs under 14 CFR §43.9 — a description of what is being corrected, the date, the name of the person performing the work if different, and the signature, certificate number, and kind of certificate of the person approving the corrected work for return to service where a return-to-service signature is involved. The original entry stays visible. The new entry transparently explains what was wrong and what the right information is. That sequence — leave the original, add a dated, signed correcting entry — is what separates an honest fix from something that can look like falsification.
Can you cross out or erase a wrong entry in an aircraft logbook?
As a matter of records integrity, no — you should not erase, white-out, or obliterate it. The original entry is part of the maintenance record, and making it disappear destroys the history an inspector may need to see and can make an honest mistake look like a cover-up. If a single word is plainly a slip of the pen, the conservative practice many mechanics follow is a single line through the error so it is still legible, with an initialed, dated correction — but anything beyond a trivial slip should be handled with a full, separate correcting entry rather than alteration of the original. The governing principle is the same either way: the original must remain legible and the correction must be transparent and dated. When in doubt, add a new entry; never make the old one unreadable.
What is the difference between correcting an entry and falsifying a record?
Intent and transparency. Correcting an entry means you found an honest error and fixed it openly — a new, dated, signed entry that anyone can see, with the original left intact. Falsification, the conduct the FAA treats as one of the most serious recordkeeping violations, is about intent to deceive: backdating a correction so compliance looks timely, erasing or replacing a record to hide something, or signing off work that was never done. The FAA's falsification prohibition (historically 14 CFR §43.12, now consolidated into 14 CFR Part 3, Subpart D as of November 3, 2025) reaches a fraudulent or intentionally false entry — not a good-faith error you correct properly. The way you handle the fix is itself evidence, which is exactly why the procedure matters. This is general information, not legal advice.
Can you backdate a logbook correction to the date the work was actually done?
No. A correcting entry is dated with the date you actually make the correction, not the date of the original work. You can — and should — reference the original entry and its date inside the correction (for example, "This entry corrects the May 3 entry, which listed the wrong tach time"), but the correction itself carries today's date and today's signature. Backdating an entry to make it appear that something was recorded or completed earlier than it was is precisely the kind of act that turns a paperwork problem into a falsification problem. If a required item was genuinely not completed on time, the honest record shows when it was actually completed — not a fabricated earlier date.
Who can sign a maintenance record correction?
It depends on what is being corrected. If you are only fixing a clerical detail in your own prior entry — a misspelled part number, a transposed work-order number — the person who made the entry can clarify it. But if the correction touches the substance of maintenance or a return-to-service approval, the signer must hold the appropriate authority under 14 CFR §43.9(a)(4): the signature, certificate number, and kind of certificate (for example, Mechanic, Mechanic with Inspection Authorization, or a repairman at a Part 145 station) of the person approving the corrected work for return to service. Remember the rule's own caution: the signature constitutes approval for return to service only for the work performed. You cannot retroactively approve work you did not actually do or are not authorized to approve.
What must a §43.9 maintenance entry contain so my correction is compliant?
Per 14 CFR §43.9(a), a maintenance, preventive maintenance, rebuilding, or alteration entry must contain: (1) a description (or reference to acceptable data) of the work performed; (2) the date of completion of the work; (3) the name of the person performing the work if other than the person in (a)(4); and (4) if the work is approved for return to service, the signature, certificate number, and kind of certificate held by the person approving it. The section also states that the signature constitutes the approval for return to service only for the work performed. A correcting entry has to carry that same content for whatever it is approving — you do not get to make a looser, less-complete entry just because it is a correction. See our full breakdown of what a §43.9 entry must contain for the element-by-element detail.
How do you correct an electronic or digital maintenance record?
The same principles apply, and a well-designed electronic system actually makes it cleaner. You do not edit the original record in place and let the change vanish; you add a new, time-stamped, attributed correcting version while the prior version is preserved. The electronic record still has to meet the FAA's expectations for legibility, retention, and signatures, and it must protect entries from unauthorized change. An append-only system that versions every change — rather than silently overwriting — gives you a tamper-evident history, so the correction is provably a transparent fix and not a quiet rewrite. That is the difference between an e-logbook that helps you and one that creates new questions.
I corrected an entry — do I need to disclose it to the FAA or my mechanic / IA?
An ordinary, transparent correction of an honest error generally lives in the record itself; you fix it properly and the corrected record speaks for itself. Whether anything more is warranted depends entirely on the facts — if the error meant required maintenance or an inspection was not actually performed, or if there is any airworthiness consequence, that is a maintenance and potentially a legal question, not just a paperwork one, and you should involve your IA, your repair station, or qualified aviation counsel. If you are correcting something in the middle of an FAA inquiry or after an event, do not act alone — talk to counsel first, and never alter records to clean them up. This page is general compliance-document information, not legal advice.
Make every correction provably honest: keep records that show their own history.
FileFlo keeps your maintenance and airworthiness records append-only, time-stamped, attributed, and instantly retrievable — so corrections are versioned new entries, the history is tamper-evident, and "produce and prove your records" is a button, not a scramble. It does not perform maintenance, represent you to the FAA, or replace your IA or your counsel. Starter $89/mo. Professional $299/mo. 5-day free trial — no credit card required.
5-day free trial · No credit card required · Cancel anytime
Written by Chad Griffith, Founder, FileFlo — compliance document intelligence. Reviewed June 15, 2026. This article is general compliance document-management information, not legal advice. How you correct a maintenance record can have airworthiness and legal consequences, and any situation involving an FAA inquiry, an accident or incident, a records demand, or a question of whether required work was actually performed is highly fact-specific. Nothing here is enforcement-defense or legal-strategy guidance. Before acting, consult your IA, your repair station, or a qualified aviation attorney — and verify every regulatory citation (including the post-November 3, 2025 location of the falsification rule in 14 CFR Part 3, Subpart D) against the current regulation via the Cornell Legal Information Institute. FileFlo keeps the documents that prove compliance audit-ready; it does not perform maintenance, decide airworthiness, represent you to any agency, or guarantee any outcome, and it does not claim SOC 2 certification.