← Technical Analysis
Cadillac in the Field · Methodology

Methodology

Cadillac in the Field · 2026 F1 Season · V2 Field-Comparison Build

V2 of this analysis ranks every driver in the 2026 F1 field (22 drivers across 11 teams) on a single physics-anchored downforce indicator: minimum apex speed at every detected corner. Higher vmin = more grip = more downforce. The driver who carries the most apex speed has the most car under them. This page documents how the canonical corner detection works, how each driver's best-lap phase split is computed (with a strict closure invariant), how the per-driver per-corner metrics are derived, and how the field-comparison cohort palette is laid out.

1 · Data Source

Telemetry comes from FastF1 v3.8.2, which mirrors livetiming.formula1.com with a fallback to the Jolpica Ergast API. For each completed 2026 race we pull race-session laps for every driver, then for each driver:

  1. Filter to clean laps only — pit-in / pit-out excluded, slower than 1.08 × the driver's fastest dropped.
  2. Pick the driver's single fastest clean lap. That one lap drives the phase split (so closure is exact).
  3. Pick the next-4 fastest clean laps and median-stack them onto the same 5 m grid for the speed-trace and per-driver κ computations (smoother than single-lap GPS).
  4. Resample all telemetry onto a common 5 m grid in lap distance.

Telemetry channels used: Speed (km/h), Throttle (%), Brake (0/1), Distance (m), X and Y (track coordinates, FastF1's native 0.1 m units — converted to metres for curvature math). Sampling rate is 4 Hz for car data, which gives ~15 m localisation uncertainty at 250 km/h — fine for corner-level analysis.

Data-quality gate. If a driver's best-lap ds/v integral disagrees with FastF1's reported LapTime by more than 1 s, the resampled telemetry is corrupt (FastF1 occasionally returns laps with bins populated by straight-line speeds inside corner windows). Those drivers are excluded from the field-comparison rankings for that race. Mid-race position-stream dropouts (frozen GPS coordinates, seen at Monaco) are screened the same way — laps whose XY trace freezes are rejected before they can poison a driver's median racing line. Across the 9 races this gate, plus DNS/early-DNF and telemetry exclusions, leaves 186 of 198 possible driver-races in the field-rank cohort. At Austria only 21 of 22 cleared the gate — Bottas's two-lap sample was rejected outright — and both Cadillac cars are additionally excluded from the season aggregate (see the Austria DNF note below).

Races analysed: Australia (R1, Mar 8), China (R2, Mar 15), Japan (R3, Mar 29), Miami (R4, May 3), Canada (R5, May 24), Monaco (R6, Jun 7), Barcelona (R7, Jun 14), Austria (R8, Jun 28). Saudi Arabia and Bahrain (the original R3 and R5) were cancelled mid-season and the schedule renumbered. Britain (R9, Silverstone) is next on the calendar.

Canada methodology note — fuel-symmetric lap sample. Sergio Pérez retired from the Canadian GP on lap 39 with a chassis fire. An F1 car burns roughly 1.6 kg of fuel per lap and laps roughly 0.3 s/lap faster for every 10 kg of fuel consumed. Comparing PER's early-stint laps against the rest of the field's late-stint clean laps would bias every survivor's apex-speed average upward by 1–2 km/h relative to PER — purely from the lower fuel load they were running.

To keep the Canadian-GP sample fuel-symmetric, we apply a single global lap cap to the race: every driver's candidate-lap pool is restricted to LapNumber ≤ 39 before picking each driver's single fastest clean lap. (Drivers who retired earlier — ALB L11, ALO L23, RUS L29, NOR L38 — naturally have smaller pools; LIN DNS.) The cap is applied only to Canada and is recorded in races.canada.meta.global_lap_cap of the pipeline output for reproducibility. No other race uses a cap.

Monaco note — why no cap there. Valtteri Bottas retired from the Monaco GP on lap 16 of 78. Applying the Canada rule would have discarded 80% of the race for every driver, and at Monaco the fuel effect matters far less: minimum apex speeds are track-limited (walls, not grip, set the line), so early full-fuel laps are representative of cornering capability. We therefore use the full race for the field and flag that BOT's Monaco sample is 16 laps, all on heavy fuel — if anything a slight headwind for his numbers, not a tailwind. PER's sample spans his full 78-lap race.

Barcelona note — why no cap there either. Valtteri Bottas retired from the Barcelona GP on lap 15 of 66. Unlike Canada — where the Cadillac car that retired (PER) was the one at a fuel disadvantage — at Barcelona Pérez ran the full race (63 laps, classified), so the headline Cadillac field comparison isn't fuel-biased. Only BOT's sample is short, and a field-wide L15 cap would discard ~77% of the race on a circuit where the cleanest fast laps come later in the stint, on lower fuel. We therefore use the full race and flag that BOT's Barcelona sample is 15 laps, all on heavy fuel — which on this high-speed aero circuit understates his pace (his −10.4 km/h Barcelona gap is partly a fuel artefact, not pure grip deficit). PER's sample spans his full race.

Austria note — both Cadillac cars excluded (asterisk). Unlike Canada, Monaco, and Barcelona — where a lap cap or a flag was enough to keep the sample honest — Austria offered no usable Cadillac data at all. Both MAC-26s retired with brake fires inside the opening laps (PER lap 4, BOT lap 2), well before either could complete a representative clean lap. A two-to-four-lap, full-fuel, cold-brake sample isn't a fuel-bias problem you can cap away — it simply isn't a measurement of cornering pace. So rather than a cap, we apply a hard exclusion: Bottas fails the data-quality gate outright, and both PER and BOT are dropped from the Austria contribution to the season averages (EXCLUDE_DRIVER_RACES = {(austria, PER), (austria, BOT)} in the pipeline). The other ~20 drivers, who completed the race, do count Austria — which is why the field's corner counts reach 122 while Cadillac's sit at 114. Net effect: Austria adds nothing to the Cadillac season figures — but Britain, where both cars finished, does, and its high-speed corners nudged the Cadillac averages slightly wider while the cushion over Aston Martin grew back to 0.92 km/h.

2 · Corner Detection

We don't have FastF1's "official" corner metadata for every track, so we identify corners directly from the geometry of the track polyline. The track outline (X, Y in metres) is sampled on the same 5 m grid as the speed traces. From it we compute the signed curvature at every point:

Track curvature
$$\kappa(s) = \frac{\,\bigl|\,x'(s)\,y''(s)\;-\;y'(s)\,x''(s)\,\bigr|\,}{\bigl(x'(s)^2 + y'(s)^2\bigr)^{3/2}}$$

where derivatives are with respect to lap distance s. A straight has κ ≈ 0. A circular arc of radius R has κ = 1 / R. We smooth lightly (5-bin uniform filter, periodic) to suppress noise from the polyline downsampling, then detect corners as local peaks in κ exceeding κmin = 0.005 m−1 (corresponding to a corner radius of ≤ 200 m), with a minimum spacing of 140 m to avoid double-counting compound turns.

Secondary-peak rescue pass. The strict 140 m separation rule is great at rejecting noise but can also reject real corners packed close together (e.g. Miami's T13–T15 chicane, where two genuine apices sit only ~90 m apart). After the strict pass we re-scan for any rejected κ peaks meeting a higher bar — κ ≥ 0.020 m−1 (radius ≤ 50 m, i.e. clearly a real corner) and at least 60 m clear of every accepted peak — and add those back. The two-stage filter keeps the algorithm conservative on long sweepers while catching the chicane-style sequences a single threshold misses.

Each detected corner is widened outward from its peak while κ > κpeak / 3, which captures the entry braking, the apex, and the early exit. Bins outside any corner window are classified as straight.

Window-overlap dedup pass. The strict and rescue passes can both fire on the same physical complex — the strict pass picks up the wide low-κ averaged "super-blob" peak that sits at the geometric centroid of a multi-apex sequence, while the rescue pass picks up the sharper high-κ apex peaks inside it. Two tightly spaced peaks can also widen out to identical valley-to- valley extents. To avoid double-counting we run a final dedup pass: for any pair of corners whose windows overlap by ≥ 80 % of either window, we drop the one with the lower κpeak. The rule keeps the sharper, more localized apex and discards the wider averaged blob — physically the right call, since the lower-κ window was just an artifact of the strict pass averaging across a multi-apex complex.

Corner-detection thresholds

ParameterValueWhy
CORNER_PEAK_KAPPA0.005 m−1Corner radius ≤ 200 m. Excludes long sweepers like Suzuka 130R from the corner mask.
CORNER_MIN_SEP_M140 mMinimum lap-distance spacing between detected peaks (strict pass). Prevents double-counting Spoon's two apices.
RESCUE_KAPPA0.020 m−1Higher κ floor for the rescue pass (radius ≤ 50 m). Reserved for unambiguous corners packed inside the 140 m strict-pass window.
RESCUE_MIN_SEP_M60 mMinimum spacing for rescue-pass peaks from any already-accepted peak. Catches chicane apices (Miami T13–T15) that the strict 140 m rule rejected.
DEDUP_OVERLAP_FRAC0.80Drop a corner if its window overlaps another corner's by ≥ 80 % of either window — keep the sharper (higher-κ) apex, discard the wider averaged super-blob.
CORNER_KAPPA_FRAC1 / 3Corner extends outward while κ > κpeak / 3 — captures the entry, apex, and early exit.
SMOOTH_WINDOW_M25 mUniform-filter window for speed/throttle smoothing.

The corner mask, visualised

Sanity-check: when the algorithm above is applied to the eight tracks Cadillac has raced in 2026 so far, the corner-bin mask (red overlay) lights up in the places anyone who's watched a Grand Prix would expect — Albert Park's Lakeside / Brabham complex, Shanghai's hairpin and the long T11-T12 sequence, Suzuka's Esses, Degner, Hairpin, and Spoon, Miami's hairpin sequence and the chicane after the back straight, and the Red Bull Ring's compact set of heavy-braking corners between the climbs. Numbered markers are the per-corner C-IDs the pipeline uses everywhere else in the analysis. The percentages at the bottom of each panel are the fraction of the lap distance classified as corner phase.

ALBERT PARK 19 CORNERS · 5.23 KM 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 S/F 32% OF LAP CLASSIFIED AS CORNER PHASE
SHANGHAI 11 CORNERS · 5.38 KM 1 2 3 4 5 6 7 8 9 10 11 S/F 21% OF LAP CLASSIFIED AS CORNER PHASE
SUZUKA 17 CORNERS · 5.76 KM 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 S/F 31% OF LAP CLASSIFIED AS CORNER PHASE
MIAMI 14 CORNERS · 5.33 KM 1 2 3 4 5 6 7 8 9 10 11 12 13 14 S/F 24% OF LAP CLASSIFIED AS CORNER PHASE
MONTRÉAL 11 CORNERS · 4.35 KM 1 2 3 4 5 6 7 8 9 10 11 S/F 18% OF LAP CLASSIFIED AS CORNER PHASE
MONTE CARLO 15 CORNERS · 3.28 KM 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 S/F 30% OF LAP CLASSIFIED AS CORNER PHASE
CATALUNYA 12 CORNERS · 4.64 KM 1 2 3 4 5 6 7 8 9 10 11 12 S/F 33% OF LAP CLASSIFIED AS CORNER PHASE
RED BULL RING 8 CORNERS · 4.29 KM 1 2 3 4 5 6 7 8 S/F 20% OF LAP CLASSIFIED AS CORNER PHASE
SILVERSTONE 15 CORNERS · 5.82 KM 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 S/F 26% OF LAP CLASSIFIED AS CORNER PHASE

3 · Headline V2 Metric — Per-driver Minimum Apex Speed

For each driver and each detected corner zone Z, the minimum apex speed is the lowest speed they recorded inside that corner window on their single fastest clean lap:

Per-driver minimum apex speed (per corner)
$$v_{\min,Z}^{(d)} \;=\; \min_{\,i \,\in\, Z}\; v_i^{(d, \text{best lap})}$$

where the minimum is taken only over valid bins — bins where the driver's actual lap telemetry covered the corner window (telemetry-gap bins are filled from the median trace for κ math but excluded from min-speed extraction). Higher vmin = more grip = more downforce. F1 race engineers call this metric the apex-V; it's the cleanest, uncapped, most defensible single-number indicator of corner grip.

Field-relative gap is what we report on the narrative page:

Driver gap to field median (per corner)
$$\Delta v_{\min,Z}^{(d)} \;=\; v_{\min,Z}^{(d)} \;-\; \mathrm{med}_{d \in \text{field}}\bigl(v_{\min,Z}^{(d)}\bigr)$$

Positive Δv means the driver is above the field median for that corner; negative means below. Each driver's season gap is the average across all detected corners across all races.

Across the 6 races (87 corners per driver after the data-quality gate), Cadillac's two drivers sit near the bottom of the average gap to the field median: PER −2.9 km/h, BOT −5.5 km/h. The driver-leader (ANT) is at +3.5 km/h. The team-leader (Ferrari) is at +3.1 km/h on the team-rank metric (median of two drivers' season gaps). Cadillac's team gap of −4.2 km/h is 10/11, ahead of Aston Martin (−4.7 km/h) for the second race running — and Monaco stretched that margin from 0.25 to 0.47 km/h.

4 · Per-driver Phase Split — Closure-invariant

For each driver, on their single fastest clean lap, classify each 5 m bin as either corner or straight using a throttle/brake heuristic computed from that driver's own telemetry — not from the canonical track κ.

Per-bin phase classifier (per driver, on best lap)
$$\text{phase}_i = \begin{cases} \text{corner} & \tilde\tau_i < 0.92 \;\;\text{or}\;\; b_i = 1 \\ \text{straight} & \text{otherwise} \end{cases}$$

where τ̃i is the driver's throttle channel (smoothed with a 5-bin uniform filter to suppress single-sample dips) and bi is the brake channel. The 0.92 threshold is calibrated against the canonical track-κ corner mask — it agrees on ~85 %+ of bins on average and absorbs the partial- throttle modulation drivers do on long sweepers (Suzuka 130R, Spoon entry) that wouldn't otherwise count as corners.

Per-phase lap-time integral
$$T_{\text{corner}} = \sum_{i \,\in\, \text{corner}} \frac{\Delta s}{v_i}\qquad T_{\text{straight}} = \sum_{i \,\in\, \text{straight}} \frac{\Delta s}{v_i}$$

Closure invariant (asserted at write time on unrounded floats, every driver, every race):

Lap-time partition (exact)
$$T_{\text{corner}} \;+\; T_{\text{straight}} \;=\; T_{\text{lap}}$$

Add the two phase totals back together and you get the lap time exactly. No averaging, no fudge factors, no masking. The story becomes "your fastest Suzuka lap was 95.604 s; 49 of that was in the corners, 47 was on the straights" — a partition you can defend down to the millisecond.

The cornering_pct = Tcorner / Tlap varies by track (Miami at ~52 %, Suzuka at ~52 %, Australia at ~52 %, China at ~58 %) and by driver style (the slowest cars spend more time in the corner phase because their corner v is lower; the fastest cars spend less). It's a useful per-race circuit-shape indicator.

Validity-mask gate. Bins where the driver's actual lap telemetry didn't reach (lap-edge truncation, brief signal drop-out) are filled from the median trace for κ math but excluded from the integration via a per-bin validity mask. The closure invariant is enforced over the valid-bin subset, so Tcorner + Tstraight = Tvalid lap even when a driver's coverage is partial.

5 · Secondary Signature — Per-driver Peak Lateral G

As a physics-anchored secondary indicator, we compute lateral G per driver per corner. From the canonical track curvature and each driver's speed trace on their best lap:

Lateral acceleration (per driver, per bin)
$$a_{\text{lat}}^{(d)}(s) \;=\; \frac{v^{(d)}(s)^2 \cdot \kappa_{\text{track}}(s)}{g}\qquad g = 9.81\; \text{m/s}^2$$

Per corner we take the 99th percentile of alat across the corner window — robust enough against single-bin noise to be reliable.

Per-driver per-corner peak lateral G
$$G_Z^{(d)} \;=\; \mathrm{P_{99}}\bigl[\,a_{\text{lat}}^{(d)}(s)\,;\; s \in Z\,\bigr]$$

Lat-G is a secondary indicator with caveats. Real F1 cars peak around 5.5 g sustained, ~6 g brief. Anything above is by definition a κ-noise or v-interpolation artefact: the canonical FastF1 reference outline has occasional kinks where κ spikes to 0.10–0.14 (vs. the ~0.04 ceiling for real F1 corners). Combined with v² these manufacture impossible 100 g+ peaks. We therefore clip lat-G at the 6 g physical ceiling and reject corners with peak κ > 0.10 (radius < 10 m) at detection time. With these gates in place, the remaining values are physically bounded but compress the field into a tight 4–5 g range — the lat-G ranking is less discriminating than the minimum-apex-speed ranking. That's why minimum apex speed is the headline V2 metric, not peak lat-G.

LAP DISTANCE SPEED FIELD MEDIAN CADILLAC — slower at apex CORNER CORNER
Schematic — Cadillac matches the field on the straights, drops below at the apex
LAP DISTANCE SPEED MIDFIELD CADILLAC — slower at apex CORNER CORNER
Schematic — Cadillac matches midfield on the straights, drops below at the apex

6 · Field-Comparison Framework

V2 abandons the "Cadillac vs midfield reference" framing of V1. Instead, every metric is computed against the full 22-driver field. The field median is the natural reference: the driver in the middle of the grid carries some apex speed, and any driver below the median is slower than half the field. The metric is honest and uncapped.

For visualisation, drivers are bucketed into four cohorts so a 22-dot scatter doesn't become a noise wash:

  • Cadillac F1 (PER, BOT) — silver fill with red outline ring, larger marker. The team we're profiling.
  • Front-runners (Red Bull · Mercedes · McLaren · Ferrari) — full-saturation team colours. Anchors the top of the field.
  • Midfield (Aston Martin · Williams · Haas) — team colours at 65 % opacity. Where Cadillac is realistically racing in race-pace terms, but no longer used as a reference set.
  • Rest of grid (Audi · Alpine · Racing Bulls) — team colours at 45 % opacity. Visual context without dominating the chart.

The field median at each point is the median across all qualifying drivers (after the data-quality gate). Median not mean: robust to one driver having an off-lap contaminate the reference.

Team gap to field median (season aggregate)
$$\Delta v_{\text{team}} \;=\; \mathrm{med}_{d \in \text{team}}\Bigl[\, \mathrm{mean}_{Z, k}\bigl(v_{\min,Z}^{(d, k)} - \mathrm{med}_{d' \in \text{field}}(v_{\min,Z}^{(d', k)})\bigr)\,\Bigr]$$

