FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 818 · Cessna 402C

27 Apr 1999 · Goldsby, OK, United States

Cessna 402C · Accident: airframe, component or system failure en route

From Dallas Love Field (DAL) to OKC Will Rogers World Airport (OKC)

Report a problem

Event

NTSB case
FTW99FA123
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
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
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 402C

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
N819BW
Operator
Unknown
Onboard fatalities
Unknown
Route
From Dallas Love Field (DAL), Dallas, TXTo OKC Will Rogers World Airport (OKC), Oklahoma City, OK
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
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
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

  • Manufacturer › Inadequate quality control
  • Wing, spar › Fatigue

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The twin-engine airplane impacted the ground in an uncontrolled descent following the in-flight separation of the right wing during a normal descent. The airplane had accumulated a total time of 20,457 hours and had been flown 52 hours since the most recent annual inspection, which was performed by the current operator 3 weeks prior to the accident. Available maintenance records indicated that since 1988, maintenance personnel had made numerous repairs to the right wing, including repairing skin cracks, working rivets, wing stub spar straps, and the right main landing gear. Metallurgical examination revealed that the right wing's front spar failed due to fatigue that started at an area of mechanical damage and rough machining marks. The presence of primer covering the mechanical damage strongly suggests that the damage was produced during the manufacturing process. It could not be determined whether the mechanical damage or the machining, acting alone, could have caused the fatigue cracking to initiate. Fatigue cracking found on the rear spar and the forward auxiliary spar is most likely secondary fatigue due to load shedding as the crack grew in the front spar.

Probable cause

The fatigue failure of the right wing spar as a result of inadequate quality control during manufacture of the spar. A factor was the inadequate inspection of the right wing by maintenance personnel, which failed to detect the crack.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW99FA123
Event ID
20001205X00460
Case number
FTW99FA123
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: c9a16bc147872672e6aa97eb37d94d27ca25d630046eb231d9a4c04710471219; retrieved 2026-09-18T13:18:43.107Z.