N500FX — 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
- 20924
- Built
- 2022
- Engines
- HONEYWELL AS907-2-1A
- Seats
- 8
- Airworthiness
- Oct 18, 2022
- Type certificate
- T00005NY
Identity
- Registration
- N500FX
- Mode-S hex
- A63A83
Registration
- Registrant
- FLEXJET LLC
- Address of record
- CLEVELAND, OH
- FAA status
- Valid
- Certificate issued
- Jun 3, 2026
- Registration expires
- Jun 30, 2033
- Registry
- United States
FAA Registry N500FX, snapshot Nov 8, 2026.
Title history
- N500FX assigned — first registration
- Registered to FLEXJET LLC
Owner history
| Years | Registered owner | Where | How it ended |
|---|---|---|---|
| Present | FLEXJET LLC | Cleveland, OH | Open — still the registered owner of record |
Every filing
| Date | Filing |
|---|---|
| Jun 30, 2026 | Other names on the registration changed Also recorded: registration certificate reissued, fractional-ownership flag changed, registration expiry date updated. 5 fields changed
|
| Apr 19, 2024 | Part 135 listing — Listed under Flexjet, LLC, certificate J7SA Seen 2024-04-19 through 2026-11-09 across 19 dated FAA workbooks. Still on the current list. |
Attribution
RegistrantFLEXJET 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 N500FX (snapshot Nov 8, 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 →