Bombardier Challenger 604 · representative
N204QS — Bombardier Challenger 604
No tracked position on file
Registered since 2025.
History
No flight history is loaded for this tail.
The aircraft
Airframe
- Type
- Bombardier Challenger 604
- Make and model on the certificate
- BOMBARDIER INC CL-600-2B16
- Category and class
- Fixed wing, multi engine · 2 × turbofan
- Serial
- 6222
- Built
- 2025
- Engines
- GE CF34-3B
- Seats
- 22
- Airworthiness
- Dec 10, 2025
Identity
- Registration
- N204QS
- Mode-S hex
- A1A24E
Registration
- Registrant
- ENZO AIR LLC
- Address of record
- OKLAHOMA CITY, OK
- FAA status
- Valid
- Certificate issued
- Dec 30, 2025
- Registration expires
- Dec 31, 2032
- Registry
- United States
FAA Registry N204QS, snapshot Sep 24, 2026.
Title history
- N204QS assigned — first registration
- Registered to ENZO AIR LLC
Owner history
| Years | Registered owner | Where | How it ended |
|---|---|---|---|
| Present | ENZO AIR LLC | Oklahoma City, OK | Open — still the registered owner of record |
Every filing
| Date | Filing |
|---|---|
| Aug 17, 2026 | Part 135 listing — Listed under NetJets Aviation, Inc., certificate DXTA Seen 2026-08-17 through 2026-09-17 across 4 dated FAA workbooks. Still on the current list. |
| May 1, 2026 | Part 135 listing — Listed under NetJets Aviation, Inc., certificate DXTA Seen on 1 dated FAA workbook (2026-05-01). Gone from the list by 2026-08-04. |
Attribution
RegistrantENZO AIR 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 N204QS (snapshot Sep 24, 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 →