Flight
JTM211
Flight history and live tracking for JTM211. 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 Dec 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21estimated | ? | ? | 14:53Z | 16:50Z | 1h 57m | N211EC |
| 2026-08-20estimated | ? | ? | 14:12Z | 16:16Z | 2h 04m | N211EC |
Earlier flights (15) - back to 2025-12-28
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-15estimated | ? | ? | 14:15Z | 18:04Z | 3h 48m | N211EC |
| 2026-07-12estimated | KAPG | KNHK | 08:16 EDT | 12:22 EDT | 4h 05m | N211EC |
| 2026-07-11estimated | KPBI | KNHK | 13:47 EDT | 15:38 EDT | 1h 51m | N211EC |
| 2026-07-09estimated | KNHK | KVRB | 11:10 EDT | 13:24 EDT | 2h 13m | N211EC |
| 2026-07-01estimated | KACK | KDOV | 14:33 EDT | 16:46 EDT | 2h 12m | N211EC |
| 2026-05-20estimated | KBWI | KAPG | 22:53 EDT | 03:58 EDT | 5h 04m | N211EC |
| 2026-05-06partial | KNHK | ? | 07:01 EDT | N211EC | ||
| 2026-04-19 | KBUR | ? | 09:38 PDT | 23:10Z | 6h 31m | N211EC |
| 2026-04-18 | ? | KBUR | 13:33Z | 13:22 PDT | 6h 48m | N211EC |
| 2026-04-16estimated | ? | ? | 12:08Z | 22:56Z | 10h 47m | N211EC |
| 2026-04-11 | KPIE | ? | 07:08 EDT | 23:06Z | 11h 57m | N211EC |
| 2026-04-04 | ? | KPIE | 16:18Z | 14:14 EDT | 1h 55m | N211EC |
| 2026-04-03estimated | ? | ? | 12:13Z | 20:50Z | 8h 37m | N211EC |
| 2026-01-09partial | KBUR | ? | 16:01 PST | A1BDA0 | ||
| 2025-12-28 | ? | KRIC | 12:40Z | 11:55 EST | 4h 15m | A1BDA0 |
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 JTM211 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]