JayhawkCO , thanks for catching this! I finally found some time to debug. The issue was caused by schedule times being returned in UTC, while users search by the flight’s local departure date. For late-day departures, the UTC date can be the next calendar day, so the searched date could be missed.
This is fixed now. We now match schedules using the origin airport’s local departure date, so a flight searched as 2026-06-03 will still be found even if its UTC timestamp falls on 2026-06-04.