Not currently tracked · last seen 26d ago
- Flights observed
- 38
- Avg flight time
- 48m
- Typical route
- BOD → BOD
- Last seen
- 26d ago
Last known area
Recent flights last 38
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-07 | - | May 7, 13:30 UTC | May 7, 14:15 UTC | 45m |
| 2026-05-07 | - | May 7, 10:25 UTC | May 7, 11:25 UTC | 1h 0m |
| 2026-05-07 | - | May 7, 08:35 UTC | May 7, 09:45 UTC | 1h 10m |
| 2026-05-06 | - | May 6, 14:00 UTC | May 6, 16:20 UTC | 2h 20m |
| 2026-05-05 | - | May 5, 15:55 UTC | May 5, 16:25 UTC | 30m |
| 2026-05-05 | - | May 5, 13:55 UTC | May 5, 15:20 UTC | 1h 25m |
| 2026-05-03 | BOD → BOD | May 3, 08:10 UTC | May 3, 08:40 UTC | 30m |
| 2026-05-01 | BOD → BOD | May 1, 09:50 UTC | May 1, 10:35 UTC | 45m |
| 2026-04-29 | - | Apr 29, 14:45 UTC | Apr 29, 15:25 UTC | 40m |
| 2026-04-29 | - | Apr 29, 12:15 UTC | Apr 29, 12:55 UTC | 40m |
| 2026-04-29 | - | Apr 29, 08:05 UTC | Apr 29, 09:35 UTC | 1h 31m |
| 2026-04-28 | - | Apr 28, 14:10 UTC | Apr 28, 14:55 UTC | 45m |
| 2026-04-28 | - | Apr 28, 09:20 UTC | Apr 28, 09:55 UTC | 35m |
| 2026-04-27 | BOD → BOD | Apr 27, 17:30 UTC | Apr 27, 18:20 UTC | 50m |
| 2026-04-27 | BOD → BOD | Apr 27, 13:10 UTC | Apr 27, 14:15 UTC | 1h 5m |
| 2026-04-27 | BOD → BOD | Apr 27, 10:55 UTC | Apr 27, 12:00 UTC | 1h 5m |
| 2026-04-26 | - | Apr 26, 10:40 UTC | Apr 26, 11:20 UTC | 40m |
| 2026-04-26 | - | Apr 26, 09:05 UTC | Apr 26, 09:35 UTC | 30m |
| 2026-04-24 | - | Apr 24, 10:40 UTC | Apr 24, 11:25 UTC | 45m |
| 2026-04-24 | - | Apr 24, 07:05 UTC | Apr 24, 07:55 UTC | 50m |
| 2026-04-23 | - | Apr 23, 20:10 UTC | Apr 23, 21:35 UTC | 1h 25m |
| 2026-04-23 | - | Apr 23, 15:30 UTC | Apr 23, 16:40 UTC | 1h 10m |
| 2026-04-23 | - | Apr 23, 13:15 UTC | Apr 23, 14:20 UTC | 1h 5m |
| 2026-04-22 | BOD → BOD | Apr 22, 19:40 UTC | Apr 22, 20:40 UTC | 1h 0m |
| 2026-04-22 | - | Apr 22, 16:05 UTC | Apr 22, 16:40 UTC | 35m |
| 2026-04-22 | - | Apr 22, 14:25 UTC | Apr 22, 15:00 UTC | 35m |
| 2026-04-21 | - | Apr 21, 16:20 UTC | Apr 21, 17:05 UTC | 45m |
| 2026-04-21 | - | Apr 21, 14:20 UTC | Apr 21, 14:50 UTC | 30m |
| 2026-04-19 | BOD → BOD | Apr 19, 16:05 UTC | Apr 19, 16:55 UTC | 50m |
| 2026-04-18 | - | Apr 18, 17:10 UTC | Apr 18, 17:45 UTC | 35m |
| 2026-04-18 | BOD → BOD | Apr 18, 14:45 UTC | Apr 18, 15:20 UTC | 35m |
| 2026-04-17 | - | Apr 17, 17:25 UTC | Apr 17, 17:35 UTC | 10m |
| 2026-04-17 | - | Apr 17, 08:55 UTC | Apr 17, 09:15 UTC | 20m |
| 2026-04-16 | BOD → BOD | Apr 16, 19:45 UTC | Apr 16, 20:20 UTC | 35m |
| 2026-04-16 | - | Apr 16, 16:05 UTC | Apr 16, 16:35 UTC | 30m |
| 2026-04-15 | - | Apr 15, 15:05 UTC | Apr 15, 15:35 UTC | 30m |
| 2026-04-15 | - | Apr 15, 14:05 UTC | Apr 15, 14:50 UTC | 44m |
| 2026-04-13 | - | Apr 13, 17:30 UTC | Apr 13, 17:55 UTC | 25m |
Specifications
| Registration | F-HAAM |
| Aircraft type | CESSNA 172 Skyhawk (C172) |
| Mode-S code | 39800C · 16300014 (octal) |
Looking for transponder-level data? View the Mode-S 39800C page for country allocation, callsign history, and ADS-B signal details.
F-HAAM frequently asked
What type of aircraft is F-HAAM?
F-HAAM is a CESSNA 172 Skyhawk (ICAO type code C172).
What is the Mode-S transponder code for F-HAAM?
F-HAAM broadcasts on Mode-S (ICAO 24-bit) address 39800C (octal 16300014). View the transponder page.
What route does F-HAAM typically fly?
F-HAAM most frequently flies between BOD and BOD based on observed flights.
Where is F-HAAM right now?
F-HAAM is not currently being tracked; last seen 26d ago.