Flight
RIBYE31
Flight history and live tracking for RIBYE31. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 16 flights since Dec 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-10-05partial | KDLF | ? | 18:18 CDT | 65-10345 | ||
| 2026-10-05estimated | KDRT | ? | 10:47 CDT | 16:34Z | 0h 46m | 68-8217 |
| 2026-10-02partial | KDLF | ? | 08:17 CDT | 64-13195 | ||
| 2026-09-30partial | KDLF | ? | 15:36 CDT | 66-4326 | ||
| 2026-09-29partial | KDLF | ? | 12:14 CDT | 66-4380 | ||
| 2026-09-25partial | KDLF | ? | 12:36 CDT | 67-14926 | ||
| 2026-09-24partial | KDLF | ? | 08:30 CDT | 64-13210 | ||
| 2026-09-22estimated | KDLF | ? | 08:25 CDT | 14:16Z | 0h 50m | 64-13210 |
| 2026-09-08estimated | ? | ? | 13:46Z | 17:06Z | 3h 19m | 64-13293 |
Earlier flights (7) - back to 2025-12-11
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-14estimated | ? | ? | 13:31Z | 14:08Z | 0h 36m | 70-1573 |
| 2026-03-12estimated | KDLF | ? | 08:12 CDT | 14:02Z | 0h 49m | 67-14922 |
| 2026-03-05estimated | ? | KDLF | 22:36Z | 17:28 CST | 0h 52m | ADFFBE |
| 2026-02-17estimated | ? | KDLF | 15:08Z | 09:34 CST | 0h 26m | 65-10461 |
| 2026-01-30estimated | ? | KDLF | 14:37Z | 09:32 CST | 0h 54m | 67-14922 |
| 2026-01-26estimated | KDLF | ? | 09:48 CST | 16:34Z | 0h 46m | 66-4385 |
| 2025-12-11estimated | KDLF | ? | 08:21 CST | 15:10Z | 0h 48m | 64-13257 |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Follow this flight
Get an email when RIBYE31 flies + if it runs late.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our archive (from $9.99, with a free one-day sample). Questions: [email protected]