- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address AAB243 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 |
|---|---|---|---|
| NJM789 | - | 56 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | NJM789 | - | Jul 12, 19:20 UTC | Jul 12, 20:01 UTC | 40m |
| 2026-07-12 | NJM789 | - | Jul 12, 14:15 UTC | Jul 12, 17:10 UTC | 2h 55m |
| 2026-07-12 | NJM789 | - | Jul 12, 11:45 UTC | Jul 12, 12:45 UTC | 1h 0m |
| 2026-07-01 | NJM789 | - | Jul 1, 20:50 UTC | Jul 1, 22:15 UTC | 1h 25m |
| 2026-06-30 | NJM789 | - | Jun 30, 15:00 UTC | Jun 30, 16:25 UTC | 1h 25m |
| 2026-06-23 | NJM789 | - | Jun 23, 19:19 UTC | Jun 23, 22:10 UTC | 2h 50m |
| 2026-06-22 | NJM789 | ORL → LAS | Jun 22, 23:14 UTC | Jun 23, 03:34 UTC | 4h 20m |
| 2026-06-22 | NJM789 | FTY → ORL | Jun 22, 19:40 UTC | Jun 22, 20:44 UTC | 1h 5m |
| 2026-06-22 | NJM789 | - | Jun 22, 14:19 UTC | Jun 22, 15:54 UTC | 1h 35m |
| 2026-06-17 | NJM789 | - | Jun 17, 22:10 UTC | Jun 18, 00:25 UTC | 2h 15m |
| 2026-06-16 | NJM789 | - | Jun 16, 17:30 UTC | Jun 16, 19:55 UTC | 2h 26m |
| 2026-06-15 | NJM789 | - | Jun 15, 14:50 UTC | Jun 15, 17:30 UTC | 2h 40m |
| 2026-06-15 | NJM789 | ORL → FXE | Jun 15, 12:55 UTC | Jun 15, 13:34 UTC | 40m |
| 2026-06-11 | NJM789 | FXE → ORL | Jun 11, 17:35 UTC | Jun 11, 18:15 UTC | 40m |
| 2026-06-11 | NJM789 | - | Jun 11, 13:30 UTC | Jun 11, 16:00 UTC | 2h 30m |
| 2026-05-31 | NJM789 | - | May 31, 23:20 UTC | Jun 1, 02:15 UTC | 2h 55m |
| 2026-05-30 | NJM789 | - | May 30, 14:50 UTC | May 30, 18:10 UTC | 3h 20m |
| 2026-05-30 | NJM789 | - | May 30, 13:05 UTC | May 30, 13:45 UTC | 40m |
| 2026-05-17 | NJM789 | - | May 17, 17:55 UTC | May 17, 18:25 UTC | 30m |
| 2026-05-17 | NJM789 | - | May 17, 15:15 UTC | May 17, 17:05 UTC | 1h 50m |
| 2026-05-16 | NJM789 | - | May 16, 19:15 UTC | May 16, 20:30 UTC | 1h 15m |
| 2026-05-16 | NJM789 | IAD → BHB | May 16, 16:35 UTC | May 16, 17:55 UTC | 1h 20m |
| 2026-05-16 | NJM789 | - | May 16, 13:51 UTC | May 16, 15:05 UTC | 1h 15m |
| 2026-05-13 | NJM789 | YYZ → GRR | May 13, 18:20 UTC | May 13, 19:10 UTC | 50m |
| 2026-05-13 | NJM789 | - | May 13, 16:05 UTC | May 13, 16:55 UTC | 50m |
| 2026-05-12 | NJM789 | - | May 12, 03:30 UTC | May 12, 04:30 UTC | 1h 0m |
| 2026-05-11 | NJM789 | - | May 11, 21:35 UTC | May 11, 22:35 UTC | 59m |
| 2026-05-11 | NJM789 | - | May 11, 19:40 UTC | May 11, 20:10 UTC | 30m |
| 2026-05-10 | NJM789 | - | May 10, 16:50 UTC | May 10, 19:09 UTC | 2h 20m |
| 2026-05-10 | NJM789 | - | May 10, 15:05 UTC | May 10, 15:39 UTC | 35m |
| 2026-05-10 | NJM789 | - | May 10, 11:45 UTC | May 10, 13:10 UTC | 1h 25m |
| 2026-05-07 | NJM789 | - | May 7, 13:25 UTC | May 7, 14:50 UTC | 1h 25m |
| 2026-05-03 | NJM789 | - | May 3, 19:34 UTC | May 3, 22:09 UTC | 2h 35m |
| 2026-05-03 | NJM789 | - | May 3, 18:09 UTC | May 3, 18:55 UTC | 45m |
| 2026-05-01 | NJM789 | - | May 1, 21:50 UTC | May 2, 00:05 UTC | 2h 15m |
| 2026-04-28 | NJM789 | ORL → DPA | Apr 28, 14:10 UTC | Apr 28, 16:25 UTC | 2h 15m |
| 2026-04-27 | NJM789 | - | Apr 27, 12:45 UTC | Apr 27, 13:25 UTC | 40m |
| 2026-04-26 | NJM789 | - | Apr 26, 21:50 UTC | Apr 26, 22:20 UTC | 30m |
| 2026-04-26 | NJM789 | - | Apr 26, 18:50 UTC | Apr 26, 20:55 UTC | 2h 5m |
| 2026-04-23 | NJM789 | - | Apr 23, 20:25 UTC | Apr 23, 21:50 UTC | 1h 25m |
| 2026-04-23 | NJM789 | - | Apr 23, 14:55 UTC | Apr 23, 17:30 UTC | 2h 35m |
| 2026-04-17 | NJM789 | - | Apr 17, 22:35 UTC | Apr 17, 23:15 UTC | 40m |
| 2026-04-17 | NJM789 | - | Apr 17, 21:25 UTC | Apr 17, 22:05 UTC | 40m |
| 2026-04-17 | NJM789 | - | Apr 17, 19:40 UTC | Apr 17, 21:20 UTC | 1h 40m |
| 2026-04-15 | NJM789 | - | Apr 15, 21:05 UTC | Apr 15, 22:25 UTC | 1h 20m |
| 2026-04-15 | NJM789 | - | Apr 15, 19:50 UTC | Apr 15, 21:00 UTC | 1h 10m |
| 2026-04-15 | NJM789 | - | Apr 15, 17:05 UTC | Apr 15, 18:20 UTC | 1h 15m |
| 2026-04-15 | NJM789 | - | Apr 15, 15:05 UTC | Apr 15, 17:00 UTC | 1h 55m |
| 2026-04-15 | NJM789 | - | Apr 15, 14:15 UTC | Apr 15, 14:55 UTC | 39m |
| 2026-04-15 | NJM789 | - | Apr 15, 00:55 UTC | Apr 15, 01:40 UTC | 45m |
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 N789DC page for operator, model, and routing details .