FTW04IA128 · Lockheed 1329-23E
Lockheed 1329-23E · Incident: airframe, component or system failure on approach
From Corpus Christi International Airport (CRP) to William P. Hobby Airport (HOU)
Event
- NTSB case
- FTW04IA128
- 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
Lockheed 1329-23E
- Aircraft type
- Lockheed 1329
- 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
- N57NR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Corpus Christi International Airport (CRP), Corpus Christi, TXTo William P. Hobby Airport (HOU), Houston, TX
- 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
- Approach · IFR final approach
- 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
- Flight control, flap attachment › Failure, total
- Flight control, flap attachment › Fatigue
- Flight control, flap › Separation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 12,500-hour pilot reported that during final approach to the airport, the flaps were extended to the full-down position. Subsequently, the airplane decelerated and rolled uncontrollably to the left. The pilot regained control of the airplane and landed without incident. A post-flight inspection of the airplane by the crewmembers revealed that the left inboard flap had separated and the attach bolts were still in the flap attach brackets. Examination of the left inboard and outboard flap actuator fittings (parts number JW121-8L and JW121-6R) revealed visible evidence of fatigue and corrosion on the surface of the inboard fitting.
Probable cause
The fatigue failure of the inboard left wing actuator fitting.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW04IA128
- Event ID
- 20040520X00619
- Case number
- FTW04IA128
- 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: a71c8b0a0a9e5c7e030c3e30d8a1107102491e4a00c16cefda845a4cb20f3ba3; retrieved 2026-09-22T07:33:26.331Z.