ERA22LA319 · Mooney M20J
Mooney M20J · Accident: system/component malfunction/failure (non-power) on approach
From Chicago Midway International Airport (MDW) to Mount Pleasant Regional Airport Faison Field (LRO)
Event
- NTSB case
- ERA22LA319
- 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
- Visual Meteorological Cond
Mooney M20J
- Aircraft type
- Mooney M20
- 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
- N9158D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chicago Midway International Airport (MDW), Chicago, ILTo Mount Pleasant Regional Airport Faison Field (LRO), Mount Pleasant, SC
- Aircraft age
- About 30 years (built 1992)
- 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
- Approach · VFR pattern final
- 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
- System/component malfunction/failure (non-power)
- 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
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After arrival to the destination airport near the conclusion of a cross-country flight the private pilot reported the landing gear circuit breaker (CB) tripped after he attempted to lower the landing gear electrically via the normal method. He reset the CB and again attempted to lower the landing gear via the normal method, but the same CB tripped. He overflew the airport then flew towards the coast where he reviewed the airplane’s Pilot’s Operating Handbook and attempted multiple times to manually lower the landing gear but was unsuccessful. He also contacted his mechanic to obtain assistance, but he was unable to lower the landing gear. At the suggestion of his mechanic, he diverted to a larger nearby airport where he performed a go-around on the first approach because the flight was too fast, then returned and landed gear-up.
According to maintenance personnel associated with recovery of the airplane, lowering the landing gear required them to disconnect the push/pull tubes near the landing gear actuator for each landing gear. Further, the emergency cable activation lever would not move and was “jammed….” Following removal of the push/pull tubes near the actuator the emergency cable activation lever would only travel about 90%. Following removal of the actuator from the airplane, manual operation revealed the actuator turned freely in the retracted direction but would not turn in the gear extension direction. Disassembly inspection of the clutch drive assembly of the landing gear actuator revealed one “tang” of the torsion spring associated with gear extension was fractured. By system design the emergency extension system did not bypass the clutch and damaged spring; thus, a single point failure (torsion spring) precluded manual and normal extension of the landing gear. According to airframe manufacturer, the landing gear actuator and fractured torsion spring are no longer available or supported, but they do have a retrofit for the landing gear actuator.
An airframe manufacturer service instruction specified replacement of the torsion spring in the drive clutch assembly of the landing gear actuator was last performed nearly 5 years and 427 hours earlier. The service instruction, due every 1,000 hours, was due again in about 573 hours. The mechanic who performed the airplane’s last annual inspection nearly 8 months and 49 hours earlier reported that as part of that inspection he performed in part, normal and emergency extension checks of the landing gear and found no issues. He did not perform any maintenance to the landing gear except for lubrication.
Probable cause
The failure of the torsion spring inside the drive clutch assembly of the landing gear actuator which prevented normal and manual extension of the landing gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA319
- Event ID
- 20220718105499
- Case number
- ERA22LA319
- 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, 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: 1da52083251f993f7af7fc2ec23616b386092d709db4333000869426564faea9; retrieved 2026-09-16T15:27:56.324Z.