sensors Mode-S transponder
AE1FBB
ICAO 24-bit transponder address
Currently assigned to 10-72172 · Airbus Helicopters UH-72A Lakota
- Hex
- AE1FBB
- Octal
- 53417673
- Decimal
- 11,411,387
- Tail
- 10-72172
- Type
- EC45
- Flights observed
- 66
- Distinct callsigns
- 14
- Country
- -
- Last broadcast
- 13d ago
Last known position
Callsign history 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| G72237 | - | 47 | 2026-07-24 |
| YOGI43 | - | 3 | 2026-05-26 |
| YOGI24 | - | 2 | 2026-05-20 |
| POBOY13 | - | 2 | 2026-06-09 |
| EMOJI60 | - | 2 | 2026-05-20 |
| BELLS10 | - | 2 | 2026-06-09 |
| RIGOR18 | - | 1 | 2026-06-04 |
| RIGOR01 | - | 1 | 2026-06-08 |
| R0972172 | - | 1 | 2026-05-05 |
| POBOY17 | - | 1 | 2026-06-10 |
| NUKED47 | - | 1 | 2026-05-19 |
| NICAD13 | - | 1 | 2026-05-15 |
| MEANY53 | - | 1 | 2026-06-04 |
| MEANY19 | - | 1 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | G72237 | - | Jul 24, 20:40 UTC | Jul 24, 20:50 UTC | 10m |
| 2026-07-24 | G72237 | - | Jul 24, 15:50 UTC | Jul 24, 17:15 UTC | 1h 25m |
| 2026-07-23 | G72237 | - | Jul 23, 21:10 UTC | Jul 23, 22:00 UTC | 50m |
| 2026-07-23 | G72237 | - | Jul 23, 17:50 UTC | Jul 23, 18:20 UTC | 30m |
| 2026-07-22 | G72237 | - | Jul 22, 19:45 UTC | Jul 22, 20:20 UTC | 35m |
| 2026-07-22 | G72237 | - | Jul 22, 17:30 UTC | Jul 22, 18:00 UTC | 30m |
| 2026-07-21 | G72237 | - | Jul 21, 17:40 UTC | Jul 21, 19:15 UTC | 1h 35m |
| 2026-07-16 | G72237 | - | Jul 16, 17:45 UTC | Jul 16, 18:34 UTC | 50m |
| 2026-07-16 | G72237 | - | Jul 16, 04:45 UTC | Jul 16, 05:30 UTC | 45m |
| 2026-07-16 | G72237 | - | Jul 16, 04:05 UTC | Jul 16, 04:40 UTC | 35m |
| 2026-07-16 | G72237 | - | Jul 16, 00:10 UTC | Jul 16, 01:50 UTC | 1h 40m |
| 2026-07-15 | G72237 | - | Jul 15, 03:55 UTC | Jul 15, 05:45 UTC | 1h 50m |
| 2026-07-15 | G72237 | - | Jul 15, 00:05 UTC | Jul 15, 02:00 UTC | 1h 55m |
| 2026-07-12 | G72237 | - | Jul 12, 19:45 UTC | Jul 12, 20:01 UTC | 15m |
| 2026-07-12 | G72237 | - | Jul 12, 19:30 UTC | Jul 12, 19:40 UTC | 10m |
| 2026-07-12 | G72237 | - | Jul 12, 19:10 UTC | Jul 12, 19:20 UTC | 10m |
| 2026-07-12 | G72237 | - | Jul 12, 18:45 UTC | Jul 12, 19:01 UTC | 15m |
| 2026-07-12 | G72237 | - | Jul 12, 18:20 UTC | Jul 12, 18:40 UTC | 20m |
| 2026-07-12 | G72237 | - | Jul 12, 17:45 UTC | Jul 12, 18:10 UTC | 25m |
| 2026-07-12 | G72237 | - | Jul 12, 17:10 UTC | Jul 12, 17:30 UTC | 20m |
| 2026-07-11 | G72237 | - | Jul 11, 20:40 UTC | Jul 11, 22:55 UTC | 2h 15m |
| 2026-06-19 | G72237 | - | Jun 19, 16:25 UTC | Jun 19, 17:24 UTC | 1h 0m |
| 2026-06-16 | G72237 | - | Jun 16, 20:00 UTC | Jun 16, 21:05 UTC | 1h 5m |
| 2026-06-16 | G72237 | - | Jun 16, 04:10 UTC | Jun 16, 05:45 UTC | 1h 35m |
| 2026-06-10 | G72237 | - | Jun 10, 20:50 UTC | Jun 10, 21:30 UTC | 40m |
| 2026-06-10 | G72237 | - | Jun 10, 15:45 UTC | Jun 10, 16:35 UTC | 50m |
| 2026-06-10 | POBOY17 | - | Jun 10, 12:35 UTC | Jun 10, 12:45 UTC | 10m |
| 2026-06-09 | BELLS10 | - | Jun 9, 21:35 UTC | Jun 9, 22:10 UTC | 35m |
| 2026-06-09 | BELLS10 | - | Jun 9, 19:05 UTC | Jun 9, 20:30 UTC | 1h 25m |
| 2026-06-09 | POBOY13 | - | Jun 9, 14:10 UTC | Jun 9, 15:25 UTC | 1h 15m |
| 2026-06-09 | POBOY13 | - | Jun 9, 12:20 UTC | Jun 9, 13:25 UTC | 1h 5m |
| 2026-06-08 | RIGOR01 | - | Jun 8, 13:15 UTC | Jun 8, 13:30 UTC | 15m |
| 2026-06-06 | G72237 | - | Jun 6, 18:14 UTC | Jun 6, 19:10 UTC | 55m |
| 2026-06-05 | G72237 | - | Jun 5, 21:25 UTC | Jun 5, 21:55 UTC | 30m |
| 2026-06-05 | G72237 | - | Jun 5, 18:40 UTC | Jun 5, 19:45 UTC | 1h 5m |
| 2026-06-05 | MEANY19 | - | Jun 5, 12:15 UTC | Jun 5, 14:00 UTC | 1h 45m |
| 2026-06-05 | G72237 | - | Jun 5, 04:40 UTC | Jun 5, 06:05 UTC | 1h 25m |
| 2026-06-04 | G72237 | - | Jun 4, 23:55 UTC | Jun 5, 02:10 UTC | 2h 15m |
| 2026-06-04 | RIGOR18 | - | Jun 4, 18:50 UTC | Jun 4, 20:45 UTC | 1h 55m |
| 2026-06-04 | MEANY53 | - | Jun 4, 12:25 UTC | Jun 4, 14:05 UTC | 1h 40m |
| 2026-06-04 | G72237 | - | Jun 4, 03:00 UTC | Jun 4, 05:20 UTC | 2h 20m |
| 2026-06-01 | G72237 | - | Jun 1, 20:30 UTC | Jun 1, 21:10 UTC | 40m |
| 2026-05-26 | YOGI43 | - | May 26, 12:54 UTC | May 26, 15:39 UTC | 2h 45m |
| 2026-05-20 | YOGI24 | - | May 20, 20:45 UTC | May 20, 21:00 UTC | 15m |
| 2026-05-20 | YOGI24 | - | May 20, 18:45 UTC | May 20, 20:15 UTC | 1h 30m |
| 2026-05-20 | EMOJI60 | - | May 20, 14:55 UTC | May 20, 15:05 UTC | 10m |
| 2026-05-20 | EMOJI60 | - | May 20, 12:35 UTC | May 20, 14:45 UTC | 2h 10m |
| 2026-05-19 | YOGI43 | - | May 19, 20:20 UTC | May 19, 21:00 UTC | 40m |
| 2026-05-19 | YOGI43 | - | May 19, 18:50 UTC | May 19, 19:15 UTC | 25m |
| 2026-05-19 | NUKED47 | - | May 19, 15:00 UTC | May 19, 15:20 UTC | 20m |
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 10-72172 page for operator, model, and routing details .