Skip to content
CarrySizer

Open data

The Airline Baggage Dataset, Free to Reuse

Every cabin-bag and personal-item limit we track for 170 airlines — as one CSV or JSON file, under CC BY 4.0. Use it in articles, apps, and research; just credit CarrySizer with a link.

Downloads

Download CSVSpreadsheet-ready, one row per airline.Download JSONIncludes license metadata and data_version.

License: CC BY 4.0 — attribution required

The dataset is published under the Creative Commons Attribution 4.0 license. Reuse it freely — including commercially — with a visible credit such as “Data: CarrySizer (carrysizer.com/open-data/)” linking back to this page. Data version: · 170 airlines, 169 active.

What each field means

FieldMeaning
slug / name / iataStable airline identifier, display name, and IATA code.
country / region / typeHome country, region bucket, and business model (full service, low cost, ultra low cost, regional, charter).
operational_statusactive, suspended, or ceased. Ceased carriers stay in the file for historical reference.
cabin_bag_*Maximum cabin-bag length, width, and depth in cm, the weight limit in kg (empty when the airline publishes none), and how many cabin bags the base allowance includes.
personal_item_*Whether a free under-seat personal item is included, plus its published dimensions and weight limit where the airline states them.
strictness_editorialCarrySizer's editorial enforcement rating (lenient / moderate / strict). This is our judgement, not an airline claim.
source_url / source_title / last_checkedThe official airline page each record is based on, and the date we last verified it.

Programmatic access

The JSON file above is a stable URL you can fetch directly from scripts and apps. AI agents and assistants can also use our Model Context Protocol endpoint, which exposes the bag-fit checker and per-airline policies as callable tools:

POST https://carrysizer.com/api/mcp/        (MCP streamable HTTP, no auth)
tools: list_airlines · get_airline_baggage_policy · check_bag_fit

Please keep request volumes reasonable and cache responses; the data behind both surfaces updates at most a few times per week.