IAD03CA068 · Aero Commander 100
Aero Commander 100 · Accident: airframe, component or system failure during landing
From Everett-Stewart Regional Airport (UCY) to Fulton Airport (1M7)
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
- IAD03CA068
- 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
- N4103X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Everett-Stewart Regional Airport (UCY), Union City, TNTo Fulton Airport (1M7), Fulton, KY
- 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 · landing roll
- 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
- Destroyed
Cause areas
- Pilot in command › Aborted landing, delayed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, he departed on a local flight to another airport. At that airport, the pilot performed a "touch-and-go" landing and did not use the brakes. Upon returning to first airport, the pilot landed normally, except that when he applied the brakes, they did not work. The pilot attempted to abort the landing and applied full power. The airplane departed the end of the runway and impacted a ravine. Upon impact, the airplane "flipped on it's back." Due to the fact that the airplane had sustained significant impact damage, and had been moved from the accident site prior to examination, it could not determine if or how the brakes failed.
Probable cause
The malfunction of the brake system and the pilot's delay in aborting the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD03CA068
- Event ID
- 20031017X01751
- Case number
- IAD03CA068
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2003-07-26.
- API snapshot SHA-256: 9de8d109edb300e11621e29cf54f8e729d33a6bf4ef88ec818916e55454cb04b; retrieved 2026-09-21T19:24:32.747Z.