For each team driver d, average the per-corner gap to the field median across all corners Z across all races k. Then take the median of the team's two drivers — that's the team's season-aggregate gap to the field. Negative = below the field.

Cohort coloring is for legibility, not weighting. Every driver in the field counts equally toward the field median — the cohort palette only changes how dots look on the charts, not how the underlying metric is computed. A "rest of grid" driver contributes the same statistical weight as a front-runner.

7 · What the Analysis Does Not Capture

  • Tyre state — best clean laps will cluster on similar compound + age profiles, but a driver burning tyres in qualifying trim would inflate their apex speeds vs Cadillac's race-stint pace. Mitigated by always using the same lap-selection rule across all 22 drivers; not eliminated.
  • Setup choices vs base car — a low-downforce configuration chosen for one race would look identical in this telemetry to a base downforce shortfall. The analysis can't separate them on a single race. The fact that Cadillac sits last across all four very different circuits (Albert Park's medium-speed flow, Shanghai's variety, Suzuka's high-speed esses, Miami's stop-and-go) is what makes the "base car" interpretation the more parsimonious one.
  • Driver effect — PER and BOT might both be cornering conservatively because they're driving around a chronic understeer. The metric reads a deficit either way; what it can't tell you is whether better-driven Cadillacs would recover the gap. The PER vs BOT comparison (chart 4) is the team's internal driver-effect indicator.
  • Race pace vs pure lap pace — these are race-session laps but specifically the single fastest clean lap per driver. Average race pace including stints in dirty air, graining, fuel weight, and strategy effects would tell a different (and probably worse for Cadillac) story.
  • Banking effects — F1 circuits have small banking we can't recover from GPS. Affects lateral G by ≤ 5 % at a few corners (Suzuka 130R, Silverstone Maggotts/Becketts). Nobody else publishes this either.
  • Sample-rate localisation — at 4 Hz car-data sampling, the per-driver speed trace is localised to ±15 m at 250 km/h. Differences smaller than that are noise.
  • Lat-G ceiling cap artefact — the secondary peak-lat-G metric clips at 6 g. At slow corners with sharp κ, most drivers hit the cap, so the lat-G ranking compresses. Minimum apex speed (the headline V2 metric) doesn't have this problem.

In short: this is not a "Cadillac is bad" report; it's an attribution of where the team specifically sits in the field. The minimum-apex-speed metric is consistent across drivers, races, and corner types — and Cadillac sits at the bottom in every breakdown. That's the claim the data supports.