CEN23FA160 · Aero Vodochody L-139 2000
Aero Vodochody L-139 2000 · Accident: collision during takeoff/landing on approach
From Perot Field/Fort Worth Alliance Airport (AFW) to an unrecorded destination
Event
- NTSB case
- CEN23FA160
- 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
- 0
- 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
Aero Vodochody L-139 2000
- Aircraft type
- Aero Vodochody L-139
- 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
- N1390A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Perot Field/Fort Worth Alliance Airport (AFW), Fort Worth, TXTo not recorded
- Aircraft age
- About 31 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
- 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 › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and the flight instructor departed in the tandem-seat airplane for an instructional flight. Upon arriving at the destination airport, a low approach was performed. The airplane did not land, and it climbed out. During the second approach, a no-flap landing was to be performed. While on a straight-in approach about one mile from the runway, the flight instructor reported the airplane encountered a “large flock of large birds.” The flight instructor, who was not flying at the time, was looking for possible bird strike damage sustained to the wings, the engine, and the empennage. While looking for the possible bird strike damage, he felt the sink rate increasing. He then initiated a go-around. As the nose of the airplane started to rise for the go-around, the airplane impacted the top of a large tree. After the airplane impacted the tree, the airplane landed upright and traveled on the ground before coming to rest partially inside of a barn. The airplane sustained substantial damage to the fuselage, both wings, and the empennage. The pilot was unable to recall what occurred during the accident flight. No signs of bird remains were observed on the airframe or in the engine. Data from an engine monitoring unit showed the engine performance parameters were normal during the accident flight. The engine power increased from 36% to 92% N1 during the last five seconds of recorded data. An airplane performance study revealed that after the airplane performed a low approach to runway 18, the engine power was reduced during the subsequent climb out and the throttle was not increased until the airplane was on the final approach and approximately 124 ft above field elevation. It is likely that the pilot failed to maintain a stabilized approach path due to her distraction while looking for possible bird strike damage. This distraction resulted in her allowing the airplane to impact a tree. It is likely that the flight instructor failed to initiate timely remedial action as he was also distracted while looking for possible bird strike damage. Toxicological testing of the pilot’s postaccident specimens indicated that she had used amphetamine. According to the FAA, amphetamine is a “do not issue/do not fly” medication. Amphetamine use can adversely affect cognition, impulse control, perception of risk, and judgment/decision-making. Medical conditions for which amphetamine may be used, such as attention-deficit/hyperactivity disorder or narcolepsy, can be impairing. There was no specific indication in reviewed records that the pilot had such a condition; however, this possibility cannot be excluded. Toxicological testing also detected phenylpropanolamine in the pilot’s urine, which is a minor metabolite of amphetamine. The pilot’s amphetamine level does not predict specific impairing effects. Based on the available evidence, the contribution of the pilot’s amphetamine use to the accident cannot be determined.
Probable cause
The pilot’s failure to maintain a stabilized approach path while checking for possible bird strike damage that resulted in a delayed go-around attempt and a collision with terrain. Contributing to the accident was the flight instructor’s distraction while looking for possible bird strike damage during the approach and his delayed remedial action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23FA160
- Event ID
- 20230420107091
- Case number
- CEN23FA160
- 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, 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: 56373131169235b287cb6051d4883758cf54d55ecf44afd2790fcb959e82b049; retrieved 2026-09-16T17:31:45.522Z.