The U.S. aircraft register, updated daily
Accidents · NTSB ERA26LA218 · Final report

Gulfstream Aerospace CORP GVII-G600 accident near Birmingham, Alabama, May 27, 2026

On May 27, 2026 at about 6:08 pm local time, a 2021 Gulfstream Aerospace CORP GVII-G600, registered N600WE, was substantially damaged in an accident during landing (landing roll) near Birmingham, Alabama (Birmingham-Shuttlesworth Intl airport). It was an executive or corporate flight under general aviation rules (Part 91). No one was hurt; 14 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The flight crew’s decision to continue the landing approach into adverse weather conditions, which resulted in a loss visual reference and loss airplane control during landing.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 27, 2026 · about 6:08 pm local time · cases in 2026
Place
Birmingham, Alabama · Birmingham-Shuttlesworth Intl · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 14 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Gulfstream Aerospace CORP GVII-G600, built 2021
Registration
N600WE · registry record · serial 73050
Damage
Substantial damage
Flight
Executive or corporate flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The flight crew of the business jet were approaching the destination airport near the conclusion of the transcontinental flight. The second-in-command (SIC) reported that air traffic control cleared the flight to land when the airplane was about 3 miles from the airport. Just after being cleared to land, the air traffic controller informed the flight crew that heavy rain would be encountered throughout the landing approach. The pilot-in-command (PIC) also described observing precipitation via weather radar and that a heavy rain cell had been reported on the runway. The SIC subsequently called the runway in sight when the airplane was about 250 feet above the airport elevation, and they continued the approach. As that airplane entered the landing flare, the forward visibility was extremely reduced, due to the heavy rain downpour, and the flight crew lost outside visual reference. Shortly after touching down the crew regained visual reference of the runway and realized that the airplane was drifting right of the runway centerline. The airplane continued right and the right main landing gear exited the paved runway surface into the grass. The pilots applied left control inputs, and the airplane rotated about 70° to the left before it came to rest on the runway, oriented nearly perpendicular to their approach path. The flight crew then applied power and were able to taxi to parking uneventfully. The airplane sustained substantial damage to the right wing during the accident sequence. The PIC reported that there were no preaccident mechanical malfunctions or failures of the airplane that would have precluded normal operation. A review of weather radar reflectivity data about the time of the accident showed that heavy to extreme precipitation was present on the approach to and over the airport. A special surface observation report was issued about the time of the accident and indicated ¾ statute mile of visibility in heavy rain, thunderstorms, and mist. Review of airport surveillance video confirmed that when the accident airplane was landing, the runway approach end was obscured by heavy rain, consistent with the flight crew, radar, and airport surface observation report. After the accident, the PIC stated, “We didn’t like the looks of the radar return, however there were no indications of sheer and the two aircraft ahead of us reported no issues. We flew a stabilized [instrument landing system] approach all the way to touchdown, but the visibility through heavy rain, gusty winds and wet runway condition should have been anticipated.”

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

  1. Loss of control on ground during landing (landing roll) defining event
  2. Other weather encounter during landing
  3. Runway excursion during landing (landing roll)

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Rain › Effect on operation
  • Environmental issues › Conditions/weather/phenomena › Convective weather › Thunderstorm › Effect on operation
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Flight crew

Pilot

  • Certificate: airline transport pilot, flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 13,462 hours in all; 652 in this make and model; 68 in the last 90 days; 39 in the last 30 days; 12,136 as pilot in command; 2,328 on instruments
  • Last flight review: January 22, 2026
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 7,680 hours in all; 550 in this make and model; 51 in the last 90 days; 29 in the last 30 days; 3,891 as pilot in command
  • Last flight review: February 13, 2026
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 783 hours
  • Last inspection: continuous airworthiness programme, March 12, 2026; 60 hours since
  • Maximum gross weight: 95,000 lb
  • Seats: 22
  • Landing gear: retractable
  • Engine 1: Pratt & Whitney Canada PW815GA (turbofan); 774 hours total
  • Engine 2: Pratt & Whiteny Canada PW815GA (turbofan); 774 hours total

The flight

  • Departed from: EIKY Kerry OF at 10:30 am
  • Flight plan: IFR
  • Runway 24, 12,007 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 180° at 7 knots
  • Visibility: 0.8 statute miles
  • Sky: broken clouds at 3,300 ft
  • Temperature: 81°F (27°C), dew point 72°F (22°C)
  • Altimeter: 30.06 inHg
  • Observation at 1:09 pm from BHM, 1 miles away

Weather report (METAR): SPECI KBHM 271809Z 18007KT 100V210 3/4SM +TSRA BR BKN033CB 27/22 A3006 RMK AO2 RAB00 TSB1758 OCNL LTGCG S TS S MOV NE CB DSNT SE-SW MOV NE TCU OHD AND NE-SE-SW P0003 T02720222 RVRNO

Injuries

FatalSeriousMinorNone
Flight crew2
Passengers12

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA26LA218.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.