How to access Boeing 737 fleet data through an API. Query the global 737 fleet by variant, airline, country of registration and age. Analyze operator concentration, fleet age distribution and live 737 operations using the AirLabs flight data API.
The Boeing 737 is the most produced commercial jet in history and by every practical measure the most common airliner in operation today. For anyone whose business touches commercial aviation — leasing companies tracking portfolios, MRO providers segmenting service markets, aviation analysts modelling capacity, insurance underwriters assessing risk, aviation media producing data-driven coverage — the global 737 fleet is not a curiosity but a core dataset.
The commercial 737 fleet spans several actively operated variants: the Next Generation family (737-700, -800 and -900), the newer 737 MAX family (MAX 7, MAX 8, MAX 9 and MAX 10), and older Classic variants still in service with cargo and secondary operators. Understanding how these variants distribute across operators, countries and age brackets is the input to almost every serious analysis of the narrowbody market — market entry studies, fleet renewal forecasts, spare-parts market sizing, competitive equipment benchmarking.
This guide covers how to query 737 fleet data through the AirLabs platform, how to break the global fleet down by variant and operator, and how the same infrastructure supports live tracking of any 737 in the air right now — using only documented AirLabs endpoints.
"The 737 fleet is the closest thing narrowbody aviation has to a shared reference dataset. Its scale means that any analysis of a global carrier, a regional market or the narrowbody segment as a whole starts with the 737 composition. The data is not exotic, but structured access to it changes what you can do with it."
Before querying the fleet, it helps to know how the different 737 variants are identified in aviation data. The AirLabs API returns two type codes for every aircraft — the ICAO designator (in the icao and aircraft_icao fields) and the IATA code (in the iata field) — alongside the plain-language model name.
For the actively operated 737 family, the common codes are:
| Variant | ICAO | IATA | Family |
| Boeing 737-700 | B737 | 73G | Next Generation |
| Boeing 737-800 | B738 | 738 | Next Generation |
| Boeing 737-900 / -900ER | B739 | 739 | Next Generation |
| Boeing 737 MAX 7 | B37M | 7M7 | MAX |
| Boeing 737 MAX 8 | B38M | 7M8 | MAX |
| Boeing 737 MAX 9 | B39M | 7M9 | MAX |
| Boeing 737 MAX 10 | B3XM | 7M0 | MAX |
Older Classic variants (737-300, -400, -500) still appear in cargo and secondary operator fleets and use codes B733, B734 and B735.
Knowing the codes matters because the AirLabs Fleets Database accepts type codes as filter parameters. That is the single lever that lets you slice the global fleet by any specific 737 variant — or by the whole family.
The core lookup is a single call to the Fleets Database filtered by the aircraft type code. To retrieve every 737-800 in the database:
GET https://airlabs.co/api/v9/fleets?icao=B738&api_key={KEY}
[{
"hex": "A9D286",
"reg_number": "N732AN",
"flag": "US",
"airline_icao": "AAL",
"airline_iata": "AA",
"icao": "B738",
"iata": "738",
"model": "Boeing 737-800",
"engine": "jet",
"engine_count": "2",
"manufacturer": "BOEING",
"type": "landplane",
"category": "M",
"built": 2015,
"age": 11,
"msn": "31549"
}]Each response record represents one airframe, with the operating airline (airline_iata), country of registration (flag), build year (built), current age (age) and manufacturer serial number (msn). The category: "M" denotes the medium wake turbulence category — standard for a 737-sized narrowbody.
Filtering by a single variant is a narrow slice; the broader 737 family is queried variant by variant, aggregating results in your application layer. Using _fields keeps the responses lean when you only need summary attributes:
https://airlabs.co/api/v9/fleets?icao=B738&_fields=reg_number,airline_iata,flag,built,age&api_key={KEY}For per-operator drill-downs, combine the aircraft type filter with the airline filter:
https://airlabs.co/api/v9/fleets?icao=B738&airline_iata=AA&api_key={KEY}This returns American Airlines' 737-800 fleet specifically. Swapping airline_iata=AA for airline_iata=RYR (Ryanair) or airline_iata=SWA (Southwest) gives the equivalent slice for those carriers — the two operators historically most associated with the 737-800 and 737 MAX 8.
Once the raw fleet records are in hand, several analytical patterns produce the metrics that fleet consumers actually need.
Operator concentration. Grouping the 737 fleet by airline_iata produces the distribution of aircraft across operators. A small number of carriers typically account for a disproportionate share of any 737 variant — 737-800 is dominated by low-cost carriers globally, 737 MAX 8 has a concentrated set of launch customers, 737-900ER is heavily used by a smaller set of North American operators. The concentration profile is one of the primary inputs to market sizing for leasing, MRO and parts distribution.
Age distribution. The age field turns the fleet into an age histogram. Buckets of 0–5, 5–10, 10–15, 15–20 and 20+ years reveal where the fleet sits in its life cycle. A 737-800 fleet heavily concentrated in the 12–18 year range is a fleet approaching renewal; a MAX 8 fleet concentrated in 0–5 years is a fleet in growth. These profiles inform fleet renewal forecasts and heavy-maintenance market timing.
Geographic distribution. The flag field (ISO 2-letter country of registration) groups the fleet by country. For 737 analysis, this often shows North American dominance for -700 and -900 variants, and a more distributed global picture for -800 and MAX 8. Regional carriers of India, Southeast Asia and Latin America increasingly appear in the newer variant totals, tracking narrowbody market growth in those regions.
Serial number tracking. The msn field provides the manufacturer serial number, which is the permanent identifier a leasing company or asset manager uses to track individual airframes across owners and lessees. Combined with built, this allows an aircraft's full ownership and utilization history to be reconstructed from documentary sources.
For a broader treatment of these analytical patterns applied to any airline's fleet, see our Airline Fleet Data Guide. For the country-of-registration dimension in more detail, see Aircraft Fleet Data by Country.
Beyond static fleet composition, the Real-Time Flights API accepts the same type code filter and returns 737s currently airborne. Filtering by aircraft_icao=B738 returns every 737-800 in the air right now with its live position:
GET https://airlabs.co/api/v9/flights?aircraft_icao=B738&api_key={KEY}
[{
"hex": "A9D286",
"reg_number": "N732AN",
"flag": "US",
"flight_iata": "AA100",
"dep_iata": "DFW",
"arr_iata": "MIA",
"airline_iata": "AA",
"aircraft_icao": "B738",
"lat": 32.55,
"lng": -95.10,
"alt": 10972,
"dir": 120,
"speed": 830,
"status": "en-route"
}]This is the live-operations view of the fleet. Each response record combines the aircraft identity (from the ADS-B feed the platform ingests) with position and flight number. For analytics workloads that need to correlate live 737 activity with static fleet data, the hex (ICAO 24-bit address) and reg_number in the live response are the join keys back to the Fleets Database record.
Adding a geographic bounding box narrows the live view further. For example, filtering to a European bounding box shows 737 operations across European airspace, useful for regional capacity monitoring.
Being explicit about what each endpoint answers avoids the most common integration mistake in aircraft-type queries.
The Fleets Database returns the catalogue of aircraft — every 737-800 the platform tracks, with static attributes (build year, model, manufacturer, MSN) that do not change from day to day. This is the right endpoint for fleet composition analysis, market sizing, age distributions and operator counts.
The Real-Time Flights API returns the live operational view — 737s currently airborne, with position, altitude and flight number. This is the right endpoint for operational monitoring, live dashboards and any application that needs to see what is happening right now.
For flight-by-flight lookups (which 737 is operating a specific scheduled flight), the Flight Information API returns the aircraft type together with the flight status; the pattern is covered in detail in our How to Find Aircraft Type by Flight Number guide.
Several industries consume 737 fleet data as a structured input to their workflows:
Leasing companies track 737 airframes across their portfolios by msn and reg_number. Fleet composition data supports lease-return analysis, remarketing strategies, portfolio benchmarking and secondary-market pricing. Because the 737 is the most common narrowbody, most large lessors have significant 737 exposure — and require systematic access to the operating fleet.
Maintenance, Repair and Overhaul providers and aftermarket parts distributors size their addressable market by aircraft type and age. A 737-800 fleet global age distribution directly informs heavy-check demand forecasting, spare-parts inventory planning and sales territory design. The same segmentation applies to MAX variants as their fleets mature.
Equity analysts covering airlines and aircraft manufacturers use fleet composition data to model airline capacity, evaluate CAPEX plans and benchmark operators. The concentration of any 737 variant across a small set of carriers means that changes at those carriers ripple through the aggregate fleet metrics visibly.
Aviation insurers segment risk by aircraft type, age and operator. 737 fleet data provides the exposure baseline — how many airframes of each variant, at what age, with which operators. Combined with the Airlines Database safety records (iosa_registered, accidents_last_5y), this supports risk-based pricing models.
Consultants preparing market entry studies, capacity plans or fleet renewal recommendations use the 737 fleet as the anchor dataset for narrowbody analysis. Cross-country comparisons of 737 age and variant distribution reveal where fleets are aging (renewal opportunity) and where they are growing (new-aircraft demand).
Trade media and specialist aviation publications increasingly produce data-driven coverage of fleet changes — MAX return-to-service progress, retirement of older variants, operator fleet updates. Structured API access to the 737 fleet supports this reporting without manual data collection from press releases and airline websites.
A few patterns make 737 fleet queries efficient in production:
B737, B738, B739, B37M, B38M, B39M) and combine the results locally for whole-family analysis._fields to keep responses lean. For fleet-composition analytics you typically need reg_number, airline_iata, flag, built and age. Requesting only these fields keeps responses compact and processing fast.hex (ICAO 24-bit) and reg_number are the reliable join keys. Both appear in Fleets and Real-Time Flights responses.age field is calculated at query time from built. For long-lived analyses, prefer built (immutable) over age (relative to now) as the storage field.Whether you are sizing an MRO market, tracking a leasing portfolio, benchmarking narrowbody operators or building a fleet analytics product, the AirLabs API provides structured access to the 737 fleet — every variant, every operator, every airframe with its identifying attributes — through documented REST endpoints.
Our Developer API allows you to create a custom experience for your users and increase the value of your product:
reg_number, hex, flag, airline_iata, built, age, msn, manufacturer, model and category.icao + airline_iata, icao + flag) for per-operator or per-country 737 subsets._fields for lean responses in analytics pipelines.You can try it right now without any obligation! Get a free flight API plan and see for yourself that we have exactly the data you need!
If you need more information, don't hesitate to contact us. We are always happy to chat with our customers and are sure to find a customized solution for each request.
Explore AirLabs, or create an account instantly and start using API.
Get FREE API Key