Not currently tracked · last seen 3d ago
- Flights observed
- 34
- Avg flight time
- 1h 33m
- Typical route
- -
- Last seen
- 3d ago
Last known area
Recent flights last 34
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-11 | - | Jul 11, 00:40 UTC | Jul 11, 01:35 UTC | 55m |
| 2026-07-10 | - | Jul 10, 23:20 UTC | Jul 10, 23:50 UTC | 30m |
| 2026-07-10 | - | Jul 10, 16:55 UTC | Jul 10, 17:30 UTC | 35m |
| 2026-07-10 | - | Jul 10, 14:40 UTC | Jul 10, 15:40 UTC | 1h 0m |
| 2026-07-07 | - | Jul 7, 07:45 UTC | Jul 7, 08:30 UTC | 45m |
| 2026-07-07 | BFI → SDM | Jul 7, 04:45 UTC | Jul 7, 07:10 UTC | 2h 25m |
| 2026-07-06 | - | Jul 6, 15:25 UTC | Jul 6, 17:35 UTC | 2h 10m |
| 2026-07-06 | - | Jul 6, 13:40 UTC | Jul 6, 14:30 UTC | 50m |
| 2026-07-03 | - | Jul 3, 17:35 UTC | Jul 3, 18:40 UTC | 1h 5m |
| 2026-06-18 | PHX → TUS | Jun 18, 20:45 UTC | Jun 18, 21:10 UTC | 25m |
| 2026-06-17 | - | Jun 17, 23:45 UTC | Jun 18, 00:35 UTC | 50m |
| 2026-06-17 | - | Jun 17, 20:45 UTC | Jun 17, 22:50 UTC | 2h 5m |
| 2026-06-17 | PHX → BFI | Jun 17, 17:25 UTC | Jun 17, 19:50 UTC | 2h 25m |
| 2026-06-16 | - | Jun 16, 23:30 UTC | Jun 17, 00:15 UTC | 45m |
| 2026-06-16 | - | Jun 16, 21:50 UTC | Jun 16, 22:50 UTC | 1h 0m |
| 2026-06-16 | - | Jun 16, 20:50 UTC | Jun 16, 21:05 UTC | 15m |
| 2026-06-16 | MSN → APA | Jun 16, 16:50 UTC | Jun 16, 18:45 UTC | 1h 55m |
| 2026-06-15 | - | Jun 15, 22:25 UTC | Jun 16, 00:40 UTC | 2h 15m |
| 2026-06-15 | - | Jun 15, 19:25 UTC | Jun 15, 20:00 UTC | 35m |
| 2026-06-15 | - | Jun 15, 16:19 UTC | Jun 15, 18:40 UTC | 2h 20m |
| 2026-06-15 | - | Jun 15, 02:04 UTC | Jun 15, 02:15 UTC | 10m |
| 2026-06-14 | - | Jun 14, 20:50 UTC | Jun 15, 00:40 UTC | 3h 50m |
| 2026-06-13 | - | Jun 13, 23:45 UTC | Jun 14, 00:35 UTC | 50m |
| 2026-06-13 | PHX → SDM | Jun 13, 22:15 UTC | Jun 13, 22:55 UTC | 40m |
| 2026-06-13 | - | Jun 13, 00:55 UTC | Jun 13, 03:45 UTC | 2h 50m |
| 2026-06-12 | - | Jun 12, 23:35 UTC | Jun 13, 00:15 UTC | 40m |
| 2026-06-12 | - | Jun 12, 21:35 UTC | Jun 12, 23:05 UTC | 1h 30m |
| 2026-06-12 | - | Jun 12, 14:10 UTC | Jun 12, 17:50 UTC | 3h 40m |
| 2026-06-07 | - | Jun 7, 20:35 UTC | Jun 7, 22:00 UTC | 1h 25m |
| 2026-06-05 | - | Jun 5, 16:40 UTC | Jun 5, 18:00 UTC | 1h 20m |
| 2026-05-21 | - | May 21, 20:50 UTC | May 22, 01:25 UTC | 4h 35m |
| 2026-05-21 | - | May 21, 19:35 UTC | May 21, 19:55 UTC | 20m |
| 2026-05-21 | YUL → YUL | May 21, 17:20 UTC | May 21, 18:25 UTC | 1h 5m |
| 2026-05-07 | - | May 7, 13:45 UTC | May 7, 18:40 UTC | 4h 55m |
Specifications
| Registration | N112CC |
| Operator | KBACCC LLC |
| Mode-S code | A033D6 · 50031726 (octal) |
Looking for transponder-level data? View the Mode-S A033D6 page for country allocation, callsign history, and ADS-B signal details.
N112CC frequently asked
Who operates N112CC?
N112CC is operated by KBACCC LLC.
What is the Mode-S transponder code for N112CC?
N112CC broadcasts on Mode-S (ICAO 24-bit) address A033D6 (octal 50031726). View the transponder page.
Where is N112CC right now?
N112CC is not currently being tracked; last seen 3d ago.