ERA11IA316 · Israel Aircraft Industries GULFSTREAM 200
NetJets Aviation Israel Aircraft Industries GULFSTREAM 200 · Incident: landing gear collapse
From Greenville-Spartanburg International Airport (GSP) to Westchester County Airport (HPN)
Event
- NTSB case
- ERA11IA316
- 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
Israel Aircraft Industries GULFSTREAM 200
- Aircraft type
- Israel GULFSTREAM 200
- 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
- N749QS
- Operator
- Netjets Aviation
- Onboard fatalities
- Unknown
- Route
- From Greenville-Spartanburg International Airport (GSP), Greer, SCTo Westchester County Airport (HPN), White Plains, NY
- 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 Subpart K: Fractional
- 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
- 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
- Landing gear collapse
- 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
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Prior to the incident flight, the flight crew performed an uneventful repositioning flight and did not experience any problems with the airplane's landing gear system. During the incident flight, the flight crew was performing a visual approach to the destination airport. The second-in-command (SIC) initiated a landing gear extension, and the landing gear extended but did not lock. The flight crew entered a holding pattern to perform the Landing Gear Down Lock Indication Failure checklist. Before the SIC reached the steps to cycle the landing gear, the flight crew was distracted by a hydraulic overheat condition and diverted to the Hydraulic System Overheat checklist to address that condition. When the SIC returned to the Landing Gear Down Lock Indication Failure checklist, he could not cycle the landing gear per the checklist instructions, because the hydraulic pressure was low. He then began the Emergency Landing Gear Extension checklist. The emergency extension resulted in all three landing gear remaining extended, but only the nosegear locked, and no further pertinent information remained in the checklist. The flight crew then performed an emergency landing at an airport with a longer runway. During the landing, the right main landing gear collapsed, and the airplane came to rest on the runway.
During postaccident examination of the airplane, the landing gear selector handle was found 1/8- to 1/4-inch from the full down position. Subsequent ground testing revealed that when the landing gear selector handle was positioned full up, followed by full down, the landing gear cycled successfully, indicating that, if the flight crew had placed the handle in the full down position, the landing gear would likely have operated normally. When the landing gear selector handle was positioned where it was found, the landing gear extended, but did not lock. A hydraulic bypass also occurred, with a resulting increase in hydraulic fluid temperature and decrease in hydraulic fluid pressure. The hydraulic bypass was most likely the reason that the landing gear did not lock when the emergency gear extension procedure (blow down) was followed during the incident flight. Although, the rigging of the landing gear selector valve arm was found to be 2 degrees beyond specifications, the fact that the landing gear was successfully cycled numerous times with this discrepancy indicates that it was not a contributing factor to this incident. After the incident, the airplane manufacturer revised several checklists by replacing the terms "normal" and "low" with actual numerical values. Additionally, the Landing Gear Down Lock Indication Failure and Emergency Landing Gear Extension checklists were revised to include more guidance on ensuring that the landing gear handle was positioned full down. Lastly, the Emergency Landing Gear Extension checklist was expanded to include a situation where the blow-down procedure failed to extend and lock all three landing gear.
Probable cause
The flight crew did not ensure that the landing gear selector handle was in the full down (extend) position. Contributing to the incident was inadequate checklist information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11IA316
- Event ID
- 20110527X40414
- Case number
- ERA11IA316
- 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, 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: 23f3bad59de0a991c157ed59f29e6105f015f54d4e8713fc3ce61dfa7e1c9076; retrieved 2026-09-15T16:13:03.422Z.