Dassault FALCON900EX accident near San Diego, California, February 13, 2021
On February 13, 2021 at about 7:50 pm local time, a 2008 Dassault FALCON900EX, registered N823RC, was substantially damaged in an accident during takeoff (rejected takeoff) near San Diego, California (Montgomery-Gibbs Exec airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 5 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The flight crew’s operation of the airplane outside of the manufacturer’s specified weight and balance limitations and with an improper trim setting, which resulted in the airplane’s inability to rotate during the attempted takeoff. Contributing to the accident, was the captain’s lack of proper certification and the crew’s lack of flight experience in the airplane make and model.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 13, 2021 · about 7:50 pm local time
- Place
- San Diego, California · Montgomery-Gibbs Exec · map
- Type
- Accident
- Injuries
- No one was hurt; 5 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Dassault FALCON900EX Easy, built 2008 · all FALCON900EXs on the register
- Registration
- N823RC · registry record · serial 201
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The flight crew was conducting a flight with two passengers and one flight attendant onboard the multiengine jet airplane. The flight crew later stated that at rotation speed, the captain applied back pressure to the control yoke; however, the nose did not rotate to a takeoff attitude. The captain attempted to rotate the airplane once more by relaxing the yoke then pulling it back again, and, with no change in the airplane’s attitude, he made the decision to reject the takeoff by retarding the thrust levers and applying maximum braking. The airplane overran the end of the runway onto a gravel pad where the landing gear collapsed. Continuity was confirmed from the flight controls to the control surfaces. No mechanical anomalies with the engines or airplane systems were noted during the investigation that would have precluded normal operation. A review of performance data indicated that the flight crew attempted to takeoff with the airplane 2,975 lbs over the maximum takeoff weight (MTOW), a center of gravity (CG) close to the most forward limit, and an incorrect stabilizer trim setting. The digital flight data recorder (DFDR) data indicated that the captain attempted takeoff at a rotation speed 23 knots (kts) slower than the calculated rotation speed for the airplane at maximum weight. Takeoff performance showed the departure runway was 575 ft shorter than the distance required for takeoff at the airplane’s weight. The captain, who was the pilot flying, did not hold any valid pilot certificates at the time of the accident because they had been revoked 2 years prior due to his falsification of logbook entries and records. Additionally, he had never held a type rating for the accident airplane and had started, but not completed, training in the accident airplane model before the accident. The first officer had accumulated about 16 hours of flight experience in the make and model of the airplane and was not authorized to operate as pilot-in-command. The airplane’s flight management system (FMS) data were not recovered; therefore, it could not be determined what data the flight crew entered into the FMS that allowed the airspeed numbers to be generated. The investigation revealed that had the actual performance numbers been entered, a “FIELD LIMITED” amber message would have illuminated warning the crew that the MTOW was exceeded, and airspeed numbers would not have been generated. Therefore, it is likely that the crew entered incorrect data into the FMS either by manually entering a longer runway length and/or decreased the weight of the fuel, passengers, and/or cargo.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Preflight or dispatch event during prior to flight
- Runway excursion during takeoff (rejected takeoff) defining event
- Collision with terrain or object (not controlled flight into terrain) during takeoff (rejected takeoff)
The NTSB's findings
- Personnel issues › Experience/knowledge › Experience/qualifications › Qualification/certification › Pilot
- Personnel issues › Task performance › Planning/preparation › Performance calculations › Pilot
- Aircraft › Aircraft oper/perf/capability › Aircraft capability › CG/weight distribution › Capability exceeded
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Configuration › Incorrect use/operation
- Aircraft › Aircraft systems › Flight control system › Stabilizer position ind system › Incorrect use/operation
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- Personnel issues › Task performance › Planning/preparation › Weight/balance calculations › Pilot
- Personnel issues › Task performance › Planning/preparation › Fuel planning › Pilot
- Aircraft › Aircraft oper/perf/capability › Aircraft capability › Takeoff distance › Capability exceeded
- Personnel issues › Action/decision › Info processing/decision › Understanding/comprehension › Copilot
Pilot
- Flight time: 8,800 hours in all; 1 in this make and model
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: no injuries
Co-pilot
- Certificate: flight instructor, commercial pilot, private
- Ratings: multi-engine land; instrument: airplane; rotorcraft: helicopter
- Flight time: 567 hours in all; 17 in this make and model; 65 in the last 90 days; 24 in the last 30 days; 406 as pilot in command; 0 on instruments
- Last flight review: September 29, 2020
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 2,914.9 hours
- Last inspection: condition inspection, June 18, 2020
- Maximum gross weight: 49,000 lb
- Seats: 13
- Landing gear: retractable
- Engine 1: Honeywell TFE 731-60-1C (turbofan); 2,973 hours total
- Engine 2: Honeywell TFE 731-60-1C (turbofan); 2,973 hours total
- Engine 3: Honeywell TFE 731-60-1C (turbofan); 4,750 hours total
- Operator: Aerospike Iron Aero, LLC
The flight
- Destination: PHKO Kailua/Kona, HI
- Flight plan: IFR
- Runway 28R, 4,598 ft by 144 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 190° at 11 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 2,900 ft; scat
- Temperature: 57°F (14°C), dew point 46°F (8°C)
- Altimeter: 29.97 inHg
- Observation at 11:00 am from KMYF
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 3 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
17 documents, released by the NTSB on June 8, 2023. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
