FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA93GA041 · Cessna 550

18 Dec 1992 · Billings, MT, United States

Department of Energy (wapa) Cessna 550 · Accident: vortex turbulence encountered on approach

From Watertown Regional Airport (ATY) to an unrecorded destination

Report a problem

Event

NTSB case
SEA93GA041
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
8 · 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
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
N6887Y
Onboard fatalities
Unknown
Route
From Watertown Regional Airport (ATY), Watertown, SDTo 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
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
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
Vortex turbulence encountered
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

  • Pilot in command › Procedures/directives, not followed
  • Wake turbulence › Encountered

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

NTSB narrative

DURING DESCENT INTO BILLINGS, THE CITATION WAS SEQUENCED BEHIND A BOEING 757, AND BOTH AIRPLANES WERE EVENTUALLY CLEARED FOR VISUAL APPROACHES. ABOUT 1-1/2 MI FROM THE RUNWAY THE CITATION WAS OBSERVED TO ROLL RAPIDLY TO THE INVERTED POSITION & DESCEND ALMOST VERTICALLY INTO THE GROUND. ACCORDING TO ATC TRANSCRIPTS AND THE AIRPLANES'S COCKPIT VOICE RECORDER, THE CREW OF THE CITATION HAD MAINTAINED VISUAL AWARENESS OF THE POSITION OF THE B-757 THROUGHOUT THE APPROACH. AT THE TIME OF THE UPSET, THE VERTICAL SEPARATION BETWEEN AIRPLANES WAS 600-1000 FT, AND THE HORIZONTAL SEPARATION WAS DECREASING BELOW 2.6 MI. ONE OF THE CITATION CAPTAIN'S LAST COMMENTS WAS 'ALMOST RAN OVER A SEVEN FIFTY SEVEN.' WINDS WERE 5 KTS.

Probable cause

THE PILOT-IN-COMMAND'S FAILURE TO FOLLOW ESTABLISHED VORTEX AVOIDANCE PROCEDURES, AS PUBLISHED IN THE AIRMAN'S INFORMATION MANUAL, TO PROVIDE HIS OWN WAKE TURBULENCE SEPARATION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA93GA041
Event ID
20001211X16242
Case number
SEA93GA041
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: 916cde3b6242aae3310173b582fa2effce8bfc80c96ecf25639146193e6787cc; retrieved 2026-09-18T14:37:45.115Z.