LAX93FA333 · Aero Commander 690A
Medic Air Aero Commander 690A · Accident: loss of control in flight en route
From Reno Tahoe International Airport (RNO) to an unrecorded destination
Event
- NTSB case
- LAX93FA333
- 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 Commander 690A
- Aircraft type
- Aero Commander 690
- 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
- N706KC
- Operator
- Medic Air
- Onboard fatalities
- Unknown
- Route
- From Reno Tahoe International Airport (RNO), Reno, NVTo 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
- En route · descent
- 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
- Company maintenance personnel › Maintenance, adjustment, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A TWIN ENGINE TURBOPROP AIRPLANE WAS DESCENDING THROUGH 16,500 FEET AT 205 KNOTS WHEN THE AIRPLANE BEGAN AN UNCOMMANDED 360- DEGREE RIGHT ROLL. THE PILOT REGAINED CONTROL OF THE AIRPLANE AND CONTINUED HIS DESCENT AND LANDED. AFTER LANDING, THE PILOT FOUND THAT THE OUTBOARD HALF OF THE RIGHT HORIZONTAL STABILIZER HAD BROKEN, FOLDING UP AND AFT 180 DEGREES OVER THE UPPER SURFACE OF THE STABILIZER. THE FAILURE OF THE STABILIZER WAS ATTRIBUTED TO OVERLOAD. METEOROLOGICAL CONDITIONS WERE DESCRIBED AS A LIGHT-TO-MODERATE CHOP. EXAMINATION OF THE AIRPLANE REVEALED OVERTRAVEL OF THE ELEVATORS AND AILERONS. NO OTHER STRUCTURAL DAMAGE WAS FOUND. THE AILERONS AND AILERON TRIM TAB WERE OUT OF ADJUSTMENT.
Probable cause
a loss of control and upset due to an inadequate adjustment of the ailerons and aileron trim tab by company maintenance personnel that resulted in a partial failure of the right horizontal stabilizer.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93FA333
- Event ID
- 20001211X13166
- Case number
- LAX93FA333
- 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. 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: 605f70754b6a6e122247dcbce7fdcde9f8cae91e4d0d38c419c806cc890ca495; retrieved 2026-09-23T01:42:22.253Z.