sensors Mode-S transponder
ADFE47
ICAO 24-bit transponder address
Currently assigned to 94-00315 · Beech C-12V Huron
- Hex
- ADFE47
- Octal
- 53377107
- Decimal
- 11,402,823
- Tail
- 94-00315
- Type
- BE20
- Flights observed
- 50
- Distinct callsigns
- 14
- Country
- -
- Last broadcast
- 8d ago
Current position
Callsign history 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PAT315 | - | 26 | 2026-06-12 |
| PAT222 | - | 4 | 2026-06-26 |
| PAT973 | - | 2 | 2026-06-15 |
| PAT764 | - | 2 | 2026-07-12 |
| PAT536 | - | 2 | 2026-06-30 |
| PAT451 | - | 2 | 2026-07-01 |
| PAT368 | - | 2 | 2026-07-15 |
| PAT233 | - | 2 | 2026-07-23 |
| PAT215 | - | 2 | 2026-07-24 |
| PAT046 | - | 2 | 2026-06-24 |
| PAT888 | - | 1 | 2026-07-21 |
| PAT852 | - | 1 | 2026-07-16 |
| PAT817 | - | 1 | 2026-06-09 |
| PAT044 | - | 1 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | PAT215 | - | Jul 24, 16:45 UTC | Jul 24, 18:50 UTC | 2h 5m |
| 2026-07-24 | PAT215 | - | Jul 24, 13:10 UTC | Jul 24, 15:45 UTC | 2h 35m |
| 2026-07-23 | PAT233 | - | Jul 23, 17:35 UTC | Jul 23, 19:55 UTC | 2h 20m |
| 2026-07-23 | PAT233 | - | Jul 23, 13:20 UTC | Jul 23, 16:10 UTC | 2h 50m |
| 2026-07-21 | PAT888 | ILG → ILG | Jul 21, 12:20 UTC | Jul 21, 14:35 UTC | 2h 15m |
| 2026-07-16 | PAT852 | - | Jul 16, 15:40 UTC | Jul 16, 18:55 UTC | 3h 15m |
| 2026-07-15 | PAT368 | - | Jul 15, 20:00 UTC | Jul 15, 21:05 UTC | 1h 5m |
| 2026-07-15 | PAT368 | - | Jul 15, 16:25 UTC | Jul 15, 19:10 UTC | 2h 45m |
| 2026-07-12 | PAT764 | - | Jul 12, 16:10 UTC | Jul 12, 18:01 UTC | 1h 50m |
| 2026-07-12 | PAT764 | - | Jul 12, 13:20 UTC | Jul 12, 15:05 UTC | 1h 45m |
| 2026-07-01 | PAT451 | - | Jul 1, 16:40 UTC | Jul 1, 20:00 UTC | 3h 20m |
| 2026-07-01 | PAT451 | - | Jul 1, 12:15 UTC | Jul 1, 16:00 UTC | 3h 45m |
| 2026-06-30 | PAT536 | - | Jun 30, 16:25 UTC | Jun 30, 18:00 UTC | 1h 35m |
| 2026-06-30 | PAT536 | - | Jun 30, 13:00 UTC | Jun 30, 14:40 UTC | 1h 40m |
| 2026-06-26 | PAT222 | - | Jun 26, 22:05 UTC | Jun 27, 00:34 UTC | 2h 30m |
| 2026-06-26 | PAT222 | - | Jun 26, 18:29 UTC | Jun 26, 21:20 UTC | 2h 50m |
| 2026-06-25 | PAT222 | - | Jun 25, 16:59 UTC | Jun 25, 19:49 UTC | 2h 50m |
| 2026-06-25 | PAT222 | - | Jun 25, 13:35 UTC | Jun 25, 16:14 UTC | 2h 40m |
| 2026-06-24 | PAT046 | - | Jun 24, 16:54 UTC | Jun 24, 18:25 UTC | 1h 30m |
| 2026-06-24 | PAT046 | - | Jun 24, 13:10 UTC | Jun 24, 15:00 UTC | 1h 50m |
| 2026-06-23 | PAT044 | - | Jun 23, 14:25 UTC | Jun 23, 16:20 UTC | 1h 55m |
| 2026-06-15 | PAT973 | - | Jun 15, 17:15 UTC | Jun 15, 19:20 UTC | 2h 5m |
| 2026-06-15 | PAT973 | - | Jun 15, 12:55 UTC | Jun 15, 15:55 UTC | 3h 0m |
| 2026-06-12 | PAT315 | - | Jun 12, 17:15 UTC | Jun 12, 18:15 UTC | 1h 0m |
| 2026-06-12 | PAT315 | - | Jun 12, 11:45 UTC | Jun 12, 12:40 UTC | 55m |
| 2026-06-11 | PAT315 | - | Jun 11, 16:45 UTC | Jun 11, 19:00 UTC | 2h 15m |
| 2026-06-11 | PAT315 | - | Jun 11, 13:10 UTC | Jun 11, 15:35 UTC | 2h 25m |
| 2026-06-10 | PAT315 | DAA → ILG | Jun 10, 15:00 UTC | Jun 10, 15:35 UTC | 35m |
| 2026-06-09 | PAT817 | - | Jun 9, 16:55 UTC | Jun 9, 18:30 UTC | 1h 35m |
| 2026-04-22 | PAT315 | - | Apr 22, 03:40 UTC | Apr 22, 05:30 UTC | 1h 50m |
| 2026-04-22 | PAT315 | UCE → CHA | Apr 22, 01:20 UTC | Apr 22, 03:10 UTC | 1h 50m |
| 2026-04-21 | PAT315 | - | Apr 21, 21:10 UTC | Apr 22, 00:15 UTC | 3h 5m |
| 2026-04-21 | PAT315 | - | Apr 21, 17:35 UTC | Apr 21, 20:05 UTC | 2h 30m |
| 2026-04-21 | PAT315 | HIO → SFO | Apr 21, 03:00 UTC | Apr 21, 06:10 UTC | 3h 10m |
| 2026-04-20 | PAT315 | - | Apr 20, 21:55 UTC | Apr 20, 22:25 UTC | 30m |
| 2026-04-20 | PAT315 | - | Apr 20, 20:35 UTC | Apr 20, 21:10 UTC | 35m |
| 2026-04-20 | PAT315 | - | Apr 20, 19:20 UTC | Apr 20, 19:30 UTC | 10m |
| 2026-04-20 | PAT315 | - | Apr 20, 17:10 UTC | Apr 20, 17:20 UTC | 10m |
| 2026-04-20 | PAT315 | - | Apr 20, 15:50 UTC | Apr 20, 16:30 UTC | 40m |
| 2026-04-20 | PAT315 | - | Apr 20, 06:10 UTC | Apr 20, 07:00 UTC | 50m |
| 2026-04-20 | PAT315 | - | Apr 20, 05:00 UTC | Apr 20, 05:10 UTC | 10m |
| 2026-04-19 | PAT315 | - | Apr 19, 21:55 UTC | Apr 19, 23:30 UTC | 1h 35m |
| 2026-04-19 | PAT315 | - | Apr 19, 17:45 UTC | Apr 19, 19:20 UTC | 1h 35m |
| 2026-04-19 | PAT315 | - | Apr 19, 16:15 UTC | Apr 19, 16:55 UTC | 40m |
| 2026-04-19 | PAT315 | - | Apr 19, 01:35 UTC | Apr 19, 02:15 UTC | 40m |
| 2026-04-18 | PAT315 | - | Apr 18, 21:10 UTC | Apr 19, 00:40 UTC | 3h 30m |
| 2026-04-18 | PAT315 | - | Apr 18, 18:10 UTC | Apr 18, 20:10 UTC | 2h 0m |
| 2026-04-18 | PAT315 | - | Apr 18, 14:25 UTC | Apr 18, 17:15 UTC | 2h 50m |
| 2026-04-17 | PAT315 | - | Apr 17, 19:25 UTC | Apr 17, 20:45 UTC | 1h 20m |
| 2026-04-17 | PAT315 | - | Apr 17, 19:10 UTC | Apr 17, 19:20 UTC | 10m |
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 94-00315 page for operator, model, and routing details .