Dassault FALCON900EX N823RC
13 February 2021 · San Diego, California, United States · No injuries
Summary
On 13 February 2021 at about 19:50 local time, a Dassault FALCON900EX registered N823RC, operated by Aerospike Iron Aero, LLC, was involved in an accident near San Diego, California, United States. 5 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 19:50
- Classification
- Accident
- Location
- San Diego, California, United States
- Nearest airport
- Montgomery-Gibbs Exec (MYF)
- Coordinates
- 32.8151, -117.1410
- Aircraft
- Dassault FALCON900EX
- Registration
- N823RC
- Category
- Airplane
- Year built
- 2008
- Engines
- 3
- Operator
- Aerospike Iron Aero, LLC
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Unknown → Kailua/Kona,
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR21LA110
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 5 | 0 | 0 | 0 | 5 |
Probable cause
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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.
Quoted verbatim from the NTSB record.
Other Dassault FALCON900EX accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 20 Oct 2010 | Dassault FALCON900EX | Teterboro, New Jersey, United States | - | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 30 Nov 2021 | Travel Air 4-D | Riverside, California, United States | Zieler Richard | No injuries | - |
| 29 Jun 2021 | Wheeler C / Wheeler K LANCAIR 235 | Borrego Springs, California, United States | Infantryship USA, Inc. | No injuries | - |
| 3 Jan 2021 | Extra Flugzeugbau EA 300/L | Santa Monica, California, United States | Marauder Aviation LLC | No injuries | - |
| 2 Dec 2021 | Russell W Dyer VORTEX | Lakeport, California, United States | - | Fatal | 1 |
| 17 May 2021 | Stearman 4E | Porterville, California, United States | William BEN Scott | No injuries | - |
| 5 Dec 2021 | Beechcraft V35 | Visalia, California, United States | - | Fatal | 4 |