IOGP 690
The offshore helicopter baseline
IOGP Report 690, Offshore Helicopter Recommended Practices, first issued June 2023 and maintained through version 1.3 TR1 (July 2025), is the recommended-practice set most oil and gas operators audit rotary contracts against.
5 sections
Scope of the audit
IOGP 690 is structured around safety management system, aircraft operations, support operations, engineering, and helicopter and equipment — an offshore contract has to satisfy all five, not just flight operations.
SGRAO Part 690
Operator-specific overlay
Major operators layer their own criteria on top: Shell's Group Requirements for Aircraft Operations Part 690 (Rev 1.0, 20 September 2023) must be read together with IOGP 690 v1.3, and adds further compliance criteria and variations.
24/7
Nigerian entry-point airport hours
All five Nigerian airports of entry (Lagos DNMM, Abuja DNAA, Port Harcourt DNPO, Kano DNKN, Enugu DNEN) operate 24 hours except as advised by NOTAM, while smaller fields typically run sunrise to sunset, roughly 0600–1700Z.
Figures are drawn from the published sources listed at the end of this article. Permit lead times are indicative and set by each civil aviation authority.
The chain, not the aircraft
An offshore rotation is a sequence: personnel arrive onshore, documentation and survival training validity are confirmed, weights are captured, the manifest is built, the aircraft and crew are positioned, the weather and deck are assessed, the flight operates, and the returning shift reverses the whole process. Each step depends on the one before it, and most of them are not aviation steps at all.
This is why fleet capacity alone never solves reliability. Adding aircraft to a chain with a coordination failure produces the same delay with more cost. The lever that moves outcomes is the sequencing and ownership around the flight, not the flight itself.
Start from the window
Offshore movements are constrained by daylight, weather, sea state, deck availability and crew duty limits. Those constraints define a usable window, and the window — not the roster — should drive the plan. When a rotation is designed from the roster forward, the window becomes something to hope for. When it is designed from the window backwards, every upstream step gets a deadline it can be held to.
In practice this means the ground programme is scheduled to deliver a complete, weighed, briefed group at the heliport with enough margin to absorb a normal amount of friction, and no more. Excess margin has its own cost: personnel waiting onshore, duty time consumed before the first departure, and pressure to compress the return leg.
Fail early, on the ground
The cheapest place to discover a problem is before anyone travels. Expired offshore survival or medical validity, an identity document that does not match the manifest, a weight that changes the load plan, a permit or pass that has lapsed — each of these is a minor administrative issue on the day before and a cancelled rotation on the day.
- Validate training, medical and identity documents against the roster the day before travel, not at check-in.
- Capture actual weights, including baggage and tools, early enough to finalise the load plan without a re-manifest.
- Confirm deck availability, lighting and any concurrent operations with the facility, not only with the client's onshore office.
- Check that pass, escort and security requirements at the departure heliport match the group as it is actually composed.
One decision owner, one cut-off
Rotations degrade badly when the go decision is distributed. Multiple parties each hold part of the picture — the operator holds duty and serviceability, the facility holds the deck, the client holds the shift requirement, the flight support team holds the plan — and in the absence of a named owner, everyone waits for someone else's confidence.
The fix is procedural, not technical. Name the decision owner for each rotation, state the cut-off time at which the movement goes, delays, splits or stands down, and make sure every party knows both before the day begins. A decision made at the cut-off, even an uncomfortable one, protects the shift handover. A decision deferred past it rarely does.
Design the recovery, not just the plan
Any rotation that matters should have a stated recovery path: a second wave later in the window, a split movement that carries safety-critical personnel first, an onshore hold plan with accommodation and transport already identified, or a held slot on the following day. Recovery options are inexpensive when arranged in advance and disproportionately expensive when improvised.
The same applies to communication. When a rotation slips, the operational cost is often smaller than the trust cost of a client discovering it late. A single coordinating point that tells everyone the same thing at the same time is part of the design.
How we work it
Earotine coordinates offshore and remote-site rotary support as a logistics problem with an aviation component: window first, ground programme built backwards from it, documentation validated before travel, a named decision owner, a stated cut-off and a pre-agreed recovery path.
Rotary capacity is arranged through approved operators, and our role is the coordination layer that keeps the chain intact — manifests, weights, permits, ground handling, transport and the single line of communication that holds it all together.