Flight
RN141
Flight history and live tracking for RN141. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 44 flights since Oct 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-09estimated | ? | ? | 17:29Z | 18:06Z | 0h 36m | 166141 |
Earlier flights (43) - back to 2025-10-29
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-31estimated | ? | ? | 17:51Z | 18:26Z | 0h 35m | 166141 |
| 2026-08-31estimated | ? | ? | 14:08Z | 14:44Z | 0h 35m | 166141 |
| 2026-06-23estimated | KNSE | KPNS | 07:10 CDT | 07:54 CDT | 0h 43m | 166141 |
| 2026-05-27estimated | ? | KGZH | 17:40Z | 12:58 CDT | 0h 17m | 166141 |
| 2026-05-21estimated | KNSE | ? | 09:28 CDT | 15:26Z | 0h 58m | 166141 |
| 2026-05-20estimated | KNPA | KNSE | 23:37 CDT | 15:38 CDT | 16h 00m | 166141 |
| 2026-04-17 | KDHN | KPNS | 18:05 CDT | 07:50 CDT | 13h 44m | AE4A16 |
| 2026-04-17estimated | ? | ? | 14:56Z | 15:26Z | 0h 29m | 166141 |
| 2026-04-16estimated | ? | KNSE | 00:00Z | 20:06 CDT | 1h 06m | 166141 |
| 2026-04-15estimated | ? | KGPT | 20:46Z | 17:10 CDT | 1h 23m | 166141 |
| 2026-04-14estimated | ? | ? | 22:14Z | 22:36Z | 0h 21m | 166141 |
| 2026-04-14estimated | ? | ? | 18:28Z | 18:56Z | 0h 28m | 166141 |
| 2026-04-14estimated | ? | ? | 01:05Z | 02:18Z | 1h 12m | 166141 |
| 2026-04-13estimated | ? | KJKA | 22:47Z | 18:18 CDT | 0h 30m | 166141 |
| 2026-03-31estimated | KPNS | ? | 15:06 CDT | 21:28Z | 1h 21m | 166141 |
| 2026-03-13estimated | ? | ? | 20:25Z | 20:48Z | 0h 22m | 166141 |
| 2026-03-13estimated | KNSE | KPNS | 11:27 CDT | 12:36 CDT | 1h 08m | 166141 |
| 2026-03-12estimated | FWMG | KPNS | 19:00 CDT | 19:42 CDT | 0h 42m | 166141 |
| 2026-03-11 | KCEW | FWMG | 18:17 CDT | 18:58 CDT | 0h 40m | 166141 |
| 2026-03-11 | KNSE | KCEW | 15:13 CDT | 16:28 CDT | 1h 14m | 166141 |
| 2026-03-11estimated | ? | ? | 14:13Z | 14:52Z | 0h 38m | 166141 |
| 2026-02-26 | KTLH | KNSE | 16:26 EST | 17:38 CST | 2h 12m | 166141 |
| 2026-02-26estimated | ? | KTLH | 20:14Z | 16:26 EST | 1h 11m | 166141 |
| 2026-02-12partial | KAVO | ? | 10:13 EST | 166141 | ||
| 2026-02-12 | KAVO | KSEF | 07:34 EST | 08:32 EST | 0h 58m | 166141 |
| 2026-01-31partial | KAVO | ? | 09:47 EST | 166141 | ||
| 2026-01-31 | KAVO | KSEF | 07:13 EST | 07:52 EST | 0h 38m | 166141 |
| 2026-01-30estimated | KLAL | KAVO | 17:23 EST | 17:50 EST | 0h 27m | 166141 |
| 2026-01-30estimated | ? | KLAL | 19:19Z | 14:42 EST | 0h 22m | 166141 |
| 2026-01-30estimated | ? | ? | 14:47Z | 15:20Z | 0h 32m | 166141 |
| 2026-01-30estimated | ? | KSEF | 12:20Z | 08:04 EST | 0h 43m | 166141 |
| 2026-01-27partial | KAVO | ? | 17:04 EST | AE4A16 | ||
| 2026-01-27estimated | ? | ? | 12:51Z | 13:40Z | 0h 48m | 166141 |
| 2026-01-22estimated | KCEW | KPNS | 19:05 CST | 20:32 CST | 1h 26m | 166141 |
| 2026-01-21 | KNSE | KCEW | 15:45 CST | 17:10 CST | 1h 25m | 166141 |
| 2026-01-08 | KMOB | KNSE | 15:48 CST | 17:16 CST | 1h 27m | 166119 |
| 2026-01-08estimated | ? | KMOB | 19:24Z | 14:26 CST | 1h 01m | 166141 |
| 2026-01-08estimated | KNSE | KPNS | 10:22 CST | 11:36 CST | 1h 13m | 166141 |
| 2026-01-05 | KGPT | KNSE | 10:14 CST | 10:46 CST | 0h 32m | 166141 |
| 2025-12-22estimated | KCEW | ? | 10:32 CST | 17:06Z | 0h 34m | 166141 |
| 2025-12-22 | KNSE | KCEW | 08:14 CST | 09:16 CST | 1h 01m | 166141 |
| 2025-12-09estimated | ? | ? | 18:49Z | 19:18Z | 0h 29m | 166141 |
| 2025-10-29estimated | KPNS | KHSA | 16:10 CDT | 17:14 CDT | 1h 03m | 166141 |
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 RN141 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]