Platinum Jet Managment Bombardier CL-600-1A11 accident
Bombardier CL-600-1A11 · Accident: overrun during takeoff
From Teterboro Airport (KTEB) to Chicago Midway International Airport (KMDW)
Narrative check · The NTSB narrative appears to contradict this record's injuries. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DCA05MA031
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Bombardier CL-600-1A11
- Aircraft type
- Bombardier CL-600
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N370V
- Operator
- Platinum Jet Managment
- Onboard fatalities
- Unknown
- Route
- From Teterboro Airport (KTEB), Teterboro, NJTo Chicago Midway International Airport (KMDW), Chicago, IL
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 135: Air Taxi & Commuter
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff · rejected takeoff
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Overrun
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Company/operator management › Information unclear
- Company/operator mgmt › Inadequate surveillance of operation
- Faa(organization) › Inadequate surveillance of operation
- Flightcrew › Aircraft weight and balance, exceeded
- Flightcrew › Preflight planning/preparation, inadequate
- Flightcrew › Rotation, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The Safety Board's full report is available at http://www.ntsb.gov/publictn/publictn.htm. The Aircraft Accident Report number is NTSB/AAR-06/04.
On February 2, 2005, about 0718 eastern standard time, a Bombardier Challenger CL-600-1A11, N370V, ran off the departure end of runway 6 at Teterboro Airport (TEB), Teterboro, New Jersey, at a ground speed of about 110 knots; through an airport perimeter fence; across a six-lane highway (where it struck a vehicle); and into a parking lot before impacting a building. The two pilots were seriously injured, as were two occupants in the vehicle. The cabin aide, eight passengers, and one person in the building received minor injuries. The airplane was destroyed by impact forces and postimpact fire. The accident flight was an on-demand passenger charter flight from TEB to Chicago Midway Airport, Chicago, Illinois. The flight was subject to the provisions of 14 Code of Federal Regulations (CFR) Part 135 and operated by Platinum Jet Management, LLC (PJM), Fort Lauderdale, Florida, under the auspices of a charter management agreement with Darby Aviation (Darby), Muscle Shoals, Alabama. Visual meteorological conditions prevailed for the flight, which operated on an instrument flight rules flight plan.
Probable cause
the pilots' failure to ensure the airplane was loaded within weight and balance limits and their attempt to takeoff with the center of gravity well forward of the forward takeoff limit, which prevented the airplane from rotating at the intended rotation speed.
Contributing to the accident were: 1) PJM's conduct of charter flights (using PJM pilots and airplanes) without proper Federal Aviation Administration (FAA) certification and its failure to ensure that all for-hire flights were conducted in accordance with 14 CFR Part 135 requirements; 2) Darby Aviation's failure to maintain operational control over 14 CFR Part 135 flights being conducted under its certificate by PJM, which resulted in an environment conducive to the development of systemic patterns of flight crew performance deficiencies like those observed in this accident; 3) the failure of the Birmingham, Alabama, FAA Flight Standards District Office to provide adequate surveillance and oversight of operations conducted under Darby's Part 135 certificate; and 4) the FAA's tacit approval of arrangements such as that between Darby and PJM.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA05MA031
- Event ID
- 20050208X00153
- Case number
- DCA05MA031
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: d4ce56e3765f396fd6e68a0bc7b13a23545b3bcf9b5a34119e9a0b059b2e640d; retrieved 2026-09-18T15:07:12.221Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states "The airplane was destroyed by impact forces and postimpact fire."