sensors Mode-S transponder
ADFECB
ICAO 24-bit transponder address
Currently assigned to 84-00485 · Beech C-12U Huron
- Hex
- ADFECB
- Octal
- 53377313
- Decimal
- 11,402,955
- Tail
- 84-00485
- Type
- BE20
- Flights observed
- 50
- Distinct callsigns
- 15
- Country
- -
- Last broadcast
- 52m ago
Last known position
Callsign history 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PAT485 | - | 13 | 2026-07-14 |
| PAT276 | - | 5 | 2026-04-13 |
| PAT341 | - | 4 | 2026-06-27 |
| PAT950 | - | 3 | 2026-04-20 |
| PAT675 | - | 3 | 2026-06-09 |
| PAT332 | - | 3 | 2026-06-24 |
| PAT093 | - | 3 | 2026-06-22 |
| PAT720 | - | 2 | 2026-06-05 |
| PAT549 | - | 2 | 2026-04-30 |
| PAT375 | - | 2 | 2026-06-03 |
| PAT280 | - | 2 | 2026-04-26 |
| PAT251 | - | 2 | 2026-05-05 |
| PAT222 | - | 2 | 2026-05-08 |
| PAT114 | - | 2 | 2026-05-06 |
| PAT112 | - | 2 | 2026-05-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | PAT485 | - | Jul 14, 17:05 UTC | Jul 14, 18:45 UTC | 1h 40m |
| 2026-07-07 | PAT485 | - | Jul 7, 17:45 UTC | Jul 7, 19:05 UTC | 1h 20m |
| 2026-07-07 | PAT485 | - | Jul 7, 14:25 UTC | Jul 7, 16:55 UTC | 2h 30m |
| 2026-07-01 | PAT485 | - | Jul 1, 13:50 UTC | Jul 1, 18:10 UTC | 4h 20m |
| 2026-06-29 | PAT485 | - | Jun 29, 16:44 UTC | Jun 29, 17:55 UTC | 1h 10m |
| 2026-06-29 | PAT485 | - | Jun 29, 14:14 UTC | Jun 29, 15:00 UTC | 45m |
| 2026-06-27 | PAT341 | - | Jun 27, 00:05 UTC | Jun 27, 02:04 UTC | 2h 0m |
| 2026-06-26 | PAT341 | - | Jun 26, 21:45 UTC | Jun 26, 23:19 UTC | 1h 35m |
| 2026-06-26 | PAT341 | - | Jun 26, 18:49 UTC | Jun 26, 21:10 UTC | 2h 20m |
| 2026-06-26 | PAT341 | - | Jun 26, 15:34 UTC | Jun 26, 17:50 UTC | 2h 15m |
| 2026-06-24 | PAT332 | - | Jun 24, 17:45 UTC | Jun 24, 19:49 UTC | 2h 5m |
| 2026-06-24 | PAT332 | - | Jun 24, 15:39 UTC | Jun 24, 16:45 UTC | 1h 5m |
| 2026-06-24 | PAT332 | - | Jun 24, 13:24 UTC | Jun 24, 15:00 UTC | 1h 35m |
| 2026-06-22 | PAT093 | - | Jun 22, 19:19 UTC | Jun 22, 22:49 UTC | 3h 30m |
| 2026-06-22 | PAT093 | - | Jun 22, 16:24 UTC | Jun 22, 18:30 UTC | 2h 5m |
| 2026-06-22 | PAT093 | - | Jun 22, 13:05 UTC | Jun 22, 15:29 UTC | 2h 25m |
| 2026-06-18 | PAT485 | - | Jun 18, 18:00 UTC | Jun 18, 18:35 UTC | 35m |
| 2026-06-18 | PAT485 | - | Jun 18, 15:45 UTC | Jun 18, 17:10 UTC | 1h 25m |
| 2026-06-15 | PAT485 | - | Jun 15, 17:54 UTC | Jun 15, 19:00 UTC | 1h 5m |
| 2026-06-15 | PAT485 | - | Jun 15, 14:30 UTC | Jun 15, 16:04 UTC | 1h 35m |
| 2026-06-09 | PAT675 | - | Jun 9, 18:20 UTC | Jun 9, 21:00 UTC | 2h 40m |
| 2026-06-09 | PAT675 | - | Jun 9, 15:35 UTC | Jun 9, 15:50 UTC | 15m |
| 2026-06-09 | PAT675 | - | Jun 9, 12:45 UTC | Jun 9, 14:25 UTC | 1h 40m |
| 2026-06-08 | PAT485 | - | Jun 8, 14:05 UTC | Jun 8, 16:15 UTC | 2h 10m |
| 2026-06-05 | PAT720 | - | Jun 5, 15:45 UTC | Jun 5, 17:35 UTC | 1h 50m |
| 2026-06-05 | PAT720 | - | Jun 5, 09:50 UTC | Jun 5, 11:35 UTC | 1h 45m |
| 2026-06-03 | PAT375 | - | Jun 3, 16:10 UTC | Jun 3, 16:45 UTC | 35m |
| 2026-06-03 | PAT375 | - | Jun 3, 14:00 UTC | Jun 3, 15:00 UTC | 1h 0m |
| 2026-05-08 | PAT222 | - | May 8, 19:45 UTC | May 8, 22:20 UTC | 2h 35m |
| 2026-05-08 | PAT222 | - | May 8, 17:20 UTC | May 8, 19:10 UTC | 1h 50m |
| 2026-05-06 | PAT114 | SVN → FFT | May 6, 17:20 UTC | May 6, 19:35 UTC | 2h 14m |
| 2026-05-06 | PAT114 | - | May 6, 13:25 UTC | May 6, 15:15 UTC | 1h 50m |
| 2026-05-05 | PAT251 | - | May 5, 17:55 UTC | May 5, 19:45 UTC | 1h 50m |
| 2026-05-05 | PAT251 | - | May 5, 10:55 UTC | May 5, 12:45 UTC | 1h 50m |
| 2026-05-04 | PAT112 | - | May 4, 13:55 UTC | May 4, 15:55 UTC | 2h 0m |
| 2026-05-04 | PAT112 | - | May 4, 11:20 UTC | May 4, 12:55 UTC | 1h 35m |
| 2026-04-30 | PAT549 | MNZ → FFT | Apr 30, 14:05 UTC | Apr 30, 15:55 UTC | 1h 50m |
| 2026-04-30 | PAT549 | - | Apr 30, 11:55 UTC | Apr 30, 13:20 UTC | 1h 25m |
| 2026-04-26 | PAT280 | MNZ → FFT | Apr 26, 22:20 UTC | Apr 26, 23:50 UTC | 1h 30m |
| 2026-04-26 | PAT280 | - | Apr 26, 19:50 UTC | Apr 26, 21:25 UTC | 1h 35m |
| 2026-04-22 | PAT485 | - | Apr 22, 16:10 UTC | Apr 22, 16:50 UTC | 40m |
| 2026-04-22 | PAT485 | - | Apr 22, 13:30 UTC | Apr 22, 15:05 UTC | 1h 35m |
| 2026-04-20 | PAT950 | - | Apr 20, 19:30 UTC | Apr 20, 20:00 UTC | 30m |
| 2026-04-20 | PAT950 | - | Apr 20, 16:15 UTC | Apr 20, 18:55 UTC | 2h 40m |
| 2026-04-20 | PAT950 | - | Apr 20, 12:45 UTC | Apr 20, 14:55 UTC | 2h 10m |
| 2026-04-13 | PAT276 | - | Apr 13, 20:00 UTC | Apr 13, 20:10 UTC | 10m |
| 2026-04-13 | PAT276 | - | Apr 13, 17:25 UTC | Apr 13, 18:25 UTC | 1h 0m |
| 2026-04-13 | PAT276 | - | Apr 13, 14:40 UTC | Apr 13, 15:40 UTC | 1h 0m |
| 2026-04-13 | PAT276 | - | Apr 13, 12:20 UTC | Apr 13, 13:35 UTC | 1h 15m |
| 2026-04-13 | PAT276 | - | Apr 13, 12:10 UTC | Apr 13, 13:35 UTC | 1h 25m |
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 84-00485 page for operator, model, and routing details .