Paying Air Passenger Duty: use the current passenger band and the 15-character X reference

Air Passenger Duty is paid by aircraft operators for chargeable passengers departing from UK airports under the applicable rules. The amount depends on destination band, class of travel and aircraft type, while the payment deadline is set by HMRC's notice to file and can receive a seven-day extension for specified electronic methods.

Use the 2026 to 2027 APD band and class rates

From 1 April 2026, reduced rates are £8 domestic, £15 Band A, £102 Band B and £106 Band C. Standard rates are £16, £32, £244 and £253 respectively. Higher rates for the relevant large private-jet category are £142, £142, £1,097 and £1,141.

Use the rate applying to the passenger's flight date and category, not the payment date.

Destination bands are based on distance categories

Current APD uses Domestic, Band A up to 2,000 miles, Band B from 2,001 to 5,500 miles and Band C above 5,500 miles, measured under the statutory framework.

Passenger class and aircraft characteristics also affect the rate, so finance should receive a passenger-category summary rather than calculate from ticket revenue.

The notice to file tells the operator when payment is due

HMRC's payment guidance says the notice to file states the deadline. Operators using the Occasional Operator Scheme instead pay within seven days of the flight under that scheme.

Calendar the exact date for each return rather than assuming every aviation tax payment falls on the same day.

Specified electronic methods get seven extra calendar days

HMRC extends the normal payment deadline by seven calendar days for Direct Debit, Faster Payments, CHAPS or Bacs, subject to the guidance.

Use the exact notice and calendar. Do not apply the concession automatically to the Occasional Operator Scheme.

Use the 15-character reference beginning with X

The operator uses the X-prefixed reference from the notice to file. Occasional operators obtain their reference from HMRC and reuse it for that scheme.

An incorrect reference can delay allocation and make a paid liability appear outstanding.

Reconcile passenger data, exemptions and the bank payment

Keep passenger counts by destination band and class, exemptions, return, reference and bank evidence together.

Submit the return even where no duty is due if HMRC requires it. Filing and payment remain separate compliance steps.

Worked example: an airline carries 1,000 chargeable reduced-rate passengers in Band B after 1 April 2026. At £102 each, the gross APD for those passengers alone is £102,000 before adding other bands and classes. Finance should be able to bridge the final return amount from passenger data rather than infer it from ticket receipts.

Build future-rate changes into commercial pricing models but keep return calculations tied to the travel date. APD rates for 2027 have already been published, making period labelling important in budgeting systems.

Check Direct Debit limits and setup time for large operators. Payments above £20 million require another route under current HMRC guidance, and a first Direct Debit needs enough lead time to be established.

Worked example: an operator carries 600 reduced-rate Band A passengers and 100 standard-rate Band A passengers after 1 April 2026. The APD for those passengers is £9,000 plus £3,200, or £12,200, before adding domestic, Band B, Band C or higher-rate passengers.

Use the booking system to classify seat class and destination automatically, but review exceptions manually. Upgrades, through tickets and unusual aircraft configurations can affect which rate applies.

Keep Occasional Operator Scheme payments separate from normal periodic returns. The seven-day-after-flight rule and reference process differ, so finance should not copy the standard airline calendar onto occasional flights.

Reconcile passenger refunds and no-shows where APD treatment changes. Ticket revenue can remain in the system even when the passenger did not travel, while APD is linked to chargeable carriage under the statutory rules.

For charter and mixed-fleet operators, maintain aircraft data alongside passenger data because higher-rate treatment depends partly on aircraft characteristics. Finance should not determine the rate solely from ticket class.

Keep the payment reference and notice-to-file centrally accessible. Airline operations can be distributed across several offices, but the HMRC payment should not depend on one employee retaining the only copy of the notice.

Use booking and departure data rather than cash-ticket receipts when calculating APD. Advance ticket sales can occur months before the passenger actually flies, while the duty follows the relevant carriage and rate rules.

Where several airlines or operating certificates sit in one group, keep APD registrations and payment references by legal operator. Central treasury can fund the cash, but the reference must correspond to the entity and return that generated the duty.