Flight
N256CW
Flight history and live tracking for N256CW. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 17 flights since Jan 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-12estimated | ? | ? | 09:35Z | 22:58Z | 13h 22m | N256CW |
| 2026-08-11estimated | ? | ? | 18:55Z | 19:18Z | 0h 22m | N256CW |
Earlier flights (15) - back to 2026-01-22
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23 | KHPN | ? | 10:52 EDT | 20:22Z | 5h 29m | A26E0F |
| 2026-07-18 | ? | KHPN | 14:23Z | 15:12 EDT | 4h 48m | A26E0F |
| 2026-07-16estimated | ? | KHWD | 22:36Z | 16:26 PDT | 0h 50m | A26E0F |
| 2026-05-25 | KRAL | KLGB | 12:34 PDT | 13:42 PDT | 1h 07m | A26E0F |
| 2026-05-20estimated | KLGB | MMCN | 10:53 PDT | 12:06 MST | 1h 12m | A26E0F |
| 2026-05-02estimated | ? | ? | 20:44Z | 21:14Z | 0h 29m | A26E0F |
| 2026-05-02estimated | KLGB | ? | 12:08 PDT | 20:12Z | 1h 03m | A26E0F |
| 2026-05-01 | KAUS | ? | 09:37 CDT | 17:34Z | 2h 56m | A26E0F |
| 2026-05-01estimated | KAUS | ? | 07:57 CDT | 13:34Z | 0h 36m | A26E0F |
| 2026-04-29 | KLGB | KAUS | 11:28 PDT | 15:52 CDT | 2h 23m | A26E0F |
| 2026-04-06estimated | ? | ? | 00:00Z | 03:18Z | 3h 18m | A26E0F |
| 2026-04-05 | KTEB | ? | 17:59 EDT | 23:58Z | 1h 58m | A26E0F |
| 2026-04-03estimated | ? | ? | 01:29Z | 06:42Z | 5h 12m | A26E0F |
| 2026-01-25 | KTUS | ? | 07:44 MST | 18:02Z | 3h 17m | A26E0F |
| 2026-01-22 | KLGB | KRAL | 07:08 PST | 13:28 PST | 6h 20m | A26E0F |
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 N256CW 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 own receiver network archive. Questions: [email protected]