FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Air America Flight Services Dassault Falcon 50 accident

27 Sept 2018 · Greensville, South Carolina, USA

Dassault FALCON 50 Undesignat · Runway Excursion / Runway Overrun On Landing / Collision with terr/obj (non-CFIT)

From St. Petersburg Clearwater International Airport (PIE) to Greenville Downtown Airport (GMU)

Report a problem

Event

NTSB case
ERA18FA264
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
Event fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
Occupants
Unknown
Survivors
Unknown
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
2
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

Dassault FALCON 50 Undesignat

Aircraft type
Dassault FALCON 50
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
N114TD
Onboard fatalities
Unknown
Route
From St. Petersburg Clearwater International Airport (PIE), St Petersburg-Clearwater, FLTo Greenville Downtown Airport (GMU), Greenville, SC
Aircraft age
About 38 years (built 1980)
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
Landing · landing roll
Defining eventThe 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
System/component malfunction/failure (non-power)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft handling/service
  • Aircraft › Aircraft systems
  • Organizational issues › Support/oversight/monitoring
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

From the Wikipedia article

An accident involving a Dassault Falcon 50 occurred on 27 September 2018 at around 13:46 local time at Greenville Downtown Airport, in Greensville, South Carolina, USA, when the Air America Flight Services (AAFS) aircraft overran the end of the runway without braking, rolled down an embankment and finally struck a road. The two pilots were killed in the accident; the two passengers survived with serious injuries. The aircraft was damaged beyond repair.

Course of the accident

The aircraft had taken off from St Petersburg-Clearwater International Airport, Florida, at around 12:30 local time on a charter flight bound for Greenville Downtown Airport. There were four people on board – two pilots and two passengers.

At around 13:46 local time the aircraft landed at Greenville Downtown Airport and, according to statements by air traffic control personnel, touched down "normally"; the thrust reversers were deployed. However, it then continued rolling – without slowing down – along the entire length of the runway, ran off it to the left at the end, rolled down an embankment, then struck the ground and came to rest on a road. On impact, the forward part of the fuselage directly behind the cockpit was torn away from the rest of the fuselage.

Investigation of the accident

The National Transportation Safety Board (NTSB) investigated the accident and published the associated final report on 3 June 2020.

It comes to the following conclusion:

Independent reporting on the accident

On 7 October 2020 the internet portal Aviation International News (AIN) Online published an article by Colleen Mondor, in which she not only reported on the accident but had also researched background on the status of AAFS as an aircraft charter operator.

In her research she came to the conclusion that at the time of the flight AAFS did not have certification to conduct commercial (paid) passenger-carrying flights. In her communication with the authority responsible for issuing such certificates, the Federal Aviation Administration (FAA), the FAA was unable to substantiate whether AAFS was certified for commercial passenger transport or whether the necessary inspections for such a certification had been carried out at all.

Translated into English with AI assistance from the German Wikipedia article “Flugunfall einer Dassault Falcon 50 der Air America Flight Services” (revision 261443896, retrieved 2026-09-19) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out; the translation may contain errors, and long articles were cut to their first 700 words. Read the article

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

German Wikipedia article: Flugunfall einer Dassault Falcon 50 der Air America Flight Services
Article
Flugunfall einer Dassault Falcon 50 der Air America Flight Services
Translation
Into English with AI assistance; names of linked operators and aircraft types from Wikidata. It may contain errors.
Revision
261443896 · 2025-11-10 · retrieved 2026-09-19
Wikidata
Q123985318
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record ERA18FA264
Event ID
20180927X41915
Case number
ERA18FA264
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
de Wikipedia article "Flugunfall einer Dassault Falcon 50 der Air America Flight Services" (page 12928828, revision 261443896), translated into English with AI assistance; merged with NTSB case ERA18FA264 (events / aircraft)
Date
NTSB record ERA18FA264: NTSB narrative opening date, consistent with the API date and time (local date)
Place and country
Wikipedia infobox: site; country from NTSB record ERA18FA264
Map position
NTSB record ERA18FA264: events decimal coordinates
Aircraft, operator and route
NTSB record ERA18FA264: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record ERA18FA264: operated under Part 135: Air Taxi & Commuter
Fatalities
NTSB record ERA18FA264: NTSB API totalFatal
Ground fatalities
NTSB record ERA18FA264: events.inj_f_grnd
Summary
Wikipedia article lead
Source notes (3)
  • One occurrence in two sources, merged: the Wikipedia article "Air America Flight Services Dassault Falcon 50 accident" and NTSB case ERA18FA264, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
  • 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.