CEN11CA503 · Aero Commander 100
Aero Commander 100 · Accident: abnormal runway contact during landing
From Llano Municipal Airport (AQO) to Llano Municipal Airport (AQO)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN11CA503
- 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 100
- Aircraft type
- Aero Commander 100
- 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
- N3656X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Llano Municipal Airport (AQO), LLano, TXTo Llano Municipal Airport (AQO), LLano, 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
- Landing · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The certified flight instructor and his student were practicing takeoffs and landings for approximately an hour. After taking a break, they continued the practice session. The pilot said that the airplane was configured properly for the landing; however, he failed to attain the proper touchdown point, and the airplane impacted a tire used to mark the approach end of the runway. The airplane bounced, yawed right, exited the runway, and collided with nearby trees. Postaccident examination of the airplane revealed the airplane sustained substantial damage to the fuselage, wings, and tail section. The pilot reported no preimpact mechanical anomalies with the airplane and said he should have selected a touchdown point further down the runway which would have allowed more room for error.
Probable cause
The student pilot's failure to attain the proper touchdown point and the flight instructor's delayed remedial action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11CA503
- Event ID
- 20110725X62703
- Case number
- CEN11CA503
- 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: 224ffbc0623891d1a1079f8060092e04440fafe0a0c30e5a78965a241da2021e; retrieved 2026-09-15T16:30:26.028Z.