The logbook holds the rule.The mechanic holds the rest.
Aviation already writes more down than almost any other industry, and that discipline works. What doesn't get captured is the layer underneath it: the judgment people build on a specific tail number, a specific airport, a specific ground crew. OakHive gets that layer down before they go.
What walks out the door
None of this is a regulatory requirement, so none of it is logged.
OakHive interviews them before they go. This is what comes back.
The seal that never failed an inspection
A mechanic knows one tail number always needs an extra look at one particular seal. It has never failed a check, so there's no write-up. There is only the mechanic.
From the handover guide, written to whoever takes the role next.
The ground handler who actually turns a flight
A dispatcher knows which handling company turns a flight around on time at a specific airport, and which one needs a call an hour early to make it happen. That call isn't in any SOP.
From the guided session that walks the role chapter by chapter.
The discipline that works, and what it doesn't cover
Maintenance logs, checklists and regulatory records exist because a missed detail can cost lives. That discipline works. It was never designed to record which handler to call an hour early.
From the chat, answering after they have gone.
The exception nobody can explain
Every operation has a process with an exception that made sense the day it was made. Whoever made it is the only one who can say why, and the paperwork was never designed to hold the reason.
From the manager's summary, ready before the last day.
Who to interview
The line mechanic who's worked the same tail numbers for years. The dispatcher who knows every station's ground crew by name. The person everyone asks instead of opening the manual.
The paperwork keeps the rule. OakHive keeps the rest.
Questions aviation teams ask
No. Maintenance logs, checklists and regulatory records stay exactly where they are. OakHive records the layer the paperwork was never designed to hold: the operational judgment a mechanic or dispatcher built over years on specific aircraft, airports and crews.
Up to two hours, in one sitting or spread over a few days, and nothing to prepare. OakHive asks about the role and follows up when an answer is vague. Smaller roles finish well inside that; two hours is the ceiling.
A handover guide written to them, a guided session that teaches the role chapter by chapter, and a chat that answers from what the leaver said. If the question touches something the interview never covered, the chat says so rather than guessing.
Bring us the questionyour company keepsanswering twice.
Thirty minutes, no deck. You describe something your team has explained more than once, and we show you what OakHive does with it.
We are taking on a small number of companies at a time, so this is a conversation rather than a signup.