sensors Mode-S transponder

A12BF1

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N175BZ · operated by WILMINGTON TRUST CO TRUSTEE

Hex
A12BF1
Octal
50225761
Decimal
10,562,545
Country
US
Tail
N175BZ
Type
BCS3
Broadcasting now · callsign MXY621 · 30,000 ft
Flights observed
99
Distinct callsigns
20
Country
US
Last broadcast
1h ago

Current position

A12BF1 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address A12BF1 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
MXY653 - 7 2026-07-10
MXY652 - 7 2026-07-10
MXY651 - 6 2026-07-07
MXY650 - 6 2026-07-07
MXY619 - 6 2026-07-12
MXY618 - 6 2026-07-13
MXY605 - 6 2026-07-07
MXY621 - 5 2026-06-21
MXY620 - 5 2026-07-15
MXY604 - 5 2026-07-12
MXY9075 - 4 2026-06-29
MXY9775 - 3 2026-07-14
MXY619B - 3 2026-07-14
MXY600 - 3 2026-06-29
MXY2313 Breeze Airways 3 2026-07-02
MXY2312 Breeze Airways 3 2026-07-02
MXY609 Breeze Airways 2 2026-06-09
MXY608 Breeze Airways 2 2026-06-08
MXY601 - 2 2026-06-22
MXY184B - 2 2026-06-20

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-15 MXY620 PVU → PHX Jul 15, 00:25 UTCJul 15, 01:35 UTC1h 10m
2026-07-14 MXY9775 - Jul 14, 17:25 UTCJul 14, 18:45 UTC1h 20m
2026-07-14 MXY619B LAS → SNA Jul 14, 03:25 UTCJul 14, 04:10 UTC45m
2026-07-14 MXY619B - Jul 14, 01:10 UTCJul 14, 02:10 UTC1h 0m
2026-07-13 MXY618 - Jul 13, 22:40 UTCJul 13, 23:35 UTC55m
2026-07-13 MXY618 - Jul 13, 20:40 UTCJul 13, 21:30 UTC50m
2026-07-13 MXY9718 PVU → SNA Jul 13, 17:40 UTCJul 13, 19:00 UTC1h 20m
2026-07-12 MXY619 - Jul 12, 23:55 UTCJul 13, 01:20 UTC1h 25m
2026-07-12 MXY619 LAS → SNA Jul 12, 22:10 UTCJul 12, 22:55 UTC45m
2026-07-12 MXY619 - Jul 12, 19:45 UTCJul 12, 20:40 UTC55m
2026-07-12 MXY618 - Jul 12, 17:15 UTCJul 12, 18:05 UTC50m
2026-07-12 MXY618 - Jul 12, 15:20 UTCJul 12, 16:05 UTC45m
2026-07-12 MXY604 PVU → SNA Jul 12, 03:50 UTCJul 12, 05:10 UTC1h 20m
2026-07-10 MXY653 LAS → PVU Jul 10, 02:50 UTCJul 10, 03:45 UTC55m
2026-07-10 MXY652 PVU → LAS Jul 10, 00:50 UTCJul 10, 01:45 UTC55m
2026-07-08 MXY653 - Jul 8, 22:50 UTCJul 8, 23:45 UTC55m
2026-07-08 MXY653 - Jul 8, 20:35 UTCJul 8, 21:55 UTC1h 20m
2026-07-08 MXY652 - Jul 8, 18:15 UTCJul 8, 19:30 UTC1h 15m
2026-07-08 MXY652 PVU → LAS Jul 8, 15:55 UTCJul 8, 16:50 UTC55m
2026-07-07 MXY651 BUR → PVU Jul 7, 22:10 UTCJul 7, 23:25 UTC1h 15m
2026-07-07 MXY651 - Jul 7, 19:35 UTCJul 7, 20:50 UTC1h 15m
2026-07-07 MXY650 - Jul 7, 16:55 UTCJul 7, 18:05 UTC1h 10m
2026-07-07 MXY650 PVU → BUR Jul 7, 14:15 UTCJul 7, 15:45 UTC1h 30m
2026-07-07 MXY605 - Jul 7, 02:55 UTCJul 7, 04:20 UTC1h 25m
2026-07-07 MXY604 - Jul 7, 00:20 UTCJul 7, 01:45 UTC1h 25m
2026-07-06 MXY113 - Jul 6, 16:40 UTCJul 6, 18:55 UTC2h 15m
2026-07-06 MXY215 PVU → DFW Jul 6, 13:10 UTCJul 6, 15:20 UTC2h 10m
2026-07-06 MXY605 - Jul 6, 01:50 UTCJul 6, 03:10 UTC1h 20m
2026-07-05 MXY604 - Jul 5, 23:15 UTCJul 6, 00:40 UTC1h 25m
2026-07-02 MXY651 BUR → PVU Jul 2, 21:00 UTCJul 2, 22:20 UTC1h 20m
2026-07-02 MXY651 - Jul 2, 18:35 UTCJul 2, 19:50 UTC1h 15m
2026-07-02 MXY650 - Jul 2, 16:00 UTCJul 2, 17:10 UTC1h 10m
2026-07-02 MXY650 PVU → BUR Jul 2, 13:15 UTCJul 2, 14:50 UTC1h 35m
2026-07-02 MXY2313 SFO → PVU Jul 2, 03:25 UTCJul 2, 04:55 UTC1h 30m
2026-07-02 MXY2312 PVU → SFO Jul 2, 00:45 UTCJul 2, 02:15 UTC1h 30m
2026-07-01 MXY653 - Jul 1, 22:00 UTCJul 1, 22:55 UTC55m
2026-07-01 MXY653 - Jul 1, 19:30 UTCJul 1, 20:45 UTC1h 15m
2026-07-01 MXY652 - Jul 1, 17:00 UTCJul 1, 18:20 UTC1h 20m
2026-07-01 MXY652 PVU → LAS Jul 1, 14:35 UTCJul 1, 15:30 UTC55m
2026-07-01 MXY2313 SFO → PVU Jul 1, 03:00 UTCJul 1, 04:15 UTC1h 15m
2026-07-01 MXY2312 PVU → SFO Jul 1, 00:15 UTCJul 1, 01:50 UTC1h 35m
2026-06-30 MXY605 - Jun 30, 21:35 UTCJun 30, 23:00 UTC1h 25m
2026-06-30 MXY1847 - Jun 30, 18:25 UTCJun 30, 19:45 UTC1h 20m
2026-06-30 MXY8601 SFO → PVU Jun 30, 01:14 UTCJun 30, 02:35 UTC1h 21m
2026-06-29 MXY601Y - Jun 29, 22:39 UTCJun 29, 23:44 UTC1h 5m
2026-06-29 MXY9005 PVU → SBD Jun 29, 19:29 UTCJun 29, 20:54 UTC1h 25m
2026-06-29 MXY9075 - Jun 29, 07:09 UTCJun 29, 08:29 UTC1h 20m
2026-06-29 MXY600 - Jun 29, 05:15 UTCJun 29, 06:09 UTC55m
2026-06-29 MXY9775 PVU → SFO Jun 29, 02:05 UTCJun 29, 03:49 UTC1h 45m
2026-06-25 MXY651 BUR → PVU Jun 25, 04:14 UTCJun 25, 05:35 UTC1h 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 N175BZ page for operator, model, and routing details .

Mode-S A12BF1 frequently asked

What is Mode-S code A12BF1?
A12BF1 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N175BZ.
Where is Mode-S A12BF1 registered?
Mode-S code A12BF1 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 A12BF1 broadcasting right now?
Yes. Mode-S A12BF1 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A12BF1, octal 50225761, decimal 10,562,545.
What flights does A12BF1 operate?
Mode-S A12BF1 has broadcast 20 distinct callsigns, including MXY653, MXY652, MXY651, MXY650, MXY619.