Flight
AZUR31
Flight history and live tracking for AZUR31. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 16 flights since Jan 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-29 | LFNE | LFMI | 21:47 CEST | 22:36 CEST | 0h 48m | 3B7FFB |
| 2026-09-29 | LFMV | LFMI | 18:46 CEST | 19:04 CEST | 0h 17m | 3B7FFB |
Earlier flights (14) - back to 2026-01-08
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-14estimated | LFPN | LFNZ | 14:36 CEST | 17:00 CEST | 2h 23m | 3B7FFB |
| 2026-07-13estimated | ? | LFPO | 11:29Z | 14:26 CEST | 0h 56m | 3B7FFB |
| 2026-07-13estimated | LFMI | ? | 12:09 CEST | 10:50Z | 0h 40m | 3B7FFB |
| 2026-06-25estimated | LFTH | LFTR | 14:02 CEST | 15:00 CEST | 0h 58m | 3B7FFB |
| 2026-06-24estimated | LFOJ | LFNZ | 14:16 CEST | 16:08 CEST | 1h 52m | 3B7FFB |
| 2026-06-23 | LFMI | LFOJ | 13:24 CEST | 15:26 CEST | 2h 01m | 3B7FFB |
| 2026-04-21 | LFMI | LFNE | 14:59 CEST | 16:42 CEST | 1h 42m | 3AAC3D |
| 2026-03-06partial | LFMI | ? | 14:40 CET | 3B7FA2 | ||
| 2026-03-06partial | LFMI | ? | 13:02 CET | 3B7FA2 | ||
| 2026-02-17partial | LFMI | ? | 13:36 CET | 3AAC3D | ||
| 2026-02-17partial | LFMI | ? | 12:52 CET | 3AAC3D | ||
| 2026-02-16partial | LFMI | ? | 13:13 CET | 3AAC3D | ||
| 2026-01-26partial | LFMI | ? | 09:16 CET | 3B7FA2 | ||
| 2026-01-08 | LFNT | LFMV | 16:30 CET | 17:06 CET | 0h 35m | 3B7FA2 |
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 AZUR31 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]