In 2011, the owner of a small air-tour and air-taxi business — who was also a certificated mechanic — needed a replacement engine for one of his airplanes after a propeller strike. He bought a used engine that had been disassembled, cleaned, inspected, and reassembled. Under FAA rules, that is not yet an overhaul: an engine is only “overhauled” once it has also been test-run according to the manufacturer's instructions, which call for specific equipment and calibrated instruments.
He installed the engine and wrote in its logbook that it had been test-run per the manufacturer's directions and that the ground runs were satisfactory. He recorded the engine's time since overhaul as zero.
The FAA moved to revoke his mechanic certificate under the rule that prohibits any fraudulent or intentionally false entry in a required maintenance record. After a five-day hearing and an appeal, the NTSB affirmed the revocation. The Board upheld findings that:
The Board's order revoked his mechanic certificate, including his airframe and powerplant ratings and his inspection authorization — the credential that allows a mechanic to sign off annual inspections on other people's aircraft.
A maintenance logbook is a system of trust. The entry is the evidence: a sentence, a date, a signature, and a certificate number. Whether the engine actually ran on a test stand with calibrated gauges leaves no mark on the page. The next mechanic, the next owner, an insurer, a passenger buying a sightseeing flight — each inherits the entry and has no practical way to look behind it.
This case is not unusual in kind. The FAA regularly brings enforcement actions over maintenance entries for work that was not done, and the usual sanction is revocation. But enforcement is retrospective. It took three years, a hearing with multiple witnesses, and an accident to establish what a single observation on the day would have settled: was the engine run, or not?
SureSight replaces the sentence in the logbook with a record of the work itself. For a task like an engine test run or an inspection, that changes what an entry is.
The entry is generated by the work. The mechanic wears the glasses and performs the procedure. Computer vision confirms the observable steps as they happen — the test setup in place, the engine running, the instruments being read — and the resulting record is timestamped first-person imagery tied to that engine. A test run that never took place has no imagery, no verified steps, and so no completed record to sign.
Missing prerequisites are visible. The Board's finding turned partly on equipment: the required instruments were not there. A step-verified procedure checks for exactly that. If the required gauge is never in view, the step that depends on it stays unverified, and the gap is flagged on the day rather than argued about years later.
Every later reader can look behind the entry. A buyer, an operator's director of maintenance, an insurer, or an FAA inspector can open the evidence supporting a record instead of relying on the signature beneath it. An entry with nothing behind it stands out immediately — which also means it cannot quietly serve as the baseline for a dozen more.
Honest mechanics are protected. The same record that makes a false entry hard to sustain is proof, for the great majority doing the work properly, that they did. When an accident triggers a records review, they have something better than their word.
No system makes fraud impossible. What an evidence-backed record does is move a false entry from effortless and invisible to difficult and conspicuous.