- Verification is a pre-contract activity. If you cannot verify, you cannot contract.
- Verify the operator (AOC holder), the specific tail (listed on the AOC) and the flight profile (within scope of authority and insurance).
- Independent safety intelligence supplements verification; it does not replace it.
- Keep a dated, signed verification file for every engagement. Version it if anything changes before departure.
- Refuse and record any arrangement that cannot be reconciled to a verified AOC.
Why verification matters
Operator verification is the point at which a charter transaction becomes either professional practice or, in the worst case, aiding an illegal charter. It is the pre-contract activity on which every downstream protection — the contract, the insurance, the safety case — ultimately depends.
A verification file also protects the broker. When a regulator, a client or an insurer asks why an operator was chosen, the honest and complete answer is the file. If the file does not exist, the answer is a story, and stories do not hold up in disputes.
What you are verifying
Three things, in this order: the operator, the aircraft, and the flight profile. Each answers a different question and each is capable of failing independently. A trusted operator with the wrong tail is not a lawful flight. A correct tail with a mismatched flight profile is not an insured flight.
- The operator holds a current Air Operator Certificate (AOC) or equivalent commercial authorisation in a recognised jurisdiction.
- The specific aircraft (by registration and serial number) is listed on that AOC for the operation intended.
- The flight profile — passenger count, route, aerodrome performance, night or IFR requirements — is within the scope of the operator's authority.
- The operator's insurance responds for that flight profile and passenger count, with limits appropriate to the mission.
- There is no pending enforcement or suspension action that would affect the flight.
A defensible verification method
A defensible method is repeatable, dated, and produces evidence you can show to a third party without further explanation. It does not depend on the memory of a specific person. It does not depend on a favour from a specific operator.
In practice, most professional brokerages combine three sources: the operator's own documentation (AOC, ops-spec pages, insurance certificate), a primary-source check against the issuing authority's public register where available, and — for higher-risk profiles — an independent third-party safety report.
Confirming the aircraft on the AOC
An AOC lists specific aircraft. A tail that is not on the AOC on the day of departure is not authorised for commercial operation under that certificate, whatever the operator's other aircraft may be permitted to do. Confirm the registration on the operations specifications and, where possible, cross-check against the aviation-authority register.
If an operator is proposing to sub-charter to another AOC-holder, verify the sub-charter chain end-to-end. Each link must be lawful in its own jurisdiction. Do not accept a verbal reassurance in place of the sub-charter agreement.
Insurance scope and limits
Obtain a current insurance certificate that names the operator, identifies the aircraft, and states the passenger and third-party liability limits. Confirm that the policy responds for the specific flight profile — some policies exclude certain geographies, aerodromes or operations without explicit endorsement.
Where the client's contract requires the broker or client to be named as an additional insured or a loss payee, obtain the endorsement in writing before contracting. Verbal confirmation is not an endorsement.
Using third-party safety intelligence
Third-party safety programmes provide useful additional intelligence: audit outcomes, incident histories and standardised safety ratings. Treat them as one input among several. They do not replace primary-source verification and they do not, by themselves, discharge a broker's professional duty to select operators competently.
Where you rely on a third-party rating, record which rating, from which programme, on which date. Ratings change. A snapshot taken twelve months ago is not the same as a current rating.
Recording the verification
The verification file for a single engagement is short and specific. It names the operator, the AOC number and issuing authority, the aircraft registration, the flight profile, the insurance certificate reference and expiry, the date and source of any third-party intelligence relied on, and the person at the brokerage who signed the verification off.
Retain the file for at least the period required by local record-keeping rules or the applicable insurance policy, whichever is longer. Where a specific engagement generates unusual documentation — sub-charter agreements, additional endorsements, unusual sanctions checks — retain those alongside.
When to refuse the arrangement
Refuse any arrangement in which the aircraft owner appears to exercise operational control while the flight is presented as commercial charter. Refuse where the operator will not or cannot provide the documentation needed to verify authority, tail and insurance. Refuse where the sub-charter chain cannot be reconstructed on the record.
Record the refusal, the reason and the date. A refusal file is professional evidence, not a liability. Regulators and insurers read them as a sign of a functioning practice.
Practical checklists
- Current AOC copy retained.
- Ops-spec pages showing intended aircraft.
- Insurance certificate with current expiry.
- Sanctions screening of operator entity and beneficial owners.
- Notes on any recent enforcement or public safety action.
- Aircraft registration confirmed on AOC on the day of verification.
- Flight profile confirmed within authority scope.
- Insurance confirmed responsive to profile and passenger count.
- Sub-charter chain (if any) documented and verified.
- Sign-off recorded with name, date and version.
Frequently asked questions
- Can I rely on a broker portal that says an operator is verified?
- You can use it as an input, but you cannot rely on it exclusively. A portal cannot know whether a specific tail is on a specific AOC on a specific day. Your professional duty is to verify the engagement, not the operator in the abstract.
- What if the operator refuses to share their AOC?
- Decline the engagement. An operator that will not evidence its own authorisation is not an operator you can lawfully sell to a client. Record the refusal and move on.
- How close to departure should I re-verify?
- For engagements contracted well in advance, re-check the aircraft listing and insurance within a short window before departure — typically inside seven days. Regulatory changes, tail transfers and insurance lapses all occur between contracting and flight.
- • Verify operator, tail and flight profile — in that order.
- • Use third-party intelligence as an input, not a substitute for primary-source checks.
- • Record who verified what, when, and against which document.
- • Re-verify close to departure for engagements booked in advance.
- • Refuse and record any arrangement that cannot be reconciled to a verified AOC.