Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

May 27, 2026 · Gulfstream Aerospace GVII-G600 · N600WE

Birmingham, AL

Overview

Report Status
Probable Cause
Event Type
Accident
Date
May 27, 2026
Injury Outcomes
No injuries (14 uninjured)
Location
Birmingham, AL
Aircraft
Gulfstream Aerospace GVII-G600 (2021)
Tail Number
N600WE
Operator
Aaa Cooper Transportation
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA26LA218

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.”

NTSB Probable Cause

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.

Full Narrative

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.”

Flight

Event TypeAccident
Event Time13:08 CDT
Nearest AirportBirmingham-Shuttlesworth Intl (0nm WNW)
Runway24
Runway Length12007 ft
Runway Width150 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftGulfstream Aerospace GVII-G600
Tail NumberN600WE
Aircraft CategoryAir
DamageSubstantial
OperatorAaa Cooper Transportation
Operating RulePart 91
Engines2
Engine TypeTurbofan
Engine DetailsPratt & Whitney Canada · PW815GA · Turbofan · 6925 | Pratt & Whiteny Canada · PW815GA · Turbofan · 6925
Seats22

People & Injuries

Injury SummaryNo injuries (14 uninjured)
Fatal0
Serious0
Minor0
Uninjured14
Total14
Crew 1Age 69 · First Class · None
Crew 2Age 61 · Second Class · None

Conditions

ConditionsIMC
LightDaylight
Wind180° @ 7 kt
Visibility0.8 sm
CeilingBroken clouds 3300 ft
Altimeter30.06 inHg
Observation Time13:09
Weather SourceWFAC

Appendix: Source Data