CEN18LA218 · Aerovodochody L 29 DELFIN
Aerovodochody L 29 DELFIN · Accident: collision during takeoff/landing on approach
From Moriarty Municipal Airport (0E0) to Moriarty Municipal Airport (0E0)
Event
- NTSB case
- CEN18LA218
- 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
- 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
Aerovodochody L 29 DELFIN
- Aircraft type
- Aerovodochody L-29
- 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
- N4323N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Moriarty Municipal Airport (0E0), Moriarty, NMTo Moriarty Municipal Airport (0E0), Moriarty, NM
- Aircraft age
- About 47 years (built 1971)
- 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
- Collision during takeoff/landing
- 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 oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot was receiving his second training flight after purchasing the vintage single-engine, turbine-powered airplane. While on a visual approach, the pilot flew below the glidepath with a slow airspeed and allowed a sink rate to develop. Subsequently, the flight instructor assumed control of the airplane and applied full engine power; however, the airplane continued to settle and impacted terrain 1/2 mile short of the runway. The flight instructor stated that he had "let his guard down" during the final approach and had not intervened quickly enough because the airplane descended below the glidepath. The pilot's failure to maintain a proper glidepath and the flight instructor's delayed remedial action allowed the airplane to descend and hit terrain short of the runway.
Probable cause
The pilot’s failure to maintain a proper glidepath during a visual approach and the flight instructor’s delayed remedial action, which resulted in ground impact before the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA218
- Event ID
- 20180611X11608
- Case number
- CEN18LA218
- 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: 6f9b9f694ec6391ca98b85678e75796e8330d090646b8921b07879985a1c92cb; retrieved 2026-09-16T07:25:36.125Z.