Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A1FB33

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N227BZ · AIRBUS A220-300 · operated by BANK OF UTAH TRUSTEE

Hex
A1FB33
Octal
50375463
Decimal
10,615,603
Country
US
Tail
N227BZ
Type
BCS3
Broadcasting now · callsign MXY578 · 34,000 ft
Flights observed
469
Distinct callsigns
20
Country
US
Last broadcast
Jul 26, 22:10 UTC

Current position

A1FB33 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address A1FB33 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
MXY259 Breeze Airways 16 2026-07-22
MXY258 Breeze Airways 16 2026-07-21
MXY117 Breeze Airways 16 2026-05-18
MXY134 Breeze Airways 15 2026-05-19
MXY2855 Breeze Airways 13 2026-06-12
MXY135 Breeze Airways 13 2026-05-19
MXY2854 Breeze Airways 12 2026-06-11
MXY147 Breeze Airways 12 2026-05-21
MXY146 Breeze Airways 12 2026-05-21
MXY116 Breeze Airways 12 2026-05-18
MXY842 Breeze Airways 11 2026-06-14
MXY843 Breeze Airways 10 2026-06-13
MXY229 Breeze Airways 10 2026-07-18
MXY228 Breeze Airways 10 2026-07-17
MXY206 Breeze Airways 10 2026-07-26
MXY207 Breeze Airways 9 2026-07-26
MXY823 Breeze Airways 8 2026-06-08
MXY822 Breeze Airways 8 2026-06-08
MXY245 Breeze Airways 8 2026-07-26
MXY244 Breeze Airways 8 2026-07-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 MXY207 LAS → CAK Jul 26, 18:15 UTCJul 26, 22:00 UTC3h 45m
2026-07-26 MXY206 CHS → CAK Jul 26, 12:50 UTCJul 26, 16:45 UTC3h 55m
2026-07-26 MXY206 CHS → CAK Jul 26, 10:15 UTCJul 26, 11:40 UTC1h 25m
2026-07-26 MXY245 RSW → CHS Jul 26, 00:05 UTCJul 26, 01:25 UTC1h 20m
2026-07-25 MXY245 RSW → CHS Jul 25, 18:35 UTCJul 25, 23:05 UTC4h 30m
2026-07-25 MXY244 RSW → LAS Jul 25, 12:35 UTCJul 25, 16:45 UTC4h 10m
2026-07-25 MXY244 RSW → LAS Jul 25, 10:20 UTCJul 25, 11:30 UTC1h 10m
2026-07-25 MXY243 SYR → CHS Jul 25, 01:35 UTCJul 25, 03:15 UTC1h 40m
2026-07-24 MXY243 SYR → CHS Jul 24, 19:55 UTCJul 25, 00:00 UTC4h 5m
2026-07-24 MXY242 SYR → LAS Jul 24, 13:25 UTCJul 24, 18:20 UTC4h 55m
2026-07-24 MXY242 SYR → LAS Jul 24, 10:35 UTCJul 24, 12:15 UTC1h 40m
2026-07-24 MXY482 ORF → CHS Jul 24, 02:15 UTCJul 24, 03:20 UTC1h 5m
2026-07-24 MXY482 ORF → CHS Jul 24, 00:15 UTCJul 24, 01:20 UTC1h 5m
2026-07-23 MXY483 ORF → ISP Jul 23, 22:15 UTCJul 23, 23:10 UTC55m
2026-07-23 MXY483 ORF → ISP Jul 23, 20:20 UTCJul 23, 21:15 UTC55m
2026-07-23 MXY209 - Jul 23, 17:35 UTCJul 23, 18:50 UTC1h 15m
2026-07-23 MXY209 - Jul 23, 15:25 UTCJul 23, 16:25 UTC1h 0m
2026-07-23 MXY208 CMH → RDU Jul 23, 13:10 UTCJul 23, 14:25 UTC1h 15m
2026-07-23 MXY208 CMH → RDU Jul 23, 10:45 UTCJul 23, 12:00 UTC1h 15m
2026-07-23 MXY245 RSW → CHS Jul 23, 00:15 UTCJul 23, 01:30 UTC1h 15m
2026-07-22 MXY245 RSW → CHS Jul 22, 18:25 UTCJul 22, 23:10 UTC4h 45m
2026-07-22 MXY244 RSW → LAS Jul 22, 12:35 UTCJul 22, 17:00 UTC4h 25m
2026-07-22 MXY244 - Jul 22, 11:10 UTCJul 22, 11:25 UTC15m
2026-07-22 MXY259 CVG → CHS Jul 22, 01:10 UTCJul 22, 02:20 UTC1h 10m
2026-07-21 MXY259 CVG → CHS Jul 21, 20:00 UTCJul 22, 00:00 UTC4h 0m
2026-07-21 MXY258 CVG → SFO Jul 21, 14:05 UTCJul 21, 18:30 UTC4h 25m
2026-07-21 MXY258 CVG → SFO Jul 21, 11:45 UTCJul 21, 13:00 UTC1h 15m
2026-07-21 MXY255 ISP → CHS Jul 21, 00:55 UTCJul 21, 02:40 UTC1h 45m
2026-07-20 MXY254 CHS → ISP Jul 20, 22:15 UTCJul 20, 23:50 UTC1h 35m
2026-07-20 MXY211 LAX → PIT Jul 20, 19:50 UTCJul 20, 21:00 UTC1h 10m
2026-07-20 MXY210 PIT → PVD Jul 20, 17:20 UTCJul 20, 18:35 UTC1h 15m
2026-07-20 MXY273 - Jul 20, 14:10 UTCJul 20, 15:55 UTC1h 45m
2026-07-20 MXY272 CHS → ALB Jul 20, 11:05 UTCJul 20, 12:50 UTC1h 45m
2026-07-19 MXY207 - Jul 19, 23:00 UTCJul 20, 00:20 UTC1h 20m
2026-07-19 MXY207 - Jul 19, 18:15 UTCJul 19, 22:10 UTC3h 55m
2026-07-19 MXY206 - Jul 19, 12:45 UTCJul 19, 16:35 UTC3h 50m
2026-07-19 MXY206 CHS → CAK Jul 19, 10:20 UTCJul 19, 11:45 UTC1h 25m
2026-07-18 MXY397 CUN → CHS Jul 18, 23:00 UTCJul 19, 01:05 UTC2h 5m
2026-07-18 MXY396 CHS → CUN Jul 18, 19:35 UTCJul 18, 21:45 UTC2h 10m
2026-07-18 MXY1655 - Jul 18, 16:45 UTCJul 18, 18:05 UTC1h 20m
2026-07-18 MXY1654 - Jul 18, 14:25 UTCJul 18, 15:40 UTC1h 15m
2026-07-18 MXY229 SDF → CHS Jul 18, 00:35 UTCJul 18, 01:45 UTC1h 10m
2026-07-17 MXY229 SDF → CHS Jul 17, 19:25 UTCJul 17, 23:35 UTC4h 10m
2026-07-17 MXY228 SDF → SFO Jul 17, 13:35 UTCJul 17, 17:40 UTC4h 5m
2026-07-17 MXY228 SDF → SFO Jul 17, 11:10 UTCJul 17, 12:19 UTC1h 10m
2026-07-17 MXY259 CVG → CHS Jul 17, 01:35 UTCJul 17, 02:45 UTC1h 10m
2026-07-16 MXY259 CVG → CHS Jul 16, 20:19 UTCJul 17, 00:35 UTC4h 15m
2026-07-16 MXY258 - Jul 16, 14:15 UTCJul 16, 18:40 UTC4h 25m
2026-07-16 MXY258 - Jul 16, 11:34 UTCJul 16, 12:44 UTC1h 10m
2026-07-16 MXY237 - Jul 16, 01:35 UTCJul 16, 02:25 UTC50m

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

Mode-S A1FB33 frequently asked

What is Mode-S code A1FB33?
A1FB33 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N227BZ.
Where is Mode-S A1FB33 registered?
Mode-S code A1FB33 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 A1FB33 broadcasting right now?
Yes. Mode-S A1FB33 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A1FB33, octal 50375463, decimal 10,615,603.
What flights does A1FB33 operate?
Mode-S A1FB33 has broadcast 20 distinct callsigns, including MXY259, MXY258, MXY117, MXY134, MXY2855.