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