Troubleshooting: incorrect mileage

**Needs Review** — Too many GPS samples were filtered out due to low accuracy. The displayed distance may be shorter than actual. MileLedger never fabricates mileage; this flag means the data was insufficient, not wrong in the other direction.

**Low GPS Accuracy** — The recorded samples have higher-than-normal horizontal error values. The distance is likely close to correct but should be verified.

**Possible Duplicate** — MileLedger detected another trip on the same day with a very similar route and distance. Review both trips and delete the one that should not be counted.

**Short Trip** — The recorded distance is below approximately 0.5 miles (804.672 m). These trips are excluded from report totals by default.

**Interrupted Session** — The tracking session ended unexpectedly (e.g. force-quit, device restart, Airplane Mode). Only the portion of the trip recorded before the interruption is included in the distance.

Distance is calculated from consecutive accepted GPS samples. It can differ from map-routing tools or your vehicle odometer, especially with curves, tunnels, or sparse samples. Use Needs Review flags and manual edits when a trip looks wrong.

This is an inherent characteristic of GPS-based tracking, not a bug. For IRS mileage log purposes, the GPS-recorded distance is acceptable documentation.

Open the drive detail and tap **Edit**.

Tap the **Distance** field and enter the correct value.

Tap **Save**. The manual override is applied and the trip detail shows that the distance was manually edited.

The original GPS route map is retained even after a distance override.

Keep the phone mounted in a position with a clear view of the sky (avoid windshield areas blocked by metallic tinting).

Avoid force-quitting MileLedger, which causes Interrupted Session flags.

Do not drive in Airplane Mode—it disables GPS entirely.