North Atlantic operations have a particular property that makes them a useful test of any management system: the procedures change incrementally, the changes are well published, and almost nobody reads them in full. It is a slow-moving, well-signposted trap.
This is not an attempt to reproduce the current guidance material — that is published, it is authoritative, and it is revised on its own schedule. Read the source. What follows is about the second problem: how a change in the source finds its way into what your crews actually do.
Three places manuals typically fall behind
1. Contingency and offset procedures
These are the paragraphs crews read least often and need most urgently. They are also revised more often than people expect. If your manual text was written to match a guidance edition that is several revisions old, the wording may still be broadly sensible while differing in detail from what is currently published — which is precisely the kind of discrepancy that surfaces at the worst possible moment.
2. Communication and surveillance requirements
Datalink and surveillance expectations in oceanic airspace have tightened progressively. Requirements that were once optional or trial-based have become entry conditions for particular airspace. Manuals written in the earlier era often describe capability as a nice-to-have.
3. The gap between the manual and the briefing pack
Even when the manual is current, the material crews actually read before an oceanic crossing is often a separate document, maintained by a different person, on a different cycle. Two documents drifting apart is the normal state unless something actively holds them together.
The check that finds this in an afternoon
You do not need a project. Take the current published guidance, take your manual, and compare only the sections that would change what a crew does. Ignore the rest.
- Contingency procedures — wording and figures
- Airspace entry requirements — equipment and approvals
- Position reporting and datalink expectations
- What your briefing pack says about all of the above
Where the two disagree, you have found either a manual update or a training item. Both are worth logging as findings in your compliance monitoring — not because someone did something wrong, but because that is how the next revision gets caught earlier.
The underlying question
The oceanic case is a symptom, not the disease. The real question is: when any external document you depend on is revised, what in your organisation notices? If the answer is "a person who happens to subscribe to the right mailing list", you have a single point of failure with a holiday entitlement.
Making it structural
Register every external source your operation depends on — guidance material, state publications, manufacturer bulletins — as a tracked item with a named owner and a review cycle. When a revision appears, it becomes a task with a due date, not an e-mail. The review may well conclude "no change required". Recorded, that conclusion is evidence. Unrecorded, it is indistinguishable from not having looked.
Want a second pair of eyes on your oceanic procedures? Book a demo and we'll walk through it with your own setup.