Mobility · Ezeiza

# Traffic fines in Ezeiza: what the API returns and what the data shows

Which fines Ezeiza issues between the airport and the motorway, what our data from the last year shows and how a chauffeur or air-cargo company queries the municipal court by plate.

![](/img/autores/francisco-orione/photo-240.ff6c48f047e6.webp)By [Francisco Orione](https://apinitro.com/en/authors/francisco-orione/)September 15, 2026

![A eucalyptus forest with mist and a dirt road in the dim light](/img/articulos/ar-traffic-fines-ar-b-ezeiza/hero-1200.62b417ad2bc7.webp)

Jurisdiction

Ezeiza (Buenos Aires) · [Buenos Aires](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/) · Argentina

Ezeiza is the partido of the international airport and the Ezeiza–Cañuelas motorway: chauffeur cars, air-cargo transport, trucks heading to the south of the province and private cars going to and from the terminal share access roads with cameras and municipal checks. Municipal fines are issued by the partido; motorway and provincial fines coexist on the same plates.

## Context and authority

Like every partido in Buenos Aires, it applies the [National Traffic Law 24.449](https://www.argentina.gob.ar/normativa/nacional/ley-24449-818/texto) through the provincial adhesion: fixed-unit amounts, a two-year limitation for minor offences and five for serious ones, and a defence before the court that issued the fine. Provincial fines are covered in the [Buenos Aires article](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/).

The municipal misdemeanour court rules on Ezeiza fines: lanes and manoeuvres at the airport approaches and the motorway roundabouts, speeding on Fair avenue and the rural roads, and red lights in downtown Ezeiza and Tristán Suárez. A defence is filed with the court within the period set by the notice.

## What the API returns for this jurisdiction

A plate lookup in Ezeiza walks the Ezeiza municipal misdemeanour court together with the integrated provincial sources of Buenos Aires, and returns each fine with the authority that issued it:

-   The authority that issued the fine and its number, unnormalised.
-   The date and description of the infraction, with the location if the court reports it.
-   The amount and status current at the source, with the payment conditions it publishes.
-   The link to the payment slip when the authority offers one.
-   Which sources answered and which did not, to tell a complete result from a partial one.

A result with no fines at the municipal court does not rule out provincial fines on the same plate; the response reports which sources were queried and which answered.

## What the data shows

Proprietary data**Ezeiza**September 1, 2025 – August 31, 2026

Lookups with at least one open fine

5%

Fines offering voluntary early payment

97%

Median age of fines without a recorded resolution

260 days

Median amount band

ARS 100,000 – ARS 250,000

Mix by infraction category

1.  Speeding27%
2.  Red light and right of way12%
3.  Lanes and manoeuvres46%
4.  Other infractions16%

Monthly distribution of fines

1.  Jan10%
2.  Feb7%
3.  Mar9%
4.  Apr7%
5.  May3%
6.  Jun5%
7.  Jul5%
8.  Aug1%
9.  Sep15%
10.  Oct13%
11.  Nov11%
12.  Dec12%

Sample: 1.000–5.000 fine records, 50.000+ lookups · [See the data methodology](https://apinitro.com/en/data-methodology/)

5% of the plate lookups in the period found at least one Ezeiza fine without a recorded resolution. The mix differs from the rest of the suburbs: lanes and manoeuvres explain almost half of the fines, speeding a little over a quarter and red lights just over a tenth.

The median amount band is ARS 100,000 – ARS 250,000, somewhat lower than in the neighbouring partidos, and the median age of open fines is 260 days, the highest among the southern partidos we publish: Ezeiza fines stay open for a long time.

97% of the fines offered voluntary payment at lookup time, almost all of them: the combination of old fines and available discount makes a lookup worth more here than in any other partido in the area.

## Case study: fleets that look up plates in Ezeiza

Proprietary data**Fleet cohort**September 1, 2025 – August 31, 2026

Fleet lookups with at least one open fine

6%

Fleet accounts in the sample

50

Distinct plates looked up by fleets

2,040

Sample: 1.000–5.000 fine records, 50.000+ lookups · [See the data methodology](https://apinitro.com/en/data-methodology/)

The fleet cohort, 50 accounts with twenty or more plates and 2,040 plates in total, found at least one Ezeiza fine in 6% of its lookups, in line with the general public.

For a chauffeur or air-cargo transport company, a plate lookup at the close of each month, with the result stored, solves two problems: assigning the fine to the driver while the trip log exists and paying with the discount before the court rules.

## How to integrate

A lookup is a POST with the plate and, optionally, the jurisdictions to include; the initial response accepts the job and the result arrives by status lookup or webhook, because official sources answer in seconds or minutes. The [asynchronous APIs](https://apinitro.com/en/articles/asynchronous-api-retries-without-duplicate-work/) guide explains how to retry without duplicating work and the [API page](https://apinitro.com/en/apis/traffic-fines-argentina/) details access.

JSONIllustrative example, not a contract.

```json
{
  "plate": "ABC123",
  "jurisdictions": [
    "AR-B-ezeiza"
  ]
}
```

For a fleet, the lookup is scheduled as a monthly batch and per event (onboarding, return, contract close); storing the per-source result next to the plate settles traceability before any dispute.

## Limits and considerations

-   Fines from the Ezeiza–Cañuelas motorway and the airport access may be provincial or national, not municipal; the response names the authority of each.
-   Fixed-unit amounts are converted at the value current at the source; the final amount is set by the authority at the time of payment.
-   Proprietary data comes from user lookups, not from a registry: the share of fines is skewed towards suspect plates.
-   A source that does not answer is reported as such, never as an absence of infractions.
-   The API neither pays fines nor handles defences; it delivers information to decide.

## Sources and further reading

-   [Municipalidad de Ezeiza](https://www.ezeiza.gob.ar/)
-   [Ley Nacional de Tránsito 24.449 — texto actualizado](https://www.argentina.gob.ar/normativa/nacional/ley-24449-818/texto)
-   [Agencia Nacional de Seguridad Vial — Consulta nacional de infracciones](https://consultainfracciones.seguridadvial.gob.ar/)

Related API

## [Argentina traffic fines API](https://apinitro.com/en/apis/traffic-fines-argentina/)

Bring vehicle fine checks into fleet operations, vehicle transactions and document review workflows.

[Ask about this API](https://apinitro.com/en/contact/?api=ar.mobility.traffic-fines&ref=article:ar-traffic-fines-ar-b-ezeiza)

## Related articles

[![](/img/articulos/ar-traffic-fines-ar-b/hero-640.e7b8a039b11b.webp)

Mobility

## Traffic fines in Buenos Aires Province: what the API returns and what the data shows

Two layers of authorities, one plate: how to look up provincial and municipal fines through the API and what a year of our data shows.

Read article ↗](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/)

[![](/img/articulos/ar-traffic-fines-ar-b-lanus/hero-640.184a670a483a.webp)

Mobility

## Traffic fines in Lanús: what the API returns and what the data shows

Which fines Lanús issues, what our data from the last year shows and how a fleet in the southern suburbs queries the municipal court and the provincial source in a single call.

Read article ↗](https://apinitro.com/en/articles/traffic-fines-lanus/)

[

Mobility

## How to assess the quality of a vehicle lookup

A useful vehicle lookup explains what was observed, where and when. These questions help teams turn records into clear product decisions.

Read article ↗](https://apinitro.com/en/articles/vehicle-data-quality/)

[

Integrations

## Asynchronous APIs: retry without duplicating work

A connection can fail after work has already started. Designing around the operation makes recovery clearer for users and integrations.

Read article ↗](https://apinitro.com/en/articles/asynchronous-api-retries-without-duplicate-work/)

[← All articles](https://apinitro.com/en/articles/)
