FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Great Lakes Aviation Flight 5150

17 May 2011 · Denver, CO, United States

Beech 1900D · Incident: landing gear collapse

From Pueblo Memorial Airport (PUB) to Denver International Airport (DEN)

Report a problem

Event

NTSB case
CEN11IA341
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
Airline
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

Beech 1900D

Aircraft type
Beechcraft 1900
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
N218YV
Onboard fatalities
Unknown
Route
From Pueblo Memorial Airport (PUB), Pueblo, COTo Denver International Airport (DEN), Denver, CO
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 121: Air Carrier
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
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

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

While on approach to landing, the first officer (the pilot flying) called for the landing gear to be extended. The captain placed the gear handle in the down position and waited for the three landing gear down-and-locked annunciator lights to illuminate. Although the “NOSE” and “RH” annunciators illuminated fully, only the “L” side of the “LH” annunciator for the left main landing gear (LMLG) appeared to be illuminated (each annunciator has two light bulbs). During the landing roll, the airplane began to wobble, and the LMLG collapsed.

An examination of the airplane revealed that the nose landing gear (NLG) actuator end cap, which was found on the runway, failed due to fatigue from multiple origins that propagated from the inside diameter toward the exterior of the cap. The end cap failure, which likely occurred once the NLG reached its down and locked position, allowed most of the hydraulic fluid to be blown out of the NLG actuator, resulting in a decrease in hydraulic system pressure before the LMLG could reach the full down-and-locked position (the LMLG is the last in the system to receive a pressure pulse). No premishap mechanical deficiencies were noted with the LMLG system that would have precluded it from operating normally if sufficient hydraulic pressure had been available. However, because the loss of hydraulic pressure also disabled the manual landing gear extension system, the Quick Reference Handbook (QRH) procedure for the flight crew to manually extend the gear would have been ineffective in securing the LMLG.

The investigation identified safety issues related to the failure mode and inspection procedure for the NLG actuator end cap. Metallurgical examination of the NLG end cap revealed that the fractured NLG end cap’s grain was not in the optimum longitudinal direction. (Grain direction in the metal’s microstructure affects its tensile properties and resistance to fatigue stresses.) The NLG end cap was manufactured before the specifications were revised to indicate a longitudinal grain direction for the part. Also, evidence indicates that the fatigue crack was likely present when the end cap was overhauled in 2008 and during a routine inspection of the airplane in 2010; however, the dye penetrant inspection performed during the overhaul did not detect the crack, which would not have been detectable during the visual inspection of the airplane (because the crack had not propagated to the outside of the end cap). As a result of this investigation, the airplane’s maintenance manual was changed to recommend ultrasonic inspections and overhauls for the NLG end cap at specified cycles.

Another safety issue was identified regarding the illuminated appearance of the LH annunciator in the cockpit. According to the system design, when the LMLG is not down and locked, the indication circuit is not complete, and the LH annunciator lights will not be illuminated in the cockpit. However, examination of the incident airplane revealed that an incorrect lamp module, which did not have a light dam, was installed in the center position. As a result, light from the illuminated "R" (in the adjacent annunciator) was able to bleed over and give the appearance that the "L" was also illuminated, providing the flight crew with an erroneous indication that the LMLG was down and locked.

The investigation examined other factors that influenced the flight crew’s belief that the LMLG was safe and the captain’s decision to continue the approach. The captain noted that, after he placed the gear handle down, the landing gear in-transit light stayed on and that the gear motor continued to run for about 16 seconds before the gear-motor relay circuit breaker popped, but he stated that he was confident that the illuminated “L” indicated that the LMLG was down and locked. The captain also noted that the gear unsafe warning horn sounded just before touchdown, but he stated that he was not concerned about the horn and elected not to go-around and run the QRH checklists because he had confirmed several times that the gear annunciator lights were illuminated, and he had visually confirmed that the landing gear appeared to be down and locked. Both crewmembers stated that their training told them that if at least one light was illuminated for each annunciator, the landing gear was safe. The captain reported that, about 3 weeks before the incident, he had experienced erroneous gear in-transit light and warning horn indications in another airplane that had resulted from a wiring problem.

The QRH procedure, LANDING GEAR MANUAL EXTENSION, states that the failure of the landing gear to fully extend may be indicated by several things, including the red in-transit light and the warning horn; however, it also states: “Because there are two redundant gear-down annunciators for each gear leg, failure of only one green gear-down annunciator to illuminate does not indicate that the gear is unsafe.” The operator’s director of flight standards stated that the company does not train for situations that would involve three illuminated gear down-and-locked lights in conjunction with other gear warnings. As a result of this incident, the operator revised its Flight Standards Manual and training modules.

Probable cause

The fatigue failure of the nose landing gear (NLG) end cap, which resulted in insufficient hydraulic pressure to secure the left main landing gear into the down and locked position. Contributing to the fatigue failure was the NLG end cap’s non-optimum grain direction and the inadequate inspection procedure performed during overhaul.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11IA341
Event ID
20110517X80339
Case number
CEN11IA341
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. 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: 3059f499d2144b5b93486b0d51148fe72fdf062b5b13f2f6888dc11bc4cc69d1; retrieved 2026-09-15T16:10:27.338Z.