Short answer. Pencil-whipping means marking a check complete without doing it. The most useful signal is time: when a procedure that should take is marked complete in a few minutes, it should be reviewed.
Definition. Pencil-whipping is marking a check or inspection as complete without actually doing it.
What pencil-whipping is and why paper cannot show it
A paper procedure shows a tick and a signature. It cannot show when each item was checked, how long the procedure took, or whether the technician was at the equipment. So a procedure done properly and a procedure filled in at the desk look the same. A well-designed procedure is easier to follow than to fake, so crews actually use it. When a procedure feels useless, they pencil-whip it and work from memory.
In aviation, re-entering a checklist at the wrong point after an interruption is a well-known error. Many cockpit checklists use a do-verify model, where the crew does the steps from memory and then runs the checklist to confirm them. ICARUS Ops is built around challenge-response: the EES presents one step at a time, in order, so each step is read, done and recorded before the next appears. Do-verify fits only tasks that are high frequency and low consequence. Challenge-response is the right methodology for almost all consequential procedures, no matter how often they are done. Electronic checklists such as the Boeing 777 ECL and the ICARUS Ops EES eliminate wrong-point re-entry: a checklist cannot be closed while any item is undone, and a deferred item moves automatically to where it belongs, as when a 777 item deferred from the descent checklist reappears on the landing checklist. Electronic checklists also cut errors overall. An unpublished Boeing simulator study of an early prototype found a 46 percent decrease in total checklist errors compared with paper (Boorman, ICAO Journal, 2001).
ICARUS Ops was founded by former Naval Aviators and airline pilots who used checklists in high-risk operations. We brought the same discipline and checklist technology to the field — clear steps, right order, confirmation of critical points, and records of every action.
Signals to look for
- Completion time far below the expected time.
- Many steps with the same time stamp.
- Missing photos on steps that need them.
- Identical readings every day.
Example
For example, a 40-minute procedure marked complete in 3 minutes is a red flag.
On paper, that would never have been caught until an incident occurred and someone went back to check the cameras.
At ICARUS Ops, we believe in making procedures so high-quality that technicians enjoy using them, and the system records accurate, verifiable data.
How to set a realistic time for each procedure
In ICARUS Ops, the procedure author sets an estimated completion time for each procedure. As crews run it, the ICARUS Ops EES platform records how long each run actually takes and builds an average. That makes it easy to benchmark every run against the average and spot anomalies, like a 40-minute procedure marked complete in 3 minutes.
What to do with a flag
- Review the record.
- Ask the technician what happened; a fast procedure is not always a skipped one.
- Coach where needed.
- Fix the procedure if a step is unclear or impossible to do.
Where ICARUS Ops fits
The ICARUS Ops Error Elimination System (EES) captures date-time curves for every step and procedure. Anomalies are flagged in both directions, so HQ can review procedures that were done too fast, or that took far longer than expected.
Demos are for teams actively evaluating software for deployment.
References
- Daniel Boorman (Boeing Commercial Airplane Group), “Today’s electronic checklists reduce likelihood of crew errors and help prevent mishaps,” ICAO Journal, vol. 56, no. 1, 2001.
Eliminating the often undetected risk of pencil-whipping.