ERA26LA218 · Gulfstream Aerospace Corp GVII-G600
AAA Cooper Transportation Gulfstream Aerospace Corp GVII-G600 · Accident: loss of control on ground during landing
From Kerry Airport (EIKY) to an unrecorded destination
Event
- NTSB case
- ERA26LA218
- 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
- Unknown
- Ground fatalities
- Unknown
- 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
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Gulfstream Aerospace Corp GVII-G600
- Aircraft type
- Gulfstream GVII-G600
- 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
- N600WE
- Operator
- AAA Cooper Transportation
- Onboard fatalities
- Unknown
- Route
- From Kerry Airport (EIKY), KerryTo not recorded
- Aircraft age
- About 5 years (built 2021)
- 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 91: General Aviation
- 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
- Loss of control on ground
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB 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.”
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA26LA218
- Event ID
- 20260528203065
- Case number
- ERA26LA218
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. 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.
- API snapshot SHA-256: 3173d95c18f4067b158da23d716cd5575777954091640ba19c886dd701718675; retrieved 2026-09-16T21:33:27.631Z.