FTW01FA104 · Cessna 402B
Cessna 402B · Accident: airframe, component or system failure on approach
From San Antonio International Airport (SAT) to Del Rio International Airport (DRT)
Event
- NTSB case
- FTW01FA104
- 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
- 1 · 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
- Charter & commuter
- 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
Cessna 402B
- Aircraft type
- Cessna 402
- 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
- N80Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From San Antonio International Airport (SAT), San Antonio, TXTo Del Rio International Airport (DRT), Del Rio, 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 135: Air Taxi & Commuter
- 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
- Airframe, component or system failure
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/spin
- 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
- Company maintenance personnel › Maintenance, installation, improper
- Flight control, elevator tab › Jammed
- Miscellaneous, bolt/nut/fastener/clamp/spring › Missing
- Pilot in command › Aircraft control, not possible
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Upon arrival at the destination airport, the commercial pilot of the Part 135 cargo flight reported to the tower that he was 7 miles to the east, intending to land on runway 13. Subsequently, the pilot reported that he would circle the airport a few times "because he was having trouble with his autopilot." After circling, the pilot positioned the airplane on final approach to runway 13. The pilot of another airplane in the traffic pattern observed the accident airplane on a "one to two mile final, in a normal flight attitude but possibly a little low." After looking at her instruments for several seconds, she made visual contact again and observed the airplane impact the ground with the "tail of the aircraft falling forward on top of a fence." She further stated that all of the radio transmissions from the accident airplane were "calm and completely un-alarmed prior to the accident." Another witness, who was located at a fixed base operator at the airport, observed the airplane turn onto final. He stated that the airplane "suddenly stalled and slammed into the ground from about two hundred feet." The 1,140 hour pilot had accumulated a total of 70 hours in the Cessna 402. The airplane was found to be within its prescribed weight and balance limitations at the time of the accident. Ground impressions and airframe deformations indicated that the impact angle was approximately 25 degrees nose down on a magnetic heading of 155 degrees with the landing gear extended and the flaps partially extended. A post-impact fire destroyed the airplane. Flight control continuity was established from the aft section of the cockpit to the rudder and elevator flight control surfaces. The elevator trim tab (located on the right elevator) was measured with a protractor and found to be in the 28 degrees tab-up position (aircraft nose down). According to the airplane manufacturer's specifications, the maximum tab-up travel limit (when connected) is 5 degrees. The trim tab would not move freely by hand forces and appeared to be jammed. The elevator skin was cut open (top side) to observe the trim tab connecting hardware. It was observed that the clevis end of the trim tab actuator rod was wedged against the front spar of the elevator's internal structure. Additionally, the bolt which connected the clevis end of the tab actuator rod to the actuator screw, was missing. After further inspection, neither the bolt nor the nut were found in the cavity of the elevator structure or the surrounding area. The clevis end of the actuator rod and the actuator screw were not damaged, and no impact damage was apparent on the trim tab. The operator's maintenance records showed that the right elevator had been replaced 10 flight hours prior to the accident.
Probable cause
the loss of control due to a jammed trim tab, which resulted from the failure of maintenance personnel to properly secure the trim tab actuator rod when installing a replacement elevator.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW01FA104
- Event ID
- 20010504X00885
- Case number
- FTW01FA104
- 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: 97ffff98f540da0bf8d4449ee30825faf28d5d3596fbbd28f1673573e46f6081; retrieved 2026-09-18T13:10:31.834Z.