UK Airport Drop-Off Charges Data: Download CSV & JSON

What you get

The drop-off and pick-up charges at 29 UK airports, each checked against a source and dated, as CSV and JSON. It is free to download and reuse, including commercially, under CC BY 4.0: all we ask is a credit. The data was last updated on 2 Oct 2026; the last full check of every airport was on 25 Aug 2026.

Downloads

File	What's in it
airports.csv	One row per airport, 12 columns: the charge, the time it covers, the overstay cost, the free alternative, and when and how it was checked. Opens in any spreadsheet.
airports.json	The full record for all 29 airports: 37 fields in all, up to 36 for any one airport. Everything in the CSV plus payment details, pick-up rules, Blue Badge terms, fee history and sources.
updates.json	The change log: 14 dated entries since 6 Jan 2026, each with its source, except the full review.

The files sit at fixed addresses, need no sign-up or key, and can be fetched from any website (cross-origin requests are allowed).

What's in the files

These 12 columns are in the CSV. All but alt_detail are in the JSON too.

airport: Airport name.
iata: Three-letter IATA airport code, for example LHR.
region: UK nation or English region.
fee_gbp: The charge in pounds for the drop-off zone nearest the terminal. 0 means it is free.
free_minutes: The time allowance in minutes: how long the charge covers, or how long is free at an airport that doesn't charge. 0 means a charge per entry with no time allowance. The name is historical.
window_note: The charge and its time limit in plain English.
overstay: What a longer stay costs.
free_alternative: The airport's own free or cheaper place to drop off. In the CSV this is its name, or "None". In the JSON it is an object: exists, name, detail, transfer (how you get to the terminal from it) and, for some airports, allow (how much extra time to leave).
alt_detail: CSV only: a description of the free alternative. In the JSON this is free_alternative.detail.
verified: The date this airport's figures were last checked, as YYYY-MM-DD.
verification: official: confirmed on the airport's own website. secondary: confirmed against published comparisons instead.
source: The website the figures were checked against.

The JSON adds these. A field is left out of a record when it doesn't apply or we have nothing checked to put in it. It is never filled with a guess.

payment: How you pay, in a line. In every record.
pay_type pay_methods pay_deadline pay_penalty pay_note: Payment in detail: whether you pay at a barrier or afterwards (postpay), the ways to pay, the deadline, and what happens if you miss it. In 25 of 29 records.
pay_url: The official payment website, where there is one. In 8 of 29 records.
dropoff_location: Where the drop-off zone is. In every record.
pickup_note: The rules and cost for picking someone up. In 26 of 29 records.
exemptions: Blue Badge terms and other exemptions. In 17 of 29 records.
previous_fee_gbp previous_fee_year: An earlier charge and the year it applied, for fee history. In 16 of 29 records.
official_check: The official page to check the charge on. In 28 of 29 records.
terminals terminals_note: The zone at each terminal, at airports with more than one. In 3 of 29 records.
rail_mode rail rail_source: The rail or tram link to the airport, with its source. In 11 of 29 records.
colour colour_source: A practical detail about the drop-off, with its source. In every record.
fact fact_source: A notable fact about the airport, often from its history, with its source. In every record.
lat lon: The airport's coordinates. In every record.
note: An extra remark about the record. In 9 of 29 records.
machines_onsite: True where an airport that charges afterwards also has pay machines on site. In 1 of 29 records.

The JSON file also has a meta block with the title, licence, the date of the last full review and what the two verification levels mean. In updates.json each entry has a date, the airport's iata code (empty for a full review), a type (correction, new-charge, review and rise), the text and a source (empty for a full review). The same file lists what is planned next under upcoming.

Licence and how to credit

The data is published under the Creative Commons Attribution 4.0 licence. You can copy it, republish it and build on it, commercially or not, as long as you give credit. A line like this is enough:

Data: airportdropoffcharges.co.uk, last updated 2 Oct 2026. CC BY 4.0.

Online, a link is the credit we'd like most: to the airport's page if you quote one airport (for example https://airportdropoffcharges.co.uk/heathrow/), or to this page for the whole dataset. For a formal reference: Airport Drop-Off Charges, UK Airport Drop-Off Charges Dataset, last updated 2 Oct 2026, https://airportdropoffcharges.co.uk/data/.

How the data is collected

Each charge is read from the airport's own website and recorded with the date and the page it came from. 28 of the 29 airports are confirmed that way; the other one is marked secondary. Every row has its own verified date, all 29 are re-checked every quarter, and changes in between are recorded in the log. The methodology has the full process.

The files on this page are the live ones: they change whenever the site does. The copies on GitHub, Kaggle and Hugging Face are snapshots and can lag behind.

Other ways to use it

Corrections

If a figure is wrong or out of date, email hello@airportdropoffcharges.co.uk with the airport and a link to the airport's page. It is checked against the official source, fixed in the files above and logged with its date.

The data: your questions

Can I use this data for free?

Yes. The dataset is published under CC BY 4.0, so you can copy, republish and build on it, commercially or not, as long as you credit airportdropoffcharges.co.uk.

How do I credit the data?

A line such as "Data: airportdropoffcharges.co.uk, last updated 2 Oct 2026. CC BY 4.0." is enough. Online, link to the airport's page if you quote one airport, or to the data page for the whole dataset.

How up to date is the data?

Every row carries the date it was last checked. All 29 airports are re-checked every quarter: the last full check was on 25 Aug 2026, and the most recent change was recorded on 2 Oct 2026.

Is there an API?

There is no key or sign-up. The CSV and JSON files sit at fixed addresses and can be fetched from any website. AI assistants and developers can also query the data through the site's MCP server.

Method & corrections

Every charge on this page is checked against the airport's own published charges and stamped with the date we checked it. We re-verify the full dataset quarterly, and after any reported change — see how we check every figure and who maintains the site.

Spotted an error? Email hello@airportdropoffcharges.co.uk — corrections are made visibly and dated. The dataset behind this page is free to reuse with attribution: JSON · CSV (CC BY 4.0) — about the data.