- Flights observed
- 25
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address AB39DF 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 |
|---|---|---|---|
| TWY822 | - | 25 | 2026-06-26 |
Recent flights last 25
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-26 | TWY822 | NCE → TEB | Jun 26, 08:45 UTC | Jun 26, 16:44 UTC | 8h 0m |
| 2026-06-21 | TWY822 | - | Jun 21, 22:44 UTC | Jun 22, 05:54 UTC | 7h 10m |
| 2026-06-19 | TWY822 | OAK → TEB | Jun 19, 21:14 UTC | Jun 20, 01:34 UTC | 4h 20m |
| 2026-06-14 | TWY822 | - | Jun 14, 19:10 UTC | Jun 15, 01:00 UTC | 5h 49m |
| 2026-06-14 | TWY822 | - | Jun 14, 16:40 UTC | Jun 14, 17:10 UTC | 30m |
| 2026-06-11 | TWY822 | - | Jun 11, 23:55 UTC | Jun 12, 04:10 UTC | 4h 15m |
| 2026-06-09 | TWY822 | - | Jun 9, 21:20 UTC | Jun 10, 01:10 UTC | 3h 50m |
| 2026-06-05 | TWY822 | OAK → TEB | Jun 5, 22:55 UTC | Jun 6, 03:35 UTC | 4h 40m |
| 2026-06-01 | TWY822 | VNY → OAK | Jun 1, 01:05 UTC | Jun 1, 01:55 UTC | 50m |
| 2026-05-29 | TWY822 | OAK → VNY | May 29, 22:35 UTC | May 29, 23:25 UTC | 50m |
| 2026-05-25 | TWY822 | - | May 25, 20:09 UTC | May 26, 01:55 UTC | 5h 45m |
| 2026-05-25 | TWY822 | - | May 25, 18:00 UTC | May 25, 18:30 UTC | 30m |
| 2026-05-17 | TWY822 | COS → TEB | May 17, 20:35 UTC | May 17, 23:35 UTC | 3h 0m |
| 2026-05-15 | TWY822 | TEB → COS | May 15, 16:20 UTC | May 15, 19:35 UTC | 3h 15m |
| 2026-05-10 | TWY822 | - | May 10, 16:55 UTC | May 10, 21:30 UTC | 4h 35m |
| 2026-05-10 | TWY822 | - | May 10, 15:09 UTC | May 10, 16:25 UTC | 1h 15m |
| 2026-05-02 | TWY822 | - | May 2, 01:40 UTC | May 2, 02:35 UTC | 55m |
| 2026-05-02 | TWY822 | OAK → LAX | May 2, 00:00 UTC | May 2, 00:55 UTC | 55m |
| 2026-04-27 | TWY822 | - | Apr 27, 01:00 UTC | Apr 27, 01:55 UTC | 55m |
| 2026-04-26 | TWY822 | - | Apr 26, 22:20 UTC | Apr 26, 23:20 UTC | 1h 0m |
| 2026-04-23 | TWY822 | - | Apr 23, 12:05 UTC | Apr 23, 18:35 UTC | 6h 29m |
| 2026-04-21 | TWY822 | - | Apr 21, 20:05 UTC | Apr 21, 21:05 UTC | 1h 0m |
| 2026-04-21 | TWY822 | - | Apr 21, 17:20 UTC | Apr 21, 17:40 UTC | 20m |
| 2026-04-20 | TWY822 | - | Apr 20, 00:45 UTC | Apr 20, 01:40 UTC | 55m |
| 2026-04-12 | TWY822 | - | Apr 12, 17:50 UTC | Apr 12, 20:15 UTC | 2h 25m |
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 N822SF page for operator, model, and routing details .