sensors Mode-S transponder

A6BF88

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N534CN · operated by CORPORATE FLIGHT MANAGEMENT INC.

Hex
A6BF88
Octal
51537610
Decimal
10,928,008
Country
US
Tail
N534CN
No current signal · last broadcast 2h ago
Flights observed
296
Distinct callsigns
20
Country
US
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S A6BF88.

Country allocation

The ICAO 24-bit address A6BF88 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 20 distinct

Callsign Airline Flights Last seen
VTE3802 - 19 2026-07-13
VTE3937 - 18 2026-07-08
VTE3936 - 16 2026-07-06
VTE3803 - 15 2026-07-13
VTE3418 - 15 2026-07-13
VTE3415 - 15 2026-07-14
VTE3934 - 13 2026-07-07
VTE3801 - 12 2026-06-24
VTE3416 - 12 2026-07-11
VTE3417 - 11 2026-07-02
VTE3421 - 10 2026-07-10
VTE3804 - 9 2026-06-23
VTE3939 - 8 2026-07-07
VTE3424 - 8 2026-07-09
VTE3422 Corporate Flight Management 7 2026-07-09
VTE3115 Corporate Flight Management 7 2026-06-14
VTE8534 - 6 2026-07-14
VTE3902 Corporate Flight Management 6 2026-05-17
VTE3423 - 6 2026-07-09
VTE3901 Corporate Flight Management 5 2026-05-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-20 VTE3027 ORD → MBL Jul 20, 16:30 UTCJul 20, 17:00 UTC30m
2026-07-20 VTE3020 MBL → ORD Jul 20, 14:10 UTCJul 20, 14:45 UTC35m
2026-07-19 VTE3029 ORD → MBL Jul 19, 23:30 UTCJul 20, 00:05 UTC35m
2026-07-19 VTE3024 MBL → ORD Jul 19, 20:15 UTCJul 19, 21:10 UTC55m
2026-07-19 VTE3027 ORD → MBL Jul 19, 16:50 UTCJul 19, 17:20 UTC30m
2026-07-19 VTE3020 MBL → ORD Jul 19, 14:10 UTCJul 19, 15:05 UTC55m
2026-07-19 VTE3029 ORD → MBL Jul 19, 00:00 UTCJul 19, 00:30 UTC30m
2026-07-18 VTE3024 MBL → ORD Jul 18, 21:30 UTCJul 18, 22:15 UTC45m
2026-07-18 VTE3027 ORD → MBL Jul 18, 19:00 UTCJul 18, 19:35 UTC35m
2026-07-18 VTE3020 MBL → ORD Jul 18, 17:00 UTCJul 18, 17:35 UTC35m
2026-07-18 VTE3093 - Jul 18, 14:20 UTCJul 18, 15:15 UTC55m
2026-07-17 VTE3092 - Jul 17, 22:29 UTCJul 17, 23:25 UTC55m
2026-07-17 VTE3091 - Jul 17, 19:30 UTCJul 17, 20:25 UTC55m
2026-07-17 VTE3094 - Jul 17, 17:44 UTCJul 17, 18:25 UTC40m
2026-07-17 VTE3093 - Jul 17, 15:00 UTCJul 17, 16:00 UTC1h 0m
2026-07-17 VTE3092 - Jul 17, 01:45 UTCJul 17, 02:39 UTC55m
2026-07-16 VTE3091 - Jul 16, 22:55 UTCJul 16, 23:55 UTC1h 0m
2026-07-16 VTE3094 - Jul 16, 21:25 UTCJul 16, 22:05 UTC40m
2026-07-16 VTE3051 MQY → ORD Jul 16, 17:25 UTCJul 16, 19:50 UTC2h 25m
2026-07-16 VTE9534 ORD → MQY Jul 16, 01:30 UTCJul 16, 02:30 UTC1h 0m
2026-07-15 VTE3093 - Jul 15, 14:15 UTCJul 15, 15:15 UTC1h 0m
2026-07-14 VTE8534 - Jul 14, 18:50 UTCJul 14, 19:45 UTC55m
2026-07-14 VTE3415 - Jul 14, 10:30 UTCJul 14, 11:25 UTC55m
2026-07-13 VTE3418 - Jul 13, 21:55 UTCJul 13, 22:40 UTC45m
2026-07-13 VTE3803 - Jul 13, 18:05 UTCJul 13, 19:10 UTC1h 5m
2026-07-13 VTE3802 - Jul 13, 15:35 UTCJul 13, 16:30 UTC55m
2026-07-12 VTE3415 - Jul 12, 10:45 UTCJul 12, 11:35 UTC50m
2026-07-11 VTE3412 - Jul 11, 18:30 UTCJul 11, 19:25 UTC55m
2026-07-11 VTE3411 - Jul 11, 15:55 UTCJul 11, 16:50 UTC55m
2026-07-11 VTE3416 - Jul 11, 14:25 UTCJul 11, 15:10 UTC45m
2026-07-10 VTE3421 - Jul 10, 12:45 UTCJul 10, 13:20 UTC35m
2026-07-09 VTE3424 - Jul 9, 23:10 UTCJul 9, 23:35 UTC25m
2026-07-09 VTE3423 - Jul 9, 20:20 UTCJul 9, 20:50 UTC30m
2026-07-09 VTE3422 CLT → BKW Jul 9, 16:40 UTCJul 9, 17:05 UTC25m
2026-07-09 VTE3421 - Jul 9, 13:25 UTCJul 9, 14:10 UTC45m
2026-07-08 VTE3428 - Jul 8, 22:05 UTCJul 8, 22:55 UTC50m
2026-07-08 VTE3427 - Jul 8, 19:20 UTCJul 8, 20:05 UTC45m
2026-07-08 VTE3422 CLT → BKW Jul 8, 16:30 UTCJul 8, 16:55 UTC25m
2026-07-08 VTE3937 - Jul 8, 12:40 UTCJul 8, 13:45 UTC1h 5m
2026-07-08 VTE5424 - Jul 8, 00:15 UTCJul 8, 00:45 UTC30m
2026-07-07 VTE5424 - Jul 7, 23:15 UTCJul 7, 23:40 UTC25m
2026-07-07 VTE3939 - Jul 7, 19:55 UTCJul 7, 21:10 UTC1h 15m
2026-07-07 VTE3934 - Jul 7, 18:10 UTCJul 7, 19:15 UTC1h 5m
2026-07-07 VTE3937 - Jul 7, 11:20 UTCJul 7, 12:30 UTC1h 10m
2026-07-06 VTE3936 - Jul 6, 22:20 UTCJul 6, 23:15 UTC55m
2026-07-06 VTE3803 - Jul 6, 18:20 UTCJul 6, 19:30 UTC1h 10m
2026-07-06 VTE3802 - Jul 6, 15:10 UTCJul 6, 16:10 UTC1h 0m
2026-07-06 VTE3937 - Jul 6, 12:00 UTCJul 6, 13:10 UTC1h 10m
2026-07-05 VTE3936 - Jul 5, 22:00 UTCJul 5, 22:55 UTC55m
2026-07-05 VTE3803 - Jul 5, 18:15 UTCJul 5, 19:30 UTC1h 15m

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 N534CN page for operator, model, and routing details .

Mode-S A6BF88 frequently asked

What is Mode-S code A6BF88?
A6BF88 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N534CN.
Where is Mode-S A6BF88 registered?
Mode-S code A6BF88 is allocated to United States (US). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is A6BF88 broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A6BF88, octal 51537610, decimal 10,928,008.
What flights does A6BF88 operate?
Mode-S A6BF88 has broadcast 20 distinct callsigns, including VTE3802, VTE3937, VTE3936, VTE3803, VTE3418.