Plane Crash List

Dassault FALCON 50 N114TD

27 September 2018 · Greenville, South Carolina, United States · Fatal

Summary

On 27 September 2018 at about 17:46 local time, a Dassault FALCON 50 registered N114TD, operated by Air America Flight Services INC, was involved in an accident near Greenville, South Carolina, United States. 4 people were on board and 2 died, 2 were seriously 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 17:46
Classification
Accident
Location
Greenville, South Carolina, United States
Nearest airport
Greenville Downtown (GMU)
Coordinates
34.8394, -82.3486
Aircraft
Dassault FALCON 50
Registration
N114TD
Category
Airplane
Year built
1980
Engines
3
Operator
Air America Flight Services INC
Operating rule
Part 135: Air Taxi & Commuter
Phase of flight
Not recorded
Route
St Petersburg-Clearwater → Greenville
Aircraft damage
Substantial
Weather
VMC
Light
Day
NTSB number
ERA18FA264

People

2 people died.

On board Died Serious Minor Uninjured
4 2 2 0 0

Probable cause

The operator's decision to allow a flight in an airplane with known, unresolved maintenance discrepancies, and the flight crew's failure to properly configure the airplane in a way that would have allowed the emergency or parking brake systems to stop the airplane during landing.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The flight crew was operating the business jet on an on-demand air taxi flight with passengers onboard. During landing at the destination airport, the cockpit voice recorder (CVR) recorded the sound of the airplane touching down followed by the pilot's and copilot's comments that the brakes were not operating. Air traffic controllers reported, and airport surveillance video confirmed, that the airplane touched down "normally" and the airplane's thrust reverser deployed but that the airplane continued down the runway without decelerating before overrunning the runway and impacting terrain. Post-accident examination of the airplane's brake system revealed discrepancies of the antiskid system that included a broken solder joint on the left-side inboard transducer and a reversal of the wiring on the right-side outboard transducer. It is likely that these discrepancies resulted in the normal braking system's failure to function during the landing. Before the accident flight, the airplane had been in long-term storage for several years and was in the process of undergoing maintenance to bring the airplane back to a serviceable condition, which in-part required the completion of several inspections, an overhaul of the landing gear, and the resolution of over 100 other unresolved discrepancies. The accident flight and four previous flights were all made with only a portion of this required maintenance having been completed and properly documented in the airplane's maintenance logs. A pilot, who had flown the airplane on four previous flights along with the accident pilot (who was acting as second-in-command during them), identified during those flights that the airplane's normal braking system was not operating when the airplane was traveling faster than 20 knots. He remedied the situation by configuring the airplane to use the emergency, rather than normal, braking system. That pilot reported this discrepancy to the operator's director of maintenance, and it is likely that maintenance personnel from the company subsequently added an "INOP" placard near the switch on the date of the accident. The label on the placard referenced the antiskid system, and the airplane's flight manual described that with the normal brake (or antiskid) system inoperative, the brake selector switch must be positioned to use the emergency braking system. Following the accident, the switch was found positioned with the normal braking system activated, and it is likely that the accident flight crew attempted to utilize the malfunctioning normal braking system during the landing. Additionally, the flight crew failed to properly recognize the failure and configure the airplane to utilize the emergency braking system, or utilize the parking brake, as described in the airplane's flight manual, in order to stop the airplane within the available runway.

Quoted verbatim from the NTSB record.

Other Dassault FALCON accidents

Date Aircraft Location Operator Outcome Died
5 Oct 2021 Dassault FALCON 20
N283SA
Thomson, Georgia, United States Pak West Airlines Inc. Fatal 2
24 Mar 2026 Dassault FALCON 20E-5
F-GPAD
Kecskemét, Hungary AVdef No injuries -
12 Feb 2009 Dassault FALCON
VP-BAF
Samedan, Switzerland
no coordinates
- Fatal 2
3 Mar 2006 Dassault FALCON 900EX
N973M
Teterboro, New Jersey, United States - No injuries -
14 Apr 2006 Dassault FALCON 2000
N722JB
Stilesville, Indiana, United States Clos De Berry Leasing LTD No injuries -
16 Jan 2003 Dassault FALCON 900EX
N11WM
United States Pistol Creek Financial Co. Serious injuries -

All 23 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
23 Nov 2018 Cirrus SR22
N82SN
Greenville, South Carolina, United States Scs Aero Llc No injuries -
19 Dec 2018 Diamond DA20
N346MA
McCormick, South Carolina, United States Falcon Aviation Academy Llc Minor injuries -
21 Apr 2018 Republic RC 3
N9042N
Pelion, South Carolina, United States - No injuries -
9 Jul 2018 Classic WACO
N96T
North Myrtle Beach, South Carolina, United States Executive Helicopters Inc No injuries -
14 Feb 2018 Robinson R22
N337H
Charleston, South Carolina, United States Holy City Helicopters No injuries -
23 Oct 2018 Cirrus SR20
N782JR
Greenville, South Carolina, United States Aerokagan LLC No injuries -

All 170,864 records in United States