FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05FA046 · Cessna T207A

8 Dec 2004 · Meadview, AZ, United States

King Airelines Cessna T207A · Accident: airframe, component or system failure en route

From Henderson Executive Airport (HND) to Henderson Executive Airport (HND)

Report a problem

Event

NTSB case
LAX05FA046
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
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

Cessna T207A

Aircraft type
Cessna 207
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
N1783U
Onboard fatalities
Unknown
Route
From Henderson Executive Airport (HND), Henderson, NVTo Henderson Executive Airport (HND), Henderson, NV
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 · cruise
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

  • Flight control, elevator › Separation
  • Flt control syst, elevator trim/tab control › Separation
  • Reason for occurrence undetermined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane impacted mountainous terrain in an extreme nose-down attitude following a departure from controlled flight. The purpose of the flight was to check the weather conditions for passenger tour flights that day. The pilot reported about 20 minutes prior to the accident that the ceiling was 6,500 feet mean sea level (msl). Radar data showed that following this weather report, the airplane's radar track continued eastbound and upon its return westbound, at an altitude of about 6,000 feet msl, the airplane entered a series of altitude fluctuations approximately 1 mile west of a ridge that was the location of the accident, descending at 4,000 feet per minute while turning northbound, and then climbing at 3,900 feet per minute while traveling eastbound, prior to disappearing from the radar. The airplane impacted on the eastern side of the ridge. There were no monitored distress calls from the aircraft and no known witnesses to the accident. Prior to the accident, there were reports of vibrations during flight on this aircraft, although many went unreported to maintenance personnel. The day (and flight) prior to the accident, a pilot experienced a vibration during flight with passengers and it was not reported to maintenance personnel because it was logged improperly in the operator's maintenance tracking system. No corrective actions were taken. During the post accident examinations, no portions of the right elevator and trim tab were identified in the wreckage, or at the accident site. The bracket attachment to the right elevator was found loose within the wreckage and was torsionally twisted counterclockwise (aft). Ground and aerial searches for the missing parts based on a trajectory study were unsuccessful. This aircraft was equipped with a foam cored elevator trim tab that was installed during aircraft manufacture. A service difficulty report (SDR) query showed that 47 reports had been issued on elevator trim tab corrosion and many included reports of vibrations during flight. On January 20, 2005, the Federal Aviation Administration (FAA) issued Special Airworthiness Information Bulletin (SAIB) CE-05-27, which addressed potential problems with foam-filled elevator trim tabs in the accident make/model airplane, and Cessna 206 and 210 series airplanes. The SAIB indicated that the foam-filled elevator trim tabs, manufactured until 1985, were reported to have corrosion between the tab and the foam. The SAIB further said, in part, "When the skin of the trim tab becomes thin enough due to the corrosion, the actuator can pull the fasteners through the skin and disconnect. When this occurs, the tab can flutter." Some reports indicated prior instances of "vibrations in the tail section and portions of the elevator tearing away with the trim tab." Prior to the issuance of the SAIB, Cessna Aircraft Company issued a Service Bulletin (SB) SEB85-7 on April 5, 1985, that addressed elevator and trim tab inspection due to corrosion from moisture trapped in the foam cored trim tabs. Based on a review of the airplane's logbooks, the SB was not complied with, nor was the operator required to do so based on the FAA approved maintenance specifications.

Probable cause

a loss of control due to the in-flight separation of the right elevator and elevator trim tab control surfaces. The precipitating reason for the elevator separation could not be resolved as related to the tab foam core issue with the available evidence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05FA046
Event ID
20041215X01993
Case number
LAX05FA046
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: 25251c846a37a9f9aeef2247852f3a848adedc7ea43eaccab98208e88869aaee; retrieved 2026-09-20T18:10:58.167Z.