SEA06IA019 · Gulfstream Aerospace G-5
Gulfstream Aerospace G-5 · Incident: airframe, component or system failure during initial climb
From Portland Hillsboro Airport (HIO) to Toronto Pearson International Airport (CYYZ)
Event
- NTSB case
- SEA06IA019
- 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
- Incident
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
- Visual Meteorological Cond
Gulfstream Aerospace G-5
- Aircraft type
- Gulfstream G-5
- 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
- N225GV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Portland Hillsboro Airport (HIO), Hillsboro, ORTo Toronto Pearson International Airport (CYYZ), Toronto
- Aircraft age
- Not recorded
- 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
- Initial climb
- First occurrenceThe 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Hydraulic system, actuator › Corroded
- Landing gear, main gear › Jammed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot said that as they raised the landing gear on takeoff, and the right main landing gear (MLG) door did not retract. He said that the checklist instructed him to cycle the landing gear; when he cycled the landing gear, the right MLG became jammed in the half down position. The pilot performed a low fly-by, and maintenance personnel on the ground photographed the bottom of the airplane. Gulfstream Aerospace engineers reviewed the photograph and advised the pilot in how to extend the landing gear. The pilot was then able to extend the landing gear. Six hours and ten minutes after takeoff, the airplane landed successfully. Post-incident examination of the right MLG revealed a black/rubber skid mark on the inside of the MLG door; the skid mark terminated at a row of 27 bolts which hold a gap seal in place. The outboard tire of the right MLG truck exhibited seven evenly spaced gouges which matched the spacing of the gap seal bolts. The MLG door uplock linkage bungee/actuator's (P/N 1159L50903-1) exterior exhibited advanced exfoliating corrosion.
Probable cause
The failure of the right main landing gear (MLG) door uplock linkage actuator due to corrosion, which resulted in jamming of the right MLG during the initial takeoff climb.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06IA019
- Event ID
- 20051123X01879
- Case number
- SEA06IA019
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 16d2df203837c3c0261541d5a881d5a6bdb8dfe96deece8d534b6e19c5c0dcb5; retrieved 2026-09-22T05:14:02.161Z.