sensors Mode-S transponder
448F2E
ICAO 24-bit transponder address · allocated to Belgium
Currently assigned to OO-CYN · EMBRAER EMB-550 Praetor 600
- Hex
- 448F2E
- Octal
- 21107456
- Decimal
- 4,493,102
- Country
- BE
- Tail
- OO-CYN
- Type
- E550
- Flights observed
- 37
- Distinct callsigns
- 20
- Country
- BE
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 448F2E falls within the block assigned to Belgium (BE) by ICAO Annex 10, Volume III. Every aircraft registered in Belgium receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OOCYN | - | 5 | 2026-04-30 |
| FYG81YN | - | 3 | 2026-06-14 |
| FYG73YN | - | 2 | 2026-05-28 |
| FYG61YN | - | 2 | 2026-05-26 |
| FYG42YN | - | 2 | 2026-06-05 |
| FYG34YN | - | 2 | 2026-06-05 |
| FYG33YN | - | 2 | 2026-06-03 |
| FYG22YN | - | 2 | 2026-06-14 |
| FYG12YN | - | 2 | 2026-05-09 |
| FYG11YN | - | 2 | 2026-06-13 |
| FYG74YN | - | 1 | 2026-05-17 |
| FYG64YN | - | 1 | 2026-05-20 |
| FYG62YN | - | 1 | 2026-05-26 |
| FYG52YN | - | 1 | 2026-05-08 |
| FYG51YN | - | 1 | 2026-05-07 |
| FYG46YN | - | 1 | 2026-05-14 |
| FYG35YN | - | 1 | 2026-05-17 |
| FYG26YN | - | 1 | 2026-05-13 |
| FYG25YN | - | 1 | 2026-05-13 |
| FYG21YN | - | 1 | 2026-05-19 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-14 | FYG22YN | - | Jun 14, 11:50 UTC | Jun 14, 14:15 UTC | 2h 25m |
| 2026-06-14 | FYG81YN | - | Jun 14, 09:15 UTC | Jun 14, 09:50 UTC | 35m |
| 2026-06-13 | FYG11YN | IBZ → KJK | Jun 13, 16:15 UTC | Jun 13, 18:05 UTC | 1h 50m |
| 2026-06-11 | FYG10YN | - | Jun 11, 07:05 UTC | Jun 11, 09:00 UTC | 1h 55m |
| 2026-06-11 | FYG13YN | ANR → KJK | Jun 11, 05:35 UTC | Jun 11, 05:55 UTC | 20m |
| 2026-06-05 | FYG42YN | - | Jun 5, 08:20 UTC | Jun 5, 09:35 UTC | 1h 15m |
| 2026-06-05 | FYG34YN | - | Jun 5, 06:30 UTC | Jun 5, 06:45 UTC | 15m |
| 2026-06-03 | FYG33YN | - | Jun 3, 10:50 UTC | Jun 3, 11:05 UTC | 15m |
| 2026-06-03 | FYG81YN | - | Jun 3, 08:05 UTC | Jun 3, 09:25 UTC | 1h 20m |
| 2026-05-31 | FYG22YN | BUD → ANR | May 31, 11:00 UTC | May 31, 12:40 UTC | 1h 40m |
| 2026-05-31 | FYG14YN | - | May 31, 09:25 UTC | May 31, 09:50 UTC | 25m |
| 2026-05-28 | FYG73YN | - | May 28, 16:35 UTC | May 28, 16:50 UTC | 15m |
| 2026-05-28 | FYG81YN | - | May 28, 14:05 UTC | May 28, 15:40 UTC | 1h 35m |
| 2026-05-26 | FYG62YN | - | May 26, 16:35 UTC | May 26, 18:50 UTC | 2h 15m |
| 2026-05-26 | FYG61YN | - | May 26, 13:04 UTC | May 26, 15:24 UTC | 2h 20m |
| 2026-05-20 | FYG64YN | - | May 20, 17:35 UTC | May 20, 19:15 UTC | 1h 40m |
| 2026-05-20 | FYG73YN | - | May 20, 14:50 UTC | May 20, 16:30 UTC | 1h 40m |
| 2026-05-20 | FYG61YN | - | May 20, 11:40 UTC | May 20, 13:45 UTC | 2h 5m |
| 2026-05-19 | FYG42YN | - | May 19, 09:15 UTC | May 19, 10:50 UTC | 1h 35m |
| 2026-05-19 | FYG21YN | - | May 19, 05:10 UTC | May 19, 06:30 UTC | 1h 20m |
| 2026-05-17 | FYG74YN | - | May 17, 12:01 UTC | May 17, 12:30 UTC | 30m |
| 2026-05-17 | FYG35YN | - | May 17, 09:35 UTC | May 17, 11:01 UTC | 1h 25m |
| 2026-05-14 | FYG34YN | - | May 14, 12:45 UTC | May 14, 14:15 UTC | 1h 30m |
| 2026-05-14 | FYG46YN | - | May 14, 11:20 UTC | May 14, 11:55 UTC | 35m |
| 2026-05-14 | FYG33YN | ANR → FMO | May 14, 07:35 UTC | May 14, 10:45 UTC | 3h 10m |
| 2026-05-13 | FYG26YN | VCE → ANR | May 13, 17:20 UTC | May 13, 18:40 UTC | 1h 20m |
| 2026-05-13 | FYG25YN | - | May 13, 14:35 UTC | May 13, 15:50 UTC | 1h 15m |
| 2026-05-09 | FYG12YN | - | May 9, 09:20 UTC | May 9, 10:30 UTC | 1h 10m |
| 2026-05-08 | FYG52YN | IBZ → CPH | May 8, 12:10 UTC | May 8, 14:55 UTC | 2h 45m |
| 2026-05-07 | FYG51YN | - | May 7, 16:15 UTC | May 7, 18:25 UTC | 2h 10m |
| 2026-05-07 | FYG12YN | - | May 7, 10:55 UTC | May 7, 12:05 UTC | 1h 10m |
| 2026-05-07 | FYG11YN | - | May 7, 08:15 UTC | May 7, 09:20 UTC | 1h 5m |
| 2026-04-30 | OOCYN | XRY → ANR | Apr 30, 17:20 UTC | Apr 30, 19:45 UTC | 2h 25m |
| 2026-04-30 | OOCYN | - | Apr 30, 13:45 UTC | Apr 30, 16:10 UTC | 2h 25m |
| 2026-04-24 | OOCYN | LIN → ANR | Apr 24, 15:55 UTC | Apr 24, 17:00 UTC | 1h 5m |
| 2026-04-23 | OOCYN | - | Apr 23, 06:10 UTC | Apr 23, 07:25 UTC | 1h 15m |
| 2026-04-18 | OOCYN | - | Apr 18, 21:05 UTC | Apr 19, 08:10 UTC | 11h 5m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the OO-CYN page for operator, model, and routing details .