- Flights observed
- 29
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 17, 12:45 UTC
Last known position
Country allocation
The ICAO 24-bit address A32BAE 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 |
|---|---|---|---|
| FFY303 | - | 29 | 2026-07-17 |
Recent flights last 29
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | FFY303 | - | Jul 17, 11:55 UTC | Jul 17, 12:45 UTC | 50m |
| 2026-07-16 | FFY303 | - | Jul 16, 12:49 UTC | Jul 16, 14:20 UTC | 1h 30m |
| 2026-07-15 | FFY303 | - | Jul 15, 12:35 UTC | Jul 15, 13:05 UTC | 30m |
| 2026-07-14 | FFY303 | - | Jul 14, 11:20 UTC | Jul 14, 12:30 UTC | 1h 10m |
| 2026-07-13 | FFY303 | - | Jul 13, 11:30 UTC | Jul 13, 12:20 UTC | 50m |
| 2026-07-09 | FFY303 | - | Jul 9, 12:55 UTC | Jul 9, 14:35 UTC | 1h 40m |
| 2026-07-06 | FFY303 | - | Jul 6, 17:20 UTC | Jul 6, 17:50 UTC | 30m |
| 2026-07-06 | FFY303 | - | Jul 6, 16:20 UTC | Jul 6, 16:40 UTC | 20m |
| 2026-07-06 | FFY303 | - | Jul 6, 14:35 UTC | Jul 6, 15:35 UTC | 1h 0m |
| 2026-07-04 | FFY303 | - | Jul 4, 22:45 UTC | Jul 4, 23:30 UTC | 45m |
| 2026-07-04 | FFY303 | - | Jul 4, 20:35 UTC | Jul 4, 20:55 UTC | 20m |
| 2026-07-02 | FFY303 | - | Jul 2, 13:50 UTC | Jul 2, 14:15 UTC | 25m |
| 2026-07-01 | FFY303 | - | Jul 1, 14:10 UTC | Jul 1, 14:25 UTC | 15m |
| 2026-06-27 | FFY303 | - | Jun 27, 13:44 UTC | Jun 27, 14:05 UTC | 20m |
| 2026-06-25 | FFY303 | - | Jun 25, 19:59 UTC | Jun 25, 20:25 UTC | 25m |
| 2026-06-25 | FFY303 | - | Jun 25, 14:04 UTC | Jun 25, 14:29 UTC | 25m |
| 2026-06-22 | FFY303 | - | Jun 22, 20:04 UTC | Jun 22, 20:14 UTC | 10m |
| 2026-06-17 | FFY303 | - | Jun 17, 18:25 UTC | Jun 17, 18:35 UTC | 10m |
| 2026-06-04 | FFY303 | - | Jun 4, 19:55 UTC | Jun 4, 20:05 UTC | 10m |
| 2026-06-02 | FFY303 | - | Jun 2, 14:50 UTC | Jun 2, 15:10 UTC | 20m |
| 2026-06-02 | FFY303 | - | Jun 2, 13:50 UTC | Jun 2, 14:05 UTC | 15m |
| 2026-05-08 | FFY303 | - | May 8, 16:30 UTC | May 8, 17:35 UTC | 1h 5m |
| 2026-05-06 | FFY303 | - | May 6, 13:45 UTC | May 6, 14:25 UTC | 40m |
| 2026-05-05 | FFY303 | - | May 5, 12:20 UTC | May 5, 13:00 UTC | 40m |
| 2026-04-23 | FFY303 | - | Apr 23, 18:20 UTC | Apr 23, 18:45 UTC | 25m |
| 2026-04-22 | FFY303 | - | Apr 22, 18:15 UTC | Apr 22, 18:45 UTC | 30m |
| 2026-04-22 | FFY303 | - | Apr 22, 00:25 UTC | Apr 22, 01:20 UTC | 55m |
| 2026-04-14 | FFY303 | - | Apr 14, 23:40 UTC | Apr 15, 00:25 UTC | 45m |
| 2026-04-14 | FFY303 | - | Apr 14, 15:00 UTC | Apr 14, 15:35 UTC | 35m |
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 N303NL page for operator, model, and routing details .