Not currently tracked · last seen 2h ago
- Flights observed
- 313 showing last 50
- Avg flight time
- 3h 50m
- Typical route
- MUC → MUC
- Last seen
- 2h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 11:10 UTC | Jul 14, 14:25 UTC | 3h 15m |
| 2026-07-14 | - | Jul 14, 08:05 UTC | Jul 14, 09:45 UTC | 1h 40m |
| 2026-07-14 | - | Jul 14, 04:50 UTC | Jul 14, 06:10 UTC | 1h 20m |
| 2026-07-13 | - | Jul 13, 17:45 UTC | Jul 13, 21:15 UTC | 3h 30m |
| 2026-07-13 | - | Jul 13, 11:25 UTC | Jul 13, 14:30 UTC | 3h 5m |
| 2026-07-13 | - | Jul 13, 07:45 UTC | Jul 13, 10:15 UTC | 2h 30m |
| 2026-07-13 | MUC → KGS | Jul 13, 04:00 UTC | Jul 13, 06:15 UTC | 2h 15m |
| 2026-07-12 | MUC → MUC | Jul 12, 11:15 UTC | Jul 12, 20:45 UTC | 9h 30m |
| 2026-07-12 | - | Jul 12, 07:50 UTC | Jul 12, 09:30 UTC | 1h 40m |
| 2026-07-12 | MUC → MAH | Jul 12, 05:01 UTC | Jul 12, 06:40 UTC | 1h 40m |
| 2026-07-11 | MUC → MUC | Jul 11, 11:40 UTC | Jul 11, 21:10 UTC | 9h 30m |
| 2026-07-11 | KGS → MUC | Jul 11, 07:50 UTC | Jul 11, 10:20 UTC | 2h 30m |
| 2026-07-11 | MUC → KGS | Jul 11, 04:15 UTC | Jul 11, 06:35 UTC | 2h 20m |
| 2026-07-10 | MUC → MUC | Jul 10, 06:30 UTC | Jul 10, 20:40 UTC | 14h 10m |
| 2026-07-09 | OPO → MUC | Jul 9, 16:35 UTC | Jul 9, 19:00 UTC | 2h 25m |
| 2026-07-09 | MUC → OPO | Jul 9, 12:40 UTC | Jul 9, 15:05 UTC | 2h 25m |
| 2026-07-09 | RHO → MUC | Jul 9, 07:50 UTC | Jul 9, 10:35 UTC | 2h 45m |
| 2026-07-09 | MUC → RHO | Jul 9, 04:15 UTC | Jul 9, 06:35 UTC | 2h 20m |
| 2026-07-08 | MUC → MUC | Jul 8, 11:20 UTC | Jul 8, 20:40 UTC | 9h 20m |
| 2026-07-08 | DJE → MUC | Jul 8, 07:35 UTC | Jul 8, 10:00 UTC | 2h 25m |
| 2026-07-08 | MUC → DJE | Jul 8, 04:30 UTC | Jul 8, 06:35 UTC | 2h 5m |
| 2026-07-07 | - | Jul 7, 11:05 UTC | Jul 7, 20:25 UTC | 9h 20m |
| 2026-07-06 | - | Jul 6, 17:10 UTC | Jul 6, 21:10 UTC | 4h 0m |
| 2026-07-06 | - | Jul 6, 11:25 UTC | Jul 6, 15:40 UTC | 4h 15m |
| 2026-07-06 | - | Jul 6, 07:50 UTC | Jul 6, 10:20 UTC | 2h 30m |
| 2026-07-06 | - | Jul 6, 04:10 UTC | Jul 6, 06:25 UTC | 2h 15m |
| 2026-07-05 | - | Jul 5, 17:00 UTC | Jul 5, 21:05 UTC | 4h 5m |
| 2026-07-05 | - | Jul 5, 11:25 UTC | Jul 5, 15:40 UTC | 4h 15m |
| 2026-07-05 | - | Jul 5, 07:45 UTC | Jul 5, 09:35 UTC | 1h 50m |
| 2026-07-05 | MUC → MAH | Jul 5, 04:55 UTC | Jul 5, 06:35 UTC | 1h 40m |
| 2026-07-04 | - | Jul 4, 17:25 UTC | Jul 4, 21:15 UTC | 3h 50m |
| 2026-07-04 | - | Jul 4, 11:40 UTC | Jul 4, 15:55 UTC | 4h 15m |
| 2026-07-04 | KGS → MUC | Jul 4, 07:35 UTC | Jul 4, 10:10 UTC | 2h 35m |
| 2026-07-04 | MUC → KGS | Jul 4, 04:15 UTC | Jul 4, 06:25 UTC | 2h 10m |
| 2026-07-03 | MUC → MUC | Jul 3, 06:25 UTC | Jul 3, 21:10 UTC | 14h 45m |
| 2026-07-02 | - | Jul 2, 17:15 UTC | Jul 2, 21:20 UTC | 4h 5m |
| 2026-07-02 | - | Jul 2, 10:50 UTC | Jul 2, 14:55 UTC | 4h 5m |
| 2026-07-02 | - | Jul 2, 07:25 UTC | Jul 2, 09:05 UTC | 1h 40m |
| 2026-07-02 | - | Jul 2, 04:25 UTC | Jul 2, 05:50 UTC | 1h 25m |
| 2026-07-01 | FNC → MUC | Jul 1, 14:55 UTC | Jul 1, 18:55 UTC | 4h 0m |
| 2026-07-01 | - | Jul 1, 12:00 UTC | Jul 1, 13:35 UTC | 1h 35m |
| 2026-06-30 | - | Jun 30, 16:00 UTC | Jun 30, 16:55 UTC | 55m |
| 2026-06-30 | - | Jun 30, 12:20 UTC | Jun 30, 15:30 UTC | 3h 10m |
| 2026-06-30 | CFU → MUC | Jun 30, 09:25 UTC | Jun 30, 11:05 UTC | 1h 40m |
| 2026-06-30 | MUC → CFU | Jun 30, 06:25 UTC | Jun 30, 07:55 UTC | 1h 30m |
| 2026-06-29 | MUC → MUC | Jun 29, 11:35 UTC | Jun 29, 21:39 UTC | 10h 5m |
| 2026-06-29 | KGS → MUC | Jun 29, 07:50 UTC | Jun 29, 10:15 UTC | 2h 25m |
| 2026-06-29 | - | Jun 29, 04:04 UTC | Jun 29, 06:34 UTC | 2h 30m |
| 2026-06-28 | - | Jun 28, 17:34 UTC | Jun 28, 21:34 UTC | 4h 0m |
| 2026-06-28 | - | Jun 28, 11:19 UTC | Jun 28, 15:14 UTC | 3h 55m |
Specifications
| Registration | D-AMAE |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 3C7425 · 17072045 (octal) |
Looking for transponder-level data? View the Mode-S 3C7425 page for country allocation, callsign history, and ADS-B signal details.
D-AMAE frequently asked
What type of aircraft is D-AMAE?
D-AMAE is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for D-AMAE?
D-AMAE broadcasts on Mode-S (ICAO 24-bit) address 3C7425 (octal 17072045). View the transponder page.
What route does D-AMAE typically fly?
D-AMAE most frequently flies between MUC and MUC based on observed flights.
Where is D-AMAE right now?
D-AMAE is not currently being tracked; last seen 2h ago.