Bombardier Challenger 300 · representative
N398JS — Bombardier Challenger 300
No tracked position on file
Registered since 2026.
History
No flight history is loaded for this tail.
The aircraft
Airframe
- Type
- Bombardier Challenger 300
- Make and model on the certificate
- BOMBARDIER INC BD-100-1A10
- Category and class
- Fixed wing, multi engine · 2 × turbofan
- Serial
- 20726
- Built
- 2018
- Engines
- HONEYWELL AS907-2-1A
- Seats
- 8
- Airworthiness
- Feb 26, 2018
- Type certificate
- T00005NY
Identity
- Registration
- N398JS
- Mode-S hex
- A4A15A
Registration
- Registrant
- CD 321 LLC
- Address of record
- AUSTIN, TX
- FAA status
- Valid
- Certificate issued
- Jan 14, 2026
- Registration expires
- Jan 31, 2033
- Registry
- United States
FAA Registry N398JS, snapshot Nov 9, 2026.
Title history
- N398JS assigned — first registration
- Registered to CD 321 LLC
Owner history
| Years | Registered owner | Where | How it ended |
|---|---|---|---|
| Present | CD 321 LLC | Austin, TX | Open — still the registered owner of record |
Every filing
| Date | Filing |
|---|---|
| Oct 8, 2026 | Security conveyance or lien indexed filed This is the FAA's index entry for the filing, not the document itself. |
| May 1, 2026 | Part 135 listing — Listed under EXCLUSIVE JETS LLC, certificate 3EJA Seen 2026-05-01 through 2026-11-09 across 11 dated FAA workbooks. Still on the current list. |
Attribution
RegistrantCD 321 LLC · FAA record
Attribution reflects public context; registration records show registrants, not passengers.
Built from JetSweep’s retained FAA registry snapshots, sourced from FAA Registry N398JS (snapshot Nov 9, 2026). Dates shown are FAA recording and snapshot dates — the day a filing was indexed or a difference was first observed, not necessarily the day the underlying transaction happened. Part 135 rows come from dated workbook retrievals and bound a listing, never date it. We track the aircraft, not who is aboard.
Registration records show registrants, not beneficial owners; FAA recording dates lag transactions. How we source this →