FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13TA113 · Cessna 550

21 Dec 2012 · Oklahoma City, OK, United States

United States Customs Service Cessna 550 · Accident: aircraft wake turbulence encounter on approach

From OKC Will Rogers World Airport (OKC) to OKC Will Rogers World Airport (OKC)

Report a problem

Event

NTSB case
CEN13TA113
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
Government
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 550

Aircraft type
Cessna 550
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
N753CC
Onboard fatalities
Unknown
Route
From OKC Will Rogers World Airport (OKC), Oklahoma City, OKTo OKC Will Rogers World Airport (OKC), Oklahoma City, OK
Aircraft age
About 32 years (built 1980)
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
Public Aircraft
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
Defining eventThe 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
Aircraft wake turbulence encounter
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

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

NTSB narrative

While on the right downwind leg, the flight crew advised the air traffic control tower controller that they would make a full stop landing. The tower controller acknowledged, told them to extend their downwind, and stated that he would call their base turn. The controller then called out the landing traffic on final, which was an Airbus A300-600 heavy airplane. The flight crew replied that they had the traffic in sight, and the controller cleared the flight to land behind the Airbus, and to be cautious of wake turbulence. The flight crew observed the Airbus abeam their current position and estimated that they made their base turn about 3 miles from the runway. Before turning onto final approach, the flight crew discussed wake turbulence avoidance procedures and planned to make a steeper approach and land beyond the Airbus's touchdown point. They also added 10 to 15 knots to the Vref speed as an additional precaution against a wake turbulence encounter. The reported wind provided by the tower controller was 180 degrees at 4 knots. The flight crew observed tire smoke from the Airbus as it touched down and discussed touching down beyond that touchdown point. The tower controller advised the flight crew to be prepared for a go-around if the Airbus did not clear the runway in time, which the flight crew acknowledged. The flight crew estimated that the Airbus had turned off the runway when their airplane was about 1,000 feet from the threshold and about 200 feet above ground level (agl). The flight crew reported having a stabilized approach to their planned landing point. When the airplane was about 150 feet agl and established on the runway centerline, the airplane experienced an uncommanded left roll. The heading swung to the left and the nose dropped. The crew reported that the airplane was buffeting heavily. Immediately, they set full power, and the flying pilot used both hands on the control wheel in an attempt to roll the airplane level and recover the pitch. He managed to get the airplane nearly back to level when the right main gear struck the ground short of the threshold and left of the runway. The airplane collided with a small drainage ditch and a dirt service road, causing the right main gear and the nose gear to collapse.

Videos from cameras at the airport recorded the accident sequence, and the accident airplane was about 51 seconds behind the Airbus.

A wake vortex study indicated that the accident airplane encountered the Airbus's right vortex, and the airplane's direction of left roll was consistent with the counter-clockwise rotation of the right vortex.

Probable cause

The flight crew's decision to fly close behind a heavy airplane, which did not ensure there was adequate distance and time in order to avoid a wake turbulence encounter with the preceding heavy airplane’s wake vortex, which resulted in a loss of airplane control during final approach.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13TA113
Event ID
20121226X20928
Case number
CEN13TA113
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: ec7a92f8826c9223c2df3e4f33824e2f7b0416c716c93caca0c697ae1eaf133b; retrieved 2026-09-15T20:40:02.786Z.