Israel Aerospace Industries Lt GULFSTREAM G150 accident near Ridgeland, South Carolina, May 5, 2021
On May 5, 2021 at about 2:33 pm local time, a 2008 Israel Aerospace Industries Lt GULFSTREAM G150, registered N22ST, was substantially damaged in an accident during landing (landing roll) near Ridgeland, South Carolina (Ridgeland-Claude Dean airport). It was an executive or corporate 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 continuation of an unstable approach and the failure of the ground air brakes to deploy upon touchdown, both of which resulted in the runway overrun. Contributing was the crew’s motivation and response to external pressures to complete the flight as quickly as possible to accommodate passenger wishes and the crew’s decision to land with a quartering tailwind that exceeded the airplane’s limitations.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 5, 2021 · about 2:33 pm local time
- Place
- Ridgeland, South Carolina · Ridgeland-Claude Dean · map
- Type
- Accident
- Injuries
- No one was hurt; 5 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Israel Aerospace Industries Lt GULFSTREAM G150 NO SERIES, built 2008
- Registration
- N22ST · no longer on the register · serial 251
- Damage
- Substantial damage
- Flight
- Executive or corporate flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot in command (PIC) and second-in-command (SIC) completed an uneventful positioning flight to pick up passengers and then continued to the destination airport. Cockpit voice recorder (CVR) information revealed that, while en route, the PIC expressed a desire to complete the flight as quickly as possible and arrive at the destination before another airplane that was also enroute to the destination airport, presumably to please the passengers. The PIC compared the flight with an automobile race, and the airplane’s overspeed warning annunciated multiple times during the descent. The flight crew elected to conduct a straight-in visual approach to land. Throughout the final approach, the airplane was high and fast, as evidenced by the SIC’s airspeed callouts. When the SIC asked whether s-turns should be made, and the PIC responded that such turns were not necessary. An electronic voice recorded by the CVR repeatedly provided “sink rate” and “pull up” warnings while the airplane was on final approach, providing indications to the crewmembers that the approach was unstable, but they continued the landing. The airplane touched down about 1,000 ft down the 4,200-ft-long runway. The PIC described that the airplane’s wheel brakes, thrust reversers, and ground air brakes did not function after touchdown, but witness and video evidence showed that the thrust reversers deployed shortly after touchdown. In addition, tire skid marks indicated that wheel braking occurred throughout the ground roll and increased heavily during the final 1,500 ft of the runway when the antiskid system activated. The ground air brakes did not deploy. The airplane overran the runway and came to rest about 400 ft past the departure end of the runway in marshy terrain. The fuselage and wings sustained substantial damage. The switch that controlled the automatic deployment of the ground air brake system was found in a position that should have allowed for their automatic deployment upon landing. There was no evidence to indicate a preaccident mechanical malfunction or failure with the hydraulic system, wheel brakes, thrust reversers, and weight-on-wheel switches, or electrical issues with either air brake switches. The airplane’s ground air brake deployment system logic required that both throttle levers be below 18° (throttle lever angle) in order to activate. The accident airplane’s throttle lever position microswitches were tested after the accident. The left throttle microswitch tested normal, but the right throttle microswitch produced an abnormal electrical current/resistance during initial testing. When the throttle was touched and then further manipulated by hand, the electrical resistance tested normal. The investigation was unable to determine whether the intermittent right throttle microswitch resistance prevented the ground air brakes from deploying because the testing was inconclusive. Landing performance calculations showed that, without ground air brakes, the landing ground roll exceeded the runway that was available from the airplane’s touchdown point about 1,000 ft down the runway. Mobile phone video evidence revealed that a quartering tailwind of about 10 to 15 knots persisted during the landing, which exceeded the manufacturer’s tailwind landing limitation of 10 knots for the airplane, and thus would have further increased the actual ground roll distance beyond that calculated. Throughout the final approach, the flight crew received several indications that the approach was unstable. The flight crew was aware that the airplane was approaching the runway high, fast, and at an abnormal sink rate. Both pilots had an opportunity to call for a go-around, which would have been the appropriate action. However, it is likely that the external pressures that the PIC and SIC accepted to complete the flight as quickly as possible influenced their decisionmaking in continuing the approach.
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
- Landing area overshoot during landing (landing roll) defining event
- Sys/Comp malf/fail (non-power) during landing (landing roll)
- Runway excursion during landing (landing roll)
The NTSB's findings
- Aircraft › Aircraft systems › Flight control system › Drag control system › Unknown/Not determined
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Flight crew
- Personnel issues › Psychological › Personality/attitude › Motivation/respond to pressure › Flight crew
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Flight crew
- Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Decision related to condition
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 9,100 hours in all; 100 in this make and model; 115 in the last 90 days; 7,390 as pilot in command
- Last flight review: February 19, 2021
- Medical certificate: Class 1
- Seat: left
- Injury: no injuries
Co-pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane
- Flight time: 1,500 hours in all; 32 in this make and model; 50 in the last 90 days; 36 in the last 30 days; 1,300 as pilot in command; 500 on instruments
- Last flight review: April 30, 2021
- Medical certificate: Class 1
- Seat: rgt
- Injury: no injuries
Passenger
- Seat: left
- Injury: no injuries
Passenger
- Seat: left
- Injury: no injuries
Passenger
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 2,580 hours
- Last inspection: continuous airworthiness programme, January 11, 2021
- Maximum gross weight: 26,100 lb
- Seats: 11
- Landing gear: retractable
- Engine 1: Honeywell TFE731-40AR-2 (turbofan); 2,580 hours total
- Engine 2: Honeywell TFE731-40AR-2 (turbofan); 2,580 hours total
The flight
- Departed from: EVB New Symrna FL at 1:45 pm
- Flight plan: IFR
- Runway 18/3, 4,200 ft by 75 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 230° at 10 knots, gusting 15
- Visibility: 10 statute miles
- Sky: overcast
- Temperature: 82°F (28°C), dew point 66°F (19°C)
- Altimeter: 29.98 inHg
- Observation at 10:33 am from NONE
Weather report (METAR): KNBC 051556Z 26013KT 10SM FEW030 BKN150 BKN200 28/19 A2998 RMK AO2 SLP152 T02830189
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
11 documents, released by the NTSB on July 24, 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
| 2 | NTSB Airworthiness Factual Report | PDF, 22 pages | View Download |
| 3 | Memorandum for Record (FAA Statement) | PDF, 2 pages | View Download |
| 4 | Memorandum for Record (Witness Statement) | PDF, 2 pages | View Download |
| 5 | Airport Manager Witness Statement | PDF, 2 pages | View Download |
| 6 | Accident Landing Video | video | View Download |
| 7 | Previous Landing (03_19_2021) | video | View Download |
| 8 | G150 AFM Tailwind Limitations_excerpt | PDF, 1 page | View Download |
| 9 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 6 pages | View Download |
| 10 | Statement of Party Representatives to NTSB Investigation | PDF, 12 pages | View Download |
| 11 | Cockpit Voice Recorder - Specialist's Factual Report | PDF, 10 pages | View Download |
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.
