sensors Mode-S transponder
A27EBF
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N26XP · HAWKER BEECHCRAFT Hawker 750/850 · operated by CZZC AVIATION LLC
- Hex
- A27EBF
- Octal
- 50477277
- Decimal
- 10,649,279
- Country
- US
- Tail
- N26XP
- Type
- H25B
- Flights observed
- 75
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address A27EBF falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| N26XP | - | 75 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | N26XP | - | Jul 24, 18:00 UTC | Jul 24, 20:05 UTC | 2h 5m |
| 2026-07-24 | N26XP | - | Jul 24, 12:20 UTC | Jul 24, 14:35 UTC | 2h 15m |
| 2026-07-22 | N26XP | - | Jul 22, 20:30 UTC | Jul 22, 22:00 UTC | 1h 30m |
| 2026-07-22 | N26XP | - | Jul 22, 18:30 UTC | Jul 22, 20:15 UTC | 1h 45m |
| 2026-07-22 | N26XP | - | Jul 22, 14:35 UTC | Jul 22, 17:20 UTC | 2h 45m |
| 2026-07-22 | N26XP | - | Jul 22, 13:50 UTC | Jul 22, 14:20 UTC | 30m |
| 2026-07-20 | N26XP | - | Jul 20, 00:45 UTC | Jul 20, 02:25 UTC | 1h 40m |
| 2026-07-19 | N26XP | - | Jul 19, 22:50 UTC | Jul 20, 00:30 UTC | 1h 40m |
| 2026-07-19 | N26XP | LAS → FMY | Jul 19, 12:35 UTC | Jul 19, 17:10 UTC | 4h 35m |
| 2026-07-17 | N26XP | - | Jul 17, 18:19 UTC | Jul 17, 23:20 UTC | 5h 0m |
| 2026-07-16 | N26XP | FTY → FMY | Jul 16, 00:35 UTC | Jul 16, 01:45 UTC | 1h 10m |
| 2026-07-15 | N26XP | - | Jul 15, 13:05 UTC | Jul 15, 14:30 UTC | 1h 25m |
| 2026-07-14 | N26XP | - | Jul 14, 00:55 UTC | Jul 14, 01:55 UTC | 1h 0m |
| 2026-07-13 | N26XP | - | Jul 13, 21:05 UTC | Jul 13, 22:20 UTC | 1h 15m |
| 2026-07-05 | N26XP | - | Jul 5, 21:20 UTC | Jul 5, 21:45 UTC | 25m |
| 2026-07-05 | N26XP | - | Jul 5, 18:35 UTC | Jul 5, 19:30 UTC | 55m |
| 2026-07-03 | N26XP | - | Jul 3, 15:40 UTC | Jul 3, 17:05 UTC | 1h 25m |
| 2026-07-03 | N26XP | - | Jul 3, 11:45 UTC | Jul 3, 13:10 UTC | 1h 25m |
| 2026-06-29 | N26XP | - | Jun 29, 18:49 UTC | Jun 29, 20:09 UTC | 1h 20m |
| 2026-06-29 | N26XP | - | Jun 29, 16:55 UTC | Jun 29, 18:14 UTC | 1h 20m |
| 2026-06-26 | N26XP | - | Jun 26, 22:40 UTC | Jun 26, 22:55 UTC | 15m |
| 2026-06-26 | N26XP | - | Jun 26, 21:39 UTC | Jun 26, 22:05 UTC | 25m |
| 2026-06-25 | N26XP | IAD → FMY | Jun 25, 17:30 UTC | Jun 25, 19:44 UTC | 2h 15m |
| 2026-06-25 | N26XP | FMY → IAD | Jun 25, 12:15 UTC | Jun 25, 14:24 UTC | 2h 10m |
| 2026-06-22 | N26XP | - | Jun 22, 22:10 UTC | Jun 23, 00:24 UTC | 2h 15m |
| 2026-06-22 | N26XP | - | Jun 22, 11:54 UTC | Jun 22, 14:14 UTC | 2h 20m |
| 2026-06-21 | N26XP | - | Jun 21, 23:14 UTC | Jun 22, 01:35 UTC | 2h 20m |
| 2026-06-21 | N26XP | - | Jun 21, 20:14 UTC | Jun 21, 22:40 UTC | 2h 25m |
| 2026-06-17 | N26XP | - | Jun 17, 19:10 UTC | Jun 17, 19:30 UTC | 20m |
| 2026-06-17 | N26XP | - | Jun 17, 17:25 UTC | Jun 17, 17:50 UTC | 25m |
| 2026-06-06 | N26XP | - | Jun 6, 19:19 UTC | Jun 6, 21:44 UTC | 2h 25m |
| 2026-06-03 | N26XP | - | Jun 3, 16:55 UTC | Jun 3, 19:30 UTC | 2h 35m |
| 2026-05-23 | N26XP | HWO → FMY | May 23, 12:00 UTC | May 23, 12:25 UTC | 25m |
| 2026-05-23 | N26XP | - | May 23, 09:45 UTC | May 23, 10:10 UTC | 25m |
| 2026-05-21 | N26XP | - | May 21, 13:05 UTC | May 21, 23:05 UTC | 10h 0m |
| 2026-05-18 | N26XP | - | May 18, 00:20 UTC | May 18, 00:45 UTC | 25m |
| 2026-05-17 | N26XP | - | May 17, 23:05 UTC | May 17, 23:35 UTC | 30m |
| 2026-05-15 | N26XP | IAD → FMY | May 15, 00:00 UTC | May 15, 02:00 UTC | 2h 0m |
| 2026-05-14 | N26XP | - | May 14, 11:30 UTC | May 14, 13:30 UTC | 2h 0m |
| 2026-05-13 | N26XP | - | May 13, 20:30 UTC | May 13, 20:55 UTC | 25m |
| 2026-05-13 | N26XP | - | May 13, 19:30 UTC | May 13, 20:00 UTC | 30m |
| 2026-05-13 | N26XP | - | May 13, 13:40 UTC | May 13, 14:00 UTC | 20m |
| 2026-05-13 | N26XP | - | May 13, 11:45 UTC | May 13, 12:10 UTC | 25m |
| 2026-05-08 | N26XP | - | May 8, 21:20 UTC | May 8, 23:50 UTC | 2h 30m |
| 2026-05-08 | N26XP | - | May 8, 16:45 UTC | May 8, 18:55 UTC | 2h 10m |
| 2026-05-08 | N26XP | TEB → FMY | May 8, 00:29 UTC | May 8, 03:49 UTC | 3h 20m |
| 2026-05-07 | N26XP | - | May 7, 12:00 UTC | May 7, 14:25 UTC | 2h 25m |
| 2026-05-05 | N26XP | - | May 5, 00:30 UTC | May 5, 02:45 UTC | 2h 15m |
| 2026-05-04 | N26XP | - | May 4, 23:40 UTC | May 4, 23:55 UTC | 15m |
| 2026-05-04 | N26XP | - | May 4, 21:35 UTC | May 4, 23:35 UTC | 2h 0m |
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 N26XP page for operator, model, and routing details .