Flight
TWY1
Flight history and live tracking for TWY1. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 19 flights since Jan 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-17estimated | ? | ? | 00:40Z | 02:34Z | 1h 53m | N898 |
| 2026-08-16estimated | ? | ? | 22:40Z | 23:30Z | 0h 50m | N898 |
| 2026-08-12 | KSTS | KSBM | 05:33 PDT | 10:54 CDT | 3h 20m | N898 |
Earlier flights (16) - back to 2026-01-26
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-06-22estimated | KNFL | ? | 17:00 PDT | 00:34Z | 0h 34m | N898 |
| 2026-06-21estimated | KRDU | ? | 15:25 EDT | 23:58Z | 4h 32m | N898 |
| 2026-06-15 | ? | KTEB | 13:15Z | 15:36 EDT | 6h 21m | N898 |
| 2026-05-20 | KLNA | KPBI | 23:46 EDT | 00:50 EDT | 1h 03m | N898 |
| 2026-05-19estimated | KSUU | MYGF | 23:33 PDT | 02:54 EDT | 0h 20m | N898 |
| 2026-05-09estimated | KCHS | KSFO | 13:41 EDT | 16:02 PDT | 5h 20m | N898 |
| 2026-05-08partial | KCHS | ? | 15:19 EDT | N898 | ||
| 2026-05-01 | ? | KCHS | 14:07Z | 14:30 EDT | 4h 22m | N898 |
| 2026-04-27estimated | ? | KSFO | 00:00Z | 18:40 PDT | 1h 40m | N898 |
| 2026-04-26estimated | MYGW | ? | 14:25 EDT | 23:58Z | 5h 32m | N898 |
| 2026-04-19estimated | ? | ? | 14:44Z | 20:30Z | 5h 45m | N898 |
| 2026-04-14estimated | ? | ? | 19:37Z | 22:06Z | 2h 28m | N898 |
| 2026-03-30partial | ? | ? | 00:00Z | N898 | ||
| 2026-03-29estimated | KBHM | ? | 17:37 CDT | 23:58Z | 1h 20m | N898 |
| 2026-02-07 | ? | ? | 06:55Z | 08:00Z | 1h 04m | AC630B |
| 2026-01-26partial | ? | ? | 00:00Z | AC630B |
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.
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 own receiver network archive. Questions: [email protected]