Not currently tracked · last seen 16m ago
- Flights observed
- 36
- Avg flight time
- 1h 22m
- Typical route
- OTZ → OTZ
- Last seen
- 16m ago
Last known area
Recent flights last 36
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 20:45 UTC | Jul 14, 21:10 UTC | 25m |
| 2026-07-11 | - | Jul 11, 17:25 UTC | Jul 11, 18:30 UTC | 1h 5m |
| 2026-07-11 | - | Jul 11, 01:45 UTC | Jul 11, 02:40 UTC | 55m |
| 2026-07-10 | - | Jul 10, 21:35 UTC | Jul 11, 01:00 UTC | 3h 25m |
| 2026-07-10 | - | Jul 10, 02:05 UTC | Jul 10, 07:10 UTC | 5h 5m |
| 2026-07-10 | OTZ → OTZ | Jul 10, 00:20 UTC | Jul 10, 01:25 UTC | 1h 5m |
| 2026-07-09 | - | Jul 9, 19:45 UTC | Jul 9, 23:45 UTC | 4h 0m |
| 2026-07-08 | - | Jul 8, 15:20 UTC | Jul 8, 16:20 UTC | 1h 0m |
| 2026-07-07 | OTZ → OTZ | Jul 7, 00:55 UTC | Jul 7, 03:35 UTC | 2h 40m |
| 2026-07-06 | - | Jul 6, 22:30 UTC | Jul 7, 00:10 UTC | 1h 40m |
| 2026-07-06 | OTZ → OTZ | Jul 6, 20:20 UTC | Jul 6, 21:55 UTC | 1h 35m |
| 2026-07-06 | - | Jul 6, 18:00 UTC | Jul 6, 19:40 UTC | 1h 40m |
| 2026-06-27 | OTZ → DCK | Jun 27, 01:09 UTC | Jun 27, 02:14 UTC | 1h 5m |
| 2026-06-26 | - | Jun 26, 22:10 UTC | Jun 26, 23:00 UTC | 50m |
| 2026-06-26 | - | Jun 26, 19:39 UTC | Jun 26, 19:55 UTC | 15m |
| 2026-06-24 | - | Jun 24, 19:04 UTC | Jun 25, 02:19 UTC | 7h 15m |
| 2026-06-24 | - | Jun 24, 17:14 UTC | Jun 24, 18:29 UTC | 1h 15m |
| 2026-06-14 | - | Jun 14, 16:15 UTC | Jun 14, 17:40 UTC | 1h 25m |
| 2026-06-12 | OTZ → OTZ | Jun 12, 18:55 UTC | Jun 12, 19:10 UTC | 15m |
| 2026-06-11 | - | Jun 11, 15:10 UTC | Jun 11, 16:10 UTC | 1h 0m |
| 2026-06-06 | BGQ → ENN | Jun 6, 19:30 UTC | Jun 6, 20:55 UTC | 1h 25m |
| 2026-06-04 | - | Jun 4, 23:15 UTC | Jun 4, 23:30 UTC | 15m |
| 2026-06-04 | - | Jun 4, 21:40 UTC | Jun 4, 22:10 UTC | 30m |
| 2026-06-04 | BGQ → BGQ | Jun 4, 18:15 UTC | Jun 4, 20:55 UTC | 2h 40m |
| 2026-06-02 | - | Jun 2, 21:35 UTC | Jun 2, 22:05 UTC | 30m |
| 2026-06-02 | - | Jun 2, 20:15 UTC | Jun 2, 20:35 UTC | 20m |
| 2026-06-02 | - | Jun 2, 18:35 UTC | Jun 2, 18:55 UTC | 20m |
| 2026-05-30 | - | May 30, 21:20 UTC | May 30, 22:00 UTC | 40m |
| 2026-05-29 | - | May 29, 17:40 UTC | May 29, 18:20 UTC | 40m |
| 2026-05-19 | - | May 19, 03:20 UTC | May 19, 03:50 UTC | 30m |
| 2026-05-18 | - | May 18, 17:30 UTC | May 18, 18:00 UTC | 30m |
| 2026-05-15 | - | May 15, 22:40 UTC | May 15, 22:50 UTC | 10m |
| 2026-05-13 | PAQ → PAQ | May 13, 19:15 UTC | May 13, 20:15 UTC | 1h 0m |
| 2026-05-13 | - | May 13, 16:55 UTC | May 13, 17:30 UTC | 35m |
| 2026-05-12 | - | May 12, 21:01 UTC | May 12, 22:01 UTC | 1h 0m |
| 2026-05-12 | - | May 12, 03:55 UTC | May 12, 04:20 UTC | 25m |
Specifications
| Registration | N380BB |
| Operator | BILLINGS FLYING SERVICE |
| Mode-S code | A45B65 · 51055545 (octal) |
Looking for transponder-level data? View the Mode-S A45B65 page for country allocation, callsign history, and ADS-B signal details.
N380BB frequently asked
Who operates N380BB?
N380BB is operated by BILLINGS FLYING SERVICE.
What is the Mode-S transponder code for N380BB?
N380BB broadcasts on Mode-S (ICAO 24-bit) address A45B65 (octal 51055545). View the transponder page.
What route does N380BB typically fly?
N380BB most frequently flies between OTZ and OTZ based on observed flights.
Where is N380BB right now?
N380BB is not currently being tracked; last seen 16m ago.