Skip to content
KnownTail
Model

Bombardier INC CL-600-2D24

315 Bombardier INC CL-600-2D24 aircraft are currently registered with the FAA, built 2003–2021. Most are registered in GA, TX and UT.

Registered today
315
Years built
2003–2021
Seats
95
Engines
2 · Turbo-fan

Airworthiness Directives

ADs published since 1998 that may apply

92 ADs match the Bombardier INC CL-600-2D24 airframe. Engine ADs depend on the engine installed and are listed on each aircraft page.

See all 92

AI-extracted — verify against original. Applicability must be confirmed by a mechanic against the aircraft's records.

Watch new ADs for the Bombardier INC CL-600-2D24

One email when a new AD may apply to this model. Stop any time.

Accident history

NTSB since 1982
NTSB events
21
Destroyed
0
Substantial damage
6
Minor damage
4
No damage
0
Per 1,000 aircraft per year, 2016–2025
4.3

Events are NTSB accidents and incidents matched to Bombardier INC CL-600-2D24 airframes by serial number or N-number; counts are approximate, because older events can't always be matched. The yearly rate divides NTSB events from 2016 to 2025 by the number of registered Bombardier INC CL-600-2D24 aircraft in each of those years. Not adjusted for hours flown: training aircraft fly far more than most.

  • Feb 12, 2026Damage not reported · minor injuries · ExhumaN589NN
  • Oct 2, 2025Minor damage · minor injuries · New York, NYN902XJ
  • Jul 17, 2025Damage not reported · serious injuries · Germantown, KYN330PQ
  • Jul 16, 2025Damage not reported · none injuries · Freeland, MIN833SK
  • Feb 17, 2025Damage not reported · Toronto, OFN932XJ

Service difficulty reports

FAA SDRs since 1995

38,069 reports on Bombardier INC CL-600-2D24 airframes. Each aircraft page lists its own reports.

Most reported parts

  1. seat track3,521
  2. light2,802
  3. stringer1,950
  4. none1,684
  5. skin1,561

Registered fleet by year built

FAA Registry
Currently registered aircraft by year built
20036
200410
20058
200623
200736
200850
200914
20113
201312
201441
201529
201623
20177
20186
201921
20209
20212
Unknown15

By state

Top 10
Currently registered aircraft by owner state
GA130
TX94
UT89
MI2

Buyer checklist

92 ADs published since 1998 may apply to the Bombardier INC CL-600-2D24; recurring ADs need to be checked at each inspection. 21 NTSB events since 1982 involve Bombardier INC CL-600-2D24 airframes; from 2016 to 2025, about 4.3 a year per 1,000 registered aircraft. Operators and repair stations filed 38,069 service difficulty reports on Bombardier INC CL-600-2D24 airframes since 1995. Check each aircraft's own record before you buy.

  • Read the logbooks for the airframe, engine and propeller, start to finish.
  • Check AD compliance records against the ADs that may apply.
  • Look for damage history and Form 337 major repairs and alterations.
  • Have an independent A&P or IA do a pre-buy inspection.
  • Run a title search and use escrow for the payment.
See the registered Bombardier INC CL-600-2D24 aircraft

Type data

FAA aircraft reference file
Aircraft type
Fixed wing multi engine
Category
Land
Certification
Type Certificated
Max takeoff weight
20,000 and over lb

CL-600-2D24 aircraft

Page 1 of 13
N-numberYearBased inCertificate issued
N131EV2009Atlanta, GAJan 30, 2009
N132EV2009Atlanta, GAFeb 23, 2009
N133EV2009Atlanta, GAMar 31, 2009
N134EV2009Atlanta, GAMar 27, 2009
N135EV2009Atlanta, GAApr 30, 2009
N136EV2009Atlanta, GAMar 26, 2009
N137EV2009Atlanta, GAMar 30, 2009
N138EV2009Atlanta, GAMay 21, 2009
N146PQ2007Atlanta, GAJan 8, 2014
N147PQ2007Atlanta, GAFeb 18, 2014
N153PQ2007Atlanta, GADec 24, 2013
N161PQ2008Atlanta, GADec 19, 2013
N162PQ2008Atlanta, GANov 19, 2013
N166PQ2008Atlanta, GADec 12, 2013
N170PQ2008Atlanta, GADec 19, 2013
N176PQ2008Atlanta, GANov 6, 2013
N181GJ2008Atlanta, GAJan 13, 2020
N181PQ2008Atlanta, GANov 13, 2013
N182GJ2008Atlanta, GAFeb 27, 2020
N183GJ2008Atlanta, GAMar 3, 2020
N184GJ2008Atlanta, GAFeb 3, 2020
N185GJ2008Atlanta, GAMar 6, 2020
N186GJ2008Atlanta, GAJan 10, 2020
N186PQ2008Atlanta, GAJan 15, 2014
N187GJ2008Atlanta, GAMar 6, 2020

Report an error on this page