FTW02LA236 · Aero Commander Callair A-9B
Aero Commander Callair A-9B · Accident: loss of control in flight on approach
From T27 · El Paso, TX to an unrecorded destination
Event
- NTSB case
- FTW02LA236
- 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
Aero Commander Callair A-9B
- Aircraft type
- Aero Commander CALLAIR A-9B
- 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
- N7718V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From T27 · El Paso, TXTo not recorded
- 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 · VFR pattern final
- 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
- Loss of control in flight
- 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
- Pilot in command › Directional control, not maintained
- Pilot in command › Recovery from bounced landing, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was performing of a series of stop and go landings to meet the insurance requirements for towing gliders in the airplane. During the second approach, the pilot was correcting for the crosswind, the airplane bounced onto the runway, veered to the right side of the runway, exited the runway, and came to rest on a sand dune. The wind was from the south-southeast approximately 7-10 knots. The accident flight was the pilot's first flight in the airplane.
Probable cause
The pilot's inadequate recovery from a bounced landing, and his failure to maintain directional control. Contributing factors were the cross wind, and the pilot's lack of experience in the make and model of the accident airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA236
- Event ID
- 20020819X01426
- Case number
- FTW02LA236
- 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: d0c246a0e77e784e5bca86b6f30111d9fea806e72f28fc753d9d5d9271a44f31; retrieved 2026-09-22T10:32:49.115Z.