How to improve motorcycle lap times with data

Start with two laps you can fairly compare

Upload a session and choose a clean lap, then select a reference. A quicker lap from the same session is a useful starting point: the bike and conditions are more likely to be similar. You can also compare sessions at the same circuit, but account for tyres, setup, weather and traffic.

Check that the GPS line and recorded channels look usable before drawing conclusions. A missing signal, position jump or sensor offset can look like a riding difference. Compare the channels both recordings actually contain.

Find the change in delta, not just the biggest gap

The time delta shows the running difference between laps. First check which lap is the reference and how the view labels faster and slower. Then look for where the gap changes. A gap already present at corner entry may have been carried from the previous straight.

Pick one corner where the comparison changes noticeably. Read from the approach through the following acceleration zone, rather than stopping at the apex.

Where lap time actually disappears in a corner

Think of the speed trace as a V: slowing down, reaching a minimum, then building speed again. It is a way to organise the comparison, not a rule about how every corner should be ridden.

Entry

Where does speed start falling? How long does the deceleration last? Compare the brake trace if it is recorded. Did the lap lose time on the approach, or did a different entry help later in the corner?

Minimum speed

Where is the slowest point, and how long does the bike stay near that speed? Compare the line and the next phase. A higher minimum speed is useful only in the context of the complete corner.

Exit

When does speed begin building again? With a throttle channel, compare the application and any interruptions. Follow the delta into the next section to see whether an apparent exit gain lasts.

Braking later is not automatically the answer. An entry that looks quicker in isolation can leave the bike poorly placed for the exit. Equally, minimum speed matters: carrying less speed than the corner needs can cost time. Read the phases together before deciding which one to work on.

An exit-speed advantage can keep paying back along the following acceleration zone. The speed difference does not have to grow for a time advantage to accumulate. Use the delta to see what actually happened in these two laps.

A real comparison: Turn 11 at Sonoma

This existing Lapfly capture compares Lap 2 with Lap 3 as the reference. The corner panel shows Lap 2 with an apex speed of 115 km/h against 99 km/h for the reference, while labelling the Turn 11 comparison 0.125 seconds slower.

That does not prove why time was lost. It does show why choosing the higher speed number is not enough. The running lap gap at the bottom of Fly is a different measure from the selected corner comparison.

What to inspect next

1. Locate the change. Return to the dashboard and inspect the delta through the approach, corner and exit. Establish where the difference begins.
2. Read the inputs. In this recording, brake and throttle traces are available. Compare their timing with the speed change; do not infer brake pressure from speed alone.
3. Check the line. Scrub both bikes through Fly. Look at their recorded paths and where acceleration begins. GPS accuracy limits how finely you can interpret a line difference; rendered track edges are illustrative.
4. Test an explanation. Check another comparable lap before treating the pattern as repeatable. One screenshot cannot establish the cause.

Check the telemetry traces

Keep the time delta beside the channels you need. RPM can help investigate a gear-change question; fork travel can add context to an entry; throttle position can show whether an acceleration phase was interrupted. Avoid adding channels that do not help answer the question.

If you ask Lapfly's AI about the corner, check its explanation against the laps and channels it cites. A useful answer gives you something to investigate, not a reason to ignore an inconsistent trace.

GPS-only data is still a useful starting point

You can compare speed, recorded line and time delta without an ECU or suspension logger. But slowing down does not tell you exactly when or how hard the rider applied the brake, and accelerating does not reveal throttle position. Keep those questions open unless the relevant sensor channels are recorded.

What to work on next session

1. Choose one repeatable difference. Start with a corner where several clean laps show the same pattern, rather than chasing one unusual lap.
2. Write down what you will check. For example: does a more consistent entry lead to a more repeatable exit? Decide which trace and section of delta will tell you.
3. Keep the comparison useful. Record setup or tyre changes, and note traffic or conditions. Changing several things at once makes the result harder to explain.
4. Review the next recording. Compare the whole corner and following section. Keep a change because the result is repeatable, not because one input looks more aggressive.

Work within your ability and use a coach to translate the observations into riding practice. Telemetry helps you ask a more precise question; it does not choose a safe riding limit for you.

Public circuit leaderboards can put your lap time in context. Use your available session telemetry to understand the difference between your own laps; a public time is not access to another rider's traces.