The logbook shortcut before renewal

The application cannot be submitted as it stands. The declaration would be false, and the supporting logbook would overstate the dispatcher's experience.

Steps:

• Freeze the submission. Do not sign the declaration until the records are corrected and reviewed.
• Reconstruct the true record. Separate dispatch releases from flight watch, identify who actually released each flight, and correct the entries with dated annotations, initials and an explanation. Do not erase the original entries; preserve an audit trail.
• Recalculate the qualifying experience. If the corrected total still meets the renewal requirement, the application may proceed on the true figures. If it does not, Kariuki needs additional qualifying experience or a different route to renewal.
• Disclose to the Authority. The operator should notify KCAA before the audit, provide the corrected records and explain the internal finding. Voluntary disclosure is materially different from discovery by an inspector.
• Assess individual accountability. The colleague who signed for work not performed is also involved. Both should be interviewed, and any disciplinary process should follow the operator's procedures and applicable employment law.

The renewal decision belongs to the Authority; the operator's job is to present accurate information.

It is a regulatory integrity issue, even if the intent was not fraudulent. Licensing depends on trustworthy records: the Authority cannot verify competence and experience if logbooks blend different functions or carry signatures for work not done.

The distinction matters:

• Record-keeping error: A clerical mistake that is corrected promptly, with no effect on the qualification claim. Consequences are usually internal retraining and improved procedures.
• Integrity issue: The record was structured to produce a qualification outcome, with a signature that misrepresented who performed the task. Even a 'shortcut' culture can amount to a false declaration if submitted.

Consequences may include:

• For Kariuki: refusal or delay of renewal, additional checking, possible enforcement action, and reputational damage. If the false record was submitted knowingly, the exposure is greater.
• For the colleague: accountability for signing for another person's work.
• For the operator: finding of deficient records, increased surveillance and possible action against the training or compliance function.

Mitigation depends on early disclosure, correction and demonstrable system fixes. The explanation 'I did not intend to mislead' is relevant to sanction but does not make the record true.

The fix should address incentives, definitions and verification, not just remind staff to be careful.

• Define the functions. The operations manual and logbook instructions should distinguish dispatch release, flight watch, flight following and supervisory review, with separate columns and clear signature rules.
• Remove the activity target conflict. If dispatchers are pressed to meet a release count, they will classify work to satisfy it. Measure quality and compliance, not raw numbers.
• Reconcile records monthly. Compare the dispatch release log, the flight watch log and the roster. A monthly reconciliation catches drift before renewal season.
• Require independent review. The postholder or compliance officer should sample logbooks before any Authority submission.
• Control signatures. Signing for another person's work should be prohibited and auditable.
• Train and communicate. Brief all dispatchers on what counts as qualifying experience and on the consequences of false records.
• Audit the audit. Check whether the same shortcut exists in other logbooks, and report the scope of the finding to the Authority.

These controls should be documented in the compliance manager's report, with owners and dates.