Flight
MXY256
Flight history and live tracking for MXY256, operated by Breeze Airways. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Breeze Airways |
| Typical origin | KMCO ORLANDO INTERNATIONAL |
| Typical destination | KLAN CAPITAL CITY |
| Distance | 876 nm |
Flight history 70 flights since Aug 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-26 | KMCO ORLANDO INTERNATIONAL | KLAN CAPITAL CITY | 06:12 EDT | 08:40 EDT | 2h 28m | N238BZ |
| 2026-09-12estimated | KMCO | KLAN | 06:03 EDT | 08:10 EDT | 2h 06m | A2992F |
| 2026-09-05estimated | KMCO | KLAN | 06:20 EDT | 08:44 EDT | 2h 23m | N217BZ |
Earlier flights (67) - back to 2025-08-16
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-29estimated | KMCO | KLAN | 06:10 EDT | 08:40 EDT | 2h 30m | A28E0A |
| 2026-08-22estimated | ? | ? | 10:14Z | 13:10Z | 2h 56m | N214BZ |
| 2026-08-15estimated | KMCO | KLAN | 06:12 EDT | 08:38 EDT | 2h 25m | N213BZ |
| 2026-08-12estimated | ? | ? | 10:12Z | 12:40Z | 2h 27m | N267BZ |
| 2026-07-22estimated | ? | KLAN | 09:15Z | 08:38 EDT | 3h 23m | N218BZ |
| 2026-07-18 | KMCO | KLAN | 05:19 EDT | 08:30 EDT | 3h 11m | A282E5 |
| 2026-07-15estimated | KMCO | KLAN | 06:38 EDT | 08:30 EDT | 1h 51m | N219BZ |
| 2026-07-11estimated | KMCO | ? | 06:07 EDT | 12:24Z | 2h 16m | A2668B |
| 2026-07-08estimated | KMCO | KLAN | 06:01 EDT | 08:22 EDT | 2h 20m | A202A1 |
| 2026-07-04estimated | KMCO | KLAN | 05:36 EDT | 08:26 EDT | 2h 49m | N204BZ |
| 2026-07-01estimated | KMCO | KLAN | 05:50 EDT | 08:32 EDT | 2h 41m | A2668B |
| 2026-06-27estimated | KMCO | KLAN | 06:15 EDT | 08:36 EDT | 2h 21m | A202A1 |
| 2026-06-24estimated | KMCO | KLAN | 06:12 EDT | 08:34 EDT | 2h 21m | A1F77C |
| 2026-06-20estimated | KMCO | KLAN | 06:24 EDT | 08:52 EDT | 2h 27m | A202A1 |
| 2026-06-17estimated | KORL | KLAN | 06:33 EDT | 08:40 EDT | 2h 06m | A1F77C |
| 2026-06-13estimated | KMCO | KLAN | 06:26 EDT | 08:48 EDT | 2h 21m | A2668B |
| 2026-05-27estimated | KMCO | KLAN | 06:19 EDT | 08:34 EDT | 2h 15m | N211BZ |
| 2026-05-23estimated | KMCO | ? | 07:12 EDT | 13:28Z | 2h 15m | A262D4 |
| 2026-05-20 | KMCO | KLAN | 06:28 EDT | 10:04 EDT | 3h 35m | A262D4 |
| 2026-05-19 | KMCO | KLAN | 22:41 EDT | 16:36 EDT | 17h 55m | N216BZ |
| 2026-05-09 | KMCO | KLAN | 06:25 EDT | 08:46 EDT | 2h 20m | A22669 |
| 2026-05-06 | KMCO | KLAN | 06:35 EDT | 09:00 EDT | 2h 24m | A1FEEA |
| 2026-05-02 | KMCO | KLAN | 08:14 EDT | 10:26 EDT | 2h 11m | A1FEEA |
| 2026-04-25 | KMCO | KLAN | 08:19 EDT | 10:30 EDT | 2h 10m | A2869C |
| 2026-04-22estimated | ? | KLAN | 12:39Z | 10:54 EDT | 2h 14m | A22A20 |
| 2026-04-18estimated | ? | ? | 12:03Z | 14:28Z | 2h 24m | A22A20 |
| 2026-04-15 | KMCO | KLAN | 08:41 EDT | 10:52 EDT | 2h 10m | N217BZ |
| 2026-04-14estimated | ? | ? | 10:40Z | 14:08Z | 3h 27m | A26DF9 |
| 2026-04-11 | KMCO | KLAN | 08:13 EDT | 10:30 EDT | 2h 16m | A2869C |
| 2026-04-04estimated | ? | ? | 11:26Z | 14:24Z | 2h 57m | N217BZ |
| 2026-03-31estimated | KMCO | KLAN | 07:03 EDT | 10:16 EDT | 3h 12m | A2101F |
| 2026-03-28estimated | KMCO | KLAN | 09:43 EDT | 10:46 EDT | 1h 02m | A233E7 |
| 2026-03-14estimated | ? | KLAN | 12:23Z | 10:52 EDT | 2h 28m | N219BZ |
| 2026-03-11estimated | KMCO | KLAN | 08:23 EDT | 10:44 EDT | 2h 20m | A1E132 |
| 2026-03-10estimated | KMCO | KLAN | 06:26 EDT | 10:22 EDT | 3h 55m | A27567 |
| 2026-03-07estimated | KMCO | KLAN | 08:10 EST | 09:28 EST | 1h 18m | A2519F |
| 2026-03-04 | KMCO | KLAN | 08:44 EST | 11:06 EST | 2h 21m | A1FB33 |
| 2026-03-03estimated | KMCO | KLAN | 06:30 EST | 10:17 EST | 3h 46m | A21B44 |
| 2026-02-28 | KMCO | KLAN | 08:25 EST | 10:58 EST | 2h 32m | N219BZ |
| 2026-02-25 | KMCO | KLAN | 08:31 EST | 11:12 EST | 2h 41m | N204BZ |
| 2026-02-24 | KMCO | KLAN | 07:38 EST | 10:38 EST | 2h 59m | N218BZ |
| 2026-02-21 | KMCO | KLAN | 08:25 EST | 10:50 EST | 2h 24m | A21B44 |
| 2026-02-18 | KMCO | KLAN | 08:26 EST | 10:54 EST | 2h 28m | A1FB33 |
| 2026-02-17 | KMCO | KLAN | 07:48 EST | 10:26 EST | 2h 37m | A2101F |
| 2026-02-14 | KMCO | KLAN | 08:18 EST | 10:54 EST | 2h 36m | A1E132 |
| 2026-02-11 | KMCO | KLAN | 10:42 EST | 13:10 EST | 2h 27m | A1E132 |
| 2026-02-07 | KMCO | KLAN | 08:06 EST | 11:12 EST | 3h 05m | A1E132 |
| 2026-02-04 | KMCO | KLAN | 08:29 EST | 10:56 EST | 2h 27m | A1E132 |
| 2026-01-31 | KMCO | KLAN | 08:16 EST | 10:30 EST | 2h 13m | N215BZ |
| 2026-01-28 | KMCO | KLAN | 08:16 EST | 10:34 EST | 2h 17m | A21B44 |
| 2026-01-24 | KMCO | KLAN | 08:21 EST | 10:36 EST | 2h 14m | A282E5 |
| 2026-01-21 | KMCO | KLAN | 08:24 EST | 10:40 EST | 2h 15m | A2791E |
| 2026-01-07 | KMCO | KLAN | 08:23 EST | 11:14 EST | 2h 51m | A233E7 |
| 2026-01-03 | KMCO | KLAN | 08:37 EST | 10:52 EST | 2h 14m | N215BZ |
| 2025-12-31 | KMCO | KLAN | 08:44 EST | 11:12 EST | 2h 27m | N214BZ |
| 2025-12-27 | KMCO | KLAN | 08:31 EST | 11:38 EST | 3h 07m | A233E7 |
| 2025-12-24 | KMCO | KLAN | 08:41 EST | 11:18 EST | 2h 36m | A27567 |
| 2025-12-20 | KMCO | KLAN | 08:31 EST | 10:48 EST | 2h 16m | A1EC57 |
| 2025-12-17 | KMCO | KLAN | 08:35 EST | 11:06 EST | 2h 30m | A2101F |
| 2025-12-13 | KMCO | KLAN | 08:33 EST | 11:02 EST | 2h 28m | A222B2 |
| 2025-12-10 | KMCO | KLAN | 08:35 EST | 10:50 EST | 2h 14m | A27567 |
| 2025-11-26estimated | KMCO | KLAN | 08:34 EST | 10:52 EST | 2h 17m | A21EFB |
| 2025-10-29estimated | KMCO | KLAN | 08:41 EDT | 10:46 EDT | 2h 05m | A25B66 |
| 2025-10-15 | KMCO | KLAN | 08:40 EDT | 10:58 EDT | 2h 17m | A1EC57 |
| 2025-08-23 | KMCO | KLAN | 09:49 EDT | 12:12 EDT | 2h 23m | A208B1 |
| 2025-08-21 | KMCO | KLAN | 01:38 EDT | 03:00 EDT | 1h 21m | A208B1 |
| 2025-08-16 | KMCO | KLAN | 09:10 EDT | 11:18 EDT | 2h 07m | A2519F |
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 MXY256 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]