sensors Mode-S transponder
AC89F7
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N907JB · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AC89F7
- Octal
- 53104767
- Decimal
- 11,307,511
- Country
- US
- Tail
- N907JB
- Type
- A321
- Flights observed
- 264
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 24m ago
Last known position
Country allocation
The ICAO 24-bit address AC89F7 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 |
|---|---|---|---|
| JBU373 | JetBlue Airways | 9 | 2026-06-22 |
| JBU274 | JetBlue Airways | 7 | 2026-05-11 |
| JBU1347 | - | 6 | 2026-06-27 |
| JBU474 | - | 5 | 2026-06-22 |
| JBU303 | - | 5 | 2026-07-03 |
| JBU904 | - | 4 | 2026-07-11 |
| JBU869 | - | 4 | 2026-06-24 |
| JBU862 | JetBlue Airways | 4 | 2026-05-20 |
| JBU774 | JetBlue Airways | 4 | 2026-04-19 |
| JBU574 | JetBlue Airways | 4 | 2026-05-02 |
| JBU221 | JetBlue Airways | 4 | 2026-04-28 |
| JBU2023 | - | 4 | 2026-06-28 |
| JBU1858 | - | 4 | 2026-07-02 |
| JBU1829 | - | 4 | 2026-07-13 |
| JBU162 | JetBlue Airways | 4 | 2026-04-25 |
| JBU1095 | JetBlue Airways | 4 | 2026-05-16 |
| JBU993 | JetBlue Airways | 3 | 2026-05-09 |
| JBU887 | - | 3 | 2026-07-01 |
| JBU74 | JetBlue Airways | 3 | 2026-04-16 |
| JBU724 | JetBlue Airways | 3 | 2026-06-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU330 | SDQ → BOS | Jul 13, 22:35 UTC | Jul 14, 15:45 UTC | 17h 11m |
| 2026-07-13 | JBU1829 | - | Jul 13, 17:00 UTC | Jul 13, 17:30 UTC | 30m |
| 2026-07-13 | JBU1830 | BOS → BOS | Jul 13, 12:55 UTC | Jul 13, 13:00 UTC | 5m |
| 2026-07-12 | JBU309 | JFK → BOS | Jul 12, 23:05 UTC | Jul 13, 12:40 UTC | 13h 35m |
| 2026-07-12 | JBU18 | POS → JFK | Jul 12, 02:34 UTC | Jul 12, 23:50 UTC | 21h 17m |
| 2026-07-11 | JBU904 | - | Jul 11, 14:00 UTC | Jul 11, 14:50 UTC | 50m |
| 2026-07-11 | JBU904 | - | Jul 11, 11:35 UTC | Jul 11, 11:50 UTC | 15m |
| 2026-07-11 | JBU904 | SJU → JFK | Jul 11, 11:35 UTC | Jul 12, 07:05 UTC | 19h 31m |
| 2026-07-10 | JBU854 | - | Jul 10, 10:56 UTC | Jul 11, 04:10 UTC | 17h 15m |
| 2026-07-09 | JBU1053 | - | Jul 9, 23:28 UTC | Jul 10, 21:45 UTC | 22h 18m |
| 2026-07-09 | JBU2536 | STI → JFK | Jul 9, 07:19 UTC | Jul 10, 02:00 UTC | 18h 41m |
| 2026-07-09 | JBU937 | JFK → STI | Jul 9, 02:36 UTC | Jul 10, 01:45 UTC | 23h 9m |
| 2026-07-08 | JBU361 | - | Jul 8, 12:10 UTC | Jul 8, 16:55 UTC | 4h 45m |
| 2026-07-08 | JBU361 | JFK → BGI | Jul 8, 12:05 UTC | Jul 9, 09:45 UTC | 21h 40m |
| 2026-07-07 | JBU2110 | SDQ → JFK | Jul 7, 11:35 UTC | Jul 8, 03:20 UTC | 15h 46m |
| 2026-07-06 | JBU9 | JFK → JFK | Jul 6, 22:20 UTC | Jul 7, 15:05 UTC | 16h 45m |
| 2026-07-06 | JBU510 | SDQ → JFK | Jul 6, 14:56 UTC | Jul 7, 13:45 UTC | 22h 50m |
| 2026-07-05 | JBU609 | JFK → SDQ | Jul 5, 21:30 UTC | Jul 6, 19:10 UTC | 21h 40m |
| 2026-07-05 | JBU510 | SDQ → JFK | Jul 5, 15:01 UTC | Jul 6, 10:45 UTC | 19h 44m |
| 2026-07-05 | JBU209 | JFK → JFK | Jul 5, 10:05 UTC | Jul 5, 18:30 UTC | 8h 25m |
| 2026-07-04 | JBU779 | JFK → MBJ | Jul 4, 17:28 UTC | Jul 5, 10:55 UTC | 17h 27m |
| 2026-07-04 | JBU779 | - | Jul 4, 17:30 UTC | Jul 4, 20:00 UTC | 2h 30m |
| 2026-07-03 | JBU2904 | SJU → JFK | Jul 3, 09:09 UTC | Jul 3, 23:25 UTC | 14h 16m |
| 2026-07-03 | JBU303 | JFK → SJU | Jul 3, 00:42 UTC | Jul 3, 23:25 UTC | 22h 43m |
| 2026-07-03 | JBU303 | JFK → SJU | Jul 3, 00:45 UTC | Jul 3, 04:05 UTC | 3h 20m |
| 2026-07-02 | JBU1858 | - | Jul 2, 18:30 UTC | Jul 2, 21:50 UTC | 3h 20m |
| 2026-07-02 | JBU1858 | - | Jul 2, 17:40 UTC | Jul 2, 18:00 UTC | 20m |
| 2026-07-02 | JBU757 | JFK → AUA | Jul 2, 12:10 UTC | Jul 2, 16:05 UTC | 3h 55m |
| 2026-07-01 | JBU887 | JFK → JFK | Jul 1, 15:40 UTC | Jul 2, 00:50 UTC | 9h 10m |
| 2026-06-30 | JBU904 | SJU → JFK | Jun 30, 17:53 UTC | Jul 1, 16:10 UTC | 22h 17m |
| 2026-06-30 | JBU1603 | JFK → SJU | Jun 30, 13:15 UTC | Jun 30, 21:25 UTC | 8h 11m |
| 2026-06-29 | JBU268 | PUJ → JFK | Jun 29, 15:53 UTC | Jun 30, 13:50 UTC | 21h 58m |
| 2026-06-28 | JBU636 | STI → JFK | Jun 28, 23:06 UTC | Jun 29, 19:15 UTC | 20h 9m |
| 2026-06-28 | JBU2023 | BOS → STI | Jun 28, 17:49 UTC | Jun 29, 11:10 UTC | 17h 21m |
| 2026-06-28 | JBU724 | STI → BOS | Jun 28, 09:02 UTC | Jun 29, 02:25 UTC | 17h 23m |
| 2026-06-28 | JBU2637 | JFK → STI | Jun 28, 02:26 UTC | Jun 29, 01:44 UTC | 23h 19m |
| 2026-06-28 | JBU2637 | - | Jun 28, 02:29 UTC | Jun 28, 02:54 UTC | 25m |
| 2026-06-27 | JBU1604 | - | Jun 27, 23:14 UTC | Jun 28, 00:04 UTC | 50m |
| 2026-06-27 | JBU1604 | - | Jun 27, 20:34 UTC | Jun 27, 20:44 UTC | 10m |
| 2026-06-27 | JBU1347 | - | Jun 27, 18:39 UTC | Jun 27, 18:49 UTC | 10m |
| 2026-06-27 | JBU1348 | - | Jun 27, 00:34 UTC | Jun 27, 01:39 UTC | 1h 5m |
| 2026-06-26 | JBU1348 | - | Jun 26, 22:10 UTC | Jun 26, 22:25 UTC | 15m |
| 2026-06-26 | JBU1348 | SJU → DCA | Jun 26, 22:08 UTC | Jun 27, 20:44 UTC | 22h 37m |
| 2026-06-26 | JBU1603 | - | Jun 26, 12:59 UTC | Jun 26, 16:35 UTC | 3h 35m |
| 2026-06-25 | JBU662 | - | Jun 25, 15:24 UTC | Jun 26, 01:50 UTC | 10h 25m |
| 2026-06-25 | JBU361 | - | Jun 25, 12:30 UTC | Jun 25, 13:05 UTC | 35m |
| 2026-06-24 | JBU60 | JFK → JFK | Jun 24, 22:00 UTC | Jun 25, 08:55 UTC | 10h 55m |
| 2026-06-24 | JBU869 | - | Jun 24, 10:39 UTC | Jun 24, 11:20 UTC | 40m |
| 2026-06-24 | JBU869 | JFK → PUJ | Jun 24, 10:39 UTC | Jun 25, 08:55 UTC | 22h 16m |
| 2026-06-23 | JBU2023 | BOS → JFK | Jun 23, 17:25 UTC | Jun 24, 02:30 UTC | 9h 5m |
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 N907JB page for operator, model, and routing details